Allen,
As I understand it, the list of all db and log volumes is maintained on each and every db and log volume. The dsmserv.dsk file only needs to point to one of these volumes. When TSM comes up, it will read that volume, obtain the full list, and access the others. Someone from IBM can correct me if I am wrong, or if this has changed over the years.
Years ago, I actually went through the scenario you describe. We split the DB mirror, and brought up TSM on only half of the mirrors, while we ran an auditdb on the other half of the mirrors.
We run TSM as non-root. We just changed the ownership of the split mirrors so that TSM could not access them.
..Paul
At 09:34 AM 5/20/2005, Allen S. Rout wrote:
I've been unable to find docs on starting a server on only one half of a mirror. Anybody ever done this?
For most of the operations which begin with "Take another backup of your database", I've often wanted to replace that with "Break the mirror, and work with one half of it". You could do that indefinitely, so long as between botched operations you re-mirror the volumes.
The obvious path (halt the server, edit the .dsk file) seems to have no effect: evidently the list of volumes is squirreled away somewhere else too. You get a happy running server with all mirrors present and accounted for.
- Allen S. Rout
-- Paul Zarnowski Ph: 607-255-4757 719 Rhodes Hall, Cornell University Fx: 607-255-8521 Ithaca, NY 14853-3801 Em: [EMAIL PROTECTED]
