Paul, If you need to restore from the new node name, you would launch the CLI or GUI specifying the alternate options file name. For example, in the example below:
GUI: TDPSQL /TSMOPTFILE=DSMARCH.OPT CLI: TDPSQLC RESTORE dbname full /TSMOPTFILE=DSMARCH.OPT This will tell Data Protection for SQL to connect to the TSM Server using the alternate options file, thus the alternate NODENAME. Del ---------------------------------------------------- "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 01/22/2008 11:54:12 PM: > OK - I have done this and it is working as far as backing up the SQL > database goes. > > Now what do I do if I need to restore from this new node name back onto > the client? > > Do I need to do anything with the dsm.opt and dsmarch.opt files before > starting the restore? > > > > -----Original Message----- > > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On > > Behalf Of Del Hoobler > > Sent: Saturday, 4 August 2007 2:37 AM > > To: ADSM-L@VM.MARIST.EDU > > Subject: Re: [ADSM-L] TDP for SQL question > > > > Paul, > > > > Typically... I see that people will name their node > > the same as their primary SQL node with an extension. > > Something like: > > Primary: SQLSRV23_SQL > > Archive: SQLSRV23_SQL_ARCH > > > > And they will have a separate DSM.OPT file, something like > > DSMARCH.OPT that has the archive nodename. > > > > Thanks, > > > > Del
