Re: Archiving basic queries
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.
Re: Archiving basic queries
You can execute an expire inventory at anytime It sounds like you are in a pinch for library space. Maybe the better thing to obtain space in the tape library more quickly would be to see how many volumes would be freed if you dropped your reclamation value on the storage pool(s) that occupy the library. Those would be triggered immediately. - Original Message - From: Angus Macdonald [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 4:27 AM Subject: Re: [ADSM-L] Archiving basic queries 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,
Re: Archiving basic queries
Yes, library space is threatening to become an issue in the near future so I want to do some housekeeping. I already run a fairly agressive reclamation scheme so there aren't any underused tapes around. If I drop my retention values to 0, say, and run EXPIRE INVENTORY, I'm guessing I'll expire my archived files plus old versions of current, unarchived files. That's not something that'll make me popular! I'm not that short of library space at the moment so perhaps I'll just archive anything that hasn't been accessed in the last couple of years and wait for the database to catch up. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Larry Clark Sent: 22 October 2007 12:16 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Archiving basic queries You can execute an expire inventory at anytime It sounds like you are in a pinch for library space. Maybe the better thing to obtain space in the tape library more quickly would be to see how many volumes would be freed if you dropped your reclamation value on the storage pool(s) that occupy the library. Those would be triggered immediately. - Original Message - From: Angus Macdonald [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 4:27 AM Subject: Re: [ADSM-L] Archiving basic queries 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
Re: Archiving basic queries
On Oct 22, 2007, at 5:27 AM, Angus Macdonald wrote: ... 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? I think we're all puzzled as to why you would have bothered archiving files which you could have simply deleted from the file system, to achieve the same effect? You need to dig into the B/A client manual, the chapter Archiving and retrieving your data, which describes all the aspects and factors of file archiving - including deleting archive data. You need a solid grounding in the area that you are pursuing, in order to make best use of it. Going at it piecemeal is not a good approach when dealing with data retention regimens. Richard Sims http://people.bu.edu/rbs
Re: Archiving basic queries
I may not be describing it very well ;-) I have lots of old, unaccessed files that need to be retained indefinitely. To free up library space I want to archive them to tape and delete from the fileservers. It would be nice if I could remove the Tivoli database entries for these files to free up the library sooner rather than later. I know how to select and archive only those files with a last accessed date earlier than some arbitrary date in the past. I was interested in the possibility of expiring only those files and not others from Tivoli afterwards. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Richard Sims Sent: 22 October 2007 12:34 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Archiving basic queries On Oct 22, 2007, at 5:27 AM, Angus Macdonald wrote: ... 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? I think we're all puzzled as to why you would have bothered archiving files which you could have simply deleted from the file system, to achieve the same effect? You need to dig into the B/A client manual, the chapter Archiving and retrieving your data, which describes all the aspects and factors of file archiving - including deleting archive data. You need a solid grounding in the area that you are pursuing, in order to make best use of it. Going at it piecemeal is not a good approach when dealing with data retention regimens. Richard Sims http://people.bu.edu/rbs 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.
Re: Archiving basic queries
Have you considered creating a separate managment class with its own archive pool, archive/deleteing your files to that, then checking out those volumes and storing them on a shelf someplace? - Original Message - From: Angus Macdonald [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 7:41 AM Subject: Re: [ADSM-L] Archiving basic queries I may not be describing it very well ;-) I have lots of old, unaccessed files that need to be retained indefinitely. To free up library space I want to archive them to tape and delete from the fileservers. It would be nice if I could remove the Tivoli database entries for these files to free up the library sooner rather than later. I know how to select and archive only those files with a last accessed date earlier than some arbitrary date in the past. I was interested in the possibility of expiring only those files and not others from Tivoli afterwards. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Richard Sims Sent: 22 October 2007 12:34 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Archiving basic queries On Oct 22, 2007, at 5:27 AM, Angus Macdonald wrote: ... 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? I think we're all puzzled as to why you would have bothered archiving files which you could have simply deleted from the file system, to achieve the same effect? You need to dig into the B/A client manual, the chapter Archiving and retrieving your data, which describes all the aspects and factors of file archiving - including deleting archive data. You need a solid grounding in the area that you are pursuing, in order to make best use of it. Going at it piecemeal is not a good approach when dealing with data retention regimens. Richard Sims http://people.bu.edu/rbs 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.
Re: Archiving basic queries
That's the plan. I have an archiving storage pool setup and ready, although not a separate management class. The bit I'm working on is getting the existing backups of the files I'm archiving, out of the existing main storage pool. I can then reclaim the main storage pool tapes and regain a lot of library space. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Larry Clark Sent: 22 October 2007 13:49 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Archiving basic queries Have you considered creating a separate managment class with its own archive pool, archive/deleteing your files to that, then checking out those volumes and storing them on a shelf someplace? - Original Message - From: Angus Macdonald [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 7:41 AM Subject: Re: [ADSM-L] Archiving basic queries I may not be describing it very well ;-) I have lots of old, unaccessed files that need to be retained indefinitely. To free up library space I want to archive them to tape and delete from the fileservers. It would be nice if I could remove the Tivoli database entries for these files to free up the library sooner rather than later. I know how to select and archive only those files with a last accessed date earlier than some arbitrary date in the past. I was interested in the possibility of expiring only those files and not others from Tivoli afterwards. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Richard Sims Sent: 22 October 2007 12:34 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Archiving basic queries On Oct 22, 2007, at 5:27 AM, Angus Macdonald wrote: ... 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? I think we're all puzzled as to why you would have bothered archiving files which you could have simply deleted from the file system, to achieve the same effect? You need to dig into the B/A client manual, the chapter Archiving and retrieving your data, which describes all the aspects and factors of file archiving - including deleting archive data. You need a solid grounding in the area that you are pursuing, in order to make best use of it. Going at it piecemeal is not a good approach when dealing with data retention regimens. Richard Sims http://people.bu.edu/rbs 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
Re: Archiving basic queries
May I suggest something ? I had to deal with a problem like that, involving externalization of datas, for legal archiving. I made a specific node, specific mgmt class and archive datas like that, then export node to deal with externalization of cartridges. I keep node definition but I had deleted filespaces under it and freed db space like that. Data's are on export cartridge. It is easy to retrieve it with an import node dates=relative. Regards, Pierre -Message d'origine- De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De la part de Angus Macdonald Envoyé : lundi 22 octobre 2007 15:02 À : ADSM-L@VM.MARIST.EDU Objet : Re: [ADSM-L] Archiving basic queries That's the plan. I have an archiving storage pool setup and ready, although not a separate management class. The bit I'm working on is getting the existing backups of the files I'm archiving, out of the existing main storage pool. I can then reclaim the main storage pool tapes and regain a lot of library space. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Larry Clark Sent: 22 October 2007 13:49 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Archiving basic queries Have you considered creating a separate managment class with its own archive pool, archive/deleteing your files to that, then checking out those volumes and storing them on a shelf someplace? - Original Message - From: Angus Macdonald [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 7:41 AM Subject: Re: [ADSM-L] Archiving basic queries I may not be describing it very well ;-) I have lots of old, unaccessed files that need to be retained indefinitely. To free up library space I want to archive them to tape and delete from the fileservers. It would be nice if I could remove the Tivoli database entries for these files to free up the library sooner rather than later. I know how to select and archive only those files with a last accessed date earlier than some arbitrary date in the past. I was interested in the possibility of expiring only those files and not others from Tivoli afterwards. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Richard Sims Sent: 22 October 2007 12:34 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Archiving basic queries On Oct 22, 2007, at 5:27 AM, Angus Macdonald wrote: ... 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? I think we're all puzzled as to why you would have bothered archiving files which you could have simply deleted from the file system, to achieve the same effect? You need to dig into the B/A client manual, the chapter Archiving and retrieving your data, which describes all the aspects and factors of file archiving - including deleting archive data. You need a solid grounding in the area that you are pursuing, in order to make best use of it. Going at it piecemeal is not a good approach when dealing with data retention regimens. Richard Sims http://people.bu.edu/rbs 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
Re: Archiving basic queries
In my case that would involve moving all the files to be archived to a different server and backup the server en-masse. Not out of the question but also not something I relish. Maybe I should just use Veritas! -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of CAYE PIERRE Sent: 22 October 2007 14:12 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Archiving basic queries May I suggest something ? I had to deal with a problem like that, involving externalization of datas, for legal archiving. I made a specific node, specific mgmt class and archive datas like that, then export node to deal with externalization of cartridges. I keep node definition but I had deleted filespaces under it and freed db space like that. Data's are on export cartridge. It is easy to retrieve it with an import node dates=relative. Regards, Pierre -Message d'origine- De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De la part de Angus Macdonald Envoyé : lundi 22 octobre 2007 15:02 À : ADSM-L@VM.MARIST.EDU Objet : Re: [ADSM-L] Archiving basic queries That's the plan. I have an archiving storage pool setup and ready, although not a separate management class. The bit I'm working on is getting the existing backups of the files I'm archiving, out of the existing main storage pool. I can then reclaim the main storage pool tapes and regain a lot of library space. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Larry Clark Sent: 22 October 2007 13:49 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Archiving basic queries Have you considered creating a separate managment class with its own archive pool, archive/deleteing your files to that, then checking out those volumes and storing them on a shelf someplace? - Original Message - From: Angus Macdonald [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 7:41 AM Subject: Re: [ADSM-L] Archiving basic queries I may not be describing it very well ;-) I have lots of old, unaccessed files that need to be retained indefinitely. To free up library space I want to archive them to tape and delete from the fileservers. It would be nice if I could remove the Tivoli database entries for these files to free up the library sooner rather than later. I know how to select and archive only those files with a last accessed date earlier than some arbitrary date in the past. I was interested in the possibility of expiring only those files and not others from Tivoli afterwards. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Richard Sims Sent: 22 October 2007 12:34 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Archiving basic queries On Oct 22, 2007, at 5:27 AM, Angus Macdonald wrote: ... 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? I think we're all puzzled as to why you would have bothered archiving files which you could have simply deleted from the file system, to achieve the same effect? You need to dig into the B/A client manual, the chapter Archiving and retrieving your data, which describes all the aspects and factors of file archiving - including deleting archive data. You need a solid grounding in the area that you are pursuing, in order to make best use of it. Going at it piecemeal is not a good approach when dealing with data retention regimens. Richard Sims http://people.bu.edu/rbs 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
Re: Archiving basic queries
Why that ? It is possible to define system and option files for that purpose and to deal with another node on the same platform. Therefore you just have to build inclexcl rule adapted to your need and enjoy the result... It's just a problem of configuration... -Message d'origine- De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De la part de Angus Macdonald Envoyé : lundi 22 octobre 2007 15:16 À : ADSM-L@VM.MARIST.EDU Objet : Re: [ADSM-L] Archiving basic queries In my case that would involve moving all the files to be archived to a different server and backup the server en-masse. Not out of the question but also not something I relish. Maybe I should just use Veritas! -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of CAYE PIERRE Sent: 22 October 2007 14:12 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Archiving basic queries May I suggest something ? I had to deal with a problem like that, involving externalization of datas, for legal archiving. I made a specific node, specific mgmt class and archive datas like that, then export node to deal with externalization of cartridges. I keep node definition but I had deleted filespaces under it and freed db space like that. Data's are on export cartridge. It is easy to retrieve it with an import node dates=relative. Regards, Pierre -Message d'origine- De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De la part de Angus Macdonald Envoyé : lundi 22 octobre 2007 15:02 À : ADSM-L@VM.MARIST.EDU Objet : Re: [ADSM-L] Archiving basic queries That's the plan. I have an archiving storage pool setup and ready, although not a separate management class. The bit I'm working on is getting the existing backups of the files I'm archiving, out of the existing main storage pool. I can then reclaim the main storage pool tapes and regain a lot of library space. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Larry Clark Sent: 22 October 2007 13:49 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Archiving basic queries Have you considered creating a separate managment class with its own archive pool, archive/deleteing your files to that, then checking out those volumes and storing them on a shelf someplace? - Original Message - From: Angus Macdonald [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 7:41 AM Subject: Re: [ADSM-L] Archiving basic queries I may not be describing it very well ;-) I have lots of old, unaccessed files that need to be retained indefinitely. To free up library space I want to archive them to tape and delete from the fileservers. It would be nice if I could remove the Tivoli database entries for these files to free up the library sooner rather than later. I know how to select and archive only those files with a last accessed date earlier than some arbitrary date in the past. I was interested in the possibility of expiring only those files and not others from Tivoli afterwards. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Richard Sims Sent: 22 October 2007 12:34 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Archiving basic queries On Oct 22, 2007, at 5:27 AM, Angus Macdonald wrote: ... 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? I think we're all puzzled as to why you would have bothered archiving files which you could have simply deleted from the file system, to achieve the same effect? You need to dig into the B/A client manual, the chapter Archiving and retrieving your data, which describes all the aspects and factors of file archiving - including deleting archive data. You need a solid grounding in the area that you are pursuing, in order to make best use of it. Going at it piecemeal is not a good approach when dealing with data retention regimens. Richard Sims http://people.bu.edu/rbs 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 â
Willy MORISSEAU est absent.
Je serai absent(e) à partir du 22/10/2007 de retour le 26/10/2007. Je suis en formation chez IBM à noisy le grand Je répondrai à votre message dès mon retour. *** L'intégrité de ce message n'étant pas entièrement assurée sur internet, le Groupe Vauban Humanis ne peut être tenu responsable de son contenu. Toute utilisation de ce message non conforme à sa destination est interdite, sauf autorisation expresse. Si vous n'êtes pas destinataire de ce message, merci de le détruire et d'avertir l'expéditeur. ***
Scheduling a full archive of data once/month
Hello everyone, I have just received the task of scheduling an archive of all data from several windows servers the first Saturday of every month for 7 years. What is the best method of accomplishing this? I would like to do this from the TSM server which is an AIX 5.3 TSM 5.3.5.2 server. Any suggestions are greatly appreciated! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED]
Re: TSM client ignores filesystems mounted by TSM preschedule command
Hi John, As I said earlier, I needed to double-check that earlier statement I made about the behavior. After checking the code, I found that the DOMAIN should get picked up as part of incremental processing, which is initiated *after* PRESCHEDULECMD. A bit more research (I knew this sounded familiar) found APAR IC53628. The APAR is still open. Until the APAR is closed and a fix is available, try specifying DOMAIN ALL-LOCAL in your options file (I suspect you are using the default, with no DOMAIN coded at all) and see if that makes a difference. It is the workaround documented in the APAR. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 10/19/2007 02:50:20 PM: Greetings, With all due respect to the Software Group, I think this behavior, assuming it is working as designed, is nuts. The whole reason the -preschedulecmd option exists is to permit the customer to perform necessary setup on his client BEFORE the backup actually starts. Establishing the Domain is certainly part of the backup, and something the -preschedulecmd option ought to execute ahead of. Is there some logic here eluding me? Best Regards, John D. Schneider Lead Systems Administrator - Storage Sisters of Mercy Health Systems 3637 South Geyer Road St. Louis, MO 63127 Phone: 314-364-3150 Cell: 314-486-2359 Email: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Raibeck Sent: Friday, October 19, 2007 3:05 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM client ignores filesystems mounted by TSM preschedule command Yes, the domain is picked up before executing PRESCHEDULECMD... I need to double-check this. But to get the desired behavior, my earler suggestion still stands. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageMan ager.html The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 10/19/2007 12:49:35 PM: Hi John, Yes, the domain is picked up before executing PRESCHEDULECMD, hence the behavior you see. There is no TSM setting to change this. One alternative you could try is to define a schedule with ACTION=COMMAND OBJECTS=/opt/misd/bin/importPrdVg prdaok PRIORITY=1 Set the start time for this schedule at the same time as your backup schedule. Due to the higher priority, the ACTION=COMMAND schedule will run first, mounting the file systems. Then the incremental schedule will run. Note that the above is just a sketch of the idea, I assume you can take it from here (if you wish to go this route). Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Product Development Level 3 Team Lead Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www.ibm. com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. Good enough is the enemy of excellence. ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 10/19/2007 11:59:43 AM: Greetings, I have a situation where the TSM client seems to be ignoring some mounted filesystems. I have a need to have a TSM preschedule command which imports some volume groups and mounts their filesystems. (This data is an EMC disk clone of another system, but that is immaterial). Once the preschedule command mounts the filesystems, I run an incremental of the system which should back up only those filesystems that are the ones I just mounted, which happen to all be mounts behind the same mount point /tsmprdaok. My include/exclude file is extremely simple: exclude /.../* include /tsmprdaok/.../* ( I know this will need to exclude other filesystems eventually, but for the sake of keeping it simple this is how it is for now.) When the backup runs, it produces: Executing scheduled command now. 10/18/07 17:45:12 Executing Operating System command or
Re: Scheduling a full archive of data once/month
Something like: 1). def sched domain monthlyarch act=archive scheds=enhanced week=first day=saturday options='-subdir=yes -domain=all-local' expiration=10/30/2014 2). associate your clients with the schedule - Original Message - From: Joni Moyer [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 10:49 AM Subject: [ADSM-L] Scheduling a full archive of data once/month Hello everyone, I have just received the task of scheduling an archive of all data from several windows servers the first Saturday of every month for 7 years. What is the best method of accomplishing this? I would like to do this from the TSM server which is an AIX 5.3 TSM 5.3.5.2 server. Any suggestions are greatly appreciated! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED]
Re: Scheduling a full archive of data once/month
Hello Larry, I was just wondering where you found this syntax? From the command line when I did a help define schedule it didn't give me all of these features. I just thought I would ask before I try this out. Thanks again! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED] Larry Clark [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 10/22/2007 11:28 AM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: Scheduling a full archive of data once/month Something like: 1). def sched domain monthlyarch act=archive scheds=enhanced week=first day=saturday options='-subdir=yes -domain=all-local' expiration=10/30/2014 2). associate your clients with the schedule - Original Message - From: Joni Moyer [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 10:49 AM Subject: [ADSM-L] Scheduling a full archive of data once/month Hello everyone, I have just received the task of scheduling an archive of all data from several windows servers the first Saturday of every month for 7 years. What is the best method of accomplishing this? I would like to do this from the TSM server which is an AIX 5.3 TSM 5.3.5.2 server. Any suggestions are greatly appreciated! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED]
Re: 7500 Mb/s on 10 GbE!
Orville Lantto wrote: Doesn't the DDR2 slot in a p570 go twice as fast as the normal PCI slot? don't know anout p570's, my most recent p550 has a 266 MHz pci-x slot, at 64 bits that could possibly be good enough for 10 GE (and tsm is mostly one-way traffic anyway). Orville L. Lantto From: Kauffman, Tom Sent: Thu 10/18/2007 21:43 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] 7500 Mb/s on 10 GbE! The PCI bus on a P5 will saturate at 400 MB/Sec; you'll need to go to the P6 to exceed that. That, and the $8,000 per end cost are the reasons I have 4 independent gigabit backup networks. (At the lat time I looked, the IBM card was $8,000 and a populated 8-port board for our Cisco switch was $64,000, with the per-port cost getting uglier as you cut the ports down). Tom Kauffman NIBCO, Inc -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Curtis Preston Sent: Thursday, October 18, 2007 8:44 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: 7500 Mb/s on 10 GbE! The reason I posted this is that up to now, I've never seen anyone go any faster than about 400 MB/s (3200 Mb/s). If you're able to test that you can go indeed go anywhere near the speed that this guy had, using your P5s of course, I'd love to post your results, too. I'm just trying to help get the backup community beyond the 100 MB/s barrier we've been at for a while. --- W. Curtis Preston Backup Blog @ www.backupcentral.com VP Data Protection, GlassHouse Technologies -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Bob Booth Sent: Thursday, October 18, 2007 4:40 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] 7500 Mb/s on 10 GbE! On Thu, Oct 18, 2007 at 07:00:29PM -0400, Curtis Preston wrote: I monitor several backup-related mailing lists, and a user on another list is getting 7500 Mb/s on his 10 GbE card and was willing to share how he did it. We don't have a back to back 10Gb connection, but we do have 3 1Gb servers going into a foundry switch, which has a private 10Gb connection to our TSM server. We achieve 1590Mb/sec. 6 TSM image backups streaming, two from each server, going directly to 3592 drives. P5 - 570 TSM server, does not break a sweat, and I'm sure more is possible. It's a NetBackup user, but that's not what the post is about. It's about how he got 7500 MB/s into a single backup server, and how he did it is just as relevant to TSM users: http://www.backupcentral.com/content/view/146/47/ Has anyone accomplished this kind of throughput on other platforms? (He's using Sun Solaris.) --- W. Curtis Preston Backup Blog @ www.backupcentral.com VP Data Protection, GlassHouse Technologies CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message. -- Met vriendelijke groeten, Remco Post SARA - Reken- en Netwerkdiensten http://www.sara.nl High Performance Computing Tel. +31 20 592 3000Fax. +31 20 668 3167 PGP Key fingerprint = 6367 DFE9 5CBC 0737 7D16 B3F6 048A 02BF DC93 94EC I really didn't foresee the Internet. But then, neither did the computer industry. Not that that tells us very much of course - the computer industry didn't even foresee that the century was going to end. -- Douglas Adams
Re: Scheduling a full archive of data once/month
84 Monthly Archives - be careful on how that will make your TSM-database grow... (Depending on how many nodes and how many objects backed up per node...) Our TSM database grew from 30GB to over 300GB in under two years and nearly cratered the Win2k server. We moved to 3 TSM servers (same versions as you have) - 2 beefy AIX servers for daily backups and 1 AIX server strictly for the monthly archive. The archive server backs up less than a dozen nodes (with detailed incl/excl) for the past 5 years we currently have about a TSM-database of around 150GB... Just a heads-up... Regards, Troy Barnhart, Sr. Systems Programmer [EMAIL PROTECTED] Regional Health, Inc. 353 Fairmont Boulevard Rapid City, South Dakota 57701 PH: 605-716-8352 / FAX: 605-716-8302 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joni Moyer Sent: Monday, October 22, 2007 9:47 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Scheduling a full archive of data once/month Hello Larry, I was just wondering where you found this syntax? From the command line when I did a help define schedule it didn't give me all of these features. I just thought I would ask before I try this out. Thanks again! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED] Larry Clark [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 10/22/2007 11:28 AM To ADSM-L@VM.MARIST.EDU cc Subject Re: Scheduling a full archive of data once/month Something like: 1). def sched domain monthlyarch act=archive scheds=enhanced week=first day=saturday options='-subdir=yes -domain=all-local' expiration=10/30/2014 2). associate your clients with the schedule - Original Message - From: Joni Moyer [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 10:49 AM Subject: [ADSM-L] Scheduling a full archive of data once/month Hello everyone, I have just received the task of scheduling an archive of all data from several windows servers the first Saturday of every month for 7 years. What is the best method of accomplishing this? I would like to do this from the TSM server which is an AIX 5.3 TSM 5.3.5.2 server. Any suggestions are greatly appreciated! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED] ***Note: The information contained in this message, including any attachments, may be privileged, confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by a reply to sender only message and destroy all electronic or paper copies of the communication, including any attachments.
Re: Scheduling a full archive of data once/month
opps...you need a start time.. - Original Message - From: Joni Moyer [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 11:47 AM Subject: Re: [ADSM-L] Scheduling a full archive of data once/month Hello Larry, I was just wondering where you found this syntax? From the command line when I did a help define schedule it didn't give me all of these features. I just thought I would ask before I try this out. Thanks again! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED] Larry Clark [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 10/22/2007 11:28 AM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: Scheduling a full archive of data once/month Something like: 1). def sched domain monthlyarch act=archive scheds=enhanced week=first day=saturday options='-subdir=yes -domain=all-local' expiration=10/30/2014 2). associate your clients with the schedule - Original Message - From: Joni Moyer [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 10:49 AM Subject: [ADSM-L] Scheduling a full archive of data once/month Hello everyone, I have just received the task of scheduling an archive of all data from several windows servers the first Saturday of every month for 7 years. What is the best method of accomplishing this? I would like to do this from the TSM server which is an AIX 5.3 TSM 5.3.5.2 server. Any suggestions are greatly appreciated! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED]
Re: Scheduling a full archive of data once/month
try the admin ref manuals. they are online at: http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp - Original Message - From: Joni Moyer [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 11:47 AM Subject: Re: [ADSM-L] Scheduling a full archive of data once/month Hello Larry, I was just wondering where you found this syntax? From the command line when I did a help define schedule it didn't give me all of these features. I just thought I would ask before I try this out. Thanks again! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED] Larry Clark [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 10/22/2007 11:28 AM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: Scheduling a full archive of data once/month Something like: 1). def sched domain monthlyarch act=archive scheds=enhanced week=first day=saturday options='-subdir=yes -domain=all-local' expiration=10/30/2014 2). associate your clients with the schedule - Original Message - From: Joni Moyer [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 10:49 AM Subject: [ADSM-L] Scheduling a full archive of data once/month Hello everyone, I have just received the task of scheduling an archive of all data from several windows servers the first Saturday of every month for 7 years. What is the best method of accomplishing this? I would like to do this from the TSM server which is an AIX 5.3 TSM 5.3.5.2 server. Any suggestions are greatly appreciated! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED]
Re: Scheduling a full archive of data once/month
Thanks! And how/where do you specify the management class? I've looked at this command and it doesn't really give any examples of how to do so. Thanks again! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED] Larry Clark [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 10/22/2007 12:03 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: Scheduling a full archive of data once/month opps...you need a start time.. - Original Message - From: Joni Moyer [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 11:47 AM Subject: Re: [ADSM-L] Scheduling a full archive of data once/month Hello Larry, I was just wondering where you found this syntax? From the command line when I did a help define schedule it didn't give me all of these features. I just thought I would ask before I try this out. Thanks again! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED] Larry Clark [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 10/22/2007 11:28 AM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: Scheduling a full archive of data once/month Something like: 1). def sched domain monthlyarch act=archive scheds=enhanced week=first day=saturday options='-subdir=yes -domain=all-local' expiration=10/30/2014 2). associate your clients with the schedule - Original Message - From: Joni Moyer [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 10:49 AM Subject: [ADSM-L] Scheduling a full archive of data once/month Hello everyone, I have just received the task of scheduling an archive of all data from several windows servers the first Saturday of every month for 7 years. What is the best method of accomplishing this? I would like to do this from the TSM server which is an AIX 5.3 TSM 5.3.5.2 server. Any suggestions are greatly appreciated! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED]
Re: Scheduling a full archive of data once/month
modify your optioons parm on the def sched to explicity reference a specific one: options='-subdir=yes -domain=all-local' -archmc=YOURARCHIVEMC no different that if you executed a dsmc archive (such and such) from the command line, you just place the (such and such) in the options portion of the def sched. - Original Message - From: Joni Moyer [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 12:16 PM Subject: Re: [ADSM-L] Scheduling a full archive of data once/month Thanks! And how/where do you specify the management class? I've looked at this command and it doesn't really give any examples of how to do so. Thanks again! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED] Larry Clark [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 10/22/2007 12:03 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: Scheduling a full archive of data once/month opps...you need a start time.. - Original Message - From: Joni Moyer [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 11:47 AM Subject: Re: [ADSM-L] Scheduling a full archive of data once/month Hello Larry, I was just wondering where you found this syntax? From the command line when I did a help define schedule it didn't give me all of these features. I just thought I would ask before I try this out. Thanks again! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED] Larry Clark [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 10/22/2007 11:28 AM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: Scheduling a full archive of data once/month Something like: 1). def sched domain monthlyarch act=archive scheds=enhanced week=first day=saturday options='-subdir=yes -domain=all-local' expiration=10/30/2014 2). associate your clients with the schedule - Original Message - From: Joni Moyer [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 10:49 AM Subject: [ADSM-L] Scheduling a full archive of data once/month Hello everyone, I have just received the task of scheduling an archive of all data from several windows servers the first Saturday of every month for 7 years. What is the best method of accomplishing this? I would like to do this from the TSM server which is an AIX 5.3 TSM 5.3.5.2 server. Any suggestions are greatly appreciated! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED]
Sropping expiration for specific clients
Hello, Due to a legal request we are being asked not to expire any data for some specific TSM clients. Is there a way to exclude a group of clients from expiring any data for a time period? I see there is a way to do this for archived data. I'm talking incremental backup data. If I stop expiring altogether I think it wouldn't be long before I put my whole environment at risk. The only way I can think of to do this would be to rename all filespaces where I suspect there might be data I do not want to expire. This however would cause all those renamed filespaces to back up in full tonight. We're talking several TB of file server data. Any ideas? Sincerely, Joy Joy Hanna Enterprise Storage Group I.T. Computer Operations (503)745-7748 [EMAIL PROTECTED]
Re: Sropping expiration for specific clients
Joy, Our approach has been to create a separate domain which contain the same management classes that the data is already bound to. In this way, we can move the affected nodes to the new domain with no rebinding of data, and maintain the inactive as well as the active data. It also allows TSM to continue tracking and protecting the data We then, of course, expect the platform areas to restore the data they need to a separate location, so that we aren't stuck with open-ended interminable retention requirements that no one can agree to revert Hope this is useful! Kathleen _ Kathleen Hallahan Freddie Mac Joy Hanna [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 10/22/2007 12:59 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Sropping expiration for specific clients Hello, Due to a legal request we are being asked not to expire any data for some specific TSM clients. Is there a way to exclude a group of clients from expiring any data for a time period? I see there is a way to do this for archived data. I'm talking incremental backup data. If I stop expiring altogether I think it wouldn't be long before I put my whole environment at risk. The only way I can think of to do this would be to rename all filespaces where I suspect there might be data I do not want to expire. This however would cause all those renamed filespaces to back up in full tonight. We're talking several TB of file server data. Any ideas? Sincerely, Joy Joy Hanna Enterprise Storage Group I.T. Computer Operations (503)745-7748 [EMAIL PROTECTED]
Re: Sropping expiration for specific clients
I'd consider looking at something like defining a new policy domain with new retention rules, then doing an: update node node name domain=new domain (for the node with your new special retention needs) with the consideration below in mind. from the manual: For servers with data retention protection enabled, an archived registered node cannot be reassigned to a different policy domain. See the Administrator's Guide for more information. never did it myself - Original Message - From: Joy Hanna [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 12:59 PM Subject: [ADSM-L] Sropping expiration for specific clients Hello, Due to a legal request we are being asked not to expire any data for some specific TSM clients. Is there a way to exclude a group of clients from expiring any data for a time period? I see there is a way to do this for archived data. I'm talking incremental backup data. If I stop expiring altogether I think it wouldn't be long before I put my whole environment at risk. The only way I can think of to do this would be to rename all filespaces where I suspect there might be data I do not want to expire. This however would cause all those renamed filespaces to back up in full tonight. We're talking several TB of file server data. Any ideas? Sincerely, Joy Joy Hanna Enterprise Storage Group I.T. Computer Operations (503)745-7748 [EMAIL PROTECTED]
Re: Sropping expiration for specific clients
Been there, done that. There is no way to stop expiration for only some nodes. It is either all or nothing. A few options: - export the data on the clients you do NOT want to expire. That would keep them on their own, but you would need to import it with relative dates when you wanted to look at it. - If the data is all archived to it's own management class, you could raise the retention on that MC to keep it around longer. Ben -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joy Hanna Sent: Monday, October 22, 2007 10:59 AM To: ADSM-L@VM.MARIST.EDU Subject: Sropping expiration for specific clients Hello, Due to a legal request we are being asked not to expire any data for some specific TSM clients. Is there a way to exclude a group of clients from expiring any data for a time period? I see there is a way to do this for archived data. I'm talking incremental backup data. If I stop expiring altogether I think it wouldn't be long before I put my whole environment at risk. The only way I can think of to do this would be to rename all filespaces where I suspect there might be data I do not want to expire. This however would cause all those renamed filespaces to back up in full tonight. We're talking several TB of file server data. Any ideas? Sincerely, Joy Joy Hanna Enterprise Storage Group I.T. Computer Operations (503)745-7748 [EMAIL PROTECTED]
expire question
Hello, Due to a legal request we are being asked not to expire any data for some specific TSM clients. Is there a way to exclude a group of clients from expiring any data for a time period? I see there is a way to do this for archived data. I'm talking incremental backup data. If I stop expiring altogether I think it wouldn't be long before I put my whole environment at risk. The only way I can think of to do this would be to rename all filespaces where I suspect there might be data I do not want to expire. This however would cause all those renamed filespaces to back up in full tonight. We're talking several TB of file server data. Any ideas? Sincerely, Joy Joy Hanna Enterprise Storage Group I.T. Computer Operations (503)745-7748 [EMAIL PROTECTED]
Re: Sropping expiration for specific clients
h... so would you define a new copygroup in the new domain with new retention rules using the same managment class (name)? - Original Message - From: Kathleen M Hallahan [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 1:15 PM Subject: Re: [ADSM-L] Sropping expiration for specific clients Joy, Our approach has been to create a separate domain which contain the same management classes that the data is already bound to. In this way, we can move the affected nodes to the new domain with no rebinding of data, and maintain the inactive as well as the active data. It also allows TSM to continue tracking and protecting the data We then, of course, expect the platform areas to restore the data they need to a separate location, so that we aren't stuck with open-ended interminable retention requirements that no one can agree to revert Hope this is useful! Kathleen _ Kathleen Hallahan Freddie Mac Joy Hanna [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 10/22/2007 12:59 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Sropping expiration for specific clients Hello, Due to a legal request we are being asked not to expire any data for some specific TSM clients. Is there a way to exclude a group of clients from expiring any data for a time period? I see there is a way to do this for archived data. I'm talking incremental backup data. If I stop expiring altogether I think it wouldn't be long before I put my whole environment at risk. The only way I can think of to do this would be to rename all filespaces where I suspect there might be data I do not want to expire. This however would cause all those renamed filespaces to back up in full tonight. We're talking several TB of file server data. Any ideas? Sincerely, Joy Joy Hanna Enterprise Storage Group I.T. Computer Operations (503)745-7748 [EMAIL PROTECTED]
Re: expire question
Define a new domain, define mgmtclass and copygroups with higher retention, define client schedules, update nodes to new domain, associate to client schedules, recycle the client scheduler and you are done. Thanks Regards, Samiran Das -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joy Hanna Sent: Monday, October 22, 2007 1:24 PM To: ADSM-L@VM.MARIST.EDU Subject: expire question Hello, Due to a legal request we are being asked not to expire any data for some specific TSM clients. Is there a way to exclude a group of clients from expiring any data for a time period? I see there is a way to do this for archived data. I'm talking incremental backup data. If I stop expiring altogether I think it wouldn't be long before I put my whole environment at risk. The only way I can think of to do this would be to rename all filespaces where I suspect there might be data I do not want to expire. This however would cause all those renamed filespaces to back up in full tonight. We're talking several TB of file server data. Any ideas? Sincerely, Joy Joy Hanna Enterprise Storage Group I.T. Computer Operations (503)745-7748 [EMAIL PROTECTED] This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing.
Re: Sropping expiration for specific clients
Yes, exactly. We have a domain with its own copygroup, storage pools, etc. We just reuse the names of the management classes and assign different retention to them inside of those. Since our management classes are pretty standardized anyway, it's not too complicated to do. _ Kathleen Hallahan Freddie Mac Larry Clark [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 10/22/2007 01:29 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: Sropping expiration for specific clients h... so would you define a new copygroup in the new domain with new retention rules using the same managment class (name)? - Original Message - From: Kathleen M Hallahan [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 1:15 PM Subject: Re: [ADSM-L] Sropping expiration for specific clients Joy, Our approach has been to create a separate domain which contain the same management classes that the data is already bound to. In this way, we can move the affected nodes to the new domain with no rebinding of data, and maintain the inactive as well as the active data. It also allows TSM to continue tracking and protecting the data We then, of course, expect the platform areas to restore the data they need to a separate location, so that we aren't stuck with open-ended interminable retention requirements that no one can agree to revert Hope this is useful! Kathleen _ Kathleen Hallahan Freddie Mac Joy Hanna [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 10/22/2007 12:59 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Sropping expiration for specific clients Hello, Due to a legal request we are being asked not to expire any data for some specific TSM clients. Is there a way to exclude a group of clients from expiring any data for a time period? I see there is a way to do this for archived data. I'm talking incremental backup data. If I stop expiring altogether I think it wouldn't be long before I put my whole environment at risk. The only way I can think of to do this would be to rename all filespaces where I suspect there might be data I do not want to expire. This however would cause all those renamed filespaces to back up in full tonight. We're talking several TB of file server data. Any ideas? Sincerely, Joy Joy Hanna Enterprise Storage Group I.T. Computer Operations (503)745-7748 [EMAIL PROTECTED]
Re: Sropping expiration for specific clients
Ok, just wanted to clarify. Those would be different management classes even though they have the same name. - Original Message - From: Kathleen M Hallahan [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 1:33 PM Subject: Re: [ADSM-L] Sropping expiration for specific clients Yes, exactly. We have a domain with its own copygroup, storage pools, etc. We just reuse the names of the management classes and assign different retention to them inside of those. Since our management classes are pretty standardized anyway, it's not too complicated to do. _ Kathleen Hallahan Freddie Mac Larry Clark [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 10/22/2007 01:29 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: Sropping expiration for specific clients h... so would you define a new copygroup in the new domain with new retention rules using the same managment class (name)? - Original Message - From: Kathleen M Hallahan [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 1:15 PM Subject: Re: [ADSM-L] Sropping expiration for specific clients Joy, Our approach has been to create a separate domain which contain the same management classes that the data is already bound to. In this way, we can move the affected nodes to the new domain with no rebinding of data, and maintain the inactive as well as the active data. It also allows TSM to continue tracking and protecting the data We then, of course, expect the platform areas to restore the data they need to a separate location, so that we aren't stuck with open-ended interminable retention requirements that no one can agree to revert Hope this is useful! Kathleen _ Kathleen Hallahan Freddie Mac Joy Hanna [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 10/22/2007 12:59 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Sropping expiration for specific clients Hello, Due to a legal request we are being asked not to expire any data for some specific TSM clients. Is there a way to exclude a group of clients from expiring any data for a time period? I see there is a way to do this for archived data. I'm talking incremental backup data. If I stop expiring altogether I think it wouldn't be long before I put my whole environment at risk. The only way I can think of to do this would be to rename all filespaces where I suspect there might be data I do not want to expire. This however would cause all those renamed filespaces to back up in full tonight. We're talking several TB of file server data. Any ideas? Sincerely, Joy Joy Hanna Enterprise Storage Group I.T. Computer Operations (503)745-7748 [EMAIL PROTECTED]
Re: Sropping expiration for specific clients
They are, but for retention purposes they do work as the same one. In other words, when a node is moved from one domain to another, no rebinding takes place. Which I'm very glad of, since I don't know how we'd do this otherwise. :-) _ Kathleen Hallahan Freddie Mac Larry Clark [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 10/22/2007 02:01 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: Sropping expiration for specific clients Ok, just wanted to clarify. Those would be different management classes even though they have the same name. - Original Message - From: Kathleen M Hallahan [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 1:33 PM Subject: Re: [ADSM-L] Sropping expiration for specific clients Yes, exactly. We have a domain with its own copygroup, storage pools, etc. We just reuse the names of the management classes and assign different retention to them inside of those. Since our management classes are pretty standardized anyway, it's not too complicated to do. _ Kathleen Hallahan Freddie Mac Larry Clark [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 10/22/2007 01:29 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: Sropping expiration for specific clients h... so would you define a new copygroup in the new domain with new retention rules using the same managment class (name)? - Original Message - From: Kathleen M Hallahan [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 1:15 PM Subject: Re: [ADSM-L] Sropping expiration for specific clients Joy, Our approach has been to create a separate domain which contain the same management classes that the data is already bound to. In this way, we can move the affected nodes to the new domain with no rebinding of data, and maintain the inactive as well as the active data. It also allows TSM to continue tracking and protecting the data We then, of course, expect the platform areas to restore the data they need to a separate location, so that we aren't stuck with open-ended interminable retention requirements that no one can agree to revert Hope this is useful! Kathleen _ Kathleen Hallahan Freddie Mac Joy Hanna [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 10/22/2007 12:59 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Sropping expiration for specific clients Hello, Due to a legal request we are being asked not to expire any data for some specific TSM clients. Is there a way to exclude a group of clients from expiring any data for a time period? I see there is a way to do this for archived data. I'm talking incremental backup data. If I stop expiring altogether I think it wouldn't be long before I put my whole environment at risk. The only way I can think of to do this would be to rename all filespaces where I suspect there might be data I do not want to expire. This however would cause all those renamed filespaces to back up in full tonight. We're talking several TB of file server data. Any ideas? Sincerely, Joy Joy Hanna Enterprise Storage Group I.T. Computer Operations (503)745-7748 [EMAIL PROTECTED]
Re: Scheduling a full archive of data once/month
I do not believe that the DOMAIN option is valid for the ARCHIVE function. The description for DOMAIN is the drives to be included for incremental backup processing. For ARCHIVE you have to specify what you want processed in the OBJECTS= parameter for the schedule. ARCHIVE also does not process your systemobject, system services or system state objects. If you want to use a schedule and ARCHIVE for everything, you'll need to specify each drive in a separate schedule for each node. OBJECT='C:\* D:\*'for example. It is not dynamic in that if the admin adds a drive, you will need to adjust the schedule to include the new drive. Bill Boyer Nothing is foolproof to a sufficiently talented fool. - Murphy -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Larry Clark Sent: Monday, October 22, 2007 11:29 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Scheduling a full archive of data once/month Something like: 1). def sched domain monthlyarch act=archive scheds=enhanced week=first day=saturday options='-subdir=yes -domain=all-local' expiration=10/30/2014 2). associate your clients with the schedule - Original Message - From: Joni Moyer [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 10:49 AM Subject: [ADSM-L] Scheduling a full archive of data once/month Hello everyone, I have just received the task of scheduling an archive of all data from several windows servers the first Saturday of every month for 7 years. What is the best method of accomplishing this? I would like to do this from the TSM server which is an AIX 5.3 TSM 5.3.5.2 server. Any suggestions are greatly appreciated! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED]
finding the tsm client download page
ok, I give. I've been all over the tivoli support pages, where do you download clients? I see all kinds of sales stuff, but clidking what appear to be download related links leads me in circles. RANT ON. Please, ibm folks, make your pages less complex and markety. RANT OFF. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
Re: finding the tsm client download page
Try http://www-1.ibm.com/support/docview.wss?rs=663uid=swg21239415 Or just get them from the ftp site: ftp://service.software.ibm.com/storage/tivoli-storage-management/maintenance/client/v5r4 Orville L. Lantto From: ADSM: Dist Stor Manager on behalf of Lee, Gary D. Sent: Mon 10/22/2007 15:09 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] finding the tsm client download page ok, I give. I've been all over the tivoli support pages, where do you download clients? I see all kinds of sales stuff, but clidking what appear to be download related links leads me in circles. RANT ON. Please, ibm folks, make your pages less complex and markety. RANT OFF. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
Re: Scheduling a full archive of data once/month
your right.you would need to explicit reference each drive with the -subdir=yes included to get all files. I don't think a system backup was involved in the question, just a archive of all files. - Original Message - From: William Boyer [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 1:57 PM Subject: Re: [ADSM-L] Scheduling a full archive of data once/month I do not believe that the DOMAIN option is valid for the ARCHIVE function. The description for DOMAIN is the drives to be included for incremental backup processing. For ARCHIVE you have to specify what you want processed in the OBJECTS= parameter for the schedule. ARCHIVE also does not process your systemobject, system services or system state objects. If you want to use a schedule and ARCHIVE for everything, you'll need to specify each drive in a separate schedule for each node. OBJECT='C:\* D:\*'for example. It is not dynamic in that if the admin adds a drive, you will need to adjust the schedule to include the new drive. Bill Boyer Nothing is foolproof to a sufficiently talented fool. - Murphy -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Larry Clark Sent: Monday, October 22, 2007 11:29 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Scheduling a full archive of data once/month Something like: 1). def sched domain monthlyarch act=archive scheds=enhanced week=first day=saturday options='-subdir=yes -domain=all-local' expiration=10/30/2014 2). associate your clients with the schedule - Original Message - From: Joni Moyer [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, October 22, 2007 10:49 AM Subject: [ADSM-L] Scheduling a full archive of data once/month Hello everyone, I have just received the task of scheduling an archive of all data from several windows servers the first Saturday of every month for 7 years. What is the best method of accomplishing this? I would like to do this from the TSM server which is an AIX 5.3 TSM 5.3.5.2 server. Any suggestions are greatly appreciated! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED]
Re: Scheduling a full archive of data once/month
Joni Does the requirement explicitly say an archive? or just that there is to be a point in time backup once a month that is kept for 7 years? The problem with archives is that you must explicitly specify what is to be backed up and that is not always easy to know. One place I worked I kept a record of the filesystems on each node, and once a month compared last month and current filesystems and programmatically re-generated the archive commands. Archives are also not good from an include-exclude point of view as you have to explicitly code an include.archive or exclude.archive whenever you add a backup rule, and also you *may* want to exclude some files eg databases from backup but not from archive most of the time, but not during your monthly archives. The better solution to most of this is a second TSM Server which does a monthly incremental backup. Less data backed up, less data stored, less DB space used :) more complexity on the client, more complexity in the server setup and node maintenance :( If you also have the requirement that one backup a year be kept indefinitely ( in my case this was government healthcare and some records needed to be kept for the life of the patient + 20 years, so the simple-minded approach was - keep everything) there may even be a case for a yearly incremental setup as well, although these days a backupset will probably do the job as effectively. Finally, one idea that I toyed with but never tried was a periodic export backupactive server to server. with the fromdate/fromtime option. The mgmtclasses on the receiver would have to have the same names as the sender, but with different retentions. Hope this Helps Steve Steven Harris TSM Admin Sydney, Australia Joni Moyer [EMAIL PROTECTED] ARK.COM To Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager [EMAIL PROTECTED] Subject .EDU [ADSM-L] Scheduling a full archive of data once/month 23/10/2007 12:49 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] .EDU Hello everyone, I have just received the task of scheduling an archive of all data from several windows servers the first Saturday of every month for 7 years. What is the best method of accomplishing this? I would like to do this from the TSM server which is an AIX 5.3 TSM 5.3.5.2 server. Any suggestions are greatly appreciated! Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED]
