I moved an application from a server running Solaris 8 to Solaris 10. To accomplish this, I added SAN disks to the application's disk group, which previously only had local disks. The disks on the SAN were visible to both old and new servers. Deported the disks on the old server, and imported on the new. I had to do a '-f' import, but no problem, worked fine. I had failed disks and plexes on the new server, so I removed them.
Not sure if this is relevant or not, but after cleaning up the failed disks and plexes on the new server, I re-imported on the old server to look at something. I did not start any volumes or mount anything, but for a time the disk group was imported on both old and new servers.
Now it looks like I may need to move back to the old server. The SAN admins have taken away access to the SAN disks, but no problem, I have all the local disks, right? Problem is, I get "import failed: Disk group has no valid configuration copies". This was unexpected, because the disk group was up and running fine with only the local disks; it was not until a couple of months ago that we added the SAN disks to the disk group.
So, I'm looking for a way to recover this disk group. I can't give the server access to the SAN disks again, because they now have data on them from this failed application upgrade. I can however, get 'vxprint' output from the new server, and use that to rebuild my volumes. Just not sure how to go about this or if there is another way around this error message.
Solved! Go to Solution.
Thanks Gaurav. Old server is VxVM 4.1, new is VxVM 5.0. I know about the config copies, and was careful that disks on the SAN had active config copies so that they would import on the new server. I didn't even check the local disks, but for a long time this server had only local disks -- no SAN disks -- so I am sure there were active config copies on the local disks.
As for the /etc/vx/cbr/bk/<diskgroup> directory -- the files in there are very old. I suspect that they do not represent the latest disk group configuration. These are supposed to get updated when the disk group is imported, correct? Well the server was rebooted several times after the oldest file in this directory, so I don't know why these files are showing such an old date. There is another disk group on this server that was also imported to the new server, and I have no problem importing it back. It shows recent files in its /etc/vx/cbr/bk/<diskgroup> directory.
I'd like to try to get the disk group info from the new server. I believe that the info in the /etc/vx/cbr/bk/<diskgroup> directory contains the disk group status before I removed the plexes and disks that were local to the old server.