AIX

Well, it might work.

If you are not allowed access to the production server, can you ask for some details about it? The output of lsvg -l rootvg would be really useful. I'm assuming that you haven't acquired a mksysb media illegally, of course.......

If you have space and servers, what I have seen done is to read in the image to a NIM server that you can then use to provision a new cloned server and you get the chance to resize/move the logical volumes at that point. You would need a NIM server and plenty of disk space and disks to restore to on it & the eventual target.



Robin

"I am not allow to do/check anything on the production server."
what I mean is that i was still new at that time, my senior did the mksysb backup and checked that the backup was good.
my task at that time, was to ensure that the DR testing is successful, for audit purpose, which i was very fortunate that it ended well.
i have taken all the pointers, and make an mksysb.
now waiting for a chance to do the restoration at our DR site and hope that it will go through.

Can you share the output from lsvg -l rootvg so we can point out any risks?



Robin

Good idea. You should include the output of lsvg rootvg (without the -l) too, because LV sizes in the output of lsvg -l is in PPs and only lsvg will tell you the PP size.

I hope this helps.

bakunin

i will have to do another mksysb and exclude /opt/bea92 and /opt/filenet.
these two filesystems are installed and mounted on rootvg, each allocated 20GB, usage is 70%

As already said, that is a bad design, however it depends on the hardware you have available.

What hdisk do you have available on the production side? It would be far better to create replacement filesystems in another volume group and move the data. Is this possible? With increasing minimum sizes of disks, it is becoming more common to have huge amounts of unused space in rootvg and it is important to keep the contents down to the minimum to boot the OS. Anything to do with the application or data storage should really be kept out of rootvg to avoid problems like this.


Kind regards,
Robin

this production server is an legacy.
my seniors taking over from the previous vendor, did not even do any mksysb backup until i join and ask them to do it.
that is where, I encounter so many problems with the restoration.
and the server has not been shutdown before.
i know from reading thru threads here, it is an terrible design, waiting for disaster to happen.
so until, the management gives me approval to change it, i am afraid i also cannot do anything.
once i do another mksysb backup excluding the two filesystems /opt/bea92 and /opt/filenet, i will find a chance to do the restoration at our Disaster Recovery vendor's site.
if the restoration is successful, i will stick to my workable ways to do restoration during Disaster Recovery Testing.
although more work to do and take more times.
thank you everyone for the help and advise.