SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
Change retention policy on specific volumes
Author Message
Post Change retention policy on specific volumes 
Hi All,

I have been asked to move multiple volumes to another storage pool so that I can change the retention to no limit. I do not want to change all of the volumes on a node, only select volumes. I know that retention is determined by the management class and if you change the management class it rebinds on the next backup but I need to be able to change it on existing volumes without backing up again or changing it on all of the data. Is there any way to do this and if so, how can I accomplish this quickly. We were informed today and they want it by tomorrow. Thanks for the help.


Debbie Haberstroh
Server Administration

Post Change retention policy on specific volumes 
Data on specific volumes...
How do you know what is on those volumes?
Need more information...
Is this copy pool data?
Is it data for a single node and you know what is on it because of
collocation?

Dwight

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of
Haberstroh, Debbie (IT)
Sent: Thursday, July 31, 2008 1:58 PM
To: ADSM-L < at > VM.MARIST.EDU
Subject: [ADSM-L] Change retention policy on specific volumes

Hi All,

I have been asked to move multiple volumes to another storage pool so that I
can change the retention to no limit. I do not want to change all of the
volumes on a node, only select volumes. I know that retention is determined
by the management class and if you change the management class it rebinds on
the next backup but I need to be able to change it on existing volumes
without backing up again or changing it on all of the data. Is there any
way to do this and if so, how can I accomplish this quickly. We were
informed today and they want it by tomorrow. Thanks for the help.


Debbie Haberstroh
Server Administration

Post Change retention policy on specific volumes 
I think you mean volumes on your system, not TSM volumes. Without
running another backup, I don't believe you can change the retention on
specific volumes. If you change the retention policy in the management
class for the node, all of the data will be retained in that way. You
are correct: if you create a new management class with the desired
retention, then include those volumes requiring that retention in your
dsm.opt file, running another backup will rebind those volumes to the
new management class. That is the only way to be discrete to the volume
level.

Kelly Lipp
CTO
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
719-266-8777
www.storserver.com


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of
Dwight Cook
Sent: Thursday, July 31, 2008 1:05 PM
To: ADSM-L < at > VM.MARIST.EDU
Subject: Re: [ADSM-L] Change retention policy on specific volumes

Data on specific volumes...
How do you know what is on those volumes?
Need more information...
Is this copy pool data?
Is it data for a single node and you know what is on it because of
collocation?

Dwight

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of
Haberstroh, Debbie (IT)
Sent: Thursday, July 31, 2008 1:58 PM
To: ADSM-L < at > VM.MARIST.EDU
Subject: [ADSM-L] Change retention policy on specific volumes

Hi All,

I have been asked to move multiple volumes to another storage pool so
that I
can change the retention to no limit. I do not want to change all of
the
volumes on a node, only select volumes. I know that retention is
determined
by the management class and if you change the management class it
rebinds on
the next backup but I need to be able to change it on existing volumes
without backing up again or changing it on all of the data. Is there
any
way to do this and if so, how can I accomplish this quickly. We were
informed today and they want it by tomorrow. Thanks for the help.


Debbie Haberstroh
Server Administration

Post Change retention policy on specific volumes 
I mean actual tape volumes, not system volumes.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU]On Behalf Of
Kelly Lipp
Sent: Thursday, July 31, 2008 2:08 PM
To: ADSM-L < at > VM.MARIST.EDU
Subject: Re: [ADSM-L] Change retention policy on specific volumes


I think you mean volumes on your system, not TSM volumes. Without
running another backup, I don't believe you can change the retention on
specific volumes. If you change the retention policy in the management
class for the node, all of the data will be retained in that way. You
are correct: if you create a new management class with the desired
retention, then include those volumes requiring that retention in your
dsm.opt file, running another backup will rebind those volumes to the
new management class. That is the only way to be discrete to the volume
level.

Kelly Lipp
CTO
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
719-266-8777
www.storserver.com


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of
Dwight Cook
Sent: Thursday, July 31, 2008 1:05 PM
To: ADSM-L < at > VM.MARIST.EDU
Subject: Re: [ADSM-L] Change retention policy on specific volumes

Data on specific volumes...
How do you know what is on those volumes?
Need more information...
Is this copy pool data?
Is it data for a single node and you know what is on it because of
collocation?

Dwight

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of
Haberstroh, Debbie (IT)
Sent: Thursday, July 31, 2008 1:58 PM
To: ADSM-L < at > VM.MARIST.EDU
Subject: [ADSM-L] Change retention policy on specific volumes

Hi All,

I have been asked to move multiple volumes to another storage pool so
that I
can change the retention to no limit. I do not want to change all of
the
volumes on a node, only select volumes. I know that retention is
determined
by the management class and if you change the management class it
rebinds on
the next backup but I need to be able to change it on existing volumes
without backing up again or changing it on all of the data. Is there
any
way to do this and if so, how can I accomplish this quickly. We were
informed today and they want it by tomorrow. Thanks for the help.


Debbie Haberstroh
Server Administration

Post Change retention policy on specific volumes 
The specific volumes are determined by a SQL query, the tapes are in the primary tapepool. Multiple nodes are affected.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU]On Behalf Of
Dwight Cook
Sent: Thursday, July 31, 2008 2:05 PM
To: ADSM-L < at > VM.MARIST.EDU
Subject: Re: [ADSM-L] Change retention policy on specific volumes


Data on specific volumes...
How do you know what is on those volumes?
Need more information...
Is this copy pool data?
Is it data for a single node and you know what is on it because of
collocation?

Dwight

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of
Haberstroh, Debbie (IT)
Sent: Thursday, July 31, 2008 1:58 PM
To: ADSM-L < at > VM.MARIST.EDU
Subject: [ADSM-L] Change retention policy on specific volumes

Hi All,

I have been asked to move multiple volumes to another storage pool so that I
can change the retention to no limit. I do not want to change all of the
volumes on a node, only select volumes. I know that retention is determined
by the management class and if you change the management class it rebinds on
the next backup but I need to be able to change it on existing volumes
without backing up again or changing it on all of the data. Is there any
way to do this and if so, how can I accomplish this quickly. We were
informed today and they want it by tomorrow. Thanks for the help.


Debbie Haberstroh
Server Administration

Post Change retention policy on specific volumes 
Since data retention is at the data item level, you need to go back to that
to extend set things to "no limit".

I had to freeze some past data (only... no future data) so I renamed the
nodes to <existingname>_xxx (where your xxx can be something like
"frozen")
Build a domain such as outlined below... move your nodes that require their
data be frozen into that domain... then reregister the initial node name
again under their normal domain.
Since their existing management class won't really exist in this new domain,
it will all fall under the retention grace period.
To get that frozen data shifted around you can either:
1) use move nodedata to isolate it into a newly created storage pool
2) simply export the blah_xxx nodes (the unlimited domain gives you time to
perform the export without the required data expiring)
This all allows the node(s) to return to normal nightly processing while you
deal with the frozen data.


tsm: TSMSRV1>q domain unlimited f=d

Policy Domain Name: UNLIMITED
Activated Policy Set: STANDARD
Activation Date/Time: 04/30/2005 12:29:12
Days Since Activation: 1,188
Activated Default Mgmt Class: UNLIMITED
Number of Registered Nodes: 0
Description:
Backup Retention (Grace Period): 9,999
Archive Retention (Grace Period): 30,000
Last Update by (administrator): xxxxx
Last Update Date/Time: 04/30/2005 12:29:12
Managing profile:
Changes Pending: No
Active Data Pool List:

tsm: TSMSRV1>q copy unlimited

Policy Policy Mgmt Copy Versions
Versions Retain Retain
Domain Set Name Class Group Data
Data Extra Only
Name Name Name Exists
Deleted Versions Version
--------- --------- --------- --------- --------
-------- -------- -------
UNLIMITED ACTIVE UNLIMITED STANDARD No Limit No
Limit No Limit No Lim-

it
UNLIMITED STANDARD UNLIMITED STANDARD No Limit No
Limit No Limit No Lim-

it


tsm: TSMSRV1>q copy unlimited t=a

Policy Policy Mgmt Copy Retain
Domain Set Name Class Group Version
Name Name Name
--------- --------- --------- --------- --------
UNLIMITED ACTIVE UNLIMITED STANDARD No Limit
UNLIMITED STANDARD UNLIMITED STANDARD No Limit

tsm: TSMSRV1>

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of
Haberstroh, Debbie (IT)
Sent: Thursday, July 31, 2008 2:33 PM
To: ADSM-L < at > VM.MARIST.EDU
Subject: Re: [ADSM-L] Change retention policy on specific volumes

The specific volumes are determined by a SQL query, the tapes are in the
primary tapepool. Multiple nodes are affected.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU]On Behalf Of
Dwight Cook
Sent: Thursday, July 31, 2008 2:05 PM
To: ADSM-L < at > VM.MARIST.EDU
Subject: Re: [ADSM-L] Change retention policy on specific volumes


Data on specific volumes...
How do you know what is on those volumes?
Need more information...
Is this copy pool data?
Is it data for a single node and you know what is on it because of
collocation?

Dwight

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of
Haberstroh, Debbie (IT)
Sent: Thursday, July 31, 2008 1:58 PM
To: ADSM-L < at > VM.MARIST.EDU
Subject: [ADSM-L] Change retention policy on specific volumes

Hi All,

I have been asked to move multiple volumes to another storage pool so that I
can change the retention to no limit. I do not want to change all of the
volumes on a node, only select volumes. I know that retention is determined
by the management class and if you change the management class it rebinds on
the next backup but I need to be able to change it on existing volumes
without backing up again or changing it on all of the data. Is there any
way to do this and if so, how can I accomplish this quickly. We were
informed today and they want it by tomorrow. Thanks for the help.


Debbie Haberstroh
Server Administration

Post Change retention policy on specific volumes 
You can only change the retention of the management class. You don't
rebind if the files are already bound to the management class you change.
(You don't change retention by volume)
If you can change the retention by the node, then you can move the nodes
to a new domain with the same name management classes. Than just change
the expiration of those management classes

Regards,
Shawn
________________________________________________
Shawn Drew





Internet
HABERDE < at > VOUGHTAIRCRAFT.COM

Sent by: ADSM-L < at > VM.MARIST.EDU
07/31/2008 03:32 PM
Please respond to
ADSM-L < at > VM.MARIST.EDU


To
ADSM-L
cc

Subject
Re: [ADSM-L] Change retention policy on specific volumes





The specific volumes are determined by a SQL query, the tapes are in the
primary tapepool. Multiple nodes are affected.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU]On Behalf Of
Dwight Cook
Sent: Thursday, July 31, 2008 2:05 PM
To: ADSM-L < at > VM.MARIST.EDU
Subject: Re: [ADSM-L] Change retention policy on specific volumes


Data on specific volumes...
How do you know what is on those volumes?
Need more information...
Is this copy pool data?
Is it data for a single node and you know what is on it because of
collocation?

Dwight

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of
Haberstroh, Debbie (IT)
Sent: Thursday, July 31, 2008 1:58 PM
To: ADSM-L < at > VM.MARIST.EDU
Subject: [ADSM-L] Change retention policy on specific volumes

Hi All,

I have been asked to move multiple volumes to another storage pool so that
I
can change the retention to no limit. I do not want to change all of the
volumes on a node, only select volumes. I know that retention is
determined
by the management class and if you change the management class it rebinds
on
the next backup but I need to be able to change it on existing volumes
without backing up again or changing it on all of the data. Is there any
way to do this and if so, how can I accomplish this quickly. We were
informed today and they want it by tomorrow. Thanks for the help.


Debbie Haberstroh
Server Administration


This message and any attachments (the "message") is intended solely for
the addressees and is confidential. If you receive this message in error,
please delete it and immediately notify the sender. Any use not in accord
with its purpose, any dissemination or disclosure, either whole or partial,
is prohibited except formal approval. The internet can not guarantee the
integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will)
not therefore be liable for the message if modified. Please note that certain
functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.

Post Change retention policy on specific volumes 
Thanks all.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU]On Behalf Of
Dwight Cook
Sent: Thursday, July 31, 2008 2:47 PM
To: ADSM-L < at > VM.MARIST.EDU
Subject: Re: [ADSM-L] Change retention policy on specific volumes


Since data retention is at the data item level, you need to go back to that
to extend set things to "no limit".

I had to freeze some past data (only... no future data) so I renamed the
nodes to <existingname>_xxx (where your xxx can be something like
"frozen")
Build a domain such as outlined below... move your nodes that require their
data be frozen into that domain... then reregister the initial node name
again under their normal domain.
Since their existing management class won't really exist in this new domain,
it will all fall under the retention grace period.
To get that frozen data shifted around you can either:
1) use move nodedata to isolate it into a newly created storage pool
2) simply export the blah_xxx nodes (the unlimited domain gives you time to
perform the export without the required data expiring)
This all allows the node(s) to return to normal nightly processing while you
deal with the frozen data.


tsm: TSMSRV1>q domain unlimited f=d

Policy Domain Name: UNLIMITED
Activated Policy Set: STANDARD
Activation Date/Time: 04/30/2005 12:29:12
Days Since Activation: 1,188
Activated Default Mgmt Class: UNLIMITED
Number of Registered Nodes: 0
Description:
Backup Retention (Grace Period): 9,999
Archive Retention (Grace Period): 30,000
Last Update by (administrator): xxxxx
Last Update Date/Time: 04/30/2005 12:29:12
Managing profile:
Changes Pending: No
Active Data Pool List:

tsm: TSMSRV1>q copy unlimited

Policy Policy Mgmt Copy Versions
Versions Retain Retain
Domain Set Name Class Group Data
Data Extra Only
Name Name Name Exists
Deleted Versions Version
--------- --------- --------- --------- --------
-------- -------- -------
UNLIMITED ACTIVE UNLIMITED STANDARD No Limit No
Limit No Limit No Lim-

it
UNLIMITED STANDARD UNLIMITED STANDARD No Limit No
Limit No Limit No Lim-

it


tsm: TSMSRV1>q copy unlimited t=a

Policy Policy Mgmt Copy Retain
Domain Set Name Class Group Version
Name Name Name
--------- --------- --------- --------- --------
UNLIMITED ACTIVE UNLIMITED STANDARD No Limit
UNLIMITED STANDARD UNLIMITED STANDARD No Limit

tsm: TSMSRV1>

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of
Haberstroh, Debbie (IT)
Sent: Thursday, July 31, 2008 2:33 PM
To: ADSM-L < at > VM.MARIST.EDU
Subject: Re: [ADSM-L] Change retention policy on specific volumes

The specific volumes are determined by a SQL query, the tapes are in the
primary tapepool. Multiple nodes are affected.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU]On Behalf Of
Dwight Cook
Sent: Thursday, July 31, 2008 2:05 PM
To: ADSM-L < at > VM.MARIST.EDU
Subject: Re: [ADSM-L] Change retention policy on specific volumes


Data on specific volumes...
How do you know what is on those volumes?
Need more information...
Is this copy pool data?
Is it data for a single node and you know what is on it because of
collocation?

Dwight

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L < at > VM.MARIST.EDU] On Behalf Of
Haberstroh, Debbie (IT)
Sent: Thursday, July 31, 2008 1:58 PM
To: ADSM-L < at > VM.MARIST.EDU
Subject: [ADSM-L] Change retention policy on specific volumes

Hi All,

I have been asked to move multiple volumes to another storage pool so that I
can change the retention to no limit. I do not want to change all of the
volumes on a node, only select volumes. I know that retention is determined
by the management class and if you change the management class it rebinds on
the next backup but I need to be able to change it on existing volumes
without backing up again or changing it on all of the data. Is there any
way to do this and if so, how can I accomplish this quickly. We were
informed today and they want it by tomorrow. Thanks for the help.


Debbie Haberstroh
Server Administration

Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB