Re: Tivoli (TSM) / Onbar Imported Restore, how to?
Two things, based on your example:
1) It is not necessary to rename the database server on the target machine.
You can rename the oncfg file instead and it will restore fine with the
target and source systems having different names. As far the restore is
concerned, the ixbar file contains a unique id for each object requested
from TSM. This is used in conjunction with the nodename to determine where
the object is located on the backup media.
2) It is not necessary to change dsm.sys each and everytime you perform one
of these restores. You can use the DSMI_CONFIG environment variable in
conjunction with virtualnode/nodename entries in the dsm.sys file. In doing
this you do not impact other backup/restore activity on the server. This
works with V3.2+
Mark
----- Original Message -----
From: "Fred Prose" <fprose@hotmail.com>
To: <informix-list@iiug.org>
Sent: Friday, August 08, 2003 17:21
Subject: Re: Tivoli (TSM) / Onbar Imported Restore, how to?
> All kidding aside - you just have to fake it!
>
> We do this all the time. In a condensed version, this is what the
> environment would look like for the procedure.
>
> Production server: PRODSRVR
> Instance: PRODINFMX
>
> Test Server: TESTSRVR
> Instance: TESTINFMX
>
> First of all, you need to build the TESTINFMX instance to look just
> like PRODINFMX, but I’ll assume you know that since you’ve
> been using optape for this.
>
> Second, make sure that Tivoli actually works on TESTSRVR (and
> TESTINFMX). Even a simple backup will test this – and since
> Tivoli’s error messages are VERY cryptic (and non revealing)
> it’s better to validate before the restore.
>
> When the server (client) actually communicates with the TSM server,
> the client identifies itself through the dsm.sys configuration file.
> This will be in a path like:
> /usr/tivoli/tsm/client/ba/bin/dsm.sys
> The entries include the following (of interest):
> SERVERNAME tsmserver <-- your tsm backup
> server
> COMMMETHOD TCPip
> TCPPORT 1500
> TCPSERVERADDRESS 192.168.96.14 <-- address of backup server
> NODENAME TESTSRVR <-- the client server identification
>
> So, assuming you want to get the contents of PRODINFMX over to
> TESTINFMX, here are the steps.
>
> 1. You copy the $INFORMIXDIR/etc/ ixbar.x file from the PRODINFMX
> server to the TESTINFMX server (where x is the server number from
> onconfig. This is how onbar knows what to request.
> 2. You copy the onnconfig from PROD to TEST so that both Informix
> servers are named PRODINFMX. You need to change the environment
> variables as well.
> 3. You change the NODENAME entry in the TESTSRVR dsm.sys file to
> PRODSRVR
> 4. During this time, until you change the dsm.sys entry back, no TSM
> backups should run!
> 5. Cold restore. When done, shut the instance down and bring back the
> original onconfig file and environment variables so that the instance
> once again thinks it’s TESTINFMX.
> 6. Bring up TESTINFMX
> 7. Change the entries back in dsm.sys
>
> Changing the instance name by making changes to the onconfig file and
> the environment variables is not required if your production instance
> and your test instance are the same name.
>
> fprose at supreme dot sp dot state dot az dot us
sending to informix-list