• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2675
  • Last Modified:

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.

0
MECIT
Asked:
MECIT
  • 18
  • 14
2 Solutions
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
This can sometimes happen.

Also check the time of the applicance is correct with vCenter

Delete the Jobs and Re-create.
0
 
Danny McDanielClinical Systems AnalystCommented:
and make sure you have the latest version:

Version      1.2.1
Build Number      369570
Release Date      2011/03/18
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Also for the new vDR 1.2.1 you need to be on at least VMware vSphere 4.1 Update 1.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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.
0
 
MECITAuthor Commented:
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.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
login into to the vDR appliance and shutdown correctly, don't just reboot it!

try logging in at the console, via Vcenter, logjn and shutdown, or try a shutdown and restart correctly.

if you just warm reboot it, it will want to do an integrity check again, which can take many hours.
0
 
MECITAuthor Commented:
after the reboot, I have an Inactive status.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Do you know when the backups are suppose to start?

0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
anything in the log?
0
 
MECITAuthor Commented:
Earliest backup runs at 6pm.

in the logs:
5/9  2:09PM
starting vmware data recovery
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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.
0
 
MECITAuthor Commented:
No Errors.
I will follow up tommorow to see if the backup runs.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Check all the jobs can be run manually.
0
 
MECITAuthor Commented:
Yes they can.One is running right now.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
that youve manually started or auto started?
0
 
MECITAuthor Commented:
I r-clicked the backup job>backup>outdated sources.
Is this the manual start
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
yes
0
 
MECITAuthor Commented:
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.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Where is the destination volume?

is it full?
0
 
MECITAuthor Commented:
It is a Netgear Ready NAS 2100 with 6TB.
It has 3.65TB of fre space left.
This device is used for backups.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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.
0
 
MECITAuthor Commented:
Mounted CIF share
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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.

0
 
MECITAuthor Commented:
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?
0
 
MECITAuthor Commented:
Also Volume shadow copy service was stopped within the vCenter vm.

Could this be related as well?
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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 ....

0
 
MECITAuthor Commented:
I am going to try the NFS way and will update tommorrow.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
By moving towards NFS, will mean re-creating a new Repository, but don't worry you can have as many Repository's as you like, and use different jobs to backup to them.
0
 
MECITAuthor Commented:
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.
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
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.
0
 
MECITAuthor Commented:
The backups seem to be running smoothly. thanks for your help
0
 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Pleasure.
0

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 18
  • 14
Tackle projects and never again get stuck behind a technical roadblock.
Join Now