Possibly because the system is confused because of the new system id/serial which is part of the snapshot name. You did use exactly the same system names ? They are case sensitive as far as snapshot naming is concerned. Or Protection Manager may have deleted them because it is confused about something. Can you restart them with "snapvault start -S -r" ?
On Fri, Jul 5, 2013 at 3:08 AM, Jeff Cleverley jeff.cleverley@avagotech.com wrote:
Greetings,
I upgraded heads on our filers. The new 6290s had their own disks and I have 8.1.2P4 on them. The old 6080s were 7.3.5.1P4. For the update I kept the 6290 root/vol0 drives and changed ownership of all the other drives. The aggregates were brought online and all the volumes came up OK. I'm now seeing none of my backups are running because the snapvault snapshot is missing. I still have the acs snapshot. I've tried the snapvault start -S command and it says it is already a snapvault relationship. When I try to tell it to do a snapvault update, it says the base snapshot no longer exists on the source.
What happened to all my snapvault snapshots? Why did the snapvault snapshots get released? I thought those were in the volume and should have carried over in the hardware migration. I still have access to the old root volumes and backups of the old root volumes if there is anything that can be salvaged. I would rather not have to re-baseline 100+TB of source data.
Thanks,
Jeff
-- Jeff Cleverley Unix Systems Administrator 4380 Ziegler Road Fort Collins, Colorado 80525 970-288-4611
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters