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:[EMAIL PROTECTED] 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 -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Henrik Wahlstedt Sent: Donnerstag, 18. Juli 2002 11:55 To: [EMAIL PROTECTED] Subject: Re: Expire data on a server that doesnt exist any longer. Hi, What I´m trying to do is to get rid of xyz´s extra version since that is a node that doesnt exist anymore. And let the node expire away. I dont want to delete the filespace. //Henrik Daniel Sparrman <daniel.sparrman To: [EMAIL PROTECTED] @EXIST.SE> cc: (bcc: Henrik Wahlstedt) Sent by: "ADSM: Subject: Re: Expire data on a server that doesnt exist any longer. Dist Stor Manager" <[EMAIL PROTECTED] T.EDU> 2002-07-18 11:18 Please respond to "ADSM: Dist Stor Manager" Hi The q fi xyz doesn't show data stored on the backupserver, only the filespaces, and how much each filespace is utilized. Try running a q occ xyz, this will show you how much space each filespace (sto-ln02\e$, xyz\c$ and xyz\e$) takes up on the backupserver. The table you're showing below, doesn't show how many versions, or how much data you have in your backupsystem. Best Regards Daniel Sparrman ----------------------------------- Daniel Sparrman Exist i Stockholm AB Propellervägen 6B 183 62 HÄGERNÄS Växel: 08 - 754 98 00 Mobil: 070 - 399 27 51 Henrik Wahlstedt <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 2002-07-18 11:05 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: Re: Expire data on a server that doesnt exist any longer. Thanks for your answers. It seems like I miss something here. I copied the domain and updated/validated/activated the policy set and updated the node. When I do a 'dsmc incr' with a modified dsm.opt (NodeName xyz and Exclude E:\...\*) on a different node, STO-LN02, I only backup STO-LN02´s filespace and doesn´t trim out my extra versions on xyz. If I do a 'q fi xyz' it looks like this: tsm: STO-W03>q fi xyz Node Name Filespace Platform Filespace Capacity Pct Name Type (MB) Util ------------------------------ ----------- -------- --------- -------- ----- xyz \\xyz\c$ WinNT NTFS 4,044.1 60.9 xyz \\xyz\e$ WinNT NTFS 42,385.0 68.8 xyz \\sto-ln02\e$ WinNT NTFS 34,719.8 29.8 tsm: STO-W03> What can I and should do to trim out xyz´s extra versions? rgs Henrik Zlatko Krastev To: [EMAIL PROTECTED] <acit@ATTGLOB cc: (bcc: Henrik Wahlstedt) AL.NET> Subject: Re: Expire data on a server that doesnt exist any longer. Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED] RIST.EDU> 2002-07-12 00:48 Please respond to "ADSM: Dist Stor Manager" then after expiration takes place update the node back to original domain and delete the copy. Zlatko Krastev IT Consultant Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: Expire data on a server that doesnt exist any longer. To trim out the extra versions, I would copy the domain the node is now in to a new domain. Update the copygroups to these values - verexists 1 verdeleted 1 retextra 0 retonly 9999 Activate the poilcyset and then update the node to be in the new domain. The next expiration will trim all the inactive versions except for the last version of a deleted file. Hope this helps, Bill At 10:17 AM 7/11/2002, you wrote: >> If I have backup of a server which is out of production. What can I do and >> how, if I want to expire all extra backup copies (versions data exist) >> except the last backup (versions data deleted)? >> I can change mgmtclass but I still have to do a backup to rebind my files. >> If I use a client and log on with 'dsmc -virtualnodename=xyz' and exclude >> E:\...\* , what happens then? Will it expire xyz´s E:\ files or the client >> node E:\ files? > >A dsmc command as such won't affect file retentions at all. You will need >to run an incremental backup. > >A 'dsmc inc' with the exclude statement and virtualnodename option shown >would affect files from xyz. However, that approach would make me very >nervous about the possibility of an incremental backup with the exclude >statement but not the option. I would be inclined to copy the options >file, put the special exclude statement and a 'nodename xyz' statement in >the copy, and run dsmc with an 'optfile' option telling it to use the >copy. > >It is easier to describe the effect of a backup that excludes everything >on the E drive in terms of what happens to backups of a file than in terms >of what happens to backups of an entire population of files. Consider an >active backup of a file that was on xyz's E drive. A backup with the >exclude statement described above would cause this backup to switch to >inactive status. If the number of versions of the file was greater than >the verdeleted parameter of the relevant copy group the next 'expire >inventory' on the TSM server would delete enough of the oldest versions >to get the number of versions down to the verdeleted parameter value. >If there was still more than one version of the file subsequent 'expire >inventory' operations would remove each extra version after it reached >the age limit set by the retextra parameter. Eventually, 'expire >inventory' would remove the last backup version when it passed the age >limit set by the retonly parameter. ---------- Bill Colwell C. S. Draper Lab Cambridge Ma. ------------------------------------------------------------------- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you. ------------------------------------------------------------------- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you.
