ldmwndletsm
ADSM.ORG Senior Member
- Joined
- Oct 30, 2019
- Messages
- 232
- Reaction score
- 5
- Points
- 0
We're conducting a (D)isaster (R)ecovery test wherein we want to test restoring the primary backup server's database to a test/DR server and then attempt to restore some client data, from a couple of tape(s) written on the primary server, for proof of concept. The idea is to rely as little as possible on the existing configuration on the primary server and do it all from scratch wherein a basic Linux OS is installed (same version), TSM (same version) is installed from a download and we go from there.
This is on RHEL Linux for both machines. The DR server will not have access to the tape library, but we will be able to access (read-only) one of the tape drives via iSCSI, but no robotics. The required database tape will be manually loaded via mtx. We installed the same version of TSM on the test server, and we think we have the database configured and formatted. We did install the ibm lin_tape driver, and we have demonstrated that we can see that device over iSCSI from the command line (outside of TSM), but we have not tested it with a tape in the drive.
How can we make that device visible to TSM so we can try to restore the database?
I did look through some of the information on IBM's site, but it's a tad bewildering with so many links on every page. Sheesh!
This is on RHEL Linux for both machines. The DR server will not have access to the tape library, but we will be able to access (read-only) one of the tape drives via iSCSI, but no robotics. The required database tape will be manually loaded via mtx. We installed the same version of TSM on the test server, and we think we have the database configured and formatted. We did install the ibm lin_tape driver, and we have demonstrated that we can see that device over iSCSI from the command line (outside of TSM), but we have not tested it with a tape in the drive.
How can we make that device visible to TSM so we can try to restore the database?
I did look through some of the information on IBM's site, but it's a tad bewildering with so many links on every page. Sheesh!