Re: permanent retention
When create archive copy group use retver=NOLimit On Wed, Dec 12, 2012 at 6:39 PM, Lee, Gary g...@bsu.edu wrote: Just received a request to have a few files stored in tsm essentially forever. I am trying to figure out the best way to accomplish this with minimal administrative overhead. So far, 1. create a management class with an archive group set for days, then archive the files. 2. create a management class and use backup, but I am unclear how to accomplish permanent retention there? Any ideas well be appreciated. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
permanent retention
Just received a request to have a few files stored in tsm essentially forever. I am trying to figure out the best way to accomplish this with minimal administrative overhead. So far, 1. create a management class with an archive group set for days, then archive the files. 2. create a management class and use backup, but I am unclear how to accomplish permanent retention there? Any ideas well be appreciated. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
Re: permanent retention
Thanks. Forgot about that one. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Chavdar Cholev Sent: Wednesday, December 12, 2012 11:49 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] permanent retention When create archive copy group use retver=NOLimit On Wed, Dec 12, 2012 at 6:39 PM, Lee, Gary g...@bsu.edu wrote: Just received a request to have a few files stored in tsm essentially forever. I am trying to figure out the best way to accomplish this with minimal administrative overhead. So far, 1. create a management class with an archive group set for days, then archive the files. 2. create a management class and use backup, but I am unclear how to accomplish permanent retention there? Any ideas well be appreciated. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
Re: permanent retention
Ron: I understand that archive is preferable, but there is sufficient data there as to interfere with daily backups. Therefore, I want to do it with backups so as not to re-move data. I have a management class permanent-retain with a backup copygroup defined as follows: Copy Group Type: Backup Versions Data Exists: 1 Versions Data Deleted: 1 Retain Extra Versions: No Limit Retain Only Version: No Limit in dsm.opt I have: INCLUDE.BACKUP *:\Keep\...\* permanent-retain INCLUDE.BACKUP *:\Keep\...\*.* permanent-retain Will this do the job and not retain too much data? Thanks for the help. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Ron Delaware Sent: Wednesday, December 12, 2012 12:08 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] permanent retention Gary, You really don't want to use backup's for long term retention, that is an archive function. But if you must, you set everything to NOLIMIT NOLIMIT NOLIMIT NOLIMIT that way the data will hang around forever, but as I stated, Archives are the way to go _ Ronald C. Delaware IBM IT Plus Certified Specialist- Expert IBM Corporation | Tivoli Software IBM Certified Solutions Advisor - Tivoli Storage IBM Certified Deployment Professional 916-458-5726 (Office) 925-457-9221 (cell phone) email: ron.delaw...@us.ibm.com Storage Services Offerings From: Lee, Gary g...@bsu.edu To: ADSM-L@vm.marist.edu Date: 12/12/2012 10:46 AM Subject:[ADSM-L] permanent retention Sent by:ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Just received a request to have a few files stored in tsm essentially forever. I am trying to figure out the best way to accomplish this with minimal administrative overhead. So far, 1. create a management class with an archive group set for days, then archive the files. 2. create a management class and use backup, but I am unclear how to accomplish permanent retention there? Any ideas well be appreciated. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
Re: permanent retention
Also consider exporting the data with a very descriptive note taped to it. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Ron Delaware Sent: Wednesday, December 12, 2012 11:08 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] permanent retention Gary, You really don't want to use backup's for long term retention, that is an archive function. But if you must, you set everything to NOLIMIT NOLIMIT NOLIMIT NOLIMIT that way the data will hang around forever, but as I stated, Archives are the way to go _ Ronald C. Delaware IBM IT Plus Certified Specialist- Expert IBM Corporation | Tivoli Software IBM Certified Solutions Advisor - Tivoli Storage IBM Certified Deployment Professional 916-458-5726 (Office) 925-457-9221 (cell phone) email: ron.delaw...@us.ibm.com Storage Services Offerings From: Lee, Gary g...@bsu.edu To: ADSM-L@vm.marist.edu Date: 12/12/2012 10:46 AM Subject:[ADSM-L] permanent retention Sent by:ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Just received a request to have a few files stored in tsm essentially forever. I am trying to figure out the best way to accomplish this with minimal administrative overhead. So far, 1. create a management class with an archive group set for days, then archive the files. 2. create a management class and use backup, but I am unclear how to accomplish permanent retention there? Any ideas well be appreciated. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
Re: permanent retention
Gary, The problem you will run into is that the backup data will be mixed in with all of the other backup data, unless you have a management class that sends the data to a separate storage pool and tape pool. If you need to have this data isolated, archives or a separate storage pool is the only way to go. _ Ronald C. Delaware IBM IT Plus Certified Specialist- Expert IBM Corporation | Tivoli Software IBM Certified Solutions Advisor - Tivoli Storage IBM Certified Deployment Professional 916-458-5726 (Office) 925-457-9221 (cell phone) email: ron.delaw...@us.ibm.com Storage Services Offerings From: Lee, Gary g...@bsu.edu To: ADSM-L@vm.marist.edu Date: 12/12/2012 01:53 PM Subject:Re: [ADSM-L] permanent retention Sent by:ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Ron: I understand that archive is preferable, but there is sufficient data there as to interfere with daily backups. Therefore, I want to do it with backups so as not to re-move data. I have a management class permanent-retain with a backup copygroup defined as follows: Copy Group Type: Backup Versions Data Exists: 1 Versions Data Deleted: 1 Retain Extra Versions: No Limit Retain Only Version: No Limit in dsm.opt I have: INCLUDE.BACKUP *:\Keep\...\* permanent-retain INCLUDE.BACKUP *:\Keep\...\*.* permanent-retain Will this do the job and not retain too much data? Thanks for the help. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Ron Delaware Sent: Wednesday, December 12, 2012 12:08 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] permanent retention Gary, You really don't want to use backup's for long term retention, that is an archive function. But if you must, you set everything to NOLIMIT NOLIMIT NOLIMIT NOLIMIT that way the data will hang around forever, but as I stated, Archives are the way to go _ Ronald C. Delaware IBM IT Plus Certified Specialist- Expert IBM Corporation | Tivoli Software IBM Certified Solutions Advisor - Tivoli Storage IBM Certified Deployment Professional 916-458-5726 (Office) 925-457-9221 (cell phone) email: ron.delaw...@us.ibm.com Storage Services Offerings From: Lee, Gary g...@bsu.edu To: ADSM-L@vm.marist.edu Date: 12/12/2012 10:46 AM Subject:[ADSM-L] permanent retention Sent by:ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Just received a request to have a few files stored in tsm essentially forever. I am trying to figure out the best way to accomplish this with minimal administrative overhead. So far, 1. create a management class with an archive group set for days, then archive the files. 2. create a management class and use backup, but I am unclear how to accomplish permanent retention there? Any ideas well be appreciated. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
Re: permanent retention
Gary, You really don't want to use backup's for long term retention, that is an archive function. But if you must, you set everything to NOLIMIT NOLIMIT NOLIMIT NOLIMIT that way the data will hang around forever, but as I stated, Archives are the way to go _ Ronald C. Delaware IBM IT Plus Certified Specialist- Expert IBM Corporation | Tivoli Software IBM Certified Solutions Advisor - Tivoli Storage IBM Certified Deployment Professional 916-458-5726 (Office) 925-457-9221 (cell phone) email: ron.delaw...@us.ibm.com Storage Services Offerings From: Lee, Gary g...@bsu.edu To: ADSM-L@vm.marist.edu Date: 12/12/2012 10:46 AM Subject:[ADSM-L] permanent retention Sent by:ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Just received a request to have a few files stored in tsm essentially forever. I am trying to figure out the best way to accomplish this with minimal administrative overhead. So far, 1. create a management class with an archive group set for days, then archive the files. 2. create a management class and use backup, but I am unclear how to accomplish permanent retention there? Any ideas well be appreciated. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
Re: permanent retention
Gary, Since you're using backup for archiving, you can route these backups to your disk/tape archive pools, then you'll avoid having to move the data around much once it's been saved. Bob. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Ron Delaware Sent: Wednesday, December 12, 2012 2:49 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] permanent retention Gary, The problem you will run into is that the backup data will be mixed in with all of the other backup data, unless you have a management class that sends the data to a separate storage pool and tape pool. If you need to have this data isolated, archives or a separate storage pool is the only way to go. _ Ronald C. Delaware IBM IT Plus Certified Specialist- Expert IBM Corporation | Tivoli Software IBM Certified Solutions Advisor - Tivoli Storage IBM Certified Deployment Professional 916-458-5726 (Office) 925-457-9221 (cell phone) email: ron.delaw...@us.ibm.com Storage Services Offerings From: Lee, Gary g...@bsu.edu To: ADSM-L@vm.marist.edu Date: 12/12/2012 01:53 PM Subject:Re: [ADSM-L] permanent retention Sent by:ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Ron: I understand that archive is preferable, but there is sufficient data there as to interfere with daily backups. Therefore, I want to do it with backups so as not to re-move data. I have a management class permanent-retain with a backup copygroup defined as follows: Copy Group Type: Backup Versions Data Exists: 1 Versions Data Deleted: 1 Retain Extra Versions: No Limit Retain Only Version: No Limit in dsm.opt I have: INCLUDE.BACKUP *:\Keep\...\* permanent-retain INCLUDE.BACKUP *:\Keep\...\*.* permanent-retain Will this do the job and not retain too much data? Thanks for the help. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Ron Delaware Sent: Wednesday, December 12, 2012 12:08 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] permanent retention Gary, You really don't want to use backup's for long term retention, that is an archive function. But if you must, you set everything to NOLIMIT NOLIMIT NOLIMIT NOLIMIT that way the data will hang around forever, but as I stated, Archives are the way to go _ Ronald C. Delaware IBM IT Plus Certified Specialist- Expert IBM Corporation | Tivoli Software IBM Certified Solutions Advisor - Tivoli Storage IBM Certified Deployment Professional 916-458-5726 (Office) 925-457-9221 (cell phone) email: ron.delaw...@us.ibm.com Storage Services Offerings From: Lee, Gary g...@bsu.edu To: ADSM-L@vm.marist.edu Date: 12/12/2012 10:46 AM Subject:[ADSM-L] permanent retention Sent by:ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Just received a request to have a few files stored in tsm essentially forever. I am trying to figure out the best way to accomplish this with minimal administrative overhead. So far, 1. create a management class with an archive group set for days, then archive the files. 2. create a management class and use backup, but I am unclear how to accomplish permanent retention there? Any ideas well be appreciated. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310 This electronic transmission and any documents accompanying this electronic transmission contain confidential information belonging to the sender. This information may be legally privileged. The information is intended only for the use of the individual or entity named above. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action in reliance on or regarding the contents of this electronically transmitted information is strictly prohibited.
Re: Permanent retention
Look at the Archive function of TSM client. It can be invoked from CLI by using dsmc archive objects options or from GUI/Web pressing button Archive instead of Backup. With appropriate settings in archive copygroup (which is different from backup copygroup) this is very easy to achieve. Look for def copy t=a server command. Zlatko Krastev IT Consultant Dorothy LIM Kay Choo [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 02.12.2002 08:47 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Permanent retention Hi, I would like to seek advise on how to use TSM to keep my information permanent. Before the application, execute the end-of-day processing, a set of database will be dump. After the end-of-day processing, there is another dump to database which will overwrite the previous. I need to keep both set for a retention of 7 years. Any advise ? Regards, Dorothy Lim Systems Network Division, United Overseas Bank Limited mailing address: 396 Alexandra Road, #04-00, BP Tower Singapore 119954 e-mail: [EMAIL PROTECTED] // tel: 371 5813 // fax: 270 3944 Privileged/Confidential information may be contained in this communication (which includes any attachment(s)). If you are not an intended recipient, you must not use, copy, disclose, distribute or retain this communication or any part of it. Instead, please delete all copies of this communication from your computer system and notify the sender immediately by reply email. Thank you.
Re: Permanent retention
Hi Zlatko, Thks for the suggestion. I understand that the archive function will result in huge database. I believe there is a protential problem if the database grows too big. Because of the above, I tried to used backupset which was recommended to be as a better option. Regards, Dorothy Lim Systems Network Division, United Overseas Bank Limited mailing address: 396 Alexandra Road, #04-00, BP Tower Singapore 119954 e-mail: [EMAIL PROTECTED] // tel: 371 5813 // fax: 270 3944 Privileged/Confidential information may be contained in this communication (which includes any attachment(s)). If you are not an intended recipient, you must not use, copy, disclose, distribute or retain this communication or any part of it. Instead, please delete all copies of this communication from your computer system and notify the sender immediately by reply email. Thank you. -Original Message- From: Zlatko Krastev/ACIT [mailto:[EMAIL PROTECTED]] Sent: Monday, December 02, 2002 4:01 PM To: [EMAIL PROTECTED] Subject: Re: Permanent retention Look at the Archive function of TSM client. It can be invoked from CLI by using dsmc archive objects options or from GUI/Web pressing button Archive instead of Backup. With appropriate settings in archive copygroup (which is different from backup copygroup) this is very easy to achieve. Look for def copy t=a server command. Zlatko Krastev IT Consultant Dorothy LIM Kay Choo [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 02.12.2002 08:47 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Permanent retention Hi, I would like to seek advise on how to use TSM to keep my information permanent. Before the application, execute the end-of-day processing, a set of database will be dump. After the end-of-day processing, there is another dump to database which will overwrite the previous. I need to keep both set for a retention of 7 years. Any advise ? Regards, Dorothy Lim Systems Network Division, United Overseas Bank Limited mailing address: 396 Alexandra Road, #04-00, BP Tower Singapore 119954 e-mail: [EMAIL PROTECTED] // tel: 371 5813 // fax: 270 3944 Privileged/Confidential information may be contained in this communication (which includes any attachment(s)). If you are not an intended recipient, you must not use, copy, disclose, distribute or retain this communication or any part of it. Instead, please delete all copies of this communication from your computer system and notify the sender immediately by reply email. Thank you.
Re: Permanent retention
How I do long term retention is... I register a node by a new name of old_name_exp ex. dbserver01_exp then, on that box, I create a special SErver entry it the dsm.sys file that uses that ~_exp node name ex. SErver export_srv NODE dsmserver01_exp rest of normal stuff Then I tell whoever it is to archive what they want I then produce two exports of that node and send them off-site I have a sample set of tapes I keep locally to verify media stability and ability to import after server upgrades. Best way I've come up with... Dwight E. Cook Software Application Engineer III Science Applications International Corporation 509 S. Boston Ave. Suite 220 Tulsa, Oklahoma 74103-4606 Office (918) 732-7109 -Original Message- From: Dorothy LIM Kay Choo [mailto:[EMAIL PROTECTED]] Sent: Monday, December 02, 2002 12:48 AM To: [EMAIL PROTECTED] Subject: Permanent retention Hi, I would like to seek advise on how to use TSM to keep my information permanent. Before the application, execute the end-of-day processing, a set of database will be dump. After the end-of-day processing, there is another dump to database which will overwrite the previous. I need to keep both set for a retention of 7 years. Any advise ? Regards, Dorothy Lim Systems Network Division, United Overseas Bank Limited mailing address: 396 Alexandra Road, #04-00, BP Tower Singapore 119954 e-mail: [EMAIL PROTECTED] // tel: 371 5813 // fax: 270 3944 Privileged/Confidential information may be contained in this communication (which includes any attachment(s)). If you are not an intended recipient, you must not use, copy, disclose, distribute or retain this communication or any part of it. Instead, please delete all copies of this communication from your computer system and notify the sender immediately by reply email. Thank you.
Re: Permanent retention
Dorothy, 2 archives/day * 365.25 * 7 * 800b (600b+200b for copy) = about 4.1 MB/object at the end of 7 years. How many objects will you archive each day? When you're fully populated at 7 years, your database would have grown by only 1GB due to these archives if you're archiving as many as 240 objects twice a day. I'd say your archives, unless you're doing thousands of objects twice a day, probably shouldn't grow your database as much as you might fear. Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail -Original Message- From: Dorothy LIM Kay Choo [mailto:[EMAIL PROTECTED]] Sent: Monday, December 02, 2002 1:43 AM To: [EMAIL PROTECTED] Subject: Re: Permanent retention Hi Zlatko, Thks for the suggestion. I understand that the archive function will result in huge database. I believe there is a protential problem if the database grows too big. Because of the above, I tried to used backupset which was recommended to be as a better option. Regards, Dorothy Lim Systems Network Division, United Overseas Bank Limited mailing address: 396 Alexandra Road, #04-00, BP Tower Singapore 119954 e-mail: [EMAIL PROTECTED] // tel: 371 5813 // fax: 270 3944 Privileged/Confidential information may be contained in this communication (which includes any attachment(s)). If you are not an intended recipient, you must not use, copy, disclose, distribute or retain this communication or any part of it. Instead, please delete all copies of this communication from your computer system and notify the sender immediately by reply email. Thank you. -Original Message- From: Zlatko Krastev/ACIT [mailto:[EMAIL PROTECTED]] Sent: Monday, December 02, 2002 4:01 PM To: [EMAIL PROTECTED] Subject: Re: Permanent retention Look at the Archive function of TSM client. It can be invoked from CLI by using dsmc archive objects options or from GUI/Web pressing button Archive instead of Backup. With appropriate settings in archive copygroup (which is different from backup copygroup) this is very easy to achieve. Look for def copy t=a server command. Zlatko Krastev IT Consultant Dorothy LIM Kay Choo [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 02.12.2002 08:47 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Permanent retention Hi, I would like to seek advise on how to use TSM to keep my information permanent. Before the application, execute the end-of-day processing, a set of database will be dump. After the end-of-day processing, there is another dump to database which will overwrite the previous. I need to keep both set for a retention of 7 years. Any advise ? Regards, Dorothy Lim Systems Network Division, United Overseas Bank Limited mailing address: 396 Alexandra Road, #04-00, BP Tower Singapore 119954 e-mail: [EMAIL PROTECTED] // tel: 371 5813 // fax: 270 3944 Privileged/Confidential information may be contained in this communication (which includes any attachment(s)). If you are not an intended recipient, you must not use, copy, disclose, distribute or retain this communication or any part of it. Instead, please delete all copies of this communication from your computer system and notify the sender immediately by reply email. Thank you.
Re: Permanent retention
- Backupsets do not have the ability to have copies in TSM. Count yourself how many times a tape (of the backupset) can become bad during those 7 years.If you realize it on the 4-th or 6-th year ...? - Will you stay at current tape drive technology forever? What should you do after 7 years - today's backupsets are let say on DLT, during 2003-2004 you will use LTOv2 and later will be say on LTOv4?!? You will have to keep *operative* and working for restores all technologies used during last 7 years. - What do you mean as huge? Alex already did some math. The only thing he did not added is: there are many people successfully driving 80, 100, even 180 GB TSM DB (with appropriate hardware of course). And it works every day! - Backupset lives alone on a cartridge and nothing else can use it. If your backupset is for example 30 GB and you still use DLT 7000 wasted space will be only 14%. If DLT8000 is used it will grow to 25%, for 100 GB LTO and 110 GB SDLT - 70% and 73% respectively. This will mean unused *expensive* cartridges. For 7 years, 2 cartridges (minimum) per day, ... do the math yourself. (TSM rulez! sorry, cannot resist to ask bean counters how it will cost using *any* other product :-) I can only add that if *each* copy is so important to force you to make them twice a day, you have to be careful. Zlatko Krastev IT Consultant Alex Paschal [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 02.12.2002 18:18 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Re: Permanent retention Dorothy, 2 archives/day * 365.25 * 7 * 800b (600b+200b for copy) = about 4.1 MB/object at the end of 7 years. How many objects will you archive each day? When you're fully populated at 7 years, your database would have grown by only 1GB due to these archives if you're archiving as many as 240 objects twice a day. I'd say your archives, unless you're doing thousands of objects twice a day, probably shouldn't grow your database as much as you might fear. Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail -Original Message- From: Dorothy LIM Kay Choo [mailto:[EMAIL PROTECTED]] Sent: Monday, December 02, 2002 1:43 AM To: [EMAIL PROTECTED] Subject: Re: Permanent retention Hi Zlatko, Thks for the suggestion. I understand that the archive function will result in huge database. I believe there is a protential problem if the database grows too big. Because of the above, I tried to used backupset which was recommended to be as a better option. Regards, Dorothy Lim Systems Network Division, United Overseas Bank Limited mailing address: 396 Alexandra Road, #04-00, BP Tower Singapore 119954 e-mail: [EMAIL PROTECTED] // tel: 371 5813 // fax: 270 3944 Privileged/Confidential information may be contained in this communication (which includes any attachment(s)). If you are not an intended recipient, you must not use, copy, disclose, distribute or retain this communication or any part of it. Instead, please delete all copies of this communication from your computer system and notify the sender immediately by reply email. Thank you. -Original Message- From: Zlatko Krastev/ACIT [mailto:[EMAIL PROTECTED]] Sent: Monday, December 02, 2002 4:01 PM To: [EMAIL PROTECTED] Subject: Re: Permanent retention Look at the Archive function of TSM client. It can be invoked from CLI by using dsmc archive objects options or from GUI/Web pressing button Archive instead of Backup. With appropriate settings in archive copygroup (which is different from backup copygroup) this is very easy to achieve. Look for def copy t=a server command. Zlatko Krastev IT Consultant Dorothy LIM Kay Choo [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 02.12.2002 08:47 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Permanent retention Hi, I would like to seek advise on how to use TSM to keep my information permanent. Before the application, execute the end-of-day processing, a set of database will be dump. After the end-of-day processing, there is another dump to database which will overwrite the previous. I need to keep both set for a retention of 7 years. Any advise ? Regards, Dorothy Lim Systems Network Division, United Overseas Bank Limited mailing address: 396 Alexandra Road, #04-00, BP Tower Singapore 119954 e-mail: [EMAIL PROTECTED] // tel: 371 5813 // fax: 270 3944 Privileged/Confidential information may be contained in this communication (which includes any attachment(s)). If you are not an intended recipient, you must not use, copy, disclose, distribute or retain this communication or any part of it. Instead, please delete all copies of this communication from your computer system
Re: Permanent retention
I agree with Zlatko; I don't think the archives will grow your data base all that much. But even if your DB got too big over time, you could use a second instance of the TSM server and use just THAT server for your archives, to split the DB into more manageable pieces. But you shouldn't have to do that for a long time. -Original Message- From: Dorothy LIM Kay Choo [mailto:[EMAIL PROTECTED]] Sent: Monday, December 02, 2002 4:43 AM To: [EMAIL PROTECTED] Subject: Re: Permanent retention Hi Zlatko, Thks for the suggestion. I understand that the archive function will result in huge database. I believe there is a protential problem if the database grows too big. Because of the above, I tried to used backupset which was recommended to be as a better option. Regards, Dorothy Lim Systems Network Division, United Overseas Bank Limited mailing address: 396 Alexandra Road, #04-00, BP Tower Singapore 119954 e-mail: [EMAIL PROTECTED] // tel: 371 5813 // fax: 270 3944 Privileged/Confidential information may be contained in this communication (which includes any attachment(s)). If you are not an intended recipient, you must not use, copy, disclose, distribute or retain this communication or any part of it. Instead, please delete all copies of this communication from your computer system and notify the sender immediately by reply email. Thank you. -Original Message- From: Zlatko Krastev/ACIT [mailto:[EMAIL PROTECTED]] Sent: Monday, December 02, 2002 4:01 PM To: [EMAIL PROTECTED] Subject: Re: Permanent retention Look at the Archive function of TSM client. It can be invoked from CLI by using dsmc archive objects options or from GUI/Web pressing button Archive instead of Backup. With appropriate settings in archive copygroup (which is different from backup copygroup) this is very easy to achieve. Look for def copy t=a server command. Zlatko Krastev IT Consultant Dorothy LIM Kay Choo [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 02.12.2002 08:47 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Permanent retention Hi, I would like to seek advise on how to use TSM to keep my information permanent. Before the application, execute the end-of-day processing, a set of database will be dump. After the end-of-day processing, there is another dump to database which will overwrite the previous. I need to keep both set for a retention of 7 years. Any advise ? Regards, Dorothy Lim Systems Network Division, United Overseas Bank Limited mailing address: 396 Alexandra Road, #04-00, BP Tower Singapore 119954 e-mail: [EMAIL PROTECTED] // tel: 371 5813 // fax: 270 3944 Privileged/Confidential information may be contained in this communication (which includes any attachment(s)). If you are not an intended recipient, you must not use, copy, disclose, distribute or retain this communication or any part of it. Instead, please delete all copies of this communication from your computer system and notify the sender immediately by reply email. Thank you.
Re: Permanent retention
do the directory archives still go to the management class with the longest retention ? I put a 10 year archive management class in systems I built 6 years ago and as people performed thousands of archives a day (for each of hundreds of registered clients) the tsm databases grew out of controll... I believe such issues are currently resolved (one way or another) but I still don't make long term archive management classes available... I deal with those needs in other ways (export of the data/node) Dwight -Original Message- From: Prather, Wanda [mailto:[EMAIL PROTECTED]] Sent: Monday, December 02, 2002 11:39 AM To: [EMAIL PROTECTED] Subject: Re: Permanent retention I agree with Zlatko; I don't think the archives will grow your data base all that much. But even if your DB got too big over time, you could use a second instance of the TSM server and use just THAT server for your archives, to split the DB into more manageable pieces. But you shouldn't have to do that for a long time. -Original Message- From: Dorothy LIM Kay Choo [mailto:[EMAIL PROTECTED]] Sent: Monday, December 02, 2002 4:43 AM To: [EMAIL PROTECTED] Subject: Re: Permanent retention Hi Zlatko, Thks for the suggestion. I understand that the archive function will result in huge database. I believe there is a protential problem if the database grows too big. Because of the above, I tried to used backupset which was recommended to be as a better option. Regards, Dorothy Lim Systems Network Division, United Overseas Bank Limited mailing address: 396 Alexandra Road, #04-00, BP Tower Singapore 119954 e-mail: [EMAIL PROTECTED] // tel: 371 5813 // fax: 270 3944 Privileged/Confidential information may be contained in this communication (which includes any attachment(s)). If you are not an intended recipient, you must not use, copy, disclose, distribute or retain this communication or any part of it. Instead, please delete all copies of this communication from your computer system and notify the sender immediately by reply email. Thank you. -Original Message- From: Zlatko Krastev/ACIT [mailto:[EMAIL PROTECTED]] Sent: Monday, December 02, 2002 4:01 PM To: [EMAIL PROTECTED] Subject: Re: Permanent retention Look at the Archive function of TSM client. It can be invoked from CLI by using dsmc archive objects options or from GUI/Web pressing button Archive instead of Backup. With appropriate settings in archive copygroup (which is different from backup copygroup) this is very easy to achieve. Look for def copy t=a server command. Zlatko Krastev IT Consultant Dorothy LIM Kay Choo [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 02.12.2002 08:47 Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: Subject:Permanent retention Hi, I would like to seek advise on how to use TSM to keep my information permanent. Before the application, execute the end-of-day processing, a set of database will be dump. After the end-of-day processing, there is another dump to database which will overwrite the previous. I need to keep both set for a retention of 7 years. Any advise ? Regards, Dorothy Lim Systems Network Division, United Overseas Bank Limited mailing address: 396 Alexandra Road, #04-00, BP Tower Singapore 119954 e-mail: [EMAIL PROTECTED] // tel: 371 5813 // fax: 270 3944 Privileged/Confidential information may be contained in this communication (which includes any attachment(s)). If you are not an intended recipient, you must not use, copy, disclose, distribute or retain this communication or any part of it. Instead, please delete all copies of this communication from your computer system and notify the sender immediately by reply email. Thank you.
Permanent retention
Hi, I would like to seek advise on how to use TSM to keep my information permanent. Before the application, execute the end-of-day processing, a set of database will be dump. After the end-of-day processing, there is another dump to database which will overwrite the previous. I need to keep both set for a retention of 7 years. Any advise ? Regards, Dorothy Lim Systems Network Division, United Overseas Bank Limited mailing address: 396 Alexandra Road, #04-00, BP Tower Singapore 119954 e-mail: [EMAIL PROTECTED] // tel: 371 5813 // fax: 270 3944 Privileged/Confidential information may be contained in this communication (which includes any attachment(s)). If you are not an intended recipient, you must not use, copy, disclose, distribute or retain this communication or any part of it. Instead, please delete all copies of this communication from your computer system and notify the sender immediately by reply email. Thank you.
