Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Malc backs up a 300GB IDS database to disk with onbar and ISM and needs an imported restore onto a dev machine running several instances, where re-initializing ISM is not allowed. david suggested ism_show -devices, linking the volume, ism_op -mount and ism_recatalog -recreate_from. LIGHT SCANS suggested ontape with compression or copying chunk files. Unresolved.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
For reasons to complex to go into, we're now backing up to disk (data
and logs), using onbar -w and ISM, pool names ISMDiskData and
ISMDiskLogs whereas before we used an external storage manager to
tape.
We do a copy of our live database (300Gb or so) on a regular basis
onto our development system, a separate machine running the same
version of IDS and HP-UX, to an instance configured exactly the same
as the live instance (spacenames, chunknames etc).
Under the old system we had a procedure we followed that worked fine;
now we're building the procedure to do this under the new ISM regime.
All the "Imported Restore" methods I've seen include a step to re-
initialize ISM on the target machine and rebuild the indexes, catalogs
etc using the imported catalogs and indexes from the source machine,
but that's not an option on our development system because we have
several IDS instances running and communicating with ISM, only one
instance of which is to be restored over; so if we overwrite ISM we
prevent the other running instances from using it, which we can't do.
Anyone know how to do an imported restore under these circumstances?
Can't we import just the relevant
So far I've looked at:
http://www-01.ibm.com/support/docview.wss?uid=swg21416790&myns=swgimgmt&mynp=OCSSGU8G&mync=Rhttp://publib.boulder.ibm.com/infocenter/idshelp/v115/index.jsp?topic=/com.ibm.ism.doc/sii051000051.htm
C'mon, anyone?
To use ISM restore an instance from our live server to our test
server, which carries 3 instances, we have to trash all ISM info on
the target server regarding all 3 instances?
No way around that?
On Nov 11, 10:21 am, Malc <mal...@googlemail.com> wrote:
> C'mon, anyone?
> To use ISM restore an instance from our live server to our test
> server, which carries 3 instances, we have to trash all ISM info on
> the target server regarding all 3 instances?
> No way around that?
As per http://publib.boulder.ibm.com/infocenter/idshelp/v117/index.jsp?topic=/com.ibm.ism.doc/ism02.htm
- run ism_show -devices
- link your volume to the device
- run ism_op -mount <device>
- run ism_recatalog -recreate_from <device>
You may need to recreate the storage poosl for the original server
first, I have some undocumented commands to do that which I canot
share, check early Legato Networker documentation.
Hello Malc,
David is probably right. Another option is to backup the live
production to disk using ontape with compression. It is easier, more
reliable, usually 1/10 the original size and usually "fast enough".
Or, if you can shutdown production, then run cp, rcp, dd or whatever
to copy the chunk files to the backup (or restore) location. I have a
terabyte cooked system and for more speed I run "compress -c FILENAME
> /NEW_DIR/FILENAME.Z &" for all chunks in parallel. The original
files remain full size and I get a compressed copy in my backup
directory.
-LS
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.