VMWare vData Recovery
I am us vData Recovery for backups and restores.
I have following settings:
Retetion policy - Few
Destionation - NAS storage
Backup Window - pread out from 6pm -to 11pm to start
Since 4/29/11, the backups have not ran. If I manually run them they are able to backup.
Could it be a setting that could have made them stop running automatically or an issue in vCenter.
I have following settings:
Retetion policy - Few
Destionation - NAS storage
Backup Window - pread out from 6pm -to 11pm to start
Since 4/29/11, the backups have not ran. If I manually run them they are able to backup.
Could it be a setting that could have made them stop running automatically or an issue in vCenter.
and make sure you have the latest version:
Version 1.2.1
Build Number 369570
Release Date 2011/03/18
Version 1.2.1
Build Number 369570
Release Date 2011/03/18
If may be worth updating you vDR from vDR 1.2.0.37 to vDR 1.2.1. (but I've seen this issue in 1.2.1 caused by incorrect time between vDR appliance and vCenter/hosts, and Backup Jobs that just need re-creating)
But there's a warning here, that if you did you may lose current backups, because VMware recommend, you create a new repository for the upgrade.
But there's a warning here, that if you did you may lose current backups, because VMware recommend, you create a new repository for the upgrade.
Also for the new vDR 1.2.1 you need to be on at least VMware vSphere 4.1 Update 1.
Also Backups Could have stopped because of an Integrity Check error, you may want to examine logs, and also check space left in the Repository. Or run a Manual Integrity Check (warning this can take a very long time to complete!).
So Kick-off manual jobs for the Jobs, and when complete start a Manual Integrity Check.
So Kick-off manual jobs for the Jobs, and when complete start a Manual Integrity Check.
ASKER
My version is 1.2.0.1131 and the status is polling.
Is that what the status is supposed to be at.
Time is the same as the vCenter but Im trying to log into the vData Recovery and im getting unable to connect to server,like it is timing out
The integrity check are the only thing running and they are completing successfully.
Im going to try and reboot.
Is that what the status is supposed to be at.
Time is the same as the vCenter but Im trying to log into the vData Recovery and im getting unable to connect to server,like it is timing out
The integrity check are the only thing running and they are completing successfully.
Im going to try and reboot.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
after the reboot, I have an Inactive status.
Do you know when the backups are suppose to start?
anything in the log?
ASKER
Earliest backup runs at 6pm.
in the logs:
5/9 2:09PM
starting vmware data recovery
in the logs:
5/9 2:09PM
starting vmware data recovery
is there anything in the logs, that suggest any issues?
looks like you'll have to wait until tomorrow at 6pm to see if they start.
looks like you'll have to wait until tomorrow at 6pm to see if they start.
ASKER
No Errors.
I will follow up tommorow to see if the backup runs.
I will follow up tommorow to see if the backup runs.
Check all the jobs can be run manually.
ASKER
Yes they can.One is running right now.
that youve manually started or auto started?
ASKER
I r-clicked the backup job>backup>outdated sources.
Is this the manual start
Is this the manual start
ASKER
I checked the logs this morning and I had somes errors.
"Task Incomplete - Trouble writing to destination volume, error 102 (I/O error)"
there were about 5 vm's that had the same error
Then 2 hrs later ,they eventually completed the backup successfully as well as the integrity Check.
"Task Incomplete - Trouble writing to destination volume, error 102 (I/O error)"
there were about 5 vm's that had the same error
Then 2 hrs later ,they eventually completed the backup successfully as well as the integrity Check.
Where is the destination volume?
is it full?
is it full?
ASKER
It is a Netgear Ready NAS 2100 with 6TB.
It has 3.65TB of fre space left.
This device is used for backups.
It has 3.65TB of fre space left.
This device is used for backups.
So this is NFS connected to the ESXi server?
or a mounted CIFs share?
There was obviously a network issue at that time, or lost commication with the NAS.
or a mounted CIFs share?
There was obviously a network issue at that time, or lost commication with the NAS.
ASKER
Mounted CIF share
mounted cifs share are very slow, its recommended to mount the nas using nfs, and then create a virtual disk attached to the vdr appliance stored on the nas.
you may experience weird issues using cifs share.
you may experience weird issues using cifs share.
ASKER
I checked event viewer and the was a VSS error around this time . it had an event ID 8194
I also ran the vss admin and got a non-retryable error
Writer name: ADAM<vmwareVCMSDS> writer
Last error: non-retryable error
Would this be related?
I also ran the vss admin and got a non-retryable error
Writer name: ADAM<vmwareVCMSDS> writer
Last error: non-retryable error
Would this be related?
ASKER
Also Volume shadow copy service was stopped within the vCenter vm.
Could this be related as well?
Could this be related as well?
It's very coincidental that the errors happen at the same time, but as the appliance is responsible for the backups and connecting to the NAS, and the NAS is a standalone unit, I'm finding it hard to link them.
Unless there is a wide issue on your network ....
Unless there is a wide issue on your network ....
ASKER
I am going to try the NFS way and will update tommorrow.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
So far it has been backup with the nfs and the way I created it the first time. I will let it run for about another week.
Often problems occur with vDR.
1. datastore runs out of space.
2. datastore becomes corrupted.
3. datastore i/o errors because of network issues.
4. issue with VM because cannot snapshot.
1. datastore runs out of space.
2. datastore becomes corrupted.
3. datastore i/o errors because of network issues.
4. issue with VM because cannot snapshot.
ASKER
The backups seem to be running smoothly. thanks for your help
Also check the time of the applicance is correct with vCenter
Delete the Jobs and Re-create.