Repair TSM misconfiguration

[adomeij]

Hi,

We have set up the CMOD 'backend' for storage to be TSM.
We have 2 TSM servers (a primary and a secondary) with 'Node replication: primary -> secondary' enabled.
Unfortunately the person responsible for the TSM setup missed the "indefinite" flag for TSM retention time on the primary node.
This led to TSM discarding loads older than 750 days (without waiting for CMOD to order the removal) on the primary node and, not surprisingly, documents in the removed loads are no longer retrievable from a CMOD instance running against the TSM primary node.
Fortunately (I hope) we can fix this since the backup node was set up correctly visavi the "indefinite" flag so the file systems removed from the primary node still reside on the secondary (no CMOD instance has ordered removal of any files).

Is it possible to reverse the roles of the 2 TSM servers so the files on the secondary server will be replicated to the primary server and by magic and/or pure luck be accessible again from the CMOD instance running against the primary node?

Thanks in advance

Anders.

[Justin Derrick]

Hi Anders.

You can try swapping the TSM servers, but it depends on the type of replication you're doing between them.  I've set up server-to-server backups, but never mirroring.  You'd want to check with your TSM Administrators to ensure that if you change your CMOD config to point at the secondary server, that it will appear the same to the client as the primary server.

If you get that working, you should be able to iterate over the database records and pull the missing files from the secondary server and push them back into the primary server.  I've got some utilities that I've developed that will help automate that process if you're interested.  I'm also not sure if loads that go into the secondary server would be replicated back to the primary server...  You're in uncharted territory here.

-JD.

[adomeij]

Thanks for yor answer, I'll pass it along to our TSM guys
Rgds
Anders