Multiple stanzas unusable: /usr/bin/dsmc already running.
Dear List, for a client with large filespaces, we would like to split the backup up into several nodes in order to balance the load. On the basis of the TSM-client documentation we created several stanzas in the dsm.sys file with different servername entries. In the init-script several dsmc processes are started with the -servername option referring to those stanzas. Now everything works fine with a 6.2.0.0 client (all processes are started and are backing up as expected). On a very similar box with client version 6.2.4.4 something goes wrong: Some dsmc processes are started successfully, some are not, the numbers vary. So there could be some runtime condition. The error message (printed on stdout) is: /usr/bin/dsmc already running. Has anybody observed this issue and knows about a solution? Best regards, Ethan
Re: Calculate PVUs for NDMP-backups
According to: http://www.spec.org/sfs2008/results/res2012q1/sfs2008-20120201-00205.htmlthere are two E8400 dual-cores, so I'll guess 400 PVU's. But it's better to contact IBM Sales for this. Regards, Maurice van 't Loo http://mvantloo.nl/ 2012/12/11 Hans Christian Riksheim bull...@gmail.com Hitachi 3090
Re: Multiple stanzas unusable: /usr/bin/dsmc already running.
-Ethan Günther wrote: - for a client with large filespaces, we would like to split the backup up into several nodes in order to balance the load. On the basis of the TSM-client documentation we created several stanzas in the dsm.sys file with different servername entries. In the init-script several dsmc processes are started with the -servername option referring to those stanzas. Now everything works fine with a 6.2.0.0 client (all processes are started and are backing up as expected). On a very similar box with client version 6.2.4.4 something goes wrong: Some dsmc processes are started successfully, some are not, the numbers vary. So there could be some runtime condition. The error message (printed on stdout) is: /usr/bin/dsmc already running. Has anybody observed this issue and knows about a solution? Are you using the style of script that does the following? * Store the process ID in a specific file after a successful start. * Delete the ID file after stopping dsmc. * Refuse a request to start dsmc if the ID file exists and contains the ID of a running dsmc process. If so, I suspect that the scripts are trying to use the same ID file for dmsc processes associated with different stanzas. Thomas Denier Thomas Jefferson University Hospital
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
Re: Multiple stanzas unusable: /usr/bin/dsmc already running.
Hello, Ethan. I've not seen this. Do they run if you start them manually? How about if you remove 6.2.4.4 and backlevel to 6.2.0.0 to match the working box? -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Ethan Günther Sent: Wednesday, December 12, 2012 1:43 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Multiple stanzas unusable: /usr/bin/dsmc already running. Dear List, for a client with large filespaces, we would like to split the backup up into several nodes in order to balance the load. On the basis of the TSM-client documentation we created several stanzas in the dsm.sys file with different servername entries. In the init-script several dsmc processes are started with the -servername option referring to those stanzas. Now everything works fine with a 6.2.0.0 client (all processes are started and are backing up as expected). On a very similar box with client version 6.2.4.4 something goes wrong: Some dsmc processes are started successfully, some are not, the numbers vary. So there could be some runtime condition. The error message (printed on stdout) is: /usr/bin/dsmc already running. Has anybody observed this issue and knows about a solution? Best regards, Ethan - No virus found in this message. Checked by AVG - www.avg.com Version: 2013.0.2793 / Virus Database: 2634/5938 - Release Date: 12/05/12 Internal Virus Database is out of date.
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.
