2009-06-10 08:44 AM
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.
Solved! SEE THE SOLUTION
2009-06-10 08:55 AM
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 "-"
So you can still protect your ,TBs of VMware datastores within flexvols without qtrees using protection manager.
2009-06-10 09:07 AM
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?
2009-06-10 10:27 AM
Integration of SMVI, SnapVault, Protection Manager is planned for mid 2010. If you need additional information, please contact me offline.
2009-06-10 10:29 AM
Does Protection Manager support importing already created volume-based snapvault relationships? It doesnt seems to list them under External Relationships.
2009-06-10 10:37 AM
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.
2009-06-10 10:39 AM
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.