We are actually saying the same thing...
I don't have deactivating and expiration confused at all.
The point I was trying to say , but maybe not that clearly, is that once
file in inactivated (removed from client) regardless of retention date.
for example lets say its 1 month.
If you were stop exp
On Nov 6, 2008, at 4:05 AM, Craig TSM wrote:
Interesting, I am aware of the deactivation time you mentioned.
Now its been a while but from what I remember changing the policy
retention either by changing current or moving node to another, did
not
change this deactivation date, remembering this
Understand, though, what the actual TSM handling is, to fully
appreciate what happens with stored objects. Files don't have
expiration dates in the TSM database: they have instantiation
datestamps and deactivation datestamps. The deactivation datestamp
plus the retention period determines the ex
On Nov 4, 2008, at 3:07 AM, Craig TSM wrote:
If you have backed a file up the expiration date _cannot_ be changed
if
file is already deleted !!! even if you associate with another Policy
with different retentions
Understand, though, what the actual TSM handling is, to fully
appreciate what hap
ovember 02, 2008 10:23 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] How to stop data from expiring
Hello
I would like to know how to stop data from a specific filespace within a
node from being expired based on that node's copygroup membership
Eg lets say I have a node called ABC against Co
@VM.MARIST.EDU
Subject: Re: [ADSM-L] How to stop data from expiring
On Nov 2, 2008, at 11:23 PM, Cheung, Richard wrote:
> ...
> Today is Monday.. I have just been told that I need to keep the
> backup
> for /etc from Saturday until further notice due to a business
> requirement
> .
: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Cheung, Richard
Sent: Sunday, November 02, 2008 10:23 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] How to stop data from expiring
Hello
I would like to know how to stop data from a specific filespace within a
node from being exp
On Nov 2, 2008, at 11:23 PM, Cheung, Richard wrote:
...
Today is Monday.. I have just been told that I need to keep the
backup
for /etc from Saturday until further notice due to a business
requirement
...
It sounds like they want to freeze a copy of what was on that file
system Saturday.
On 3 nov 2008, at 09:11, Michael Green wrote:
Another way maybe is to create an additional mgmt class with longer
retention policy and to rebind that FS to the new mgmtclass using
include statement.
which might not be feasible. since data may already have been deleted
from the node and 'until
Another way maybe is to create an additional mgmt class with longer
retention policy and to rebind that FS to the new mgmtclass using
include statement.
On Mon, Nov 3, 2008 at 9:43 AM, Remco Post <[EMAIL PROTECTED]> wrote:
> Hi,
>
>
> look into backupsets and node exports.
>
--
Warm regards,
Mich
Hi,
look into backupsets and node exports.
On 3 nov 2008, at 05:23, Cheung, Richard wrote:
Hello
I would like to know how to stop data from a specific filespace
within a
node from being expired based on that node's copygroup membership
Eg lets say I have a node called ABC against CopyGroup
Hello
I would like to know how to stop data from a specific filespace within a
node from being expired based on that node's copygroup membership
Eg lets say I have a node called ABC against CopyGroup called 'Nightly'
which says keep 7 versions.
Within the node ABC it has paths
/home
/etc
/bin
12 matches
Mail list logo
