ADSM-L

TDP for MS SQL Version 2 - Changing Management Classes

2001-08-23 08:48:52
Subject: TDP for MS SQL Version 2 - Changing Management Classes
From: William Degli-Angeli <billybob AT US.IBM DOT COM>
Date: Thu, 23 Aug 2001 08:49:40 -0400
If you have configured the management classes of your meta and data objects
with different Copy Destinations, as suggested in the "Installation and
User's
Guide" - "TSM Policy Requirements and Recommendations", you should not
change
your management classes unless the new management classes of BOTH the meta
and
data objects have the SAME Copy Destinations in the backup copy group.

A bug has been identified (APAR # IC31372 ) in Tivoli Data Protection for
Microsoft SQL Server
Version 2 that may cause a loss of backup data when the management classes
of
your meta OR data objects is changed and the NEW management classes for the
meta
and data objects have different Copy Destinations.

Until a fix for this APAR is available, the problem can be avoided by
ensuring that the meta and
data objects go to the same storage pool (they have the same copy
destination) if it is necessary
to change a current management class assignment.

We will post this forum again when a fix for this APAR is available.

If you need to change a management class used by TDP for SQL and would like
assistance with the specific steps to avoid this problem, please contact
Tivoli support for further instructions.


    Thanks,
        Bill

William Degli-Angeli
IGS TDP Development
Endicott, NY
(607) 752-6749
TieLine: 852-6749
Internet: BillyBob AT US.IBM DOT Com
<Prev in Thread] Current Thread [Next in Thread>
  • TDP for MS SQL Version 2 - Changing Management Classes, William Degli-Angeli <=