Right, I think I have the archiving process clear in my own mind now. I may be wrong but that's purely my own fault ;-)
The next query is expiration. Ideally, I'd like to immediately expire the files which have been archived, to free up library space. I currently retain 3 versions up to 100 days and the final version up to 365 days. I can set all of those values temporarily nice and low but as I understand it, the database objects are only finally removed by the EXPIRE INVENTORY process at the server end. This would presumably remove all old versions, not just those I have archived. Is there a way around this, am I simply wrong, or will I just have to wait for the normal expiration process timeout? Thanks again Angus -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Larry Clark Sent: 19 October 2007 11:59 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Archiving basic queries Yes, if you use the -deletefiles=yes, they will be removed from the client when you run the archive. Then on the next backup, TSM will update its database entries the same as if you simply deleted the files without an archive. Then on the next expire inventory, your backup rules will be applied. They will be expired from the backup primary and copypool pools per your rules. You might want to check your defs on your (default or explicit management class you select for the archives) archive pool to verify how long your files will be retained once archived. ----- Original Message ----- From: "Angus Macdonald" <[EMAIL PROTECTED]> To: <ADSM-L@VM.MARIST.EDU> Sent: Friday, October 19, 2007 5:22 AM Subject: Re: [ADSM-L] Archiving basic queries Thanks for that. Makes it a lot clearer. So, if I create a filelist of files I want to archive and archive them with the -deletefiles option, they will be gone from the source, correct? If I then run an expire with the same filelist, the files will be expired from the Tivoli primary storage pools but not the archive, thereby freeing up library space (once the archive tapes are safely removed), also correct? I hope so - the job might actually be fairly simple that way! Thanks again Angus Gallai'r e-bost yma gynnwys gwybodaeth gyfrinachol a/neu ddeunydd hawlfraint. Os ydych chi'n meddwl eich bod wedi derbyn yr e-bost yma drwy gamgymeriad rydym yn ymddiheuro am hyn; peidiwch os gwelwch yn dda â datgelu, anfon ymlaen, printio, copïo na dosbarthu gwybodaeth yn yr e-bost yma na gweithredu mewn unrhyw fodd drwy ddibynnu ar ei gynnwys: gwaherddir gwneud hynny'n gyfan gwbl a gallai fod yn anghyfreithlon. Rhowch wybod i'r anfonwr fod y neges yma wedi mynd ar goll cyn ei dileu. Mae unrhyw safbwynt neu farn a gyflwynir yn eiddo i'r awdur ac nid ydynt o anghenraid yn cynrychioli safbwynt neu farn Ymddiriedolaeth GIG Gogledd Orllewin Cymru. Gallai cynnwys yr e-bost yma gael ei ddatgelu i'r cyhoedd o dan Gôd Bod yn Agored y GIG neu Ddeddf Rhyddid Gwybodaeth 2000. Nid oes modd gwarantu cyfrinachedd y neges ac unrhyw ateb. Bydd y neges yma ac unrhyw ffeiliau cysylltiedig wedi cael eu gwirio gan feddalwedd canfod firws cyn eu trosglwyddo. Ond rhaid i'r sawl sy'n derbyn wirio rhag firws ei hun cyn agor unrhyw ymgysylltiad. Nid yw'r Ymddiriedolaeth yn derbyn unrhyw gyfrifoldeb am unrhyw golled neu niwed a allai gael ei achosi gan firws meddalwedd. This e-mail may contain confidential information and/or copyright material. If you believe that you have received this e-mail in error please accept our apologies; please do not disclose, forward, print, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Please inform the sender that this message has gone astray before deleting it. Any views or opinions presented are to be understood as those of the author and do not necessarily represent those of the North West Wales NHS Trust. The contents of this e-mail may be subject to public disclosure under the NHS Code of Openness or the Freedom of Information Act 2000. The confidentiality of the message and any reply cannot be guaranteed. This message and any attached files will have been checked with virus detection software before transmission. However, recipients must carry out their own virus checks before opening any attachment. The Trust accepts no liability for any loss or damage, which may be caused by software viruses.