Last week I added a new vSphere host in my homelab, after I configured and started my backup job in the Backup & Replication 7.0 patch 4 environment I received this error messages:
Processing ‘DC01’ Error: Client error: NFC storage connection is unavailable. Storage: [stg:datastore-12,nfchost:host-10,conn:vce01.vmpros.local]. Storage display name: [ESX01_VMFS02].
Failed to create NFC download stream. NFC path: [nfc://conn:vce01.vmpros.local,nfchost:host-10,stg:datastore-12@DC01/DC01.vmx].
Solution
When you look at the Backup Job log file you can see the details, logfile location: C:\ProgramData\Veeam\Backup\VMpros_-_Backup_01
In my case Veeam Backup could resolve my VMware vCenter 5.5 server but when he try to contact the vSphere host with some local datastores the backup failed. I tried to ping the hosts and couldn’t resolve the hostname of my vSphere host.
Make sure you have:
– Added the vSphere host in DNS, create a A record in your DNS server
Optionally: Add the vSphere hostsname(s) and IP-address(es) in the hostfile at your Veeam Backup server
End result
More information: Veeam
Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.
More Posts - Website
Follow Me:
A customer asked me to repair their Veeam Backup & Replication 7.0 backup job, some virtual machines were showing this warning message in the backup log:
Failed to index guest file system. Veeam Guest Agent is not started
Solution:
The default Domain Administrator (Veeam Service Account) credentials are not working at the standalone / workgroup virtual machine that is running in the DMZ VLAN.
Note: Make sure the virtual machine has the latest version of VMware Tools installed
To configure specific credentials:
– Edit the backup job
– Navigate to: Guest Processing > click: Advanced
Read more…
Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.
More Posts - Website
Follow Me:
During the network configuration at the VMware Data Protection (VDP) appliance I received this warning message:
IP/DNS could not be resolved. Please check the hostname, domain, and DNS values for forward and reverse lookup validation
Troubleshoot:
VMware VDP whitepaper: Before you deploy vSphere Data Protection, an entry needs to be added to the DNS Server for the appliance IP address and FQDN. This DNS Server must support forward and reverse lookup. Failure to have DNS set up properly can cause many runtime or configuration issues.
As you can see, the nslookup failed:
Solution:
Add the domain and search domain in the /etc/resolv.conf file
And make sure you’ve created a correct PTR record at the DNS server for reverse DNS functionality, at the DNS server:
Select: Create associated pointer (PTR) record
More information: VMware
Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.
More Posts - Website
Follow Me:
Few weeks ago I received from my sponsor PHD Virtual licenses to install and review the Backup and Replication v5.4.. after I installed this software in my vSphere 5 test lab I was exited how easy I can backup and restore virtual machines.
After installing the PHDVBA appliance, configured a static ip-address I installed the PHD Virtual Backup Console to start the configuration. The first startup the software discovered (subnet discover) the PHDVBA appliance,
Appliance and Backup Console configuration:
First I connected the software to my vCenter server, created the storage type as backup destination (in my case I used “Attached virtual disk”). If you chose this functionality you only need to add a new .vmdk file to the appliance:
After I added the 50 gb .vmdk file the appliance auto detect the new storage without rebooting.. nice!
Other backup destination options are:
Read more…
Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.
More Posts - Website
Follow Me:
After installing VMware Data Recovery I scheduled a fresh job to make a backup of my VM’s in the datacenter. The first 8 VM’s backuped successful, but the VM’s with a iSCSI target (Exchange, SQL) crashing after creating virtual machine snapshot. I received this error:
Creating a quiesced snapshot failed because the created snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine.
Read more…
Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.
More Posts - Website
Follow Me:
Last week I got some problems with making backups of my Exchange 2007 enviroment with BackupExec 12d SP3.
The status in BackupExec was: “A failure occurred querying the Writer status”
Read more…
Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.
More Posts - Website
Follow Me:
To install vcb follow the instructions on this link.
The first time I came in contact with vcb I created some batch files to make vcb snapshots. I encountered all kind of problems. Snapshots that vcb didn’t remove. unexpected errors no vss support and some more issues.
To overcome some of these problems I created a vbs script vcbBackup.vbs. The full howto is comming soon for now only the code. Read more…
Mostly you have on a terminal (citrix) server just 1 volume. With Windows 2008 it’s default not possible to create a SSB to the source volume.
You can change this do doing the following:
Create a new registry entry with the following information:
Key: HKLM\SYSTEM\CurrentControlSet\Services\wbengine\SystemStateBackup\AllowSSBToAnyVolume
Type: DWORD
Value: 1
A value of 0 prevents the storing of system state backup on a source volume. A value of 1 allows the storing of system state backup on a source volume.
However, there are known issues with storing a system state backup on a source volume:
- Backups can fail. The backup can be modified during the backup process, which might cause the backup to fail.
- It causes an inefficient use of target space. Twice the amount of space is necessary for a backup than for the original data. The volume must allocate twice the amount of space for the shadow copy process.
Just seeing that I can use VMware Data Recovery (VDR) without connecting vCenter by vSphere client, I only connect to the ESX host. You need only install the VMware Data Recovery Plugin into your VMware vSphere Client and you can manage your backups.
Little note: vCenter must be online!
Read more…
Sander Daems is founder and author of this blog and working as a Lead (Sr.) Consultant by UNICA ICT Solutions. Sander has over 15 years experience in IT, primary focus: virtualization and modern worksplace.
More Posts - Website
Follow Me:
Recent Comments