ADSM-L

TSM 4.1.2.0 - Question : How can I force dsmserv to resync DB /DBCOPY and LOG/LOGCOPY mirror volumes ?

2001-02-12 18:06:01
Subject: TSM 4.1.2.0 - Question : How can I force dsmserv to resync DB /DBCOPY and LOG/LOGCOPY mirror volumes ?
From: "Kent J. Monthei" <Kent_J_Monthei AT SBPHRD DOT COM>
Date: Mon, 12 Feb 2001 18:04:37 -0500
We just completed our ADSM 3.1.2.20 -> TSM 4.1.2.0 upgade on Sun Solaris 2.6
last weekend.

As part of our backout plan for the TSM upgrade, we first "broke" ADSM DB/DBCOPY
and LOG/LOGCOPY mirrors and then unmounted the copies to preserve a snapshot of
the old ADSM database.

Well, the TSM upgrade went very smoothly.  Today, after a week of running TSM
4.1.2.0 with no problems, I stopped 'dsmserv', remounted the old DBCOPY/LOGCOPY
volumes, then restarted TSM 'dsmserv', expecting it to automatically sync the
old copy volumes to the new TSM DB/LOG primary volumes during startup.  I was
wrong - there was no automatic resyncing.  'dsmserv' came up fine, but the
DBCOPY and LOGCOPY volumes are still marked "off-line", and no 'sync' processes
are running.

I can't find any TSM commands to sync/enable DBCOPY/LOGCOPY volumes marked
"off-line", short of deleting/re-defining them.  Did I miss something, or is
that the only way TSM provides to bring an off-lined volume back online?

 -rsvp, thanks

Kent Monthei
GlaxoSmithKline R&D
CNT Data Recovery Services
<Prev in Thread] Current Thread [Next in Thread>
  • TSM 4.1.2.0 - Question : How can I force dsmserv to resync DB /DBCOPY and LOG/LOGCOPY mirror volumes ?, Kent J. Monthei <=