Restore to different platform - IDS 7.30
Posted in 1999
Topics: Storage & Space Management, Platform-Specific Issues, Versions, Editions & End-of-Life
We need to set up a disaster recovery machine so that a level 0 archive made on the live machine can be restored. The new machine will have different disk sizes to the old machine so I can't set up (or have set up) identical slices of raw disk. I'm not sure if ones of identical size can be set up as the disks will have different geometry. Some guidance as to how to do this would be most welcome. The big question in my mind is will the restore notice and mind if the chunks on the backup machine are a slightly different size (larger) than on the source machine? I can see that we can make them the same name as on the source machine as OL refers to symbolic links, and it's easy to put the same chunks in the same dbspaces. TIA! PS Platform is SOLARIS 2.5.1 -- Surfer!
I used to do this at my old site (v7.13, Solaris 2.5). It works fine, but obviously has limited value. As soon as we could we moved on to a proper disaster recovery option using disk mirroring. Provided you have the same aggregate amount of disk space, and use symbolic links for your chunk names, I can't see why you cannot set up identically named and sized chunks on the second server. Neil Truby Londis Stores Hampton Hill, UK Surfer! wrote in message <6Tx5YCAt+CM3EwjI@nevis-view.demon.co.uk>... > >We need to set up a disaster recovery machine so that a level 0 archive >made on the live machine can be restored. The new machine will have >different disk sizes to the old machine so I can't set up (or have set >up) identical slices of raw disk. I'm not sure if ones of identical >size can be set up as the disks will have different geometry. > >Some guidance as to how to do this would be most welcome. The big >question in my mind is will the restore notice and mind if the chunks on >the backup machine are a slightly different size (larger) than on the >source machine? I can see that we can make them the same name as on the >source machine as OL refers to symbolic links, and it's easy to put the >same chunks in the same dbspaces. > >TIA! > >PS Platform is SOLARIS 2.5.1 > >-- >Surfer!
In article <7gptj8$8ct$1@taliesin.netcom.net.uk>, Neil Truby <ntruby@netcomuk.co.uk> writes >I used to do this at my old site (v7.13, Solaris 2.5). It works fine, but >obviously has limited value. As soon as we could we moved on to a proper >disaster recovery option using disk mirroring. The site does have mirrored disks etc. What we are looking at here is recovery from 'oh my god the computer centre just burnt down' kind of scenario. > >Provided you have the same aggregate amount of disk space, and use symbolic >links for your chunk names, I can't see why you cannot set up identically >named and sized chunks on the second server. So we need to get *identical* sized chunks otherwise it will fall over? > >Neil Truby >Londis Stores >Hampton Hill, UK > >Surfer! wrote in message <6Tx5YCAt+CM3EwjI@nevis-view.demon.co.uk>... >> >>We need to set up a disaster recovery machine so that a level 0 archive >>made on the live machine can be restored. The new machine will have >>different disk sizes to the old machine so I can't set up (or have set >>up) identical slices of raw disk. I'm not sure if ones of identical >>size can be set up as the disks will have different geometry. >> >>Some guidance as to how to do this would be most welcome. The big >>question in my mind is will the restore notice and mind if the chunks on >>the backup machine are a slightly different size (larger) than on the >>source machine? I can see that we can make them the same name as on the >>source machine as OL refers to symbolic links, and it's easy to put the >>same chunks in the same dbspaces. >> >>TIA! >> >>PS Platform is SOLARIS 2.5.1 >> >>-- >>Surfer! > > -- Surfer!
Surfer! wrote: > > We need to set up a disaster recovery machine so that a level 0 archive > made on the live machine can be restored. The new machine will have > different disk sizes to the old machine so I can't set up (or have set > up) identical slices of raw disk. I'm not sure if ones of identical > size can be set up as the disks will have different geometry. > > Some guidance as to how to do this would be most welcome. The big > question in my mind is will the restore notice and mind if the chunks on > the backup machine are a slightly different size (larger) than on the > source machine? I can see that we can make them the same name as on the > source machine as OL refers to symbolic links, and it's easy to put the > same chunks in the same dbspaces. Yes, works fine as long as the physical partitions are AT LEAST AS LARGE as the chunk that is being restored to it. You do not have to build any dbspaces the restore will do that for you. Just make sure that all the links for the chunk names are there and pointing to partitions of sufficient size. Art S. Kagel