tech88kur

updated

13 years ago

T

tech88kur

142 Posts

0

3039

March 5th, 2014 11:00

Time required for VADP image level restore

Hi All,

I am using 8.0.2.6 on nsr server and 8.0.2.6 on Sotrage node, both are windows 2008 R2 machine. DD 670 is used as backup target, OS on DD is 5.2.1.0-331816.

I want to know if any of you have tried VADP image level restoration, in my case for a image level restoration of a VM of size 82 GB it takes more than 5 hours which is very large considering that we are restoring from DD. Does it take similiar time or is it unusual in my case. The restoration time decreases or increases depending on size in proportion to above citation.

Whereas backup for above machine takes around three hours.

I am pasting the logs during one of the restores..

Requesting 1 recover session(s) from server.

91651:nsrvadp_recover: Successfully established AFTD DFA session for recovering save-set ID '1839487632'.

C:\Program Files\EMC NetWorker\nsr\tmp\1839487632\1\diskBitmap_0

C:\Program Files\EMC NetWorker\nsr\tmp\1839487632\1\diskBitmap_1

C:\Program Files\EMC NetWorker\nsr\tmp\1839487632\1\Disks

C:\Program Files\EMC NetWorker\nsr\tmp\1839487632\1\metaFile_C

C:\Program Files\EMC NetWorker\nsr\tmp\1839487632\1\metaFile_D

C:\Program Files\EMC NetWorker\nsr\tmp\1839487632\1\reference_C

C:\Program Files\EMC NetWorker\nsr\tmp\1839487632\1\reference_D

C:\Program Files\EMC NetWorker\nsr\tmp\1839487632\1\vm_config.xml

Making directory: [VM_OS-N-R] Server1

Recovering to original VC system.

Recovering to original ESX host system.

libCURL SSL support is ENABLED

NetWorker install path: C:\Program Files\EMC NetWorker\nsr\.

Temporary Directory for VADP created.

Temporary vmMntLoc Directory for VADP created.

Initializing VimServer...

VimServer is initialized

Volumes needed (all on-line):

cifs_share.001 at rd=server2:cifs_share

Total estimated disk space needed for recover is 391 MB.

Requesting 8 file(s), this may take a while...

Received 8 file(s) from NSR server `Server3'

Recover completion time: 6/21/2013 4:05:23 AM

Trying to find the datacenter: DC ...

Trying to find the ESX host system: server4 ...

Trying to find the resource pool: ...

Remapping Virtual Machine config data store from VM_OS-N-R to VM_OS-N-R.

Remapping Virtual Disk 'Hard disk 1' data store from VM_OS-N-R to VM_OS-N-R.

Remapping Virtual Disk 'Hard disk 2' data store from VM_DA-N-R to VM_DA-N-R.

Upload the VM to vCenter Server.

New VM Name: server1

Datacenter: DC

Resource Pool: Resources

ESX Host: server3

Transport Mode:nbd

Registering VM ...

Registering VM for 'server1' ...

Task is -1% complete

Task is -1% complete

Reconfiguring VM for 'vm-2292' ...

Task is -1% complete

Task is 50% complete

Task is 100% complete

Task is -1% complete

Reconfiguring VM for 'vm-2292' ...

Task is -1% complete

Task is 100% complete

Task is -1% complete

Deleting snapshot for 'snapshot-2293' ...

Task is -1% complete

Task is -1% complete

Requesting 1 recover session(s) from server.

Total estimated disk space needed for recover is 87 GB.

openVddkHandle() successful for disk number 2000 Using 'nbd' as the transport mode for VirtualDisk_2000.

Disk handler for disk 2000 opened successfully

C disk handle open success

...................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................

...............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................

...

.................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................

openVddkHandle() successful for disk number 2001 Using 'nbd' as the transport mode for VirtualDisk_2001.

Disk handler for disk 2001 opened successfully

D disk handle open success

..................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................

Recovering metadata for the disk 0, Please wait...

openVddkHandle() successful for disk number 2000 Using 'nbd' as the transport mode for VirtualDisk_2000.

Disk handler for disk 0 opened successfully

.....

Recovering metadata for the disk 1, Please wait...

openVddkHandle() successful for disk number 2001 Using 'nbd' as the transport mode for VirtualDisk_2001.

Disk handler for disk 1 opened successfully

.Received 111705 matching file(s) from NSR server `server2'

Recover completion time: 6/21/2013 5:04:43 AM

Temporary directory 'C:\Program Files\EMC NetWorker\nsr\tmp\1839487632' for VADP deleted.

Restore of virtual machine finished successfully

Completion time: 6/21/2013 5:04:45 AM

Total time taken: 0 hr(s) 59 min(s) 44 sec(s)

Regards

tech88kur


  • nmc2

    268 Posts

    2045

    1

    Posted March 6th, 2014 02:00

    As per my knowledge disabling FLR is the only option.

    If you want to use FLR, create 2 deferent client instances and run backup separately. When recovering use saveset without FLR to restore. Also the changes will be applicable for future backups only.

    Regards,
    Prajith

  • nmc2

    268 Posts

    2045

    1

    Posted March 6th, 2014 01:00

    As per the above log, you are using nbd mode of transport. Which uses Ethernet network to restore data, so network congestion might cause this.

    Also check if the file level recovery is enabled. If enabled, whole image level restore will take more time.

    Regards,

    Prajith

  • Constans

    1 Rookie

    •

    2 Posts

    2045

    0

    Posted March 6th, 2014 01:00

    Hello!
    Could you tell me how much time do you need for backup ?

    Usually it's depends on your network connectivity, 5 h it's a lot of time . 

  • tech88kur

    142 Posts

    2045

    0

    Posted March 6th, 2014 01:00

    Constans- for backup it takes three hours

    Prajith FLR is enabled, are there any possible ways to bring down this restore time.(this is the most important thing which I am looking for), five hours is simply unacceptable.

    Please note we can do away with FLR.

    Regards

    tech88kur

  • tech88kur

    142 Posts

    2052

    0

    Posted March 6th, 2014 05:00

    Dear Prajith,

    I appreciate your reply.

    Do you have any idea if changing the transport mode may help? What if I try SAN mode, can it give better results?

    Regards

    tech88kur

  • nmc2

    268 Posts

    2052

    0

    Posted March 6th, 2014 06:00

    Yes. SAN mode will give you better performance.

    Refer to NetWorker VMware integration guide for more information on deferent transport modes used by VADP.

    Regards,

    Prajith

  • tech88kur

    142 Posts

    2052

    0

    Posted March 8th, 2014 05:00

    Dear Prajith,

    I am taking 2 points for my action here:

    1) I will create two different clients, one will have FLR enabled for file level backup and another one will have FLR disabled, the second one will be used only for image level backup

    2) I will try with SAN mode recovery.

    It will take some time. I will update the results here.

    Regards

    tech88kur

  • tech88kur

    142 Posts

    2052

    0

    Posted April 8th, 2014 07:00

    Hi All,

    I will also add here that backup is being directed to AFTD device on DD.

    Regards

    tech88kur

  • nmc2

    268 Posts

    2052

    0

    Posted April 8th, 2014 07:00

    I don't think target device matters much here. But its worth testing on different type of devices.

    Regards,

    Prajith

  • tech88kur

    142 Posts

    392

    0

    Posted April 10th, 2014 05:00

    Dear Prajith,

    Forgot to mention that the VADP proxy and storage node are both VMs, and as such SAN mode is ruled out. I just tested it and found errors.

    Found https://emc--c.na5.visual.force.com/apex/KB_BreakFix_1?id=kA1700000000Ven which mentions the issue for 7.6.2, I think the same applies for 8.0.2.6

    That means my only option is segregating FLR based and non-FLR based backups.

    Regards

    tech88kur