Advice about configure DB2 Logs backups on a windows server
I want to configure DB2 logs backups on a windows server. Where can I find a good source to implement this? Sorry for my grammar, my native language isn't english +-- |This was sent by cyosh...@its-csi.com.pe via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: Dear Tuscon
On Mar 20, 2009, at 1:05 PM, David E Ehresman wrote: Gee. Our 3592 tapes cost somewhere around 100 dollars. We keep 5 days worth of TSM DB backups. $500 is real cheap in order to keep a copy of our most important DR resource on our most reliable backup medium. Everyone's different. When a shop is small enough that they only buy 20 3592 tapes for their new TSM image, it's hard to tell them that they need to set aside however many for once-a-week off-site backups of the TSM DB and however more so they can do daily TSM DB backups. Stacking DB backups for the on-site tapes would be nice.
Re: VTL and Dedup ( TS7569G)
LOL -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Clark, Robert A Sent: Friday, March 20, 2009 7:44 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] VTL and Dedup ( TS7569G) Dedupe is an errand boy, sent by the storage industry, to collect a bill. Dedupe is the enemy of throughput. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of W. Curtis Preston Sent: Friday, March 20, 2009 4:25 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] VTL and Dedup ( TS7569G) Why do you hate all things dedupe? -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kelly Lipp Sent: Friday, March 20, 2009 10:12 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] VTL and Dedup ( TS7569G) Funny, but I was researching the TS7650 yesterday and found this article on the IBM website. Pretty good detail about the product in a non-TSM environment. ftp://service.boulder.ibm.com/storage/tape/ts7650g_esg_validation.pdf And then this on in the TSM environment. I think this one might have been written by somebody somewhat less familiar with TSM than we would be. Seemed a little heavy handed about TSM. ftp://ftp.software.ibm.com/common/ssi/sa/wh/n/tsw03043usen/TSW03043USEN. PDF My overall impression, and I hate all things de-dup, was this is a pretty good product offering. I'm sure it's way expensive but understand there are some follow on products coming that will address the lower end of this market. Thanks, Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Alex Paschal Sent: Friday, March 20, 2009 11:03 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] VTL and Dedup ( TS7569G) Hi, Sabar. I couldn't find a TS7569G via Google, but on the TS7650G, also a deduping VTL, after data goes through the factoring (dedup) algorithm it is run through a compression algorithm. You probably won't see much deduplication, but on the first backup you should see a decrease in size similar to the decrease you would see from the compression on a tape drive. Regards, Alex -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Sabar Martin Hasiholan Panggabean Sent: Thursday, March 19, 2009 5:10 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] VTL and Dedup ( TS7569G) Hi, Does anyone here has been implementing or know how Dedup works in TSM using TS7569G ? Let say I have 100 TB of data and backup to this VTL. On the 1st attempt of backup / full backup, will this data size decrease on the VTL BR, Martin P This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication. Thank you. DISCLAIMER: This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message. IMPORTANT: E-mail sent through the Internet is not secure and timely delivery of Internet mail is not guaranteed. Legg Mason therefore, recommends that you do not send any action-oriented or time-sensitive information to us via electronic mail, or any confidential or sensitive information including: social security numbers, account numbers, or personal identification numbers. This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not use, copy or disclose to anyone any information contained in this message. If you have received this message in error, please notify the author by replying to this message and then kindly delete the message. Thank you.
Re: VTL and Dedup ( TS7569G)
Dedupe is an errand boy, sent by the storage industry, to collect a bill. Dedupe is the enemy of throughput. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of W. Curtis Preston Sent: Friday, March 20, 2009 4:25 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] VTL and Dedup ( TS7569G) Why do you hate all things dedupe? -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kelly Lipp Sent: Friday, March 20, 2009 10:12 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] VTL and Dedup ( TS7569G) Funny, but I was researching the TS7650 yesterday and found this article on the IBM website. Pretty good detail about the product in a non-TSM environment. ftp://service.boulder.ibm.com/storage/tape/ts7650g_esg_validation.pdf And then this on in the TSM environment. I think this one might have been written by somebody somewhat less familiar with TSM than we would be. Seemed a little heavy handed about TSM. ftp://ftp.software.ibm.com/common/ssi/sa/wh/n/tsw03043usen/TSW03043USEN. PDF My overall impression, and I hate all things de-dup, was this is a pretty good product offering. I'm sure it's way expensive but understand there are some follow on products coming that will address the lower end of this market. Thanks, Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Alex Paschal Sent: Friday, March 20, 2009 11:03 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] VTL and Dedup ( TS7569G) Hi, Sabar. I couldn't find a TS7569G via Google, but on the TS7650G, also a deduping VTL, after data goes through the factoring (dedup) algorithm it is run through a compression algorithm. You probably won't see much deduplication, but on the first backup you should see a decrease in size similar to the decrease you would see from the compression on a tape drive. Regards, Alex -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Sabar Martin Hasiholan Panggabean Sent: Thursday, March 19, 2009 5:10 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] VTL and Dedup ( TS7569G) Hi, Does anyone here has been implementing or know how Dedup works in TSM using TS7569G ? Let say I have 100 TB of data and backup to this VTL. On the 1st attempt of backup / full backup, will this data size decrease on the VTL BR, Martin P This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication. Thank you. DISCLAIMER: This message is intended for the sole use of the addressee, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If you are not the addressee you are hereby notified that you may not use, copy, disclose, or distribute to anyone the message or any information contained in the message. If you have received this message in error, please immediately advise the sender by reply email and delete this message.
Re: Server platform comparison
Hashed many times over the past several months. Might check the archives. Should be based on knowledge within the organization. Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mark Devine Sent: Friday, March 20, 2009 3:38 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Server platform comparison I haven't googled it just yet, but I though you folks may have references as to the best TSM server platform. Currently targeted for AIX, but the server consolidation crew is throwing around HP & Linux. Any URL's would be greatly appreciated. TIA
Re: VTL and Dedup ( TS7569G)
Why do you hate all things dedupe? -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kelly Lipp Sent: Friday, March 20, 2009 10:12 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] VTL and Dedup ( TS7569G) Funny, but I was researching the TS7650 yesterday and found this article on the IBM website. Pretty good detail about the product in a non-TSM environment. ftp://service.boulder.ibm.com/storage/tape/ts7650g_esg_validation.pdf And then this on in the TSM environment. I think this one might have been written by somebody somewhat less familiar with TSM than we would be. Seemed a little heavy handed about TSM. ftp://ftp.software.ibm.com/common/ssi/sa/wh/n/tsw03043usen/TSW03043USEN.PDF My overall impression, and I hate all things de-dup, was this is a pretty good product offering. I'm sure it's way expensive but understand there are some follow on products coming that will address the lower end of this market. Thanks, Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Alex Paschal Sent: Friday, March 20, 2009 11:03 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] VTL and Dedup ( TS7569G) Hi, Sabar. I couldn't find a TS7569G via Google, but on the TS7650G, also a deduping VTL, after data goes through the factoring (dedup) algorithm it is run through a compression algorithm. You probably won't see much deduplication, but on the first backup you should see a decrease in size similar to the decrease you would see from the compression on a tape drive. Regards, Alex -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Sabar Martin Hasiholan Panggabean Sent: Thursday, March 19, 2009 5:10 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] VTL and Dedup ( TS7569G) Hi, Does anyone here has been implementing or know how Dedup works in TSM using TS7569G ? Let say I have 100 TB of data and backup to this VTL. On the 1st attempt of backup / full backup, will this data size decrease on the VTL BR, Martin P This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication. Thank you.
Server platform comparison
I haven't googled it just yet, but I though you folks may have references as to the best TSM server platform. Currently targeted for AIX, but the server consolidation crew is throwing around HP & Linux. Any URL's would be greatly appreciated. TIA
Re: Dear Tuscon
I go a step further - I want the ability to cut two matching copies of the database backup to two tapes simultaneously. I'm currently running two backups back-to-back, but I'm unable to have sessions disabled for 40 minutes, so they are NOT identical backups. Tom -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Wanda Prather Sent: Friday, March 20, 2009 2:24 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Dear Tuscon I agree. I want my TSM DB backup on the MOST RELIABLE MEDIA/DEVICE I CAN GET. If you EVER need that DB backup tape, it's because you are already in deep do-do, and in a hurry to fix it. The last thing you'll want to deal with is the risk of encountering an I/O error on a DB restore... On Fri, Mar 20, 2009 at 2:05 PM, David E Ehresman wrote: > Gee. Our 3592 tapes cost somewhere around 100 dollars. We keep 5 days > worth of TSM DB backups. $500 is real cheap in order to keep a copy of our > most important DR resource on our most reliable backup medium. > > David Ehresman > University of Louisville > > >>> Nick Laflamme 3/20/2009 10:39 AM >>> > My heart leapt when my RSS reader presented me an article in the TSM > udpates feed from IBM with the heading, "Keeping more than one TSM > server database backup on a tape." As I'm implementing a new server > using 3592 drives, I haven't been happy with my options for this > particular issue. Maybe, I thought, I was about to learn something of > immediate use and high value! > > My heart sank when I read the actual article, which might be > paraphrased as, "Sorry, Charlie, too risky." > > Back to asking for some LTO drives just for small, inexpensive tapes > for DB backups. > 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.
Re: Dear Tuscon
I agree. I want my TSM DB backup on the MOST RELIABLE MEDIA/DEVICE I CAN GET. If you EVER need that DB backup tape, it's because you are already in deep do-do, and in a hurry to fix it. The last thing you'll want to deal with is the risk of encountering an I/O error on a DB restore... On Fri, Mar 20, 2009 at 2:05 PM, David E Ehresman wrote: > Gee. Our 3592 tapes cost somewhere around 100 dollars. We keep 5 days > worth of TSM DB backups. $500 is real cheap in order to keep a copy of our > most important DR resource on our most reliable backup medium. > > David Ehresman > University of Louisville > > >>> Nick Laflamme 3/20/2009 10:39 AM >>> > My heart leapt when my RSS reader presented me an article in the TSM > udpates feed from IBM with the heading, "Keeping more than one TSM > server database backup on a tape." As I'm implementing a new server > using 3592 drives, I haven't been happy with my options for this > particular issue. Maybe, I thought, I was about to learn something of > immediate use and high value! > > My heart sank when I read the actual article, which might be > paraphrased as, "Sorry, Charlie, too risky." > > Back to asking for some LTO drives just for small, inexpensive tapes > for DB backups. >
Re: VTL and Dedup ( TS7569G)
Hi, Kelly. Heh, you're right, that's a pretty funny document on the TSM side. I was of the same mind about dedup until I started getting familiar with the TS7650. The fact that it's in-line and that it does a binary diff after signature match addresses most of the concerns that I had. And I agree, it is expensive, but as a DR-tool it offers a lot of benefit. I get the heebie-jeebies thinking about not having tape involved at all in DR, so I guess I just have to figure out what requirements have to be met before I can feel good about using the "eliminate your tape" line. :-) I've recently found out IBM offers TS7650 "appliance" models that come packaged with disk and everything. Less setup, less angst, just plug it in and go. With 7TB, 18TB, and 36TB options, these appliances could be good for smaller sites. Thanks, Alex -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kelly Lipp Sent: Friday, March 20, 2009 10:12 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] VTL and Dedup ( TS7569G) Funny, but I was researching the TS7650 yesterday and found this article on the IBM website. Pretty good detail about the product in a non-TSM environment. ftp://service.boulder.ibm.com/storage/tape/ts7650g_esg_validation.pdf And then this on in the TSM environment. I think this one might have been written by somebody somewhat less familiar with TSM than we would be. Seemed a little heavy handed about TSM. ftp://ftp.software.ibm.com/common/ssi/sa/wh/n/tsw03043usen/TSW03043USEN. PDF My overall impression, and I hate all things de-dup, was this is a pretty good product offering. I'm sure it's way expensive but understand there are some follow on products coming that will address the lower end of this market. Thanks, Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Alex Paschal Sent: Friday, March 20, 2009 11:03 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] VTL and Dedup ( TS7569G) Hi, Sabar. I couldn't find a TS7569G via Google, but on the TS7650G, also a deduping VTL, after data goes through the factoring (dedup) algorithm it is run through a compression algorithm. You probably won't see much deduplication, but on the first backup you should see a decrease in size similar to the decrease you would see from the compression on a tape drive. Regards, Alex -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Sabar Martin Hasiholan Panggabean Sent: Thursday, March 19, 2009 5:10 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] VTL and Dedup ( TS7569G) Hi, Does anyone here has been implementing or know how Dedup works in TSM using TS7569G ? Let say I have 100 TB of data and backup to this VTL. On the 1st attempt of backup / full backup, will this data size decrease on the VTL BR, Martin P This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication. Thank you. This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication. Thank you.
Re: Dear Tuscon
Gee. Our 3592 tapes cost somewhere around 100 dollars. We keep 5 days worth of TSM DB backups. $500 is real cheap in order to keep a copy of our most important DR resource on our most reliable backup medium. David Ehresman University of Louisville >>> Nick Laflamme 3/20/2009 10:39 AM >>> My heart leapt when my RSS reader presented me an article in the TSM udpates feed from IBM with the heading, "Keeping more than one TSM server database backup on a tape." As I'm implementing a new server using 3592 drives, I haven't been happy with my options for this particular issue. Maybe, I thought, I was about to learn something of immediate use and high value! My heart sank when I read the actual article, which might be paraphrased as, "Sorry, Charlie, too risky." Back to asking for some LTO drives just for small, inexpensive tapes for DB backups.
Re: VTL and Dedup ( TS7569G)
We've got a TS7560G (with an XIV as backend storage) here now for trial and sof ar it works like a dream. Met vriendelijke groet, with kind regards, Richard van Denzel. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kelly Lipp Sent: 20 March 2009 18:12 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] VTL and Dedup ( TS7569G) Funny, but I was researching the TS7650 yesterday and found this article on the IBM website. Pretty good detail about the product in a non-TSM environment. ftp://service.boulder.ibm.com/storage/tape/ts7650g_esg_validation.pdf And then this on in the TSM environment. I think this one might have been written by somebody somewhat less familiar with TSM than we would be. Seemed a little heavy handed about TSM. ftp://ftp.software.ibm.com/common/ssi/sa/wh/n/tsw03043usen/TSW03043USEN. PDF My overall impression, and I hate all things de-dup, was this is a pretty good product offering. I'm sure it's way expensive but understand there are some follow on products coming that will address the lower end of this market. Thanks, Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Alex Paschal Sent: Friday, March 20, 2009 11:03 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] VTL and Dedup ( TS7569G) Hi, Sabar. I couldn't find a TS7569G via Google, but on the TS7650G, also a deduping VTL, after data goes through the factoring (dedup) algorithm it is run through a compression algorithm. You probably won't see much deduplication, but on the first backup you should see a decrease in size similar to the decrease you would see from the compression on a tape drive. Regards, Alex -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Sabar Martin Hasiholan Panggabean Sent: Thursday, March 19, 2009 5:10 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] VTL and Dedup ( TS7569G) Hi, Does anyone here has been implementing or know how Dedup works in TSM using TS7569G ? Let say I have 100 TB of data and backup to this VTL. On the 1st attempt of backup / full backup, will this data size decrease on the VTL BR, Martin P This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication. Thank you.
Re: TSM TDP Oracle - Expiration Opinions
We have the same setup. TDPO backups go to separate nodes that have use their own pool. We have ongoing problems with RMAN deletes not changing the file in TSM (rman backup pieces) to inactive status, which are then removed during expiration. We don't know if it's RMAN, TDPO, or us with the problem. Our DBA's run TDPOSYNC fairly often to fix things up. Something is wrong and we just haven't had time to track it down. I have a script that queries the TSM backups table for files (rman backup pieces) that are older than our retension period. I run it once a week. Rick "Gee, Norman" To Sent by: "ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager" Re: TSM TDP Oracle - Expiration Opinions 03/20/2009 01:27 PM Please respond to "ADSM: Dist Stor Manager" You will have to let RMAN do its job. Every RMAN backup piece and sets have unique file names and will never place a prior backup into an inactive status. How would you expire a RMAN backup since every backup piece is still active? Short of mass delete on filespace. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Hart, Charles A Sent: Friday, March 20, 2009 9:30 AM To: ADSM-L@VM.MARIST.EDU Subject: TSM TDP Oracle - Expiration Opinions We currently have your Oracle TDP Clients setup as a Separate node in separate a separate domain down to the storage pool hierarchy. That said we are having challenges with DBA's and their RMAN delete scripts for various reasons. According to the TDP for DB manual its recommended to have the RMAN catalog maintain retention which I would agree with but we are little success, and end up filling up virtual tape subsystems, orphaning data etc. The enough now is to have TSM maintain the RMAN retention and the DBA's would just clean their RMAN catalog with a crosscheck and delete process. What do you? Do you let RMAN maintain Retention or TSM maintain pitfalls of either? Best Regards, Charles Hart This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. - The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.
Re: TSM TDP Oracle - Expiration Opinions
You will have to let RMAN do its job. Every RMAN backup piece and sets have unique file names and will never place a prior backup into an inactive status. How would you expire a RMAN backup since every backup piece is still active? Short of mass delete on filespace. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Hart, Charles A Sent: Friday, March 20, 2009 9:30 AM To: ADSM-L@VM.MARIST.EDU Subject: TSM TDP Oracle - Expiration Opinions We currently have your Oracle TDP Clients setup as a Separate node in separate a separate domain down to the storage pool hierarchy. That said we are having challenges with DBA's and their RMAN delete scripts for various reasons. According to the TDP for DB manual its recommended to have the RMAN catalog maintain retention which I would agree with but we are little success, and end up filling up virtual tape subsystems, orphaning data etc. The enough now is to have TSM maintain the RMAN retention and the DBA's would just clean their RMAN catalog with a crosscheck and delete process. What do you? Do you let RMAN maintain Retention or TSM maintain pitfalls of either? Best Regards, Charles Hart This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.
Re: VTL and Dedup ( TS7569G)
Funny, but I was researching the TS7650 yesterday and found this article on the IBM website. Pretty good detail about the product in a non-TSM environment. ftp://service.boulder.ibm.com/storage/tape/ts7650g_esg_validation.pdf And then this on in the TSM environment. I think this one might have been written by somebody somewhat less familiar with TSM than we would be. Seemed a little heavy handed about TSM. ftp://ftp.software.ibm.com/common/ssi/sa/wh/n/tsw03043usen/TSW03043USEN.PDF My overall impression, and I hate all things de-dup, was this is a pretty good product offering. I'm sure it's way expensive but understand there are some follow on products coming that will address the lower end of this market. Thanks, Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Alex Paschal Sent: Friday, March 20, 2009 11:03 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] VTL and Dedup ( TS7569G) Hi, Sabar. I couldn't find a TS7569G via Google, but on the TS7650G, also a deduping VTL, after data goes through the factoring (dedup) algorithm it is run through a compression algorithm. You probably won't see much deduplication, but on the first backup you should see a decrease in size similar to the decrease you would see from the compression on a tape drive. Regards, Alex -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Sabar Martin Hasiholan Panggabean Sent: Thursday, March 19, 2009 5:10 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] VTL and Dedup ( TS7569G) Hi, Does anyone here has been implementing or know how Dedup works in TSM using TS7569G ? Let say I have 100 TB of data and backup to this VTL. On the 1st attempt of backup / full backup, will this data size decrease on the VTL BR, Martin P This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication. Thank you.
Re: VTL and Dedup ( TS7569G)
Hi, Sabar. I couldn't find a TS7569G via Google, but on the TS7650G, also a deduping VTL, after data goes through the factoring (dedup) algorithm it is run through a compression algorithm. You probably won't see much deduplication, but on the first backup you should see a decrease in size similar to the decrease you would see from the compression on a tape drive. Regards, Alex -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Sabar Martin Hasiholan Panggabean Sent: Thursday, March 19, 2009 5:10 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] VTL and Dedup ( TS7569G) Hi, Does anyone here has been implementing or know how Dedup works in TSM using TS7569G ? Let say I have 100 TB of data and backup to this VTL. On the 1st attempt of backup / full backup, will this data size decrease on the VTL BR, Martin P This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication. Thank you.
TSM TDP Oracle - Expiration Opinions
We currently have your Oracle TDP Clients setup as a Separate node in separate a separate domain down to the storage pool hierarchy. That said we are having challenges with DBA's and their RMAN delete scripts for various reasons. According to the TDP for DB manual its recommended to have the RMAN catalog maintain retention which I would agree with but we are little success, and end up filling up virtual tape subsystems, orphaning data etc. The enough now is to have TSM maintain the RMAN retention and the DBA's would just clean their RMAN catalog with a crosscheck and delete process. What do you? Do you let RMAN maintain Retention or TSM maintain pitfalls of either? Best Regards, Charles Hart This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.
Website and Call for Papers for TSM Symposium 2009
Please find updated information about the TSM Symposium at http://tsm2009.uni-koeln.de/ It is being hosted by University of Cologne in September 2009 taking place at Grandhotel Petersberg. At this time please consider submitting a paper proposal during the next days. Thanks and have a nice weekend, Claus -- Claus Kalle, Universitaet zu Koeln, RRZK i i Leiter Abteilung Systeme I I E-Mail: ka...@uni-koeln.deM M Fon: 0221 478 5580 /I\ Fax: 0221 478 86845 MiMiMiM Snail-Mail: Robert-Koch-Str. 10, 50931 Koeln MIMiMiM
Dear Tuscon
My heart leapt when my RSS reader presented me an article in the TSM udpates feed from IBM with the heading, "Keeping more than one TSM server database backup on a tape." As I'm implementing a new server using 3592 drives, I haven't been happy with my options for this particular issue. Maybe, I thought, I was about to learn something of immediate use and high value! My heart sank when I read the actual article, which might be paraphrased as, "Sorry, Charlie, too risky." Back to asking for some LTO drives just for small, inexpensive tapes for DB backups.
Re: Fwd: [ADSM-L] Mixing LTO2 and LTO4 drives and media in the same library
(War and Peace again - sorry): Thanks for all of your responses both on and off list. I've put some feelers out elsewhere on this too (many thanks if you're reading) and have had some interesting and contradictory responses! In summary, there do seem to be some folks out there running with exactly the proposed config below (i.e. LTO2 and LTO4 drives and media in the same logical/physical library, LTO2 used purely for offsite media generation) and, provided parameters such as MOUNTLIMIT are set carefully (as well as separate devclasses and stgpools of course), it is a happy configuration without undesired LTO2 > LTO4 cross pollination. The 'Implementing IBM Tape in Unix Systems' Redbook is an excellent read and talks about this configuration in one of its examples (going against my reading of the TSM Admin Guide): "As of Tivoli Storage Manager V5.3.5, LTO4 drives are supported, and any combination of LTO 2, 3, and 4 drives and media can be used in one library [...] Although LTO4 drives can read the LTO2 media (but cannot write to it), care should be taken to avoid attempted writing. Set the MOUNTLIMIT option for the LTO2 devclass to less than the sum of LTO2 and 3 drives (see the previous tip), thereby preventing the LTO2 media from being loaded in the LTO4 drives. The LTO2 media will still be available for normal use by the LTO2 [and 3] drives. "['Previous tip' - relates to different scenario but the point is still valid] Setting the MOUNTLIMIT parameter: For read or write tape mounts, Tivoli Storage Manager will select LTO3 drives for LTO3 media first. If no LTO3 devices are available, an available LTO4 drive will be selected for the LTO3 media. To prevent the case where all LTO4 drives are loaded with LTO3 media (leaving no drives available to read/write LTO4 media), set the DEVCLASS parameter MOUNTLIMIT appropriately. " The above is from section 5.11.1 of the Redbook. Given the headache of repartitioning the 3584 library from its base config into two partitions without ALMS (http://www-01.ibm.com/support/docview.wss?uid=swg21145429 gives an indication of this), its inherent inflexibility plus extra work required during the migration activity itself, I'm inclined to think that the single partition library solution above is the way to go after all. I would also be able to perform a good deal of the TSM Server work (defining devclasses, stgpools etc) prior to the migration weekend, de-risking the change somewhat. That's how I'm looking at the moment - many thanks again for your thoughts. /David Mc London, UK -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Baker, Jane Sent: 20 March 2009 08:19 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Fwd: [ADSM-L] Mixing LTO2 and LTO4 drives and media in the same library We have a 3584 with LTO2 & LTO3 which we use via logical partitioning, it works really well so would recommend that? As said previously as long as you have separate device classes and control paths neither will intermix. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Wanda Prather Sent: 19 March 2009 20:54 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Fwd: [ADSM-L] Mixing LTO2 and LTO4 drives and media in the same library TSM does support mixing media in the library, but I believe you are correct that with LTO2 + LTO4 drives and media, you will have a problem. I've included the text from the 5.5 TSM Admin Guide for Windows below. I interpret it to say that there is no way to keep an LTO2 scratch cartridge from landing in an LTO4 drive, and the LTO4 drive can't write to it and problems will ensue. You could indeed partition the library with ALMS. But the way I've gotten around this before with is to simply create two logical libraries in 1 physical library. (This would be especially convenient since you don't intend to keep this configuration very long.) CAVEAT: I have to say I haven't done this since TSM 5.3, so YMMV: Create a new TSM LTO4 library. Define the path for the library to point to the lbx.y.z.q device that Windows sees (this will be a control path in the library created on one of the LTO4 drives. This is usually done by the CE, but can be done easily from teh 3584 web interface.) Actually I think the path could also point to the original lba.b.c.d control point on the LTO2 drive, I don't think it matters. Define the LTO4 drives to the new LTO4 library. Your original library with the LTO2 drives will still exist just as it did before. Check in your LTO4 carts to the LTO4 library, make separate device classes and storage pools with no mixed media between them. The TSM server won't know or care that the 2 logical libraries only have 1 physical library. Again, I haven't done this with TSM 5.4 or 5.5, so test it. But it used to work. W +++ Mixing Different Media Generations in Libraries While the Tivoli Storag
Re: Fwd: [ADSM-L] Mixing LTO2 and LTO4 drives and media in the same library
We have a 3584 with LTO2 & LTO3 which we use via logical partitioning, it works really well so would recommend that? As said previously as long as you have separate device classes and control paths neither will intermix. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Wanda Prather Sent: 19 March 2009 20:54 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Fwd: [ADSM-L] Mixing LTO2 and LTO4 drives and media in the same library TSM does support mixing media in the library, but I believe you are correct that with LTO2 + LTO4 drives and media, you will have a problem. I've included the text from the 5.5 TSM Admin Guide for Windows below. I interpret it to say that there is no way to keep an LTO2 scratch cartridge from landing in an LTO4 drive, and the LTO4 drive can't write to it and problems will ensue. You could indeed partition the library with ALMS. But the way I've gotten around this before with is to simply create two logical libraries in 1 physical library. (This would be especially convenient since you don't intend to keep this configuration very long.) CAVEAT: I have to say I haven't done this since TSM 5.3, so YMMV: Create a new TSM LTO4 library. Define the path for the library to point to the lbx.y.z.q device that Windows sees (this will be a control path in the library created on one of the LTO4 drives. This is usually done by the CE, but can be done easily from teh 3584 web interface.) Actually I think the path could also point to the original lba.b.c.d control point on the LTO2 drive, I don't think it matters. Define the LTO4 drives to the new LTO4 library. Your original library with the LTO2 drives will still exist just as it did before. Check in your LTO4 carts to the LTO4 library, make separate device classes and storage pools with no mixed media between them. The TSM server won't know or care that the 2 logical libraries only have 1 physical library. Again, I haven't done this with TSM 5.4 or 5.5, so test it. But it used to work. W +++ Mixing Different Media Generations in Libraries While the Tivoli Storage Manager server now allows mixed device types in an automated library, the mixing of different generations of the same type of drive is still not supported. New drives cannot write the older media formats, and old drives cannot read new formats. If the new drive technology cannot write to media formatted by older generation drives, the older media must be marked read-only to avoid problems for server operations. Also, the older drives must be removed from the library. Some examples of combinations that the Tivoli Storage Manager server does not support in a single library are: v SDLT 220 drives with SDLT 320 drives v DLT 7000 drives with DLT 8000 drives v StorageTek 9940A drives with 9940B drives v UDO1 drives with UDO2 drives There are two exceptions to the rule against mixing generations of LTO Ultrium drives and media. The Tivoli Storage Manager server does support mixtures of the following types: v LTO Ultrium Generation 1 (LTO1) and LTO Ultrium Generation 2 (LTO2) v LTO Ultrium Generation 2 (LTO2) with LTO Ultrium Generation 3 (LTO3) v LTO Ultrium Generation 2 (LTO2) with LTO Ultrium Generation 3 (LTO3) and LTO Ultrium Generation 4 (LTO4) The server supports these mixtures because the different drives can read and write to the different media. If you plan to upgrade all drives to Generation 2 (or Generation 3 or Generation 4), first delete all existing Ultrium drive definitions and the paths associated with them. Then you can define the new Generation 2 (or Generation 3 or Generation 4) drives and paths. Notes: 1. LTO Ultrium Generation 3 drives can only read Generation 1 media. If you are mixing Ultrium Generation 1 and Ultrium Generation 3 drives and media in a single library, you must mark the Generation 1 media as read-only, and all Generation 1 scratch volumes must be checked out. 2. LTO Ultrium Generation 4 drives can only read Generation 2 media. If you are mixing Ultrium Generation 2 and Ultrium Generation 4 drives and media in a single library, you must mark the Generation 2 media as read-only, and all Generation 2 scratch volumes must be checked out. For a discussion of additional considerations when mixing LTO Ultrium generations, see "Defining and Updating LTO Device Classes" on page 245. Tivoli Storage Manager does support mixing of 3592 Generation 1 and Generation 2 drives and media. However, to minimize the potential for problems, use one of three special configurations. For details, see "Defining and Updating 3592 Device Classes" on page 237. If you plan to encrypt volumes in a library, do not mix media generations in the library. +++ On Thu, Mar 19, 2009 at 10:13 AM, David McClelland < david.mcclell...@networkc.co.uk> wrote: > Hi Team, > > I've a question about mixing LTO drives and media in