Slightly OT: ProtecTIER question
Guys A quick one, It's been a while, so I can't remember. Creating a new Virtual Library on a ProtecTIER, is that non-disruptive to existing Virtual libraries? If it makes a difference, it's the latest and greatest v2.4.1.0 Thanks Steven
TSM Operation Reporting
Hi All, Is there a free tool available which replaces the TSM Operational Reporting? And I don't mean the TSM Reporting & Monitoring (which is just a bunch of crap imho). I know about tools like TSM Reporter (PLCS) and TSMManager, but I just want a free tool which is quick and dirty and does what the old TSM Operatinal Reporting did and just mail me the quick overview of last night. Met vriendelijke groet, with kind regards, Richard van Denzel.
Looking for latest mac client documentation
Been looking through the information center and publications centers. The only mac documentation I can find is for client v5.5. Is there documentation for any later version of the client? If so, could some one please send me a link? Thanks for the help. Gary Lee Senior System Programmer Ball State University phone: 765-285-1310
Re: Looking for latest mac client documentation
Mac OS X is fully considered Unix, by TSM, now, so is in the Unix Client manual. http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp Richard Sims
Re: Slightly OT: ProtecTIER question
I had the old release 2.2.0.0 creating additional vtl was not impact the existing one. But on the host side (TSM server side) it is highly likely to reboot the server to discover the newly created vtl. Pawlos -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Steven Langdale Sent: Thursday, August 26, 2010 7:14 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Slightly OT: ProtecTIER question Guys A quick one, It's been a while, so I can't remember. Creating a new Virtual Library on a ProtecTIER, is that non-disruptive to existing Virtual libraries? If it makes a difference, it's the latest and greatest v2.4.1.0 Thanks Steven
Re: TSM Operation Reporting
FWIW, You can get OR to work OK with V6. You just have to customize it by removing the queries that go after tables that don't exist or aren't the same. Look in the activity log after you try running OR against your V6 server, you can see which queries fail and why. W -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Richard van Denzel Sent: Thursday, August 26, 2010 8:43 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM Operation Reporting Hi All, Is there a free tool available which replaces the TSM Operational Reporting? And I don't mean the TSM Reporting & Monitoring (which is just a bunch of crap imho). I know about tools like TSM Reporter (PLCS) and TSMManager, but I just want a free tool which is quick and dirty and does what the old TSM Operatinal Reporting did and just mail me the quick overview of last night. Met vriendelijke groet, with kind regards, Richard van Denzel.
Tuning 6.2 on AIX
Hello. We are in the process of upgrading our TSM-servers on AIX(5,.3/6.1) to TSM 6.2. We have always used raw devices for disk stgpools, db and logs but with 6.2 jfs2 is the rule. Any tip on mount options? Should cio be used anywhere? I understand that the application will take care of caching for the DB and storage of type DISK but it is difficult to predict that cio is a good thing anyway. Anyone been down this road? Hans Chr. Riksheim This email originates from Steria AS, Biskop Gunnerus' gate 14a, N-0051 OSLO, http://www.steria.no. This email and any attachments may contain confidential/intellectual property/copyright information and is only for the use of the addressee(s). You are prohibited from copying, forwarding, disclosing, saving or otherwise using it in any way if you are not the addressee(s) or responsible for delivery. If you receive this email by mistake, please advise the sender and cancel it immediately. Steria may monitor the content of emails within its network to ensure compliance with its policies and procedures. Any email is susceptible to alteration and its integrity cannot be assured. Steria shall not be liable if the message is altered, modified, falsified, or even edited.
Data Domain: Data Domain, and SQL-Backtrack with Sybase databases
Hello, I'm looking for anyone who is using SQL-Backtrack for Sybase and Data Domain/TSM? We are replacing our Virtual Tape libraries and physical tape library with Data Domains. One here onsite and another at our DR location. We have setup the Data Domain to emulate VTL. We are experiencing poor deduplication rates on our SQL-Backtrack Sybase compressed databases only. We see a 1:1:1 dedup ratio on Sybase data backed up with Backtrack. When the data is not compressed, we see dedup ratios anywhere from 5:1 to 150:1 on some tapes. Obviously, as you add backup versions of the same DB on DataDomain, each new version gets better dedup because a lot of common blocks are already on the appliance. But, of course then the backup runs 2x as long which is not acceptable for our RPO. Our DB2-UDB,MS-SQL,and Domino TDP all are seeing much better dedup rates. Background: TSM Server Version: 5.5.4.0 TSM Client: 5.5.2.0 TSM Client Sybase Version: ASE 15.0.3 TSM Client SQL-Backtrack Version: 6.8 Data Domain: Model: 880 Data Domain OS Version: 4.8.1.0 Nancy Leugemors Enterprise Systems HealthNow, NY 716-887-7979 CONFIDENTIALITY NOTICE: This email message and any attachments are for the sole use of the intended recipient(s) and may contain proprietary, confidential, trade secret or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited and may be a violation of law. If you are not the intended recipient or a person responsible for delivering this message to an intended recipient, please contact the sender by reply email and destroy all copies of the original message.
Re: Data Domain: Data Domain, and SQL-Backtrack with Sybase databases
We experienced the same thing in our testing. The more redundancy you have the better de-dup works :) As soon as you compress your dumps you are not going to be able to de-dup as well as uncompressed data. I have yet to see a de-dup product that is cost effective with compressed files. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Nancy L Leugemors Sent: Thursday, August 26, 2010 12:23 PM To: ADSM-L@VM.MARIST.EDU Subject: Data Domain: Data Domain, and SQL-Backtrack with Sybase databases Hello, I'm looking for anyone who is using SQL-Backtrack for Sybase and Data Domain/TSM? We are replacing our Virtual Tape libraries and physical tape library with Data Domains. One here onsite and another at our DR location. We have setup the Data Domain to emulate VTL. We are experiencing poor deduplication rates on our SQL-Backtrack Sybase compressed databases only. We see a 1:1:1 dedup ratio on Sybase data backed up with Backtrack. When the data is not compressed, we see dedup ratios anywhere from 5:1 to 150:1 on some tapes. Obviously, as you add backup versions of the same DB on DataDomain, each new version gets better dedup because a lot of common blocks are already on the appliance. But, of course then the backup runs 2x as long which is not acceptable for our RPO. Our DB2-UDB,MS-SQL,and Domino TDP all are seeing much better dedup rates. Background: TSM Server Version: 5.5.4.0 TSM Client: 5.5.2.0 TSM Client Sybase Version: ASE 15.0.3 TSM Client SQL-Backtrack Version: 6.8 Data Domain: Model: 880 Data Domain OS Version: 4.8.1.0 Nancy Leugemors Enterprise Systems HealthNow, NY 716-887-7979 CONFIDENTIALITY NOTICE: This email message and any attachments are for the sole use of the intended recipient(s) and may contain proprietary, confidential, trade secret or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited and may be a violation of law. If you are not the intended recipient or a person responsible for delivering this message to an intended recipient, please contact the sender by reply email and destroy all copies of the original message.
Re: Data Domain: Data Domain, and SQL-Backtrack with Sybase databases
This is a common problem with deduplication, and someone at EMC should have told you this before you bought. You should not/cannot run compression on your backups before they get to the dedupe system. It messes most of them up. As to finding someone with your config? Good luck with that. Data Domain VTL, Sybase, and SQL Backtrack are all products with very little market share. (Data Domain has good market share, but very few DD customers use VTL.) When you combine them together like that, your chances of finding someone else doing it is slim to none. Your best bet would be to call the SQL Backtrack guys and see what they can help you find. W. Curtis Preston On Thu, Aug 26, 2010 at 10:22 AM, Nancy L Leugemors < leugemors.na...@healthnow.org> wrote: > Hello, > > I'm looking for anyone who is using SQL-Backtrack for Sybase and Data > Domain/TSM? > > We are replacing our Virtual Tape libraries and physical tape library with > Data Domains. One here onsite and another at our DR location. We have > setup the Data Domain to emulate VTL. > > We are experiencing poor deduplication rates on our SQL-Backtrack Sybase > compressed databases only. We see a 1:1:1 dedup ratio on Sybase data > backed up with Backtrack. > > When the data is not compressed, we see dedup ratios anywhere from 5:1 to > 150:1 on some tapes. Obviously, as you add backup versions of the same > DB on DataDomain, each new version gets better dedup because a lot of > common blocks are already on the appliance. But, of course then the > backup runs 2x as long which is not acceptable for our RPO. Our > DB2-UDB,MS-SQL,and Domino TDP all are seeing much better dedup rates. > > > > Background: > > TSM Server Version: 5.5.4.0 > TSM Client: 5.5.2.0 > TSM Client Sybase Version: ASE 15.0.3 > TSM Client SQL-Backtrack Version: 6.8 > Data Domain: Model: 880 > Data Domain OS Version: 4.8.1.0 > > > > Nancy Leugemors > Enterprise Systems > HealthNow, NY > 716-887-7979 > > CONFIDENTIALITY NOTICE: This email message and any attachments are for the > sole use of the intended recipient(s) and may contain proprietary, > confidential, trade secret or privileged information. Any unauthorized > review, use, disclosure or distribution is prohibited and may be a violation > of law. If you are not the intended recipient or a person responsible for > delivering this message to an intended recipient, please contact the sender > by reply email and destroy all copies of the original > message. >
Re: Data Domain: Data Domain, and SQL-Backtrack with Sybase databases
What is your compression rate from the node? If it is in the same range of the DataDomain then do you really care? Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Nancy L Leugemors Sent: Thursday, August 26, 2010 12:23 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Data Domain: Data Domain, and SQL-Backtrack with Sybase databases Hello, I'm looking for anyone who is using SQL-Backtrack for Sybase and Data Domain/TSM? We are replacing our Virtual Tape libraries and physical tape library with Data Domains. One here onsite and another at our DR location. We have setup the Data Domain to emulate VTL. We are experiencing poor deduplication rates on our SQL-Backtrack Sybase compressed databases only. We see a 1:1:1 dedup ratio on Sybase data backed up with Backtrack. When the data is not compressed, we see dedup ratios anywhere from 5:1 to 150:1 on some tapes. Obviously, as you add backup versions of the same DB on DataDomain, each new version gets better dedup because a lot of common blocks are already on the appliance. But, of course then the backup runs 2x as long which is not acceptable for our RPO. Our DB2-UDB,MS-SQL,and Domino TDP all are seeing much better dedup rates. Background: TSM Server Version: 5.5.4.0 TSM Client: 5.5.2.0 TSM Client Sybase Version: ASE 15.0.3 TSM Client SQL-Backtrack Version: 6.8 Data Domain: Model: 880 Data Domain OS Version: 4.8.1.0 Nancy Leugemors Enterprise Systems HealthNow, NY 716-887-7979 CONFIDENTIALITY NOTICE: This email message and any attachments are for the sole use of the intended recipient(s) and may contain proprietary, confidential, trade secret or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited and may be a violation of law. If you are not the intended recipient or a person responsible for delivering this message to an intended recipient, please contact the sender by reply email and destroy all copies of the original message. This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
Re: Data Domain: Data Domain, and SQL-Backtrack with Sybase databases
We used to use SQLBacktrack with Falconstor. Regardless of the specific configuration, the problem is obviously compression/encryption doesn't mix with deduplication. You're best bet would be to speed up your backup with something other than compression. 10gb NICs or a lan-free configuration if you have fast fibre. Regards, Shawn Shawn Drew Internet leugemors.na...@healthnow.org Sent by: ADSM-L@VM.MARIST.EDU 08/26/2010 01:22 PM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject [ADSM-L] Data Domain: Data Domain, and SQL-Backtrack with Sybase databases Hello, I'm looking for anyone who is using SQL-Backtrack for Sybase and Data Domain/TSM? We are replacing our Virtual Tape libraries and physical tape library with Data Domains. One here onsite and another at our DR location. We have setup the Data Domain to emulate VTL. We are experiencing poor deduplication rates on our SQL-Backtrack Sybase compressed databases only. We see a 1:1:1 dedup ratio on Sybase data backed up with Backtrack. When the data is not compressed, we see dedup ratios anywhere from 5:1 to 150:1 on some tapes. Obviously, as you add backup versions of the same DB on DataDomain, each new version gets better dedup because a lot of common blocks are already on the appliance. But, of course then the backup runs 2x as long which is not acceptable for our RPO. Our DB2-UDB,MS-SQL,and Domino TDP all are seeing much better dedup rates. Background: TSM Server Version: 5.5.4.0 TSM Client: 5.5.2.0 TSM Client Sybase Version: ASE 15.0.3 TSM Client SQL-Backtrack Version: 6.8 Data Domain: Model: 880 Data Domain OS Version: 4.8.1.0 Nancy Leugemors Enterprise Systems HealthNow, NY 716-887-7979 CONFIDENTIALITY NOTICE: This email message and any attachments are for the sole use of the intended recipient(s) and may contain proprietary, confidential, trade secret or privileged information. Any unauthorized review, use, disclosure or distribution is prohibited and may be a violation of law. If you are not the intended recipient or a person responsible for delivering this message to an intended recipient, please contact the sender by reply email and destroy all copies of the original message. This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.
unsubscribe
unsubscribe
Re: Data Domain: Data Domain, and SQL-Backtrack with Sybase databases
Curtis, >> Data Domain has good market share, but very few DD customers use VTL. Really? That surprises me a little (i.e., the marginalised VTL usage) and isn't necessarily representative of the TSM customers I've spoken to or worked with using DDRs, many of whom still use the VTL functionality. I can't comment on whether this is so much the case with shops that use other backup software though (e.g., I know NBU has its own OST interface). In any case, whether through VTL or NFS/CIFS the principle is the same and of course you're right, pre-appliance compression or even encryption can be catastrophic to data de-dupe ratios. Without knowing any more, it sounds like you may have to make a compromise somewhere without changing your current config Nancy, either in terms of backup data storage footprint or RPO. Cheers, __ David McClelland London, UK On 26 Aug 2010, at 19:10, Nobody wrote: > Data Domain has good market share, but very few DD customers use > VTL.
Re: Data Domain: Data Domain, and SQL-Backtrack with Sybase databases
>From what I understand the EMC/DD Best Practice is to use NFS/CIFS mounts with File device classes over 10gb connections. The main benefit cited is the concurrent access to file volumes. There is a TSM/DD Best Practices document out there from Glasshouse a few years ago that mentions this. (Which might be where EMC got it) Regards, Shawn Shawn Drew Internet t...@networkc.co.uk Sent by: ADSM-L@VM.MARIST.EDU 08/26/2010 04:38 PM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject Re: [ADSM-L] Data Domain: Data Domain, and SQL-Backtrack with Sybase databases Curtis, >> Data Domain has good market share, but very few DD customers use VTL. Really? That surprises me a little (i.e., the marginalised VTL usage) and isn't necessarily representative of the TSM customers I've spoken to or worked with using DDRs, many of whom still use the VTL functionality. I can't comment on whether this is so much the case with shops that use other backup software though (e.g., I know NBU has its own OST interface). In any case, whether through VTL or NFS/CIFS the principle is the same and of course you're right, pre-appliance compression or even encryption can be catastrophic to data de-dupe ratios. Without knowing any more, it sounds like you may have to make a compromise somewhere without changing your current config Nancy, either in terms of backup data storage footprint or RPO. Cheers, __ David McClelland London, UK On 26 Aug 2010, at 19:10, Nobody wrote: > Data Domain has good market share, but very few DD customers use > VTL. This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.
Re: Data Domain: Data Domain, and SQL-Backtrack with Sybase databases
For the record, here's a link to the GlassHouse white paper - it is very good but, as Shawn pointed out, rather old now and quite a few of the figures are out of date (I should disclose I'm doing some Data Domain/TSM work for GlassHouse at the moment): http://pdf.edocr.com/6cb6a7b31a5be6dd526302c6e23918d0f37a5669.pdf There's another paper too from Data Domain which talks very practically about configuring TSM 5.5 for CIFS, NFS and VTL - I can't find a link for that online (I can't even remember where I pulled it from now), but if anyone would like a copy do ping me. Again the recommendation cited in this is, "Do not enable compression on the TSM Client". __ David McClelland London, UK -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Shawn Drew Sent: 26 August 2010 21:50 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Data Domain: Data Domain, and SQL-Backtrack with Sybase databases >From what I understand the EMC/DD Best Practice is to use NFS/CIFS mounts with File device classes over 10gb connections. The main benefit cited is the concurrent access to file volumes. There is a TSM/DD Best Practices document out there from Glasshouse a few years ago that mentions this. (Which might be where EMC got it) Regards, Shawn Shawn Drew Internet t...@networkc.co.uk Sent by: ADSM-L@VM.MARIST.EDU 08/26/2010 04:38 PM Please respond to ADSM-L@VM.MARIST.EDU To ADSM-L cc Subject Re: [ADSM-L] Data Domain: Data Domain, and SQL-Backtrack with Sybase databases Curtis, >> Data Domain has good market share, but very few DD customers use VTL. Really? That surprises me a little (i.e., the marginalised VTL usage) and isn't necessarily representative of the TSM customers I've spoken to or worked with using DDRs, many of whom still use the VTL functionality. I can't comment on whether this is so much the case with shops that use other backup software though (e.g., I know NBU has its own OST interface). In any case, whether through VTL or NFS/CIFS the principle is the same and of course you're right, pre-appliance compression or even encryption can be catastrophic to data de-dupe ratios. Without knowing any more, it sounds like you may have to make a compromise somewhere without changing your current config Nancy, either in terms of backup data storage footprint or RPO. Cheers, __ David McClelland London, UK On 26 Aug 2010, at 19:10, Nobody wrote: > Data Domain has good market share, but very few DD customers use > VTL. This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc. No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.851 / Virus Database: 271.1.1/3088 - Release Date: 08/22/10 19:35:00
Re: Data Domain: Data Domain, and SQL-Backtrack with Sybase databases
The last time I checked <10% of DD customers use the VTL option. I'm willing to bet that 60-80% of those are TSM customers. The TSM folks I've talked to seem to prefer using VTL over file-type devices, which may explain that. The rest of the world (except large enterprise customers) tends to prefer NAS devices. On Thu, Aug 26, 2010 at 1:38 PM, ADSM-L wrote: > Curtis, > > >> Data Domain has good market share, but very few DD customers use VTL. > > Really? That surprises me a little (i.e., the marginalised VTL usage) and > isn't necessarily representative of the TSM customers I've spoken to or > worked with using DDRs, many of whom still use the VTL functionality. I > can't comment on whether this is so much the case with shops that use other > backup software though (e.g., I know NBU has its own OST interface). > > In any case, whether through VTL or NFS/CIFS the principle is the same and > of course you're right, pre-appliance compression or even encryption can be > catastrophic to data de-dupe ratios. Without knowing any more, it sounds > like you may have to make a compromise somewhere without changing your > current config Nancy, either in terms of backup data storage footprint or > RPO. > > Cheers, > __ > David McClelland > London, UK > > On 26 Aug 2010, at 19:10, Nobody wrote: > > > Data Domain has good market share, but very few DD customers use > > VTL. >
