With Resilient Filesystem (ReFS) integration into Veeam Availability Suite 9.5 a whole bunch of features was integrated. One of the biggest advantages is ‚Fast Cloning Technology‘ which enables synthetic full backups by merely creating pointers to already existing datablocks on the repository.
In a small scale environment I had a hardware repository server (Win 2016) with an iSCSI Volume as repository (ReFS, 64k) as primary backup target. This constellation worked like a Swiss watch. Daily backups ran for months without any trouble. Fast cloning technology enabled weekly synthetic full backups with minimal consumption of extra space.
Brocade Fibrechannel Switches mit dem Fabric OS (FOS) werden standardmäßig mit den Benutzerkonten admin, root, user und factory ausgeliefert. Es ist wichtig, diese Default Passworte bei der ersten Konfiguration zu ändern.
Die Logins der Konten root, user und factory ändert man am schnellsten über SSH.
Login als user ‚root‘ mit Default-Password ‚fibranne‘
Bei erstem Login werden neue Passwörter für root, user und factory abgefragt. Mit <ENTER> startet man diesen Dialog, mit Ctrl-C bricht man ab. Bei nächstem Login wird man erneut zur Kennwortänderung aufgefordert.
Kontrolle der Nutzerkonten
userconfig --show -a
Hiermit werden alle lokalen Konten mit Status dargestellt.
Troubleshooting vMotion issues is in most cases a matter of networking issues. I will demonstrate in this case how to trace down the problem and how to find possible culprits.
What’s the problem?
Initiating a host vMotion between esx1 and esx2 passes all pre-checks, but then fails at 21% progress.
Migrate virtual machine:Failed waiting for data. Error 195887371. The ESX hosts failed to connect over the VMotion network.
See the error stack for details on the cause of this problem.
Time: 07.01.2018 19:08:08
vCenter Server: vc
Migration [167797862:1515348488969364] failed to connect to remote host <192.168.45.246> from host <10.0.100.102>: Timeout.
vMotion migration [167797862:1515348488969364] vMotion migration [167797862:1515348488969364] stream thread failed to connect to the remote host <192.168.45.246>: The ESX hosts failed to connect over the VMotion network
The vMotion migrations failed because the ESX hosts were not able to connect over the vMotion network. Check the vMotion network settings and physical network configuration.
Migration [167797862:1515348488969364] failed to connect to remote host <10.0.100.102> from host <192.168.45.246>: Timeout.
vMotion migration [167797862:1515348488969364] failed to create a connection with remote host <10.0.100.102>: The ESX hosts failed to connect over the VMotion network
Failed waiting for data. Error 195887371. The ESX hosts failed to connect over the VMotion network.
Agile backup job assignment with VM-tags and Veeam Backup
Organizing VMs in backup jobs can be a tedious task. Especially when there is a larger number of VMs and multiple jobs. It might happen that you miss out a VM for a job, or have it doubled.
To check whether a VM is backed up by the corresponding jobs, you either have to go through the settings of every single job or use smart tools like Veeam-One.
There are a couple of ways to add VMs to a backup job. You can choose single VMs by name, or select an entire VM folder, resource-pool or datastore. But one of the most sophisticated and versatile methods is to leverage VM-tags for selection.
What are tags?
A tag behaves like a label or a sticker that you put on a VM. It defines a property or a membership of a given VM. Think of a tag that marks a VM for daily backup. A second tag might mark a VM for hourly or weekly backup. You don’t have to adjust your backup jobs twice a week to remove or add new virtual machines. With VM-tags you don’t have to touch backup jobs at all. Just tell the job once to select all VMs with a specific tag and you’re done.
Even checking job membership for a VM is easier with tags. Just have a look at its tags.
I will now show a simple example how to use tagged VMs in combination with Veeam Backup & Replication.
I usually don’t like writing about obvious matters. Yes, fire is hot – night is dark and ice is cold. But in recent times I’ve witnessed some network topology designs (?), that made me frown.
I admit, that in some cases the situation is based on a lack of budget or just structures that have grown over years. I can understand that and it’s no shame. It’s my job to give advices and help to re-design.
On the other hand there are environments who boast with high class components that have cost a fortune and which are organized in such an inefficient way that it almost hurts.
This article is not intended as a networking deep-dive. It’s a shallow 101 about network design that should be common knowledge. It’s a guide for the novice but I’d be happy to get responses by experts too.
First let’s start with four simple networking requirements for Virtual Infrastructures.