Re: Expire data on a server that doesnt exist any longer.
2002-07-18 07:20:05
Subject: |
Re: Expire data on a server that doesnt exist any longer. |
From: |
Michael Bartl <michael.bartl AT CW DOT COM> |
Date: |
Thu, 18 Jul 2002 13:18:18 +0200 |
Henrik,
expire inventory throws out versions that were inactive longer than the
retention period defined in the domain/mgmtclass the node is
defined in.
When you want to change mgmtclass in your options for an object there is only a
rebind possible for active objects at the next
incremental backup session. To work around this restriction you can set up a
new policy domain with only a default mgmtclass and
copygroup. Move your node into this domain and the rebind happens.
It is not possible to update an object from active to inactive state without a
backup session of the existing filesystem. Only
objects in filesystems that exist and get backed up are updated. So when you
want a whole filespace to expire n days after the last
backup, you have to delete it manually after n days.
To see the results of expiration be sure to do "expire inventory" followed by
"aud lic" before "query occupancy"/"q auditocc".
Regards,
Michael
--
Michael Bartl, Dipl. Inform. (FH) mailto:michael.bartl AT cw DOT com
Michael Bartl, Dipl. Inform. (FH) mailto:michael.bartl AT cw DOT com
Backup Services, IT Ops Germany/Austria Tel: +49-89-92699-806
Cable & Wireless Deutschland GmbH. Fax: +49-89-92699-302
Landsberger Str. 155, D-80687 Muenchen http://www.cw.com/de
|
|
|