Question: V6.3 or V7.1 for a new system?
Dear all, reading the discussion about TSM 7.1 - should I upgrade or not seems to give me the answer for the question which version should I take for a completely new installation: for a new installation take TSM 7.1. but -- maybe some remarks are not given, what if so? therefore I do ask: Does anyone have remarks, experiences that suggest to take V6.3 instead of V7.1? Please tell me! We're going to use Linux on Dell R620 servers, i6k libraries and lto5/6 drives. thank you for any comment best regards Bjørn
Re: Question: V6.3 or V7.1 for a new system?
I would go with 7.1, I have it on 4 Windows 2008 R2 servers without any problems. The DB improvements are great, and the use of the Ops Manager has already provided to be very useful. :) All the best with the upgrade. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Nachtwey, Bjoern Sent: Friday, January 31, 2014 5:27 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Question: V6.3 or V7.1 for a new system? Dear all, reading the discussion about TSM 7.1 - should I upgrade or not seems to give me the answer for the question which version should I take for a completely new installation: for a new installation take TSM 7.1. but -- maybe some remarks are not given, what if so? therefore I do ask: Does anyone have remarks, experiences that suggest to take V6.3 instead of V7.1? Please tell me! We're going to use Linux on Dell R620 servers, i6k libraries and lto5/6 drives. thank you for any comment best regards Bjørn
Bad tape question
Hi roger, Thanks for the reply, i don't have another drive (the other is HS) I'am trying to do the fix=no and come to the result. Regards, Mickael +-- |This was sent by bobpatrick808...@yahoo.fr via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: Question: V6.3 or V7.1 for a new system?
For us, we're growing quickly enough that it's always easier to upgrade/install the newest version today than it is tomorrow. If you think your site will be significantly bigger in the next couple years, I would go with v7.1 and save yourself the upgrade hassle. We went with v6.1 on our new TSM servers when v6.1 was new, and our existing systems were all v5.5. v6.1 was kind of rough, but IBM was very responsive in finding workarounds for our problems, and eventually patched all the bugs. I expect v7.1 to be much more polished than v6.1, since the database backend isn't changing this time. On Fri, Jan 31, 2014 at 10:27:10AM +, Nachtwey, Bjoern wrote: Dear all, reading the discussion about TSM 7.1 - should I upgrade or not seems to give me the answer for the question which version should I take for a completely new installation: for a new installation take TSM 7.1. but -- maybe some remarks are not given, what if so? therefore I do ask: Does anyone have remarks, experiences that suggest to take V6.3 instead of V7.1? Please tell me! We're going to use Linux on Dell R620 servers, i6k libraries and lto5/6 drives. thank you for any comment best regards Bjørn -- -- Skylar Thompson (skyl...@u.washington.edu) -- Genome Sciences Department, System Administrator -- Foege Building S046, (206)-685-7354 -- University of Washington School of Medicine
preschedule / postschedule cmds for linux
Can any one share the syntax for preschedule / postschedule cmds for linux Thanks, Tim Brown Supervisor Computer Operations Central Hudson Gas Electric 284 South Ave Poughkeepsie, NY 12601 Email: tbr...@cenhud.commailto:tbr...@cenhud.com mailto:tbr...@cenhud.com Phone: 845-486-5643 Fax: 845-486-5921 Cell: 845-235-4255 This message contains confidential information and is only for the intended recipient. 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, please notify the sender immediately by replying to this note and deleting all copies and attachments.
Re: preschedule / postschedule cmds for linux
Each option takes a path to an executable, which could be compiled code, Perl, shell, etc. It runs with the same environment as the scheduler so you can access all the environment variables that the scheduler process itself sees. On Fri, Jan 31, 2014 at 06:46:52PM +, Tim Brown wrote: Can any one share the syntax for preschedule / postschedule cmds for linux -- -- Skylar Thompson (skyl...@u.washington.edu) -- Genome Sciences Department, System Administrator -- Foege Building S046, (206)-685-7354 -- University of Washington School of Medicine
Informal Poll: General question about use of policysets
The TSM books show that you can have multiple policysets per domain. I don't mean just the active vs inactive, but you can have multiple policysets like NORMAL, OFFHOUR, WEEKEND, within one domain, and switch them back and forth. I've never done that, or had a reason to. Seems inordinately confusing to me. All my customers just have one policyset per domain, with the active and inactive copy. The inactive is the one you update, then you validate it and activate it. Can I get some feedback on what other people do? Do you have just one unique policyset per domain? Or what is your use case for having multiples? Thank you!!! Wanda **Please note new office phone: Wanda Prather | Senior Technical Specialist | wanda.prat...@icfi.com | www.icfi.comhttp://www.icfi.com | 410-868-4872 (m) ICF International | 7125 Thomas Edison Dr., Suite 100, Columbia, Md |443-718-4900 (o)
Re: Informal Poll: General question about use of policysets
We have the minimal STANDARD (writable) and ACTIVE policysets for our domains. Domains are assigned by billable unit (lab, institute, cost center, etc.). I've never come up with a purpose for multiple policysets, so I also would be curious to know if one exists. On Fri, Jan 31, 2014 at 09:22:13PM +, Prather, Wanda wrote: The TSM books show that you can have multiple policysets per domain. I don't mean just the active vs inactive, but you can have multiple policysets like NORMAL, OFFHOUR, WEEKEND, within one domain, and switch them back and forth. I've never done that, or had a reason to. Seems inordinately confusing to me. All my customers just have one policyset per domain, with the active and inactive copy. The inactive is the one you update, then you validate it and activate it. Can I get some feedback on what other people do? Do you have just one unique policyset per domain? Or what is your use case for having multiples? Thank you!!! Wanda **Please note new office phone: Wanda Prather | Senior Technical Specialist | wanda.prat...@icfi.com | www.icfi.comhttp://www.icfi.com | 410-868-4872 (m) ICF International | 7125 Thomas Edison Dr., Suite 100, Columbia, Md |443-718-4900 (o) -- -- Skylar Thompson (skyl...@u.washington.edu) -- Genome Sciences Department, System Administrator -- Foege Building S046, (206)-685-7354 -- University of Washington School of Medicine
Re: nformal Poll: General question about use of policyset
Hi Wanda, It's an interesting question, and I hope you get many interesting answers. We only have one policyset per domain, partly from a lack of understandng of what's possible, and the other part from a lack of imagination. We try not to create a smorgasbord of TSM backup types and cycles. Best wishes, Keith Arbogast Indiana University
Re: nformal Poll: General question about use of policyset
When it comes to backups, simplicity is good. I try not to design anything that I cannot document succinctly. On Fri, Jan 31, 2014 at 04:35:12PM -0500, Keith Arbogast wrote: Hi Wanda, It's an interesting question, and I hope you get many interesting answers. We only have one policyset per domain, partly from a lack of understandng of what's possible, and the other part from a lack of imagination. We try not to create a smorgasbord of TSM backup types and cycles. Best wishes, Keith Arbogast Indiana University -- -- Skylar Thompson (skyl...@u.washington.edu) -- Genome Sciences Department, System Administrator -- Foege Building S046, (206)-685-7354 -- University of Washington School of Medicine
Re: Informal Poll: General question about use of policysets
Hi Wanda, Scenario 1: I am making multiple changes to my policy set. However, in case I mess something up, I'll first make a backup copy (of the inactive policy set) which will let me throw away my changes if I mess something up. copy policyset standard standard standard_2014-01-31 Scenario 1a: Alternative to the first scenario: I'll make a copy of the policy set, then make my changes to the new copy. I'll have the original one lying around in case I need to revert. copy policyset standard ps_2013-12-20 ps_2014-01-31 Scenario 2: I am going to activate my latest policy set. However, in case something goes wrong and I need to revert, I'll make a backup copy of the active policy set first: copy policyset standard active active_bkup activate policyset standard ps_2014-01-31 Best regards, - Andy Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead | stor...@us.ibm.com IBM Tivoli Storage Manager links: Product support: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager Online documentation: https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli +Documentation+Central/page/Tivoli+Storage+Manager Product Wiki: https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli +Storage+Manager/page/Home ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 2014-01-31 16:22:13: From: Prather, Wanda wanda.prat...@icfi.com To: ADSM-L@vm.marist.edu, Date: 2014-01-31 16:23 Subject: Informal Poll: General question about use of policysets Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu The TSM books show that you can have multiple policysets per domain. I don't mean just the active vs inactive, but you can have multiple policysets like NORMAL, OFFHOUR, WEEKEND, within one domain, and switch them back and forth. I've never done that, or had a reason to. Seems inordinately confusing to me. All my customers just have one policyset per domain, with the active and inactive copy. The inactive is the one you update, then you validate it and activate it. Can I get some feedback on what other people do? Do you have just one unique policyset per domain? Or what is your use case for having multiples? Thank you!!! Wanda **Please note new office phone: Wanda Prather | Senior Technical Specialist | wanda.prat...@icfi.com | www.icfi.comhttp://www.icfi.com | 410-868-4872 (m) ICF International | 7125 Thomas Edison Dr., Suite 100, Columbia, Md |443-718-4900 (o)
Re: Informal Poll: General question about use of policysets
Ah, that's a great idea. I've always captured the old settings to a file before making changes, but this makes it much faster and more reliable to recover. On Fri, Jan 31, 2014 at 04:48:25PM -0500, Andrew Raibeck wrote: Hi Wanda, Scenario 1: I am making multiple changes to my policy set. However, in case I mess something up, I'll first make a backup copy (of the inactive policy set) which will let me throw away my changes if I mess something up. copy policyset standard standard standard_2014-01-31 Scenario 1a: Alternative to the first scenario: I'll make a copy of the policy set, then make my changes to the new copy. I'll have the original one lying around in case I need to revert. copy policyset standard ps_2013-12-20 ps_2014-01-31 Scenario 2: I am going to activate my latest policy set. However, in case something goes wrong and I need to revert, I'll make a backup copy of the active policy set first: copy policyset standard active active_bkup activate policyset standard ps_2014-01-31 Best regards, - Andy Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead | stor...@us.ibm.com IBM Tivoli Storage Manager links: Product support: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager Online documentation: https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli +Documentation+Central/page/Tivoli+Storage+Manager Product Wiki: https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli +Storage+Manager/page/Home ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 2014-01-31 16:22:13: From: Prather, Wanda wanda.prat...@icfi.com To: ADSM-L@vm.marist.edu, Date: 2014-01-31 16:23 Subject: Informal Poll: General question about use of policysets Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu The TSM books show that you can have multiple policysets per domain. I don't mean just the active vs inactive, but you can have multiple policysets like NORMAL, OFFHOUR, WEEKEND, within one domain, and switch them back and forth. I've never done that, or had a reason to. Seems inordinately confusing to me. All my customers just have one policyset per domain, with the active and inactive copy. The inactive is the one you update, then you validate it and activate it. Can I get some feedback on what other people do? Do you have just one unique policyset per domain? Or what is your use case for having multiples? Thank you!!! Wanda **Please note new office phone: Wanda Prather | Senior Technical Specialist | wanda.prat...@icfi.com | www.icfi.comhttp://www.icfi.com | 410-868-4872 (m) ICF International | 7125 Thomas Edison Dr., Suite 100, Columbia, Md |443-718-4900 (o) -- -- Skylar Thompson (skyl...@u.washington.edu) -- Genome Sciences Department, System Administrator -- Foege Building S046, (206)-685-7354 -- University of Washington School of Medicine
Re: Informal Poll: General question about use of policysets
Only come across a need once in 16-years of working with *SM. This customer wanted to do periodic full backups. So I had a policy set with set to the default MODE=MODIFIED and another set to MODE=ABSOLUTE. They would activate the full policy set when they wanted to do the complete refresh. And then re-active the incremental policy set. I explained all the downsides to this, but the manager said he had experience with TSM and wanted the full so that all the data for the servers would be somewhat collocated again on the tapes without having to do collocation. That was the only time or reason I saw for multiple policy sets in a domain. Bill Everyday is a Holiday. Every Formation a Parade. Every Meal a feast.. And. Every Village has their idiot.. - ? -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Prather, Wanda Sent: Friday, January 31, 2014 4:22 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Informal Poll: General question about use of policysets The TSM books show that you can have multiple policysets per domain. I don't mean just the active vs inactive, but you can have multiple policysets like NORMAL, OFFHOUR, WEEKEND, within one domain, and switch them back and forth. I've never done that, or had a reason to. Seems inordinately confusing to me. All my customers just have one policyset per domain, with the active and inactive copy. The inactive is the one you update, then you validate it and activate it. Can I get some feedback on what other people do? Do you have just one unique policyset per domain? Or what is your use case for having multiples? Thank you!!! Wanda **Please note new office phone: Wanda Prather | Senior Technical Specialist | wanda.prat...@icfi.com | www.icfi.comhttp://www.icfi.com | 410-868-4872 (m) ICF International | 7125 Thomas Edison Dr., Suite 100, Columbia, Md |443-718-4900 (o)
Re: Informal Poll: General question about use of policysets
I’ve never been at a site that used more than one policy set. But if I had been at either of two sites that had to implement infinite “legal holds” when that order actually came, I’d have used a new policy set to do exactly that. That’s the only situation in which I’d use that option. Nick On Jan 31, 2014, at 3:22 PM, Prather, Wanda wanda.prat...@icfi.com wrote: The TSM books show that you can have multiple policysets per domain. I don't mean just the active vs inactive, but you can have multiple policysets like NORMAL, OFFHOUR, WEEKEND, within one domain, and switch them back and forth. I've never done that, or had a reason to. Seems inordinately confusing to me. All my customers just have one policyset per domain, with the active and inactive copy. The inactive is the one you update, then you validate it and activate it. Can I get some feedback on what other people do? Do you have just one unique policyset per domain? Or what is your use case for having multiples? Thank you!!! Wanda **Please note new office phone: Wanda Prather | Senior Technical Specialist | wanda.prat...@icfi.com | www.icfi.comhttp://www.icfi.com | 410-868-4872 (m) ICF International | 7125 Thomas Edison Dr., Suite 100, Columbia, Md |443-718-4900 (o)
Re: Informal Poll: General question about use of policysets
I have 2 policysets in each domain. They are identical except for the copygroup destination parameter. This is the design I came up with to implement 6.1 with dedup. Backups come into an ingest pool on hi-speed disk (bkp_1a) while policyset set_a is active. At 5 am, a schedule/script activates policyset set_b so that sessions for the next 24 hours will write to pool bkp_1b. After the switch, more schedules/scripts do id dup, copypooling and migration so that pool bkp_1a is empty and ready for the next policyset flip. That was the theory. Unfortunately, the server resources couldn't keep up. And migrated volumes weren't deleted because of the whole dereferenced chunk problem set. I still do the policyset flip/flop (on 4 servers), but id dup runs continuously and copypooling runs many times a day. Bill Colwell Draper lab -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Prather, Wanda Sent: Friday, January 31, 2014 4:22 PM To: ADSM-L@VM.MARIST.EDU Subject: Informal Poll: General question about use of policysets The TSM books show that you can have multiple policysets per domain. I don't mean just the active vs inactive, but you can have multiple policysets like NORMAL, OFFHOUR, WEEKEND, within one domain, and switch them back and forth. I've never done that, or had a reason to. Seems inordinately confusing to me. All my customers just have one policyset per domain, with the active and inactive copy. The inactive is the one you update, then you validate it and activate it. Can I get some feedback on what other people do? Do you have just one unique policyset per domain? Or what is your use case for having multiples? Thank you!!! Wanda **Please note new office phone: Wanda Prather | Senior Technical Specialist | wanda.prat...@icfi.com | www.icfi.comhttp://www.icfi.com | 410-868-4872 (m) ICF International | 7125 Thomas Edison Dr., Suite 100, Columbia, Md |443-718-4900 (o)
Re: Prevent client backups from failing over to tape stgpools
Brian TSM will only move a backup to the next pool when the pools are disk and sequential, not when sequential and sequential, so I suggest adding a dummy sequential pool with no volumes assigned in the middle. disk - dummy - tape I've come across this when using an intermediate file pool. It doesn't spill like a disk pool does should it fill up. Regards Steve Steven Harris TSM Admin Canberra Australia On 31/01/2014 8:24 AM, Skylar Thompson wrote: If the tape pool is in a separate device class from other storage pools, you could set the mount limit on the device class to 0. That's our strategy when we do library maintenance to allow operations to continue to/from our disk and file pools. On Thu, Jan 30, 2014 at 10:47:46AM -0800, Brian Kunst wrote: We???re in a situation where we want to temporarily prevent our users from ever writing directly to our tape drives. In the event that our primary random access stgpools hit 100% utilization, we want client backups to fail rather than failover over to the next, sequential access stgpool. As far as I can see, there are two ways to accomplish this: 1) Set maxnummp for all nodes to 0. This should prevent them from access a tape drive when backing up, but would also prevent them from access a tape drive to do a restore. Clearly not a good option. 2) Set the Next Storage Pool value for the primary random access stgpools to null. With this method, migrations would no longer work, but we could still move data to tape using the ???move data??? command on the random access volumes. I???m leaning towards option 2, but I would like to know if anyone cam think of another way to prevent client backups from going directly to the tape drives. Thanks, -- Brian Kunst Storage Administrator Large Scale Storage Systems UW Information Technology -- -- Skylar Thompson (skyl...@u.washington.edu) -- Genome Sciences Department, System Administrator -- Foege Building S046, (206)-685-7354 -- University of Washington School of Medicine
