Now that NT management class is no longer part of the active policy set,
files will no longer be bound to that management class.
The active policy set is simply a copy of the policy set you activate.
Thus since SQLBACK was activated, management class NT will not be part of
the active policy set since management class NT is not a part of SQLBACK.
In general, I see little use for multipe (non-active) policy sets, so
unless you have a compelling reason to use them, stick with one policy set
(say, NT). If you want new management classes, just define them to NT,
then reactivate the NT policy set to use the new management classes. Note
that you can define more than one management class to a policy set. (Note:
one possible use for multiple policy sets would be if you wanted to copy,
say, policy set NT to a new policy set, NT_BACK_20070115, then modify NT.
In this way, you have a backup of the original NT policy set, in case the
modified policy set gets so messed up that you can't figure out how to
revert it. Though you can also simply copy the ACTIVE policy set back to
NT also, if you want to revert to the active configuration.)
I think I missed earlier what you were going after. So what you need to do
is:
(a) activate the NT policy set (right away).
(b) define the SQLBACK management class and backup copy group to the NT
policy set.
(c) activate the NT policy set. Now you should have both NT and SQLBACK
management classes appearing in the ACTIVE policy set when you do Q MG and
Q CO.
(d) I also recommend reviewing the TSM Admin Guide information on how
policy sets work.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]
IBM Tivoli Storage Manager support web page:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
"ADSM: Dist Stor Manager" <[email protected]> wrote on 01/15/2007
07:00:41 AM:
I had issued the command you are referring to previously
"act pol nt sqlback" and got the results below. That then takes
the NT management class out of the active policy set and makes
SQLBACK the default in the active policy set. How will
that affect backed up files that I want to be kept bound to the
NT management class.
tsm: TSM533>q dom nt
Policy Activated Activated Number of Description
Domain Policy Default Registered
Name Set Mgmt Nodes
Class
--------- --------- --------- ----------
------------------------
NT SQLBACK SQLBACK 69 NT Servers
tsm: TSM533>
tsm: TSM533>q pol nt
Policy Policy Default Description
Domain Set Name Mgmt
Name Class
Name
--------- --------- --------- ------------------------
NT ACTIVE SQLBACK SQL Backup
NT NT NT NT Servers
NT SQLBACK SQLBACK SQL Backup
tsm: TSM533>
tsm: TSM533>q mg nt
Policy Policy Mgmt Default Description
Domain Set Name Class Mgmt
Name Name Class ?
--------- --------- --------- ---------
------------------------
NT ACTIVE SQLBACK Yes SQL Backups
NT NT NT Yes NT Servers
NT SQLBACK SQLBACK Yes SQL Backups
tsm: TSM533>
tsm: TSM533>q co nt
Policy Policy Mgmt Copy Versions Versions Retain
Retain
Domain Set Name Class Group Data Data Extra Only
Name Name Name Exists Deleted Versions
Version
--------- --------- --------- --------- -------- -------- --------
-------
NT ACTIVE SQLBACK STANDARD 2 1 2 2
NT NT NT STANDARD 4 2 365 365
NT SQLBACK SQLBACK STANDARD 2 1 2 2
----- Original Message -----
From: "Andrew Raibeck" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, January 15, 2007 8:47 AM
Subject: Re: Non default management class not working
> In your Q MG and Q CO output, notice that management class SQLBACK is
not
> shown in the ACTIVE policy set. You need to run ACTIVATE POLICYSET.
>
> Regards,
>
> Andy
>
> Andy Raibeck
> IBM Software Group
> Tivoli Storage Manager Client Development
> Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
> Internet e-mail: [EMAIL PROTECTED]
>
> IBM Tivoli Storage Manager support web page:
> http://www.ibm.
com/software/sysmgmt/products/support/IBMTivoliStorageManager.html
>
> The only dumb question is the one that goes unasked.
> The command line is your friend.
> "Good enough" is the enemy of excellence.
>
> "ADSM: Dist Stor Manager" <[email protected]> wrote on 01/15/2007
> 06:41:15 AM:
>
>> Have a non default management class created and assigned to a
specific
>> server directory. The deleted host .bak files are not getting removed
> from
>> TSM backups even with these settings.
>>
>> Include "d:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP\...\*.bak"
>> sqlback
>>
>> tsm: TSM533>q dom nt
>>
>> Policy Activated Activated Number of Description
>> Domain Policy Default Registered
>> Name Set Mgmt Nodes
>> Class
>> --------- --------- --------- ----------
> ------------------------
>> NT NT NT 69 NT Servers
>>
>> tsm: TSM533>q pol nt
>>
>> Policy Policy Default Description
>> Domain Set Name Mgmt
>> Name Class
>> Name
>> --------- --------- --------- ------------------------
>> NT ACTIVE NT NT Servers
>> NT NT NT NT Servers
>> NT SQLBACK SQLBACK SQL Backup Folders
>>
>> tsm: TSM533>q mg nt
>>
>> Policy Policy Mgmt Default Description
>> Domain Set Name Class Mgmt
>> Name Name Class ?
>> --------- --------- --------- ---------
> ------------------------
>> NT ACTIVE NT Yes NT Servers
>> NT NT NT Yes NT Servers
>> NT SQLBACK SQLBACK Yes SQL Backup
Foldlers
>>
>> tsm: TSM533>q co nt
>>
>> Policy Policy Mgmt Copy Versions Versions Retain
> Retain
>> Domain Set Name Class Group Data Data Extra
Only
>> Name Name Name Exists Deleted Versions
> Version
>> --------- --------- --------- --------- -------- -------- --------
> -------
>> NT ACTIVE NT STANDARD 4 2 365
365
>> NT NT NT STANDARD 4 2 365
365
>> NT SQLBACK SQLBACK STANDARD 1 1 2 2
>>
>>
>> Tim Brown
>> Systems Specialist
>> Central Hudson Gas & Electric
>> 284 South Ave
>> Poughkeepsie, NY 12601
>> Email: [EMAIL PROTECTED]
>> Phone: 845-486-5643
>> Fax: 845-486-5921
>> Cell: 845-235-4255
>
