Subscribe

Protection Manager 4.0 several practical questions

Hi team,

Getting to implementation of Protection Manager 4.0 and trying some use-cases different questions came up:

- doing a restore from a local or secondary backup there is always a file created named: “restore_symboltable”. This wouldn’t be too bad if this file wouldn’t be of a size of 4 MB(!) even if you restore a file of 4 KB(!).

Second: This file will grow in 4 MB (!) incremental every time you do additional restores to this destination.

How can this file be avoided? What is this file good for?

- there is a new space provisioning for the secondary in Protection Manager 4.0 which will automatically resize the secondary storage: does this relate to Aggregat-level too? E.g. Primary site Aggregat will be enlarged with several disks and the volume to be vaulted will be enlarged in nearly the same size than the growth of the Aggregat. Will Protection Manager or maybe Provisioning Manager enlarge the secondary Aggregat if there are several spare disks available? Or will there be an error-message for enlargement of the secondary volume cause there is not enough space in the Aggregat left?

- having a look at the secondary volume all snapshots related to Protection Manager are busy. Does this have any negative impact on the systems? How big will this impact be?

Is this a “normal state” for snapshots managed through PM?

- could you please explain the following space-allocation and reporting seen in PM:

Having a secondary volume created through PM with several Qtrees vaulted to this volume the secondary volume will be created with no space guarantee (very good) but showing about 50% used space (why?). Having a look at OM this isn’t the case: the volume is only as big as data is moved to this destination 2% (which is the right behavior). Why is Protection Manager showing nearly 50% used capacity?

I hope you can help me with this questions. J

Many thanks in Advance.

Greets Michael

Re: Protection Manager 4.0 several practical questions

Getting to implementation of Protection Manager 4.0 and trying some use-cases different questions came up:

- doing a restore from a local or secondary backup there is always a file created named: “restore_symboltable”. This wouldn’t be too bad if this file wouldn’t be of a size of 4 MB(!) even if you restore a file of 4 KB(!).

Second: This file will grow in 4 MB (!) incremental every time you do additional restores to this destination.

How can this file be avoided? What is this file good for?

This is Behavior of Data Ontap.

http://now.netapp.com/NOW/knowledge/docs/ontap/rel705/html/ontap/tapebkup/recove25.htm

http://now.netapp.com/NOW/knowledge/docs/ontap/rel705/html/ontap/cmdref/man1/na_restore.1.html

There have been few request to delete the same after restore.Yet it is not targeted to any release,pls get your sales folk to add your case to the request.

- there is a new space provisioning for the secondary in Protection Manager 4.0 which will automatically resize the secondary storage: does this relate to Aggregat-level too? E.g. Primary site Aggregat will be enlarged with several disks and the volume to be vaulted will be enlarged in nearly the same size than the growth of the Aggregat. Will Protection Manager or maybe Provisioning Manager enlarge the secondary Aggregat if there are several spare disks available? 

We dont add disk to aggrs to enlarge it.Protection Manager/Provisioning Manager only resizes volume.

 Or will there be an error-message for enlargement of the secondary volume cause there is not enough space in the Aggregat left?

Yes, saying there is not enough space to resize the volume as containing aggr is full and there will also be suggestion to add disk to the aggr.

- having a look at the secondary volume all snapshots related to Protection Manager are busy. Does this have any negative impact on the systems? How big will this impact be?

Is this a “normal state” for snapshots managed through PM?

Only the SnapVault or Snapmirror snapshot would be busy, can you get the output of the snaplist from the filer ?

- could you please explain the following space-allocation and reporting seen in PM:

Having a secondary volume created through PM with several Qtrees vaulted to this volume the secondary volume will be created with no space guarantee (very good) but showing about 50% used space (why?). Having a look at OM this isn’t the case: the volume is only as big as data is moved to this destination 2% (which is the right behavior). Why is Protection Manager showing nearly 50% used capacity?

Where in Protection Manager are you looking at, which is showing 50% used capacity.

Regards

adai