You can qtree SnapMirror between trad & flex vols if you are using qtrees and you do not want to use ndmpcopy.
However, does not overcome your issues with snapshot retention .....
________________________________
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of George, Andrew Sent: Tuesday, 16 May 2006 7:53 AM To: Steven Mandrake; toasters@mathworks.com Subject: RE: Upgrade 270 and keep snapshots for snapmirror
Hi I think the choices are use trad vols and keep snapshots use flex vols and loose snapshots
As you can't mirror from a flex vol to a trad vol, what we wound up doing was ndmpcopying the data, mirroring the tradvol (and snapshots) nightly, and then we cut over to the new box, initializing a second mirror - then when our last snapshot from the trad vol was expired, we destroyed the traditional mirror volume.
Sorry, I was facing the same thing and couldn't come up with a better way of doing it than what I outlined
________________________________
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Steven Mandrake Sent: Tuesday, 16 May 2006 7:21 AM To: toasters@mathworks.com Subject: Upgrade 270 and keep snapshots for snapmirror
Hello Everyone,
I am trying to upgrade from 6.5 to 7.0.4 and I currently have trad vols. I also have another filer that is hosting my snapmirrors of many trad vols.
My goal is to upgrade both filers to 7.0.4 to take advantage of flexvols.
I want to preserve my snapshots and have those moved as well. So ndmpcopy is out for me.
volcopy preserves my snapshots, but I can't seem to get it to work between trad vols and flex vols.
Is there a way I can do the following: 1. upgrade to 7G source and destination 2. Migrate from trad vol to flex while preserving my snapshots 3. update my snapmirror w/o re-initalizing the mirror.
I don't have Acopia or Neopath either. Are there tools w/in NetAPP that can help me?
Hi,
On 5/16/06, David Dalby Ddalby@asi.com.au wrote:
You can qtree SnapMirror between trad & flex vols if you are using qtrees and you do not want to use ndmpcopy.
However, does not overcome your issues with snapshot retention .....
This is my first post to this list ...
If your data is inside qtrees on the tradvol, there is a clean way to migrate everything from tradvol to flexvol. Here's the basic idea:
- stop all scheduled snapshotting on source & dest - do a QSM initialize from your tradvol qtree(s) to your qtrees on the newly created flexvol, but - and this is important - use the oldest snapshot on the source as the baseline snapshot for the "snapmirror initialize" operation(s) - afterthe transfer(s) has/have finished, take a snapshot on the destination (same name as on the source) - next, do a QSM update operation for the relations from your tradvol to your flexvol, but use the "next" snapshot as a baseline for that snapshot - after those transfers have finished, take a snapshot on the destination again.
In the end, you will have all your snapshots on the destination. The dates will be all messed up, as those snapshots will all be taken on the same day, even if they cover months of snapshot differences in data.
Now, if your tradvol data is not in qtrees, there is always a possibility to do vol-to-qtree snapmirror, by using "-" as the source qtree. (Read up on it, as this won't transfer data that isn't already in a real qtree - that data will need to be transferred separately). You will end up with a different path to your data though. There's no way around that.
Also, I don't know how this migration procedure will work with your existing snapmirror relations. Don't know if you'll be able to just move them over to flexvol. Might work, but you need to test it out...
Regards, Filip
What I did, which has some drawbacks, was rsync the data from snapshot directories in order from oldest to most recent while manually making snapshots with appropriate names on the target flexvol:
rsync weekly.3/ from source to target create weekly.3 snapshot on target weekly.2, weekly.1, nightly.6, 5, 4, 3 etc. and ending with rsyncing the live copy of data from the source to the destination, then enabling the normal snapshot schedule.
The benefit of this method is you get to keep your snapshots, as little or as many of them as you want.
The drawbacks include: - Slow, tedious procedure, worse if you have lots of snapshots - The snapshots consume much more space temporarily, until they rotate out over the next x weeks according to your snapshot schedule. More space is required because the filer doesn't understand what rsync is doing as efficiently as if real file modifications had been made. For example, a one byte change in a 10 meg file will take a whole 10 megs in snapshots instead of a minimal amount. - If your source snapshots rotate, you'll have to remember to make the same manual rotations and translations to your target. Unless your volume is small, I doubt all the snapshots you want would be possible to copy in a single day. This can be confusing and a small pain.
On Tue, May 16, 2006 at 09:08:56AM +0800, David Dalby wrote:
You can qtree SnapMirror between trad & flex vols if you are using qtrees and you do not want to use ndmpcopy.
However, does not overcome your issues with snapshot retention .....
------------------------------------------------------------------------------- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of George, Andrew Sent: Tuesday, 16 May 2006 7:53 AM To: Steven Mandrake; toasters@mathworks.com Subject: RE: Upgrade 270 and keep snapshots for snapmirror
Hi I think the choices are use trad vols and keep snapshots use flex vols and loose snapshots
As you can't mirror from a flex vol to a trad vol, what we wound up doing was ndmpcopying the data, mirroring the tradvol (and snapshots) nightly, and then we cut over to the new box, initializing a second mirror - then when our last snapshot from the trad vol was expired, we destroyed the traditional mirror volume.
Sorry, I was facing the same thing and couldn't come up with a better way of doing it than what I outlined
------------------------------------------------------------------------------- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Steven Mandrake Sent: Tuesday, 16 May 2006 7:21 AM To: toasters@mathworks.com Subject: Upgrade 270 and keep snapshots for snapmirror
Hello Everyone,
I am trying to upgrade from 6.5 to 7.0.4 and I currently have trad vols. I also have another filer that is hosting my snapmirrors of many trad vols.
My goal is to upgrade both filers to 7.0.4 to take advantage of flexvols.
I want to preserve my snapshots and have those moved as well. So ndmpcopy is out for me.
volcopy preserves my snapshots, but I can't seem to get it to work between trad vols and flex vols.
Is there a way I can do the following: 1. upgrade to 7G source and destination 2. Migrate from trad vol to flex while preserving my snapshots 3. update my snapmirror w/o re-initalizing the mirror.
I don't have Acopia or Neopath either. Are there tools w/in NetAPP that can help me?
-
Adam McDougall -
David Dalby -
Filip Sneppe