cancel
Showing results forΒ 
Search instead forΒ 
Did you mean:Β 

VMWare Flash Windows Restore Never End

HEMANPR
Level 6

Hello People

I try to restore a Virtual Machine from a backup doing with Flash Windows Backup Policy. The restore start and I saw the Machine create on the datastore and listed in VM Comsole. But the details on the Backup Restore job appear to be hang.

The job start but the Current Kb read stop (61348 never go up) Same in the KB/Sec: (115924 Never go up or increment)

Here The Status detail:

********************************************************************************************************************************************************************

2/14/2012 1:37:09 PM - begin Restore
2/14/2012 1:37:11 PM - restoring image SERVERNAME_1111111111
2/14/2012 1:37:11 PM - requesting resource @aaab3
2/14/2012 1:37:12 PM - granted resource MediaID=@aaab3;DiskVolume=DISK_VOLs;DiskPool=DISK_POOL-IP53;Path=DISK_VOLs;StorageServer=IP_OF_STORA...
2/14/2012 1:37:16 PM - Info bpdm(pid=11468) started           
2/14/2012 1:37:16 PM - started process bpdm (11468)
2/14/2012 1:37:16 PM - Info bpdm(pid=11468) reading backup image         
2/14/2012 1:37:16 PM - Info bpdm(pid=11468) requesting nbjm for media        
2/14/2012 1:37:16 PM - Info bpdm(pid=11468) using 64 data buffers        
2/14/2012 1:37:16 PM - Info bpdm(pid=11468) spawning a child process        
2/14/2012 1:37:16 PM - Info bpbrm(pid=11468) child pid: 6040         
2/14/2012 1:37:16 PM - Info bpdm(pid=6040) started           
2/14/2012 1:37:16 PM - started process bpdm (6040)
2/14/2012 1:37:17 PM - begin reading
2/14/2012 1:37:19 PM - end reading; read time: 00:00:02
2/14/2012 1:37:21 PM - Info bpdm(pid=11468) completed reading backup image        
2/14/2012 1:37:21 PM - Info bpdm(pid=11468) EXITING with status 0        
2/14/2012 1:37:32 PM - requesting resource @aaab3
2/14/2012 1:37:33 PM - Info bpbrm(pid=10676) MasterServer.bgf.gobierno.pr is the host to restore data     
2/14/2012 1:37:33 PM - Info bpbrm(pid=10676) reading file list from client       
2/14/2012 1:37:33 PM - granted resource MediaID=@aaab3;DiskVolume=DISK_VOLs;DiskPool=DISK_POOL-IP53;Path=DISK_VOLs;StorageServer=IP_OF_STORA...
2/14/2012 1:37:34 PM - connecting
2/14/2012 1:37:34 PM - Info bpbrm(pid=10676) starting bptm          
2/14/2012 1:37:39 PM - Info tar32(pid=4616) Restore started          
2/14/2012 1:37:39 PM - connected; connect time: 00:00:05
2/14/2012 1:37:40 PM - Info bptm(pid=2784) start           
2/14/2012 1:37:40 PM - started process bptm (2784)
2/14/2012 1:37:40 PM - Info bpdm(pid=2784) reading backup image         
2/14/2012 1:37:40 PM - Info bptm(pid=2784) using 64 data buffers        
2/14/2012 1:37:40 PM - Info bptm(pid=2784) spawning a child process        
2/14/2012 1:37:40 PM - Info bptm(pid=2784) child pid: 8328         
2/14/2012 1:37:40 PM - Info bptm(pid=8328) start           
2/14/2012 1:37:40 PM - started process bptm (8328)
2/14/2012 1:37:41 PM - begin reading

********************************************************************************************************************************************************************

But Dont do anything else. I dont see any actuivity on the VM Console Status

If I cancel the Job, The VM was Deleted from the VM Console.

Any Idea or Help? THANKS

12 REPLIES 12

Mark_Solutions
Level 6
Partner Accredited Certified
What version of NetBackup are you using? How long did you leave it before cancelling? Are you sure the account used for vcenter authentication has sufficient rights for the restore? Please provide as much info as possible Thanks

HEMANPR
Level 6

What version of NetBackup are you using?

7.0.1


How long did you leave it before cancelling?

3 hours (Commonly this restore take 45mins)


Are you sure the account used for vcenter authentication has sufficient rights for the restore?

Yes, I do this all the times, Just now we have this issue. 
 

rizwan84tx
Level 6
Certified

I have noticed VM restores taking long time to restore from LTO4 Tape. I dont remember the exact number, i would guess It took more than 5 hours  to restore approx 110 GB VM. What i noticed causing the delay was NBU reading the entire tape fragment (1 TB default), so it could locate the image its looking for.

This does not happens to all restore in my case.

As your case is disk, a fragment size is 512 GB by default. Do you notice Kilobytes read increasing in Job detailed status?

Does it happens to all VMs that you are trying to restore?

HEMANPR
Level 6

We have Storage Disk no LTO4

We do full restore of VM's and take almost 1 hour (Commonly 20GB)

 

Mark_Solutions
Level 6
Partner Accredited Certified

Does this particular client have thin provisioned disk and the other thick?

I have seen this happen if that is the case - although you do get lots of alerts in vCenter when this is the case

HEMANPR
Level 6

Good Question I will check that.

I let you know Thanks

Mark_Solutions
Level 6
Partner Accredited Certified

Noticed that you are on NBU 7.0.1 - There was a bug in early versions where you needed to specify NBD as the restore transport sometimes to get any speed out of a restore

If you cant upgrade to 7.1.0.3 then at least make sure you have applied the VMWare EEB for 7.0.1:

http://www.symantec.com/docs/TECH141502

HEMANPR
Level 6

Well most strange is the VM Console. I saw the steps on the Recent Tak view:

Clear Lazy zero = complete and the VM Machine was created sussesfully.

But the status on VM appear to be hanged. Any other suggestion?

HEMANPR
Level 6

Im on Netbackup 7.1

Its necessary to install this EBB? 7.0.1

Mark_Solutions
Level 6
Partner Accredited Certified
The lazy zero usually relates to restoring thin provisioned disks which is why I asked previously Check you have all updates / eebs installed to help with this or restore them as thick disks

HEMANPR
Level 6

Trying again Let see the results

HEMANPR
Level 6

Well

I found a older post on SYmantec Forums with the same issue. The only what I do is add a Restore ESX Server under Credential Tap

I do this and change on the policy to use SAN.

I do backup and restore without any issue.

 

Thanks to all for your time