Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've tried this on a production system and a test system.
I've got live data on one system thats got a bunch of luns in qtrees - that snapmirrors just fine to a secondary and from that I want to snapvault to a teritary.
Whenever I try I get messages like this:
Snapvault configuration for the qtree has been set.
Tue Oct 9 22:00:23 BST [replication.dst.err:error]: SnapVault: destination transfer from filerfour:/vol/data to /vol/sv_data/qtree : cannot replicate a volume with LUNs to a qtree; each qtree must be individually replicated to another qtree.
Tue Oct 9 22:00:23 BST [replication.src.err:error]: SnapVault: source transfer from /vol/data to filerfour:/vol/sv_data/qtree : cannot replicate a volume with LUNs to a qtree; each qtree must be individually replicated to another qtree.
Transfer aborted: cannot replicate a volume with LUNs to a qtree; each qtree must be individually replicated to another qtree.
what the hell is it on about? What has to be individually replicated? I can't SV a QSM and I can't snapvault from a qtree so whats it on about?
Solved! See The Solution
1 ACCEPTED SOLUTION
migration has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm pretty sure you should include the source qtree name in the command line.
How did you write it? it should be some thing like:
snapvault start -S filerfour:/vol/data/DesiredSourceQtreeName to filername:/vol/sv_data/qtree
This will create a snapvault relationship between the desired qtree with the contained lun inside of it to the new qtree.
Notice that the qtree called "qtree" shouldn't exist in the destination volume as it is created automatically by snapvault.
Let me know if this helps.
2 REPLIES 2
migration has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm pretty sure you should include the source qtree name in the command line.
How did you write it? it should be some thing like:
snapvault start -S filerfour:/vol/data/DesiredSourceQtreeName to filername:/vol/sv_data/qtree
This will create a snapvault relationship between the desired qtree with the contained lun inside of it to the new qtree.
Notice that the qtree called "qtree" shouldn't exist in the destination volume as it is created automatically by snapvault.
Let me know if this helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Cheers, this worked on the test system so I'll try it on production.
I was always told to go volume to qtree so didn't even think to try this!
