Pascal,

Your explanation is the best I've heard and makes sense based on what we've seen.  Since the information is in the registry, it makes me ask the next question - Is there a way to modify the registry? 

I know it is not a normal file.  It would be interesting to try and modify the registry entry for which snapshot ID is the baseline, or find a way to change the snapshot ID of a snapshot.  In a case like this I would be willing to potentially lose some data created between snapshot for backups vs baselining 400TB :-)  I'm guessing there isn't a way to make that work and most certainly would not be supported if there was.


>If this really is the case, it sounds like you can never migrate primary filers
>without taking the root volume with you.

As I already described, just execute snapvault updates from the snapvault destination to register the snapvault relationship and softlocks again in the new root volume. As long as the base snapshots have not been deleted this will work.

I'll keep that in mind next time :-)

>
>I know this does not apply to the secondary filers.  I recently took all the drives
>from a 3140 and connected them to a 3270.  Once I changed the system ID and
>updated the snapvault relationship to point to the new filer, everything was
>happy.  We've done that on several occasions with no issues.
>

With moving all disks, do you mean you also reused the original root volume (with all the registry information)? To be honest I do not have experience with new root volumes on secondary filers. But for primary filers I have seen it gone wrong for the reasons I described.

I wasn't clear with that.  The 3270 already was running as a NearStore with its own backups and root volume.  The 3140 root disks were not used.  I did do the snapvault start command with the new location to update everything which probably made everything happy.

Thanks again for all the help and explanations on this.

Jeff

Pascal.

--
The information contained in this communication and any attachments is confidential and may be privileged, and is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited.  Unless explicitly stated otherwise in the body of this communication or the attachment thereto (if any), the information is provided on an AS-IS basis without any express or implied warranties or liabilities.  To the extent you are relying on this information, you are doing so at your own risk.   If you are not the intended recipient, please notify the sender immediately by replying to this message and destroy all copies of this message and any attachments. ASML is neither liable for the proper and complete transmission of the information contained in this communication, nor for any delay in its receipt.




--
Jeff Cleverley
Unix Systems Administrator
4380 Ziegler Road
Fort Collins, Colorado 80525
970-288-4611