Hi Camila,
Tomas here from Spictera .
We have some different options for you to perform redirect restore.
Redirect restore from source to target using IBM Spectrum Protect
Alternative 1 using ASNODE:
===========================
On the Spectrum Protect server:
SP> GRANT PROXYNODE TARGET=sourcenode AGENT=targetnodeCreate a redirect restore option file (dsm.opt), pointing out other configuration stanza in dsm.sys
root@targetserver# echo SERVERNAME restore > /tmp/dsm.opt Create a new stanza in dsm.sys
root@targetserver# cat >> /opt/tivoli/tsm/client/api/bin64/dsm.sys <<- EOFSERVERNAME restore TCPSERVERADDRESS backup.server.comNODENAME targetnode ASNODE sourcenode PASSWORDACCESS generate ERRORLOGNAME /var/log/dsmerror_restore.log EOFPoint out the new option file, by setting the DSMI_CONFIG environment variable, pointing to the location of the newly created dsm.opt file
root@targetserver# export DSMI_CONFIG=/tmp/dsm.opt Perform your redirected restore
root@targetserver# onbar -r Alternative 2 using same source node credentials:
=================================================
Create a redirect restore option file (dsm.opt), pointing out other configuration stanza in dsm.sys
root@targetserver# echo SERVERNAME restore > /tmp/dsm.opt Create a redirect restore option file (dsm.opt), pointing out other configuration stanza in dsm.sys
root@targetserver# cat >> /opt/tivoli/tsm/client/api/bin64/dsm.sys <<- EOF SERVERNAME restore TCPSERVERADDRESS backup.server.comNODENAME sourcenode PASSWORDACCESS generate ERRORLOGNAME /var/log/dsmerror_restore.log EOFPoint out the new option file, by setting the DSMI_CONFIG environment variable, pointing to the location of the newly created dsm.opt file
root@targetserver# export DSMI_CONFIG=/tmp/dsm.opt Point out the new option file, by setting the DSM_CONFIG environment variable (needed to set password), pointing to the location of the newly created dsm.opt file
root@targetserver# export DSM_CONFIG=/tmp/dsm.opt Point out location of dsm.sys file for "dsmc"
root@targetserver# export DSM_DIR=/opt/tivoli/tsm/client/api/bin64 Save the source node password
root@targetserver# dsmc # Enter the sourcenode and the password for the sourcenode
If you don't remember the source nodes password, than one can set a new password on the Spectrum Protect server
SP> UPDATE NODE sourcenode newpwd Perform your redirected restore
root@targetserver# onbar -r Alternative 3 using virtualnode: <<--- have never tried this
===========================================
You need to add the "VIRTUALNODENAME sourcenode" to the current used dsm.opt file
root@targetserver# echo VIRTUALNODENAME sourcenode >> /opt/tivoli/tsm/client/api/bin64/dsm.opt Regards Tomas
Spictera creates innovative Climate Smart Energy Efficient solutions
We have agentless solutions (Spictera SPFS) where one can mount the IBM Spectrum Protect on a path on your server (mountpoint of filesystem)
Eg
#
mount -t spfs /backupAll file operations that goes via this path is translated directly to IBM Spectrum Protect Client API calls
So a backup/restore using onbar/rman/mysqldump is more easy to manage, as the solution is agentless.
One can see all the backups using native OS commands etc.
With Spictera Snapshot, one can take application consistent snapshots directly to a IBM Spectrum Protect server, using progressive block level incremental forever techniques. Controlling the retention of the snapshot on the IBM Spectrum Protect server, and are not limited to a hardware
Restoring a snapthot is nearly instant
Contact us for more information:
https://www.spictera.com Regards Tomas