Data Infrastructure Management Software Discussions

Highlighted

When will Protection Manager support volume-based SnapVault?

I have a customer with many TBs of VMware datastores within flexvols without qtrees.  When will Protection Manager support volume-based SnapVault?  We are implementing SnapVault for long-term VM retention and could really use Protection Manager for backup management.

Any plans to tightly integrate SMVI, SnapVault, Protection Manager, System Manager etc.?  The options currently available to protect different data can be very confusing to customers.  I envision a unified/combined management solution that will integrate all the current "snap" technologies so customers have a single view of their data and protection policies.

Thanks,

Dave

27 REPLIES 27
Highlighted

Re: When will Protection Manager support volume-based SnapVault?

Hi Dave,

     Even now Protection Manger supports Snapvault of entire volume(irrespective of qtree is there or not.)

What protection manger does is that, it treats those data that is  inside the volume but not the qtree as non-qtree data represented by

<filername>:/<volumename>/<qtreename> in case of non qtree the qtree name is replaced with "-"

Example.

filername:/vin1_root/-

So you can still protect your ,TBs of VMware datastores within flexvols without qtrees using protection manager.

Regards

adai

Highlighted

Re: When will Protection Manager support volume-based SnapVault?

Thanks for the quick reply.  The other question was will there be better integration with Protection Manager, SMVI, SnapVault etc. in the up-coming release of Protection Manager?  How can we help customers integrate Protection Manager, SnapVault and SMVI now or will this be better integrated in the near future?

Thanks,

Dave

Highlighted

Re: When will Protection Manager support volume-based SnapVault?

NetApp Alumni

Hi Dave,

Good questions.

Integration of SMVI, SnapVault, Protection Manager is planned for mid 2010.  If you need additional information, please contact me offline.

Thanks,

Cindy

Highlighted

Re: When will Protection Manager support volume-based SnapVault?

Does Protection Manager support importing already created volume-based snapvault relationships?  It doesnt seems to list them under External Relationships.

Thanks,

Dave

Highlighted

Re: When will Protection Manager support volume-based SnapVault?

NetApp Alumni

No.  Protection Manager does not recognize WVSV.

Highlighted

Re: When will Protection Manager support volume-based SnapVault?

OK, it doesn't reconize them but it does let you create vol-based SV relationships from scratch and manage them via PM right?

Thanks,

Dave

Highlighted

Re: When will Protection Manager support volume-based SnapVault?

No, our monitor doesn't recognize the relationship on the storage system, so it doesn't show up in our database.  Since it's not in our database, ProtMgr won't allow you to import it.

Highlighted

Re: When will Protection Manager support volume-based SnapVault?

NetApp Alumni

There is a misunderstanding on what does volume based SV support mean.

1. You can put a whole volume into protection manager and PM will create the correct SV relationship.  It does not use the ONTAP WVSV mechanism.  This is what you need for the usecase you described in the original post.

2. Some customers use WVSV, which is ONTAP technology to get around the SV performance issues when there are thousands of qtrees in a volume.  This is not the usecase you have. Protection Manager does not support this configuration today.

Thanks,

Cindy

Highlighted

Re: When will Protection Manager support volume-based SnapVault?

Please explain the acronym WVSV.  I think there is a confusion here....

Highlighted

Re: When will Protection Manager support volume-based SnapVault?

NetApp Alumni

Whole Volume SnapVault.

View solution in original post

Highlighted

Re: When will Protection Manager support volume-based SnapVault?

Let me make sure I'm clear.  If you already know all this, then excuse me for wasting bits.

There are two ways to do what you're trying to do.

One way is to set up a "normal" SnapVault relationship where the source is "-", sometimes called "qtree0".  This represents all the data not in qtrees in your volume.  Since you said you don't use qtrees, this essentially means all the data contained by the volume.  This approach is 100% supported by Protection Manager.

The second way is "whole-volume SnapVault".  In this case, the source is the volume itself, not qtree0, so you'll see a source path like "filer:/vol/mvol", not "filer:/vol/myvol/-".  No DFM-based product understands whole-volume SnapVault.

Protection Manager tries to finesse this distinction.  You can add a volume to a dataset and we'll ensure all the data in the volume is protected.  Today, we do that by building SnapVault relationships from all source qtrees and one additional relationship for qtree0.

If you already have whole-volume SV relationships, I'm not sure if there's a way to convert them into qtree0-based relationships.  If not, then you won't be able to get Protection Manager to work with them.

Highlighted

Re: When will Protection Manager support volume-based SnapVault?

yes. it doesn't allow you to import existing relationship but does allow creating from scratch and managing the same.

Highlighted

Re: When will Protection Manager support volume-based SnapVault?

Thanks for the great feedback Cindy and Peter.  This was a great help.

Dave

Highlighted

Re: When will Protection Manager support volume-based SnapVault?

Hi,

I am wondering if there is an update to the support for DFM 4.0 to support the WVSV as mentioned in this forum.

The situation I have is that a customer has created cifs volumes with a large amount of qtrees delimiting their smb share point from these qtrees within the volume, for example we have:

/vol/myvolume/busfinqt

                    /busfinblah

                    /busfinblahblah    

                    /blah

                    /blahblahetc..

(the part from the last / are qtrees)

There are approximately 250 qtrees in multiple volumes that they are looking at replicating to a snapvault location, prior to this the individual qtree method was tried and tested although the performance impact (even with Nearstore enabled) caused them to drop that design and go back to the drawing board.

The ideal end point would be for DFM/NMC (Netapp Management Console) to recognize the wholevolume snapvaults so I can import it into a mirror and backup policy, I am talking about the policy which has a different destination for each snapmirror / snapvault within the NMC rather than a cascade source => snapmirror=> snapvault relationship. It basically looks like this:

              

                   /  SnapMirror

Sourcevol   / 

                 \

                   \  Snapvault

Otherwise, the options are to live with the external management of snapvault at the WVSV level, or redesign the volumes with a higher level share and ACL the subdirectories off below i.e.:

/vol/myvolume/topshareqt/sub1

                                     /sub2

                                     /sub3

/vol/myvolume.topshare2qt/sub1

                                       /blah..

Any info or guidance appreciated!

Thanks

KD

Highlighted

Re: When will Protection Manager support volume-based SnapVault?

Hi Kd,

     You can add your /vol/myvolume to the dataset having Backup and mirror Policy, as primary member.

PM will take care and create 250 Snapvault relationships in the Backup filer and create one Snapmirror relationships in the mirror node.

Any further volumes added in the /vol/myvolume is automatically detedted by PM and SV relationships are created.

But still PM does not supported the whole volume snap vault of /vol/myvolume backedup  to a single qtree in the destination volume thus creating one SV relationships.

Hope I clarified your doubts.

Regards

adai

Try the NEW Knowledgebase!
NetApp KB Site
Forums