All my snapvaults are qtree based, but I do a 1:1 mapping of source and destination volumes. Mapping multiple sources to one destination can cause issues if one of the sources is slow, or has a lot to transfer. All the qtrees on the destination volume won't go to 'Idle' until all the transfers finish, so future updates can be missed.
Moving qtrees won't work. Best bet there is to stop it on the old volume, and start it new on the new volume. The existing snapshots will expire off.
John
-----Original Message----- From: John Stoffel [mailto:john.stoffel@taec.toshiba.com] Sent: Tuesday, December 11, 2007 12:56 PM To: Clear, John Cc: John Stoffel; toasters@mathworks.com Subject: RE: traditional SnapVault destination vol to flex vol convertion question
John> This is doable. I've moved snapvault destination volumes John> between aggregates without issue. Stop the snapvaults, vol copy John> the data, offline the old volume, rename the new volume and John> start the snapvaults again.
Duh... makes sense. I wasn't even thinking of the vol copy for some reason, mostly because I do it so infrequently.
Hmmm... the only problem is that I've got qtree based SnapVaults as well, and I'd probably prefer to move them instead if I can. But I think I need to move on a per-volume basis instead. Grr...
Thanks!