Re: Data Domain: Data Domain, and SQL-Backtrack with Sybase databases
Oooh. And the big advantage - when the NFS device fills up, it's THEIR problem! -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Allen S. Rout Sent: Saturday, August 28, 2010 1:30 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Data Domain: Data Domain, and SQL-Backtrack with Sybase databases On Fri, 27 Aug 2010 08:32:00 -0500, Hart, Charles A charles_h...@uhc.com said: I could be shot for saying the following, but using a NFS share would provide the opportunity for you to remove the backup application and its associates hardware from the data protection stack altogether for things such as data bases which in some shops is 80% of the load. We are avid TSM users and fans but if RMAN backups directly to NFS mounts works well it appears there would be an opportunity reducing complexity and costs. That is exactly what we are experimenting with, in a demo starting Monday. We've been using the TDPO shim for years, and have never gotten free of occasional manual reconciliation, which appears to match the general experience. This is constant sand in the vaseline for the Oracle admins' experience, and no pearl has accreted thus far. Furthermore, if the dedupe works as well as advertised (hah) then there are a variety of toys we can let the Oracle folks use, which are usually prohibitively expensive in disk. I don't know the buzzwords, but Flash Recovery Area seems to be one of them. Basically, if you've got lots of space to store a bunch of fulls all over the place, Oracle lets you play fun games with them. at 20:1 dedupe ratio, this would not be an issue. - Allen S. Rout
Re: Data Domain: Data Domain, and SQL-Backtrack with Sybase databases
On Fri, 27 Aug 2010 08:32:00 -0500, Hart, Charles A charles_h...@uhc.com said: I could be shot for saying the following, but using a NFS share would provide the opportunity for you to remove the backup application and its associates hardware from the data protection stack altogether for things such as data bases which in some shops is 80% of the load. We are avid TSM users and fans but if RMAN backups directly to NFS mounts works well it appears there would be an opportunity reducing complexity and costs. That is exactly what we are experimenting with, in a demo starting Monday. We've been using the TDPO shim for years, and have never gotten free of occasional manual reconciliation, which appears to match the general experience. This is constant sand in the vaseline for the Oracle admins' experience, and no pearl has accreted thus far. Furthermore, if the dedupe works as well as advertised (hah) then there are a variety of toys we can let the Oracle folks use, which are usually prohibitively expensive in disk. I don't know the buzzwords, but Flash Recovery Area seems to be one of them. Basically, if you've got lots of space to store a bunch of fulls all over the place, Oracle lets you play fun games with them. at 20:1 dedupe ratio, this would not be an issue. - Allen S. Rout
Re: Data Domain: Data Domain, and SQL-Backtrack with Sybase databases
We don't have DD or any other dedup box . . .but we think about them a lot. This has been one or our ongoing discussions. Our big database servers that use rman/tdpo/lanfree. If we could get enought throughput with straight ethernet or 10g ethernet, then we could ditch tdpo/lanfree and use straight rman to disk over NFS to the dedup box. The only value in tdpo/lanfree/vtl seems to be SAN speed. I wonder what the trade off is between tdpo/lanfree licensing and 10g ethernet adapters and switch ports . . . . h. Rick Hart, Charles A charles_h...@uhc .COM To Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager ads...@vm.marist Subject .EDU Re: Data Domain: Data Domain, and SQL-Backtrack with Sybase databases 08/27/2010 09:32 AM Please respond to ADSM: Dist Stor Manager ads...@vm.marist .EDU I could be shot for saying the following, but using a NFS share would provide the opportunity for you to remove the backup application and its associates hardware from the data protection stack altogether for things such as data bases which in some shops is 80% of the load. We are avid TSM users and fans but if RMAN backups directly to NFS mounts works well it appears there would be an opportunity reducing complexity and costs. Charles -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Nobody Sent: Thursday, August 26, 2010 5:18 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] 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 t...@networkc.co.uk 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 wcplis...@gmail.com wrote: Data Domain has good market share, but very few DD customers use VTL. 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: Data Domain: Data Domain, and SQL-Backtrack with Sybase databases
I've recently been in an environment that went from very old slow low capacity tape to slightly faster CDL/EDL. (VTL access being the only choice in that case.) EMC buying DD put DD on the inside track for doing proof of concepts for things like replacing TSM/LanFree/EDL with RMAN over NFS to DD. This use of DD reminds me of NAS. By that I mean that instead of the TSM admin being on the hook for managing capacity and availability of TSM pools, whoever admins the DD will need to work with the DBAs to make sure they understand how close they are to running out of capacity at any given point. Not being able to set nextpool to tape may make the DD less forgiving with regards capacity forecasting. It sounds like any given DD is going to be setup as one large pool. This would seem to put the capability for reporting who is using what back on the DBAs.(And the distinction of logical/physical usage sounds like a headache.) Without TSM in the picture, there is no query occupancy command to fall back on. It is going to be interesting. [RC] On Aug 27, 2010, at 08:17 AM, Richard Rhodes rrho...@firstenergycorp.com wrote: We don't have DD or any other dedup box . . .but we think about them a lot. This has been one or our ongoing discussions. Our big database servers that use rman/tdpo/lanfree. If we could get enought throughput with straight ethernet or 10g ethernet, then we could ditch tdpo/lanfree and use straight rman to disk over NFS to the dedup box. The only value in tdpo/lanfree/vtl seems to be SAN speed. I wonder what the trade off is between tdpo/lanfree licensing and 10g ethernet adapters and switch ports . . . . h. Rick Hart, Charles A charles_h...@uhc .COM To Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager ads...@vm.marist Subject .EDU Re: Data Domain: Data Domain, and SQL-Backtrack with Sybase databases 08/27/2010 09:32 AM Please respond to ADSM: Dist Stor Manager ads...@vm.marist .EDU I could be shot for saying the following, but using a NFS share would provide the opportunity for you to remove the backup application and its associates hardware from the data protection stack altogether for things such as data bases which in some shops is 80% of the load. We are avid TSM users and fans but if RMAN backups directly to NFS mounts works well it appears there would be an opportunity reducing complexity and costs. Charles -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Nobody Sent: Thursday, August 26, 2010 5:18 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] 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 t...@networkc.co.uk 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 wcplis...@gmail.com wrote: Data Domain has good market share, but very few DD customers use VTL. 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
Re: Data Domain: Data Domain, and SQL-Backtrack with Sybase databases
In my experience, reporting the space usage (cost) of each RMAN instance is the only way we can force them to expire backups. Even then, it's only administrative recommendations. As a result, I don't allow Oracle on our disk-based backups. In our environment, we need to maintain expiration control if we are to allow something into the disk-backups. Regards, Shawn Shawn Drew Internet robert_cl...@mac.com Sent by: ADSM-L@VM.MARIST.EDU 08/27/2010 11:32 AM 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 I've recently been in an environment that went from very old slow low capacity tape to slightly faster CDL/EDL. (VTL access being the only choice in that case.) EMC buying DD put DD on the inside track for doing proof of concepts for things like replacing TSM/LanFree/EDL with RMAN over NFS to DD. This use of DD reminds me of NAS. By that I mean that instead of the TSM admin being on the hook for managing capacity and availability of TSM pools, whoever admins the DD will need to work with the DBAs to make sure they understand how close they are to running out of capacity at any given point. Not being able to set nextpool to tape may make the DD less forgiving with regards capacity forecasting. It sounds like any given DD is going to be setup as one large pool. This would seem to put the capability for reporting who is using what back on the DBAs.(And the distinction of logical/physical usage sounds like a headache.) Without TSM in the picture, there is no query occupancy command to fall back on. It is going to be interesting. [RC] On Aug 27, 2010, at 08:17 AM, Richard Rhodes rrho...@firstenergycorp.com wrote: We don't have DD or any other dedup box . . .but we think about them a lot. This has been one or our ongoing discussions. Our big database servers that use rman/tdpo/lanfree. If we could get enought throughput with straight ethernet or 10g ethernet, then we could ditch tdpo/lanfree and use straight rman to disk over NFS to the dedup box. The only value in tdpo/lanfree/vtl seems to be SAN speed. I wonder what the trade off is between tdpo/lanfree licensing and 10g ethernet adapters and switch ports . . . . h. Rick Hart, Charles A charles_h...@uhc .COM To Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager ads...@vm.marist Subject .EDU Re: Data Domain: Data Domain, and SQL-Backtrack with Sybase databases 08/27/2010 09:32 AM Please respond to ADSM: Dist Stor Manager ads...@vm.marist .EDU I could be shot for saying the following, but using a NFS share would provide the opportunity for you to remove the backup application and its associates hardware from the data protection stack altogether for things such as data bases which in some shops is 80% of the load. We are avid TSM users and fans but if RMAN backups directly to NFS mounts works well it appears there would be an opportunity reducing complexity and costs. Charles -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Nobody Sent: Thursday, August 26, 2010 5:18 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] 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 t...@networkc.co.uk 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 wcplis...@gmail.com wrote: Data Domain has good market share, but very few DD customers use VTL. 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
Re: Data Domain: Data Domain, and SQL-Backtrack with Sybase databases
Trade offsss... Tdp license tdp cfg / lan free lic lan free cfg... Its just a mount poing... Let the DBA be the Master of their Own env... -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Richard Rhodes Sent: Friday, August 27, 2010 10:16 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Data Domain: Data Domain, and SQL-Backtrack with Sybase databases We don't have DD or any other dedup box . . .but we think about them a lot. This has been one or our ongoing discussions. Our big database servers that use rman/tdpo/lanfree. If we could get enought throughput with straight ethernet or 10g ethernet, then we could ditch tdpo/lanfree and use straight rman to disk over NFS to the dedup box. The only value in tdpo/lanfree/vtl seems to be SAN speed. I wonder what the trade off is between tdpo/lanfree licensing and 10g ethernet adapters and switch ports . . . . h. Rick Hart, Charles A charles_h...@uhc .COM To Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager ads...@vm.marist Subject .EDU Re: Data Domain: Data Domain, and SQL-Backtrack with Sybase databases 08/27/2010 09:32 AM Please respond to ADSM: Dist Stor Manager ads...@vm.marist .EDU I could be shot for saying the following, but using a NFS share would provide the opportunity for you to remove the backup application and its associates hardware from the data protection stack altogether for things such as data bases which in some shops is 80% of the load. We are avid TSM users and fans but if RMAN backups directly to NFS mounts works well it appears there would be an opportunity reducing complexity and costs. Charles -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Nobody Sent: Thursday, August 26, 2010 5:18 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] 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 t...@networkc.co.uk 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 wcplis...@gmail.com wrote: Data Domain has good market share, but very few DD customers use VTL. 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. 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
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.
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 wcplis...@gmail.com 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 wcplis...@gmail.com 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 wcplis...@gmail.com 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 t...@networkc.co.uk 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 wcplis...@gmail.com wrote: Data Domain has good market share, but very few DD customers use VTL.
Re: Expiration / deletion of inactive files do not appear to be working for SQL-BACKTRACK
In TSM for Databases, each backup file has a unique name and rman is responsible for deleting them, thus triggering the TSM expiration cycle. Does Backtrack work the same way? [EMAIL PROTECTED] 05/19/05 2:34 PM Hi: We've just discovered q peculiar problem with expiration involing the SQL-BACKTRACK product and SYBASE and ORACLE databases. They do not appear to be expiring. The managment class rules are: DOMAIN_NAME CLASS_NAME VEREXISTS VERDELETED RETEXTRA RETONLY DESTINATION SPAIX DBBKUP1 60 0 30 0 AIXDISKBACK And a query backup /BACKTRACK:obackups.physical/*/* -inactive returns a HUGE list of files that are inactive. They should all have been deleted with the RETONLY set to 0. Am I missing something? A DB called SQL-BACKTRACK support and the responce was SQL-BACKTRACK marked them inactive; at that point TSM is not correctly removing them per the definitions. Flat files in other management groups are behaving correctly. API 5,242,880 B 10/15/03 02:54:53DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.15-10-2003.02:55:41-21544 API 5,242,880 B 11/15/03 02:59:13DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.15-11-2003.02:59:04-43356 API 5,242,880 B 12/15/02 02:55:59DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.15-12-2002.02:55:42-31662 API 5,242,880 B 12/15/03 02:50:43DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.15-12-2003.02:50:28-19182 API 5,242,880 B 01/16/03 03:03:22DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.16-01-2003.03:03:16-32618 API 5,242,880 B 01/16/04 02:57:23DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.16-01-2004.02:57:00-28874 API 5,242,880 B 02/16/03 02:48:22DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.16-02-2003.02:48:26-21274 API 5,242,880 B 02/16/04 02:48:41DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.16-02-2004.02:48:10-39458 API 5,242,880 B 03/16/03 02:50:47DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.16-03-2003.02:50:59-32472 API 5,242,880 B 03/16/04 02:54:33DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.16-03-2004.02:54:33-33320 API 5,242,880 B 04/16/03 03:04:45DBBKUP1 A /BACKTRACK:obackups.phy [EMAIL PROTECTED] 05/10/2005 9:27:12 AM Mario, We've been using St. Bernard OFM 9 in conjuction with TSM 5.2.2 (client vers. of course) to backup both our GroupWise 6, and now GroupWise 6.5 servers in the last year without problems. We've also done successful restores of the GroupWise servers. [EMAIL PROTECTED] 05/09/05 3:41 PM Hi list, I need to perform an online backup of a Novell Groupwise environment using TSM ... does anybody knows how can I accomplish this ? Thanks. Mario Yahoo! Mail Stay connected, organized, and protected. Take the tour: http://tour.mail.yahoo.com/mailtour.html
q backup for SQL-BACKTRACK
We have two clients on NT boxes with oracle databses. (One TSM install). One is the flat file backup, the 2nd with its own dsm.opt file is for SQl-BACKTRACK. We cannot query the backups on SQL-BACTRACK since the dsmc invokes with the flat file client dsm.opt ( and hence can't do a set access for SQL-BACKTRACK. Is there a way of invoking the dsmc for the SQL-BACTRACK client?
Re: Expiration / deletion of inactive files do not appear to be working for SQL-BACKTRACK
Yes, SQL-BACKTRACK is responsible for updating the status of the uniquely name file. [EMAIL PROTECTED] 05/20/2005 10:43:53 AM In TSM for Databases, each backup file has a unique name and rman is responsible for deleting them, thus triggering the TSM expiration cycle. Does Backtrack work the same way? [EMAIL PROTECTED] 05/19/05 2:34 PM Hi: We've just discovered q peculiar problem with expiration involing the SQL-BACKTRACK product and SYBASE and ORACLE databases. They do not appear to be expiring. The managment class rules are: DOMAIN_NAME CLASS_NAME VEREXISTS VERDELETED RETEXTRA RETONLY DESTINATION SPAIX DBBKUP1 60 0 30 0 AIXDISKBACK And a query backup /BACKTRACK:obackups.physical/*/* -inactive returns a HUGE list of files that are inactive. They should all have been deleted with the RETONLY set to 0. Am I missing something? A DB called SQL-BACKTRACK support and the responce was SQL-BACKTRACK marked them inactive; at that point TSM is not correctly removing them per the definitions. Flat files in other management groups are behaving correctly. API 5,242,880 B 10/15/03 02:54:53DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.15-10-2003.02:55:41-21544 API 5,242,880 B 11/15/03 02:59:13DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.15-11-2003.02:59:04-43356 API 5,242,880 B 12/15/02 02:55:59DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.15-12-2002.02:55:42-31662 API 5,242,880 B 12/15/03 02:50:43DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.15-12-2003.02:50:28-19182 API 5,242,880 B 01/16/03 03:03:22DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.16-01-2003.03:03:16-32618 API 5,242,880 B 01/16/04 02:57:23DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.16-01-2004.02:57:00-28874 API 5,242,880 B 02/16/03 02:48:22DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.16-02-2003.02:48:26-21274 API 5,242,880 B 02/16/04 02:48:41DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.16-02-2004.02:48:10-39458 API 5,242,880 B 03/16/03 02:50:47DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.16-03-2003.02:50:59-32472 API 5,242,880 B 03/16/04 02:54:33DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.16-03-2004.02:54:33-33320 API 5,242,880 B 04/16/03 03:04:45DBBKUP1 A /BACKTRACK:obackups.phy [EMAIL PROTECTED] 05/10/2005 9:27:12 AM Mario, We've been using St. Bernard OFM 9 in conjuction with TSM 5.2.2 (client vers. of course) to backup both our GroupWise 6, and now GroupWise 6.5 servers in the last year without problems. We've also done successful restores of the GroupWise servers. [EMAIL PROTECTED] 05/09/05 3:41 PM Hi list, I need to perform an online backup of a Novell Groupwise environment using TSM ... does anybody knows how can I accomplish this ? Thanks. Mario Yahoo! Mail Stay connected, organized, and protected. Take the tour: http://tour.mail.yahoo.com/mailtour.html
Re: q backup for SQL-BACKTRACK
Have you tried 'dsmc -virtualnode= . . .'? [EMAIL PROTECTED] 05/20/05 11:02 AM We have two clients on NT boxes with oracle databses. (One TSM install). One is the flat file backup, the 2nd with its own dsm.opt file is for SQl-BACKTRACK. We cannot query the backups on SQL-BACTRACK since the dsmc invokes with the flat file client dsm.opt ( and hence can't do a set access for SQL-BACKTRACK. Is there a way of invoking the dsmc for the SQL-BACTRACK client?
Re: Expiration / deletion of inactive files do not appear to be working for SQL-BACKTRACK
Then, since TSM see them all as still active, I'd guess that Backtrack is not expiring the files. David [EMAIL PROTECTED] 05/20/05 11:05 AM Yes, SQL-BACKTRACK is responsible for updating the status of the uniquely name file. [EMAIL PROTECTED] 05/20/2005 10:43:53 AM In TSM for Databases, each backup file has a unique name and rman is responsible for deleting them, thus triggering the TSM expiration cycle. Does Backtrack work the same way? [EMAIL PROTECTED] 05/19/05 2:34 PM Hi: We've just discovered q peculiar problem with expiration involing the SQL-BACKTRACK product and SYBASE and ORACLE databases. They do not appear to be expiring. The managment class rules are: DOMAIN_NAME CLASS_NAME VEREXISTS VERDELETED RETEXTRA RETONLY DESTINATION SPAIX DBBKUP1 60 0 30 0 AIXDISKBACK And a query backup /BACKTRACK:obackups.physical/*/* -inactive returns a HUGE list of files that are inactive. They should all have been deleted with the RETONLY set to 0. Am I missing something? A DB called SQL-BACKTRACK support and the responce was SQL-BACKTRACK marked them inactive; at that point TSM is not correctly removing them per the definitions. Flat files in other management groups are behaving correctly. API 5,242,880 B 10/15/03 02:54:53DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.15-10-2003.02:55:41-21544 API 5,242,880 B 11/15/03 02:59:13DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.15-11-2003.02:59:04-43356 API 5,242,880 B 12/15/02 02:55:59DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.15-12-2002.02:55:42-31662 API 5,242,880 B 12/15/03 02:50:43DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.15-12-2003.02:50:28-19182 API 5,242,880 B 01/16/03 03:03:22DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.16-01-2003.03:03:16-32618 API 5,242,880 B 01/16/04 02:57:23DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.16-01-2004.02:57:00-28874 API 5,242,880 B 02/16/03 02:48:22DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.16-02-2003.02:48:26-21274 API 5,242,880 B 02/16/04 02:48:41DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.16-02-2004.02:48:10-39458 API 5,242,880 B 03/16/03 02:50:47DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.16-03-2003.02:50:59-32472 API 5,242,880 B 03/16/04 02:54:33DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.16-03-2004.02:54:33-33320 API 5,242,880 B 04/16/03 03:04:45DBBKUP1 A /BACKTRACK:obackups.phy [EMAIL PROTECTED] 05/10/2005 9:27:12 AM Mario, We've been using St. Bernard OFM 9 in conjuction with TSM 5.2.2 (client vers. of course) to backup both our GroupWise 6, and now GroupWise 6.5 servers in the last year without problems. We've also done successful restores of the GroupWise servers. [EMAIL PROTECTED] 05/09/05 3:41 PM Hi list, I need to perform an online backup of a Novell Groupwise environment using TSM ... does anybody knows how can I accomplish this ? Thanks. Mario Yahoo! Mail Stay connected, organized, and protected. Take the tour: http://tour.mail.yahoo.com/mailtour.html
Expiration / deletion of inactive files do not appear to be working for SQL-BACKTRACK
Hi: We've just discovered q peculiar problem with expiration involing the SQL-BACKTRACK product and SYBASE and ORACLE databases. They do not appear to be expiring. The managment class rules are: DOMAIN_NAME CLASS_NAME VEREXISTS VERDELETED RETEXTRA RETONLY DESTINATION SPAIX DBBKUP1 60 0 30 0 AIXDISKBACK And a query backup /BACKTRACK:obackups.physical/*/* -inactive returns a HUGE list of files that are inactive. They should all have been deleted with the RETONLY set to 0. Am I missing something? A DB called SQL-BACKTRACK support and the responce was SQL-BACKTRACK marked them inactive; at that point TSM is not correctly removing them per the definitions. Flat files in other management groups are behaving correctly. API 5,242,880 B 10/15/03 02:54:53DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.15-10-2003.02:55:41-21544 API 5,242,880 B 11/15/03 02:59:13DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.15-11-2003.02:59:04-43356 API 5,242,880 B 12/15/02 02:55:59DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.15-12-2002.02:55:42-31662 API 5,242,880 B 12/15/03 02:50:43DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.15-12-2003.02:50:28-19182 API 5,242,880 B 01/16/03 03:03:22DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.16-01-2003.03:03:16-32618 API 5,242,880 B 01/16/04 02:57:23DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.16-01-2004.02:57:00-28874 API 5,242,880 B 02/16/03 02:48:22DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.16-02-2003.02:48:26-21274 API 5,242,880 B 02/16/04 02:48:41DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.16-02-2004.02:48:10-39458 API 5,242,880 B 03/16/03 02:50:47DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.16-03-2003.02:50:59-32472 API 5,242,880 B 03/16/04 02:54:33DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.16-03-2004.02:54:33-33320 API 5,242,880 B 04/16/03 03:04:45DBBKUP1 A /BACKTRACK:obackups.phy [EMAIL PROTECTED] 05/10/2005 9:27:12 AM Mario, We've been using St. Bernard OFM 9 in conjuction with TSM 5.2.2 (client vers. of course) to backup both our GroupWise 6, and now GroupWise 6.5 servers in the last year without problems. We've also done successful restores of the GroupWise servers. [EMAIL PROTECTED] 05/09/05 3:41 PM Hi list, I need to perform an online backup of a Novell Groupwise environment using TSM ... does anybody knows how can I accomplish this ? Thanks. Mario Yahoo! Mail Stay connected, organized, and protected. Take the tour: http://tour.mail.yahoo.com/mailtour.html
Re: Expiration / deletion of inactive files do not appear to be working for SQL-BACKTRACK
Hi: We've just discovered q peculiar problem with expiration involing the SQL-BACKTRACK product and SYBASE and ORACLE databases. They do not appear to be expiring. The managment class rules are: DOMAIN_NAME CLASS_NAME VEREXISTS VERDELETED RETEXTRA RETONLY DESTINATION SPAIX DBBKUP1 60 0 30 0 AIXDISKBACK And a query backup /BACKTRACK:obackups.physical/*/* -inactive returns a HUGE list of files that are inactive. They should all have been deleted with the RETONLY set to 0. Am I missing something? The -inactive option causes the query to list inactive files as well as active files, not inactive files instead of active files. In the query output line below, the 'A' after 'DBBKUP1' indicates that the file is active. The rest of the query output lines in your original message also showed active files. It is not clear that you have any inactive backups of Oracle and Sybase data. When our site had problems with SQL/BackTrack (we has since switched to TDP), the most frequent cause was forgetting to specify 'backdelete=yes' when registering nodes. A DB called SQL-BACKTRACK support and the responce was SQL-BACKTRACK marked them inactive; at that point TSM is not correctly removing them per the definitions. Flat files in other management groups are behaving correctly. API 5,242,880 B 10/15/03 02:54:53DBBKUP1 A /BACKTRACK:obackups.phy sical/BRSSBKUP/controlfiles-0.15-10-2003.02:55:41-21544
Re: TSM, Lotus Notes and SQL BACKTRACK
We use the Domino TDP's to backup our Lotus Notes servers. Backing up the Lotus Notes databases with the regular TSM Backup Client used too much of our resources. The architecture is such that even using incrementals, they were using up tapes faster than we could order them. Each Lotus Notes database averages well over 120 GB's, the reason we switched to the TDP's, which work specifically with the architecture of the Lotus Notes databases. To backup many of our SQL databases though, the DB Administrator creates a flat file within the client server at a certain time each evening. TSM then incrementally backs up that flat file after it is created. Shannon Bach Madison Gas Electric Co Operations Analyst -Data Center Services Information Management Systems [EMAIL PROTECTED] Lawrence Clark [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 05/09/2005 12:57 PM Please respond to ADSM: Dist Stor Manager To:ADSM-L@VM.MARIST.EDU cc: Subject:Re: TSM, Lotus Notes and SQL BACKTRACK Yes, you can do incremental backups on SQL Backups. Most places would do weekly full, and daily incrementals, with triggered logs backups as they fill. [EMAIL PROTECTED] 05/09/2005 1:30:24 PM Folks, We have been eating up a LOT of tapes doing Notes and SQL backups (Oracle). Does anyone have any pointers concerning tape management and these? BTWWe have a permanent retention policy on our Notes backups dictated by Corporate. Also, I was told that we cannot do incrementals on either Notes or SQL backups. Thanks! DaveZ
Re: TSM, Lotus Notes and SQL BACKTRACK
The senario you use for SQL databases would only allow restore to the point in time that is in the export file you are backing up. Depending on your requirements, that may be sufficient. However, many businesses would require a way of capturing activity that occurred since the last backup of an export file. We use SQL-BACKTRACK for our SYBASE and ORACLE backups, and the TDP for the MS-SQL databases, though we are looking at the TDP for Oracle. [EMAIL PROTECTED] 05/10/2005 9:10:13 AM We use the Domino TDP's to backup our Lotus Notes servers. Backing up the Lotus Notes databases with the regular TSM Backup Client used too much of our resources. The architecture is such that even using incrementals, they were using up tapes faster than we could order them. Each Lotus Notes database averages well over 120 GB's, the reason we switched to the TDP's, which work specifically with the architecture of the Lotus Notes databases. To backup many of our SQL databases though, the DB Administrator creates a flat file within the client server at a certain time each evening. TSM then incrementally backs up that flat file after it is created. Shannon Bach Madison Gas Electric Co Operations Analyst -Data Center Services Information Management Systems [EMAIL PROTECTED] Lawrence Clark [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 05/09/2005 12:57 PM Please respond to ADSM: Dist Stor Manager To: ADSM-L@VM.MARIST.EDU cc: Subject:Re: TSM, Lotus Notes and SQL BACKTRACK Yes, you can do incremental backups on SQL Backups. Most places would do weekly full, and daily incrementals, with triggered logs backups as they fill. [EMAIL PROTECTED] 05/09/2005 1:30:24 PM Folks, We have been eating up a LOT of tapes doing Notes and SQL backups (Oracle). Does anyone have any pointers concerning tape management and these? BTWWe have a permanent retention policy on our Notes backups dictated by Corporate. Also, I was told that we cannot do incrementals on either Notes or SQL backups. Thanks! DaveZ
TSM, Lotus Notes and SQL BACKTRACK
Folks, We have been eating up a LOT of tapes doing Notes and SQL backups (Oracle). Does anyone have any pointers concerning tape management and these? BTWWe have a permanent retention policy on our Notes backups dictated by Corporate. Also, I was told that we cannot do incrementals on either Notes or SQL backups. Thanks! DaveZ
Re: TSM, Lotus Notes and SQL BACKTRACK
Yes, you can do incremental backups on SQL Backups. Most places would do weekly full, and daily incrementals, with triggered logs backups as they fill. [EMAIL PROTECTED] 05/09/2005 1:30:24 PM Folks, We have been eating up a LOT of tapes doing Notes and SQL backups (Oracle). Does anyone have any pointers concerning tape management and these? BTWWe have a permanent retention policy on our Notes backups dictated by Corporate. Also, I was told that we cannot do incrementals on either Notes or SQL backups. Thanks! DaveZ
AIX 5.2, Sql-backtrack 4.0.10 and TSM 5.2
Hello! I am getting the following error when backing up oracle db with sqlbacktrack: OLE_LINK1[dtocheck 671956] Verifying options for PROD -- physical. [dtocheck 671956] Resyncing database with profile... [dtocheck 671956] BMCBKO4401298E: obsi/adsm: FATAL: TSM: dsmInit failed, unable to validate password, ANS1217E (RC409) Server name not found in System Options File Any help is greatly appreciated! Laura Lantz
Expiration of SQL BackTrack Filespaces
Hello all, How does TSM handle the expiration of SQL Backtrack filespaces if the data was originally written directly to tape, thus never existing on hard disk? We have a situation where these filespaces are not expiring and are not even being marked as inactive yet they are in a MC that is set to retain only ten versions. TSM Server: 5.1.5.5 OS Version: AIX 5.1 SQL BT Version: 3.4.10 TIA, Rob
Re: Expiration of SQL BackTrack Filespaces
It handles expiration like Oracle RMAN (in general). The expiration is done by the client, not the normal versioning of TSM. The SQL-BT setup and config should have info on setting up Management Class on TSM for this. I have SQL-BT version 4.2 on AIX Sybase Client. The config on SQL-BT allows you to specify how many versions you want to keep, and SQL-BT expires old version each day when it does a backup. Whether the data went to TSM disk pool first and then to tape or directly to tape has no bearing at all on the expiration. David B. Longo System Administrator Health First, Inc. 3300 Fiske Blvd. Rockledge, FL 32955-4305 PH 321.434.5536 Pager 321.634.8230 Fax:321.434.5509 [EMAIL PROTECTED] [EMAIL PROTECTED] 01/21/04 10:39AM Hello all, How does TSM handle the expiration of SQL Backtrack filespaces if the data was originally written directly to tape, thus never existing on hard disk? We have a situation where these filespaces are not expiring and are not even being marked as inactive yet they are in a MC that is set to retain only ten versions. TSM Server: 5.1.5.5 OS Version: AIX 5.1 SQL BT Version: 3.4.10 TIA, Rob ## This message is for the named person's use only. It may contain confidential, proprietary, or legally privileged information. No confidentiality or privilege is waived or lost by any mistransmission. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it, and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. Health First reserves the right to monitor all e-mail communications through its networks. Any views or opinions expressed in this message are solely those of the individual sender, except (1) where the message states such views or opinions are on behalf of a particular entity; and (2) the sender is authorized by the entity to give such views or opinions. ##
Re: Expiration of SQL BackTrack Filespaces
Rob, Like David said, etc... During SQL-BT setup, you should have created a MC for SQL-BT backups w/ Backup CopyGroup w/ VerExists=1 VerDeleted=0 RetExtra=0 RetOnly=0. SQL-BT incorporates datime values in its TSM backup filenames so that each backup filename is unique; if you setup SQL-BT to keep 10 versions, you might have 11 dbf backups (uniquely named Active TSM backup files) until SQL-BT dtoexpire processing runs. Then, SQL-BT expires a backup version by marking the appropriate TSM backup files Inactive. During the next TSM EXPIre Inventory processing, these Inactive backup files are deleted immediately (because your SQL-BT-MC B-CG has VerD=0.) Some tape space can be reclaimed immediately (during EXPIre Inventory processing) iff your tape STGpool is collocated by filespace and one/more tape(s) no longer contain(s) any Active SQL-BT backups. Otherwise, you have to run tape reclamation processing for that STGpool to recover the partially available tapes for reuse. -- [EMAIL PROTECTED] (203.432.6693) David Longo wrote: It handles expiration like Oracle RMAN (in general). The expiration is done by the client, not the normal versioning of TSM. The SQL-BT setup and config should have info on setting up Management Class on TSM for this. I have SQL-BT version 4.2 on AIX Sybase Client. The config on SQL-BT allows you to specify how many versions you want to keep, and SQL-BT expires old version each day when it does a backup. Whether the data went to TSM disk pool first and then to tape or directly to tape has no bearing at all on the expiration. [EMAIL PROTECTED] 01/21/04 10:39AM Hello all, How does TSM handle the expiration of SQL Backtrack filespaces if the data was originally written directly to tape, thus never existing on hard disk? We have a situation where these filespaces are not expiring and are not even being marked as inactive yet they are in a MC that is set to retain only ten versions. TSM Server: 5.1.5.5 OS Version: AIX 5.1 SQL BT Version: 3.4.10 TIA, Rob
SQL Backtrack and TSM
Hello all, We have a SQL Backtrack process that invokes a TSM retrieval and has been aborting with the error: ANS1314E (RC14) File data currently unavailable on server. To remedy this we created a management class that would move this data directly to our primary diskpool instead of pooling up in our tapepool first. This was to eliminate a possibility of migration moving the data before SQL Backtrack was able to accept the data. Other fixes we have tried is to set our IDLETimeout much higher in hopes that the extra time would allow SQL Backtrack time to create the destination, then retrieve to it. Unfortunately Tivoli has been unusually slow in responding, so any help on this would be appreciated! Thanks, Rob
TDP for SAP R/3 versus BMC SQL Backtrack
Hello, on our site SQL Backtrack is in production for nearly two years. Now I have to compare both solutions. We are running 50+ SAP systems on HP and SUN Solaris systems with Oracle 64bit databases. Has anyone draw a comparison of this two products? Are there major benefits in one of the products? Any comment will be helpful. Thanks in advance. Rolf Meyer Systems Consultant Info Business Systems GmbH 22607 Hamburg
Re: TDP for SAP R/3 versus BMC SQL Backtrack
We used to run SQL Backtrack and we now run TDP for SAP R/3. In my opinion here are the differences SQL Backtrack Benefits - great compression ratio - seems to handle well large databases Disadvantages - licenses are based on size of database if you grow alot (which we do) you spend alot of time and money upgrading your license - support seems to frequently blame the problem on tsm TDP for SAP R/3 Benefits - licenses are based on server not database - support is Tivoli so it can bounce between TDP and TSM support with little effort on your part - a little bit more flexibility between threads and multiplexing as to who data is passed. Disadvantages - compression is only blank space - doesn't seem to handle as well databases over 500 or so GBthis is improving slowly This was our experience and I will happily answer any other questions offline Becky -Original Message- From: Rolf Meyer [mailto:rolf.meyer;SUBNET.DE] Sent: Friday, October 25, 2002 12:03 PM To: [EMAIL PROTECTED] Subject: TDP for SAP R/3 versus BMC SQL Backtrack Hello, on our site SQL Backtrack is in production for nearly two years. Now I have to compare both solutions. We are running 50+ SAP systems on HP and SUN Solaris systems with Oracle 64bit databases. Has anyone draw a comparison of this two products? Are there major benefits in one of the products? Any comment will be helpful. Thanks in advance. Rolf Meyer Systems Consultant Info Business Systems GmbH 22607 Hamburg
SQL Backtrack
Hi guys, Has anybody experience in SQL Backtrack with TSM 4.2 in SAN environment? I upgraded LAN environment to SAN. When I had LAN all worked properly but in SAN doesn't. I have: TSM Server 4.2.2.5 Storage Agent 4.2.2.5 TSM client 4.2.2.1 Latest TSM API and latest versions of SQL Backtrack for Oracle and OBSI. When I try to backup Oracle vi SQL Backtrack I get en error: ANS0201E Help me, please! ukasz Dobosz S4E S.A. mobile: +48 609 666 356 e-mail: [EMAIL PROTECTED] office: +48 12 296 4545 fax: +48 12 296 4546
Re: TSM 5.1 and SQL Backtrack
As of Wednesday AM, BMC was saying no support for the OBSI witn V5R1. As of Thursday afternoon, BMC reversed thier position. (It may have something to do with the check for support that was cut on Tuesday.) This has pushed back our upgrade by a week, but we've found no problems in testing with AIX 4.3.3. Quoting Steve Figel [EMAIL PROTECTED]: Has anyone heard of issues or problems surrounding TSM 5.1 and SQL BACKTRACK We are planning on installing 5.1 and use SQL BACKTRACK and I just heard that there is a problem with 5.1 Thanks Steve Figel Storage Consultant Salem Group 336.744.5999 (ext 1290) 336.414.0224 Cell [EMAIL PROTECTED] Fred Johanson
errors using SQL-Backtrack
Has anyone seen these errors or know if they point to a problem with TSM at all? DT-01610E: Attempted to insert new dump process using duplicate PID: 25176 DT-01610E: The OS re-assigned a PID before it had been removed from the OBT task list. DT-01610E: The backup must be restarted. Nothing has been damaged. This is an unusual event. The oncall reran the job and got the following error: DT-01251W: Interrupted '41 of 304 database files backed up so far' on 04/04/2002 00:14:46. DT-01251W: Interrupted 'dtoquery for dtobackup [8589]' on 04/04/2002 00:14:46. DT-01380W: Terminated by Hangup (signo = 1) DT-01380W: Terminated by Hangup (signo = 1) DT-02928F: dtoquery write error , Broken pipe Thanks, [EMAIL PROTECTED]
Re: how does TSM / sql backtrack use management classes?
We have a management class called SQLBACKTRACK and the copy class has the following attributes: vere=nolimit verd=0 rete=nolim reto=0 In the include/exclude file we point the SQL Backtrack backup to the management class: include /BACKTRACK:*/.../* sqlbacktrack In the SQL Backtrack control file you indicate how many versions of the backups to keep. If the database is deleted off the server make sure to delete the backups off the TSM server before deleting the control file (indicate 0 versions to be kept). If not you will end up keeping all the backups for that server. We currently have 30 TB of data backed up by SQL Backtrack. Any questions feel free to call. Frank Mauro Backup and Recovery Services [EMAIL PROTECTED] Telephone Number: 603.245.3207 Beeper Number: 888.797.0806 -Original Message- From: Steve Argersinger [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 05, 2002 9:42 AM To: [EMAIL PROTECTED] Subject: Re: how does TSM / sql backtrack use management classes? I asked this question of BMC at least 6-12 months ago and officially got the answer of this is unsupported . We are getting around it by creating a separate profile in a different location and move it back and forth between the temporary area, and the real area before starting the backup. Seemed like a reasonable request to have 2 different mgmtclasses for backups, and archives, but they said no. Steve Argersinger Ruan Transportation -Original Message- From: Rolf Meyer [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 05, 2002 12:25 AM To: [EMAIL PROTECTED] Subject: Re: how does TSM / sql backtrack use management classes? Hello, using SQL BackTrack, all retention management is done by SQL-BT acording to definitions in the so called Oracatalog. Every backup object is unique, because the name includes a timestamp. Versioning from TSM sight cannot be established. In the inst. guide of SQLBT-interface mode to TSM, called obsi.adsm, you find the nessessary defs for the backup or archive copy groups. Greetings Rolf Meyer On Monday, 4. March 2002 22:20, you wrote: We're using SQL backtrack to backup our oracle database. If two backtrack backup scripts are run using two different management classes against the same database, (ie.. management class one has 3 version, 30 days and management class two has 6 versions 60 days) how does TSM handle the backup? Will it in effect use the shortest management class. Or will it keep two sets of the database, one for 3/30 and the other for 6/60?
Re: how does TSM / sql backtrack use management classes?
I asked this question of BMC at least 6-12 months ago and officially got the answer of this is unsupported . We are getting around it by creating a separate profile in a different location and move it back and forth between the temporary area, and the real area before starting the backup. Seemed like a reasonable request to have 2 different mgmtclasses for backups, and archives, but they said no. Steve Argersinger Ruan Transportation -Original Message- From: Rolf Meyer [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 05, 2002 12:25 AM To: [EMAIL PROTECTED] Subject: Re: how does TSM / sql backtrack use management classes? Hello, using SQL BackTrack, all retention management is done by SQL-BT acording to definitions in the so called Oracatalog. Every backup object is unique, because the name includes a timestamp. Versioning from TSM sight cannot be established. In the inst. guide of SQLBT-interface mode to TSM, called obsi.adsm, you find the nessessary defs for the backup or archive copy groups. Greetings Rolf Meyer On Monday, 4. March 2002 22:20, you wrote: We're using SQL backtrack to backup our oracle database. If two backtrack backup scripts are run using two different management classes against the same database, (ie.. management class one has 3 version, 30 days and management class two has 6 versions 60 days) how does TSM handle the backup? Will it in effect use the shortest management class. Or will it keep two sets of the database, one for 3/30 and the other for 6/60?
how does TSM / sql backtrack use management classes?
We're using SQL backtrack to backup our oracle database. If two backtrack backup scripts are run using two different management classes against the same database, (ie.. management class one has 3 version, 30 days and management class two has 6 versions 60 days) how does TSM handle the backup? Will it in effect use the shortest management class. Or will it keep two sets of the database, one for 3/30 and the other for 6/60?
Re: how does TSM / sql backtrack use management classes?
Not familiar with SQL BT for Oracle but I use (unfortunately) SQL BackTrack for Informix. There is a $DTICATALOG directory (as database instance owner, echo $DTICATALOG). Within the DTI Catalog directory, there is a file called dtoptions. One stanza from this file shows how a BMQ SQ BT backup pool is bound to a TSM management class whether it is a backup or archive as well as the TSM filespace (remember that the backup_pool=V35003DM is a BMC reference: begin backup_pool=V35003DM obsi=adsm dsmi_config=/usr/tivoli/tsm/client/api/bin/dsm.opt mount-wait=y filespace=/V35003DM management_class=32day storage-pool=archive end backup_pool This is the line in the backup script where the BMC -to option points the backup to a BMC backup_pool: dtibackup -whole_system -quiet -noprompt -to V35003DM -debug -debugfile /tmp/dbg.dmartbkup and to add a bit more to this mess, there is an instance directory within the $DTICATALOG path that contains the default for any backups make by this instance user in case a -to option is not specified. It contains defaults for all dbspaces plus a default for logical logs. The name of the instance directory is dbcci and there is another instance directory called psinf_73uc1. In the case of an Informix database, the place where the default BMC backup_pool is set is called onbarconfig: informix at afcprod1: /usr/bmc/IFX/data/dtcat $ ls dbccidtoptionsdtseqpsinf_73uc1 informix at afcprod1: /usr/bmc/IFX/data/dtcat $ cd dbcci informix at afcprod1: /usr/bmc/IFX/data/dtcat/dbcci $ ls exportconfig exporthistory onbarconfigonbarhistory profile schemahistory informix at afcprod1: /usr/bmc/IFX/data/dtcat/dbcci $ more onbarconfig begin object=@@default pool=V35003DM end object begin object=logical-log pool=V35003DM end object Hope all that mess helped... take this with a grain of salt as the BMC SQL BT for Oracle product may work differently... George Lesho AFC Enterprises Reichmuth, Michael R. To: [EMAIL PROTECTED] mrreich@NPPD. cc: (bcc: George Lesho/Partners/AFC) COM Subject: how does TSM / sql backtrack use Sent by: management classes? ADSM: Dist Stor Manager [EMAIL PROTECTED] IST.EDU 03/04/02 03:20 PM Please respond to ADSM: Dist Stor Manager We're using SQL backtrack to backup our oracle database. If two backtrack backup scripts are run using two different management classes against the same database, (ie.. management class one has 3 version, 30 days and management class two has 6 versions 60 days) how does TSM handle the backup? Will it in effect use the shortest management class. Or will it keep two sets of the database, one for 3/30 and the other for 6/60?
Re: how does TSM / sql backtrack use management classes?
Hello, using SQL BackTrack, all retention management is done by SQL-BT acording to definitions in the so called Oracatalog. Every backup object is unique, because the name includes a timestamp. Versioning from TSM sight cannot be established. In the inst. guide of SQLBT-interface mode to TSM, called obsi.adsm, you find the nessessary defs for the backup or archive copy groups. Greetings Rolf Meyer On Monday, 4. March 2002 22:20, you wrote: We're using SQL backtrack to backup our oracle database. If two backtrack backup scripts are run using two different management classes against the same database, (ie.. management class one has 3 version, 30 days and management class two has 6 versions 60 days) how does TSM handle the backup? Will it in effect use the shortest management class. Or will it keep two sets of the database, one for 3/30 and the other for 6/60?
question about TDP for Oracle/RMAN vs. BMC's SQL BackTrack dry run
hi, You can use a RMAN command 'validate'. Please see RMAN reference manual to find out more about validate command. regards, Thiha does anyone know whether TDPO v2.2 allows for dry run restores /or a preview of a restore to validate the media without writing the data, like SBT does? (I've perused the website the Redbook, and don't see that it does.)
question about TDP for Oracle/RMAN vs. BMC's SQL BackTrack dry run
Hello all, does anyone know whether TDPO v2.2 allows for dry run restores /or a preview of a restore to validate the media without writing the data, like SBT does? (I've perused the website the Redbook, and don't see that it does.) thanks! lisa
Re: SQL-BACKTRACK ORACLE
We use sql-backtrack for Sybase, but not Oracle - never wanted to spend the money. We've also looked at RMAN, but rejected it for various reasons. The incremental hot seems good, but you're still just pulling out changed blocks, which is basically whats in the logs. The vast majority of our oracle databases run a hot once a week and full export on the other 6 nights as an integrity check. Logs are backed up nightly to tsm. On certain large and active databases, we run hots 3 times a week with 4 full exports. There is a lot of log activity on these systems, so we backup the logs to tsm each hour. All of our Hot backups are performed by a multi-threaded ksh script that creates a compressed backup on disk. The current project is to modify this script to handle raw volumes. Rick On 13 Aug 2001, at 15:49, Thiha Than wrote: hi, Our oracle DBA claims that 'hot' incremental backups of Oracle takes as = long as 'hot' full backups using SQL-BACKTRACK. Instead he does weekly = full 'hot' backups of the database and backups of the redo logs thru the = week. Is that how others using SQL-BACKTRACK and ORACLE do thier backups? It's the same for backing up oracle databases using RMAN, incremental takes almost as long as a full backup. I have never used sql-backtrack before so I cannot comment on it. With RMAN, it has to scan through every single Oracle data block to find the changed block. So the incremental backup will take a long time, but the amount of data sent through can be significantly less. regards, Thiha
Re: SQL-BACKTRACK ORACLE
We used to use SQL Backtrack and we did a hot full backup of a 1 TB database nightly in about 3-4 hours going to a 300GB disk pool with 16 threads. We then backed up the redo logs nightly. -Original Message- From: Lawrence Clark [mailto:[EMAIL PROTECTED]] Sent: Friday, August 10, 2001 3:07 PM To: [EMAIL PROTECTED] Subject: SQL-BACKTRACK ORACLE Hi: Our oracle DBA claims that 'hot' incremental backups of Oracle takes as long as 'hot' full backups using SQL-BACKTRACK. Instead he does weekly full 'hot' backups of the database and backups of the redo logs thru the week. Is that how others using SQL-BACKTRACK and ORACLE do thier backups? Larry Clark NYS Thruway Authority (518)-471-4202 Certified: Aix 4.3 System Administration Aix 4.3 System Support Tivoli ADSM/TSM V 3 Consultant
Re: SQL-BACKTRACK ORACLE
We do incremental on weekdays and full on weekends for our Oracle databases. I do find that both types of backup take about the same amount of time. As far as I know we never looked into backup of just redo during the week but I think we will now. -Original Message- From: Davidson, Becky [mailto:[EMAIL PROTECTED]] Sent: Monday, August 13, 2001 2:15 PM To: [EMAIL PROTECTED] Subject: Re: SQL-BACKTRACK ORACLE We used to use SQL Backtrack and we did a hot full backup of a 1 TB database nightly in about 3-4 hours going to a 300GB disk pool with 16 threads. We then backed up the redo logs nightly. -Original Message- From: Lawrence Clark [mailto:[EMAIL PROTECTED]] Sent: Friday, August 10, 2001 3:07 PM To: [EMAIL PROTECTED] Subject: SQL-BACKTRACK ORACLE Hi: Our oracle DBA claims that 'hot' incremental backups of Oracle takes as long as 'hot' full backups using SQL-BACKTRACK. Instead he does weekly full 'hot' backups of the database and backups of the redo logs thru the week. Is that how others using SQL-BACKTRACK and ORACLE do thier backups? Larry Clark NYS Thruway Authority (518)-471-4202 Certified: Aix 4.3 System Administration Aix 4.3 System Support Tivoli ADSM/TSM V 3 Consultant
SQL-BACKTRACK ORACLE
hi, Our oracle DBA claims that 'hot' incremental backups of Oracle takes as = long as 'hot' full backups using SQL-BACKTRACK. Instead he does weekly = full 'hot' backups of the database and backups of the redo logs thru the = week. Is that how others using SQL-BACKTRACK and ORACLE do thier backups? It's the same for backing up oracle databases using RMAN, incremental takes almost as long as a full backup. I have never used sql-backtrack before so I cannot comment on it. With RMAN, it has to scan through every single Oracle data block to find the changed block. So the incremental backup will take a long time, but the amount of data sent through can be significantly less. regards, Thiha
Re: SQL backtrack /ADSM problem
We had that problem at ADSM 3.1 on AIX 4.3.3 but only when we did a backup of the archive logs...the full backups were fine. We never managed to resolve that problem we just stopped doing the archive log backups and are now migrating to Tivoli Data Protection. Becky Davidson Data Manager/AIX Administrator EDS/Earthgrains voice: 314-259-7589 fax: 314-877-8589 email: [EMAIL PROTECTED] -Original Message- From: Jason Jackson [mailto:[EMAIL PROTECTED]] Sent: Tuesday, June 26, 2001 5:06 PM To: [EMAIL PROTECTED] Subject: SQL backtrack /ADSM problem I am running ADSM 3.7 on AIX 4.3.2 and have intermittant problems with an Oracle backup. Oracle is version 8.1.5. We use BMC SQL Backtrack to backup the Oracle database and move that backup to storage via ADSM. Once in a while, I receive errors through SQL backtrack: [dtodump 180482} DT-01254E: Program error 11 (Segmentation fault), saving core file in '/datatools/obacktrack-3.2.80.3/cdump/dtodump-06.18.2001-21:22-180482/core' According to the logs, everything is fine with ADSM. I know DTODUMP is a SQL Backtrack function. I've been advised to check the recommended API levels for ADSM to work with this version of SQL Backtrack. Has anyone else come across similar problems using Backtrack ADSM?
Re: SQL backtrack /ADSM problem
Once in a while, I receive errors through SQL backtrack: [dtodump 180482} DT-01254E: Program error 11 (Segmentation fault), saving core file in '/datatools/obacktrack-3.2.80.3/cdump/dtodump-06.18.2001-21:22-180482/core' I remember one situation using TSM and Backtrack with such errors after a 100% full of archlog filesystem, moving the archlog data to another fs, then backup the remaining files, and copy back the moved files twice (some time later). If Backtrack found the same archlog dataset the second time, it crashes. We need a day to find out. -- Herzliche Gruesse / Many greetings Rolf Meyer Raalandsweg 22 D-22559 Hamburg [EMAIL PROTECTED][EMAIL PROTECTED]
SQL backtrack /ADSM problem
I am running ADSM 3.7 on AIX 4.3.2 and have intermittant problems with an Oracle backup. Oracle is version 8.1.5. We use BMC SQL Backtrack to backup the Oracle database and move that backup to storage via ADSM. Once in a while, I receive errors through SQL backtrack: [dtodump 180482} DT-01254E: Program error 11 (Segmentation fault), saving core file in '/datatools/obacktrack-3.2.80.3/cdump/dtodump-06.18.2001-21:22-180482/core' According to the logs, everything is fine with ADSM. I know DTODUMP is a SQL Backtrack function. I've been advised to check the recommended API levels for ADSM to work with this version of SQL Backtrack. Has anyone else come across similar problems using Backtrack ADSM?
Re: SQL-Backtrack OBSI Module (via TSM API)
Hello all, We are experiencing this same problem with BackTrack not being able to perform node authentication following the upgrade to 2.5 and I was wondering if there have been any resolution. We are predominantly running on AIX and backing up Sybase. By CC: to BMC support, I would like to open a problem report with you (for my company info, please reference case 444873) and point out that it appears your people need to have more training regarding the ADSM OBSI module. Also, is it true that you officially do not support TSM 4.1. If so, is there a planned date for this support? Thanks, Scott McCambly At 02:44 PM 3/12/01 -0600, Allen Barth wrote: Hi all We've been using SQL-Backtrack for Sybase and Oracle for 4+ years. And recently: Upgrading the obsi to v2.5 yielded a non functioning system. BMC personnel, after spending 3 days trying to dial into our system (got warm fuzzies just with that alone) did manage to get their stuff to work BUT They don't seem to be able to support PASSWORDACCESS Generate They strongly felt they needed to create a new client node to contain the backtrack info and were unable to use the nodename (hostname) of the machine from where the databases reside. Further they didn't understand the impact of a nodename change (we use colocation, and they wouldn't be able to restore any old SQL backups) They claim they don't support TSM4.1.2 They could not understand what client option sets were They want us to change ownership of the generated password file away from root to they could read it. Calls to support are indeed frustrating. Where it my choice, I'd move to another method ASAP. Al Barth Mark A. Adams mark_adams@CSGSYTo: [EMAIL PROTECTED] STEMS.COM cc: Sent by: ADSM: Subject: Re: SQL-Backtrack OBSI Module (via TSM API) for Oracle Dist Stor-versus- TSM TDP for Oracle Manager [EMAIL PROTECTED] .EDU 03/12/01 10:38 AM Please respond to ADSM: Dist Stor Manager We have been using SQL-Backtrack for 3 years now. We like it very well. Yes, it will do hot backups. SQL-Backtrack backs up directly to TSM using the API interface. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Larry Girardi Sent: Friday, March 09, 2001 11:30 AM To: [EMAIL PROTECTED] Subject: SQL-Backtrack OBSI Module (via TSM API) for Oracle -versus- TSM TDP for Oracle People, I am wondering if anyone has any experience with this stuff. I am really interested in both Oracle and SQL Server! 1) Does SQL-Backtrack backup directly into TSM without having to use/buy the TSM TDP for Oracle/SQL Server ? 2) Can you do a HOT backup of the Oracle/SQL Server database ? 3) Is it slick ... does it work well ? Thank you, Larry Scott McCambly AIX/NetView/ADSM Specialist - Unopsys Inc. Ottawa, Ontario, Canada (613)799-9269
SQL-BACKTRACK oracle db restore seems to be hanging?
ADSM V3,1,0.6 AIX 4.3.2.0 STK-9710 with DLT7000 drives Problem: Trying to restore an oracle db backup that was backed up via SQL-BACTRACK. Some of the files restore quickly. Others mount a tape and seem to hang at about 61.1k Sess State changes from Run to IdleW. When in Stat of Run the Wait Time remains at 0 S, of course, yet nothing gets restored, and the session stays in this state for hours. If State is IdleW it can wait for hours. The session has the tape that it is requesting, but nothing happens. Cancel of the session seems to take forever. The restores that seem to hang are usually trying to restore from two specific tapes. However there are only four tapes involved with this restore. Some files have been, quickly and successfully restored from the suspect tapes as well. EXAMPLE SESSION: Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name Number Method StateTimeSent Recvd Type -- -- -- -- --- --- - 1,965 ShMem Run 0 S 61.1 K 833 Node SQL-BACKTRACKWEICISP4 Any ideas as to why this restore is taking so long would be greatly appreciated. If you require more information for proper analysis please ask. ThanX Jim Taylor Senior Associate, Technical Services Enlogix * E-mail: [EMAIL PROTECTED] * Office: (416) 496-5264 ext. 286 * Cell: (416)458-6802 * Fax: (416) 496-5245
Re: SQL-BACKTRACK oracle db restore seems to be hanging?
SQL-Backtrack have some issues to restore from different AIX levels. Are u doing physical restore or logical extraction? You can monitor restore process with "dtwatch" at client side. Check ocatalog directory, if it's not in sync with ADSM, restore causes problems. For more correct analysis report problem to BMC support. Thank you, Bandu Vibhute, Bestfoods Baking Company, 55 Paradise Lane, Bay Shore, NY, 11706 Voice: 631-951-5212, Cell: 516-702-0323 -Original Message- From: Jim Taylor [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 04, 2001 2:23 PM To: [EMAIL PROTECTED] Subject: SQL-BACKTRACK oracle db restore seems to be hanging? ADSM V3,1,0.6 AIX 4.3.2.0 STK-9710 with DLT7000 drives Problem: Trying to restore an oracle db backup that was backed up via SQL-BACTRACK. Some of the files restore quickly. Others mount a tape and seem to hang at about 61.1k Sess State changes from Run to IdleW. When in Stat of Run the Wait Time remains at 0 S, of course, yet nothing gets restored, and the session stays in this state for hours. If State is IdleW it can wait for hours. The session has the tape that it is requesting, but nothing happens. Cancel of the session seems to take forever. The restores that seem to hang are usually trying to restore from two specific tapes. However there are only four tapes involved with this restore. Some files have been, quickly and successfully restored from the suspect tapes as well. EXAMPLE SESSION: Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name Number Method StateTimeSent Recvd Type -- -- -- -- --- --- - 1,965 ShMem Run 0 S 61.1 K 833 Node SQL-BACKTRACKWEICISP4 Any ideas as to why this restore is taking so long would be greatly appreciated. If you require more information for proper analysis please ask. ThanX Jim Taylor Senior Associate, Technical Services Enlogix * E-mail: [EMAIL PROTECTED] * Office: (416) 496-5264 ext. 286 * Cell: (416)458-6802 * Fax: (416) 496-5245 "WorldSecure Server baking.bestfoods.com" made the following annotations on 04/04/01 14:38:27 - The origin of this electronic mail message was the Internet. Bestfoods Baking cannot validate the authenticity of the sender and therefore cannot be held accountable for any content within. === "WorldSecure Server baking.bestfoods.com" made the following annotations on 04/04/01 14:47:36 - This message may contain confidential and trade secret information of Bestfoods Baking, and be subject to the Economic Espionage Act of 1996. For recipient's use only. If you have received this message in error, please delete immediately, and alert the sender. ===
Sybase Dump Striping using BMC SQL-Backtrack
Hi everyone, We've been using SQL-Backtrack (was Datatools, now BMC... trying to get all those key words in to help those future searches ;-) successfully for many years now to backup Sybase. Recently one database has grown so large so as to exceed the maximum file size allowed at our current level of AIX when it is dumped for backup. For this reason and to try and maximize performance we want to implement dump striping. The documentation on this, however, with respect to using the ADSM/TSM OBSI module is vague at best and has left us a little confused. It states that separate management classes must be used for each stripe, and that these must reference separate tape pools, but it is not clear if these "pools" are the Backtrack pool definitions or the actual TSM storage pools. Does anyone have experience in implementing this? Do we indeed need separate management class definitions, or just a MC that points to a tape pool using a DevClass that has multiple mount points available? And I'm assuming in this case that collocation would need to be OFF for this tape pool. Any advise would be appreciated. TIA - Scott PS: The folks at BMC support can reference Case 444873. Scott McCambly AIX/NetView/ADSM Specialist - Unopsys Inc. Ottawa, Ontario, Canada (613)799-9269
R?f:Re: SQL-Backtrack OBSI Module (via TSM API) for Oracle
Hello I have a problem which looks like yours Before Y2000, I have upgraded obsi to version 2.5 without problem. I'm working on a desaster recovery plan. After restoring on a test server (Sun Solaris) all the files saved from the production server, reinstalling and customizing the SQLBT programs with the CPU ID I am not able to restore a database. Reason: ADSM message Objet doesn't exist on server. After tracing network traffic with command snoop, I see a difference between production and test server. Production server ask for an objet /BACKTRACK/x/xx.01234567 Test server ask for an objet /BACKTRACK/x/xx.01234567oracle In ADSM API programming manual a backup objet is defined by: filespace name ex /BACKTRACK hl name(directory) ex control_files ll name (filename) ex system.dbf.0123456 owner ex oracle I have found a workaround to force owner field to blank in the obsi by adding the line owner= in the file oracatalog/poolinfo/POOLS before end backup_pool In France SQLBT support doesn't know ADSM. Hope this help Alain Ricois email [EMAIL PROTECTED] Sparateur de messages Objet : Re: SQL-Backtrack OBSI Module (via TSM API) for Oracle -vers Auteur : "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Date :12/03/2001 21:49 Hi all We've been using SQL-Backtrack for Sybase and Oracle for 4+ years. And recently: Upgrading the obsi to v2.5 yielded a non functioning system. BMC personnel, after spending 3 days trying to dial into our system (got warm fuzzies just with that alone) did manage to get their stuff to work BUT They don't seem to be able to support PASSWORDACCESS Generate They strongly felt they needed to create a new client node to contain the backtrack info and were unable to use the nodename (hostname) of the machine from where the databases reside. Further they didn't understand the impact of a nodename change (we use colocation, and they wouldn't be able to restore any old SQL backups) They claim they don't support TSM4.1.2 They could not understand what client option sets were They want us to change ownership of the generated password file away from root to they could read it. Calls to support are indeed frustrating. Where it my choice, I'd move to another method ASAP. Al Barth "Mark A. Adams" mark_adams@CSGSYTo: [EMAIL PROTECTED] STEMS.COM cc: Sent by: "ADSM: Subject: Re: SQL-Backtrack OBSI Module (via TSM API) for Oracle Dist Stor-versus- TSM TDP for Oracle Manager" [EMAIL PROTECTED] .EDU 03/12/01 10:38 AM Please respond to "ADSM: Dist Stor Manager" We have been using SQL-Backtrack for 3 years now. We like it very well. Yes, it will do hot backups. SQL-Backtrack backs up directly to TSM using the API interface. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Larry Girardi Sent: Friday, March 09, 2001 11:30 AM To: [EMAIL PROTECTED] Subject: SQL-Backtrack OBSI Module (via TSM API) for Oracle -versus- TSM TDP for Oracle People, I am wondering if anyone has any experience with this stuff. I am really interested in both Oracle and SQL Server! 1) Does SQL-Backtrack backup directly into TSM without having to use/buy the TSM TDP for Oracle/SQL Server ? 2) Can you do a HOT backup of the Oracle/SQL Server database ? 3) Is it slick ... does it work well ? Thank you, Larry ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify [EMAIL PROTECTED] ** Unknown data type
Re: SQL-Backtrack OBSI Module (via TSM API) for Oracle -versus- TSM TDP for Oracle
We have been using SQL-Backtrack for 3 years now. We like it very well. Yes, it will do hot backups. SQL-Backtrack backs up directly to TSM using the API interface. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Larry Girardi Sent: Friday, March 09, 2001 11:30 AM To: [EMAIL PROTECTED] Subject: SQL-Backtrack OBSI Module (via TSM API) for Oracle -versus- TSM TDP for Oracle People, I am wondering if anyone has any experience with this stuff. I am really interested in both Oracle and SQL Server! 1) Does SQL-Backtrack backup directly into TSM without having to use/buy the TSM TDP for Oracle/SQL Server ? 2) Can you do a HOT backup of the Oracle/SQL Server database ? 3) Is it slick ... does it work well ? Thank you, Larry
Re: SQL Backtrack Restore
It's been our experience that you need a valid control file to do such a move. We such a move every week via a script that crossmounts a control file from machine to machine. At 08:06 AM 3/9/2001 -0800, you wrote: Can backups that were created via SQLBACKTRACK be restored to a different client using the TSM fromnode feature? If yes, what would the 'set access' command be on the source client? Jim Taylor Senior Associate, Technical Services Enlogix * E-mail: [EMAIL PROTECTED] * Office: (416) 496-5264 ext. 286 * Cell: (416)458-6802 * Fax: (416) 496-5245
Re: SQL Backtrack Restore
Jim, I use SQL BackTrack for Informix to restore backups made on one node to another using the virtualnodename parameter set to the source machine's name and placed into the target machine's dsm.opt file. Since you didn't specify which SQL BackTrack product you are using and I don't know if all of them work the same way, I can't give you any more info. If you are using the SQL BackTrack for Informix product, let me know and I will describe the steps to backing up on one machine and restoring to another... Lot of small details to get a sucsessful restore... George Lesho Storage/System Admin AFC Enterprises Jim Taylor [EMAIL PROTECTED] on 03/09/2001 10:06:06 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: George Lesho/Partners/AFC) Fax to: Subject: SQL Backtrack Restore Can backups that were created via SQLBACKTRACK be restored to a different client using the TSM fromnode feature? If yes, what would the 'set access' command be on the source client? Jim Taylor Senior Associate, Technical Services Enlogix * E-mail: [EMAIL PROTECTED] * Office: (416) 496-5264 ext. 286 * Cell: (416)458-6802 * Fax: (416) 496-5245
SQL-Backtrack OBSI Module (via TSM API) for Oracle -versus- TSM TDP for Oracle
People, I am wondering if anyone has any experience with this stuff. I am really interested in both Oracle and SQL Server! 1) Does SQL-Backtrack backup directly into TSM without having to use/buy the TSM TDP for Oracle/SQL Server ? 2) Can you do a HOT backup of the Oracle/SQL Server database ? 3) Is it slick ... does it work well ? Thank you, Larry
Re: SQL-Backtrack OBSI Module (via TSM API) for Oracle -versus- T SM TDP for Oracle
We are currently using SQL Backtrack on our production database and TDP for SAP R/3 on development systems migrating to TDP on all. In answer to your questions 1) Yes SQL Backtrack goes directly into TSM 2) Yes you can do a hot backup. We do a 1 T database hot every night 3) Hate it. We have problems with just about everything with it. Setting it up is an issue. Upgrading versions has caused us problems. Getting support has caused us major problems because there is a tendency to not fully look into the problem and just immediately blame it on TSM. If there is a tape error it does not retry very well and the entire backup fails. We have had problems with SQL Backtrack doing it's own expiration. The licensing scheme is done on the size of your database. I suppose that is ok if your database doesn't grow much but ours does so you have to get a license at 250, 500, 750, 1200 which of course costs significantly more. For us financially TDP is the better solution. The installation is easier and support has been better. We have also had fewer problems with it. Then again we are also using TDP for SAP R/3 so I am not sure if TDP for Oracle is better or worse. That's my .02 Becky Davidson Data Manager/AIX Administrator EDS/Earthgrains voice: 314-259-7589 fax: 314-877-8589 email: [EMAIL PROTECTED] -Original Message- From: Larry Girardi [mailto:[EMAIL PROTECTED]] Sent: Friday, March 09, 2001 11:30 AM To: [EMAIL PROTECTED] Subject: SQL-Backtrack OBSI Module (via TSM API) for Oracle -versus- TSM TDP for Oracle People, I am wondering if anyone has any experience with this stuff. I am really interested in both Oracle and SQL Server! 1) Does SQL-Backtrack backup directly into TSM without having to use/buy the TSM TDP for Oracle/SQL Server ? 2) Can you do a HOT backup of the Oracle/SQL Server database ? 3) Is it slick ... does it work well ? Thank you, Larry
Re: SQL-Backtrack OBSI Module (via TSM API) for Oracle -versus- T SM TDP for Oracle
Becky, Thank you! That is what I needed (the straight poop!). Does anyone have a differing opinion or additional experience? Thanks again, Larry "Davidson, Becky" [EMAIL PROTECTED] on 03/09/2001 12:36:57 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: Larry Girardi/IS/Travelers) Subject: Re: SQL-Backtrack OBSI Module (via TSM API) for Oracle -versus- T SM TDP for Oracle We are currently using SQL Backtrack on our production database and TDP for SAP R/3 on development systems migrating to TDP on all. In answer to your questions 1) Yes SQL Backtrack goes directly into TSM 2) Yes you can do a hot backup. We do a 1 T database hot every night 3) Hate it. We have problems with just about everything with it. Setting it up is an issue. Upgrading versions has caused us problems. Getting support has caused us major problems because there is a tendency to not fully look into the problem and just immediately blame it on TSM. If there is a tape error it does not retry very well and the entire backup fails. We have had problems with SQL Backtrack doing it's own expiration. The licensing scheme is done on the size of your database. I suppose that is ok if your database doesn't grow much but ours does so you have to get a license at 250, 500, 750, 1200 which of course costs significantly more. For us financially TDP is the better solution. The installation is easier and support has been better. We have also had fewer problems with it. Then again we are also using TDP for SAP R/3 so I am not sure if TDP for Oracle is better or worse. That's my .02 Becky Davidson Data Manager/AIX Administrator EDS/Earthgrains voice: 314-259-7589 fax: 314-877-8589 email: [EMAIL PROTECTED] -Original Message- From: Larry Girardi [mailto:[EMAIL PROTECTED]] Sent: Friday, March 09, 2001 11:30 AM To: [EMAIL PROTECTED] Subject: SQL-Backtrack OBSI Module (via TSM API) for Oracle -versus- TSM TDP for Oracle People, I am wondering if anyone has any experience with this stuff. I am really interested in both Oracle and SQL Server! 1) Does SQL-Backtrack backup directly into TSM without having to use/buy the TSM TDP for Oracle/SQL Server ? 2) Can you do a HOT backup of the Oracle/SQL Server database ? 3) Is it slick ... does it work well ? Thank you, Larry
Re: SQL-Backtrack OBSI Module (via TSM API) for Oracle -versus- T SM TDP for Oracle
We use SQL BackTrack for Informix and my experience is idential with Becky's... sent her comments to my co-workers and they got a good chuckle... The first time I called BMC for support, the person who was working the problem claimed they had never heard of this product too many acquisitions too fast and too few users (calls to their help people) add up to dismal support. Their documentation for V 3.0 was mostly incorrect as well... Still haven't finished upgrading from 2.1 to 3.0 because I can't get expiration to work George Lesho Storage/System Admin AFC Enterprises Larry Girardi [EMAIL PROTECTED] on 03/09/2001 01:10:12 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: George Lesho/Partners/AFC) Fax to: Subject: Re: SQL-Backtrack OBSI Module (via TSM API) for Oracle -versus- T SM TDP for Oracle Becky, Thank you! That is what I needed (the straight poop!). Does anyone have a differing opinion or additional experience? Thanks again, Larry "Davidson, Becky" [EMAIL PROTECTED] on 03/09/2001 12:36:57 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: Larry Girardi/IS/Travelers) Subject: Re: SQL-Backtrack OBSI Module (via TSM API) for Oracle -versus- T SM TDP for Oracle We are currently using SQL Backtrack on our production database and TDP for SAP R/3 on development systems migrating to TDP on all. In answer to your questions 1) Yes SQL Backtrack goes directly into TSM 2) Yes you can do a hot backup. We do a 1 T database hot every night 3) Hate it. We have problems with just about everything with it. Setting it up is an issue. Upgrading versions has caused us problems. Getting support has caused us major problems because there is a tendency to not fully look into the problem and just immediately blame it on TSM. If there is a tape error it does not retry very well and the entire backup fails. We have had problems with SQL Backtrack doing it's own expiration. The licensing scheme is done on the size of your database. I suppose that is ok if your database doesn't grow much but ours does so you have to get a license at 250, 500, 750, 1200 which of course costs significantly more. For us financially TDP is the better solution. The installation is easier and support has been better. We have also had fewer problems with it. Then again we are also using TDP for SAP R/3 so I am not sure if TDP for Oracle is better or worse. That's my .02 Becky Davidson Data Manager/AIX Administrator EDS/Earthgrains voice: 314-259-7589 fax: 314-877-8589 email: [EMAIL PROTECTED] -Original Message- From: Larry Girardi [mailto:[EMAIL PROTECTED]] Sent: Friday, March 09, 2001 11:30 AM To: [EMAIL PROTECTED] Subject: SQL-Backtrack OBSI Module (via TSM API) for Oracle -versus- TSM TDP for Oracle People, I am wondering if anyone has any experience with this stuff. I am really interested in both Oracle and SQL Server! 1) Does SQL-Backtrack backup directly into TSM without having to use/buy the TSM TDP for Oracle/SQL Server ? 2) Can you do a HOT backup of the Oracle/SQL Server database ? 3) Is it slick ... does it work well ? Thank you, Larry
SQL BackTrack For Informix V 3.0
IS ANYBODY USING THIS PRODUCT? Have you been able to make "expiration" work... Not having much luck and would appreciate some assistance. TSM server 3.7.3.6 on AIX 4.3.2 and Client 3.7.2 on AIX 4.3.3. Informix 731UC2. The BMC Product, as mentioned in the subject line is V 3.0 and the obsi module is obsi-adsm 2.4.10. Any hints on how to make expiration work would be welcome... BMC has proved less than helpful. George Lesho Storage/System Admin AFC Enterprises
Re: Antwort: Re: SQL-Backtrack and multiple tapes
Rolf Meyer [EMAIL PROTECTED] on 02/05/2001 01:48:11 AM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc:(bcc: George Lesho/Partners/AFC) Fax to: Subject: Antwort: Re: SQL-Backtrack and multiple tapes Steffan, I am new on the list but am familiar with SQL-BackTrack for Informix. I know this is a different product but it uses and OBSI module which specifies "ADSM" instead of tapes or drives. The "mount points" needed, thus, are not directly attibutable to the tape or drive resources available but seem to represent communication threads available. During testing, we found that sometimes backups would work with 1 mount point, they would work most of the time with 2 and work all the time with three. Hope this info is of some help. George Lesho Storage Admin AFC Enterprises Thema: Re: SQL-Backtrack and multiple tapes Rolf, update the client's registration parameter maximum number of mount points to 2. Steffan Rolf Meyer wrote: Hello I use TSM 4.1.2 on Solaris 8 with BMC SQL Backtrack for Oracle. Trying to do a backup of a 300G SAP DB using more than one backup stream. SQL-BT starts two sessions to TSM, one gets a tape from 3494 lib, other stays on MediaW. Both stream go to same Managementclass/Storage Pool. How should I configure TSM to let SQL-BT writing to more than one tape. Thanks for your help Rolf Meyer SATISFACTORY Info Business Systems GmbH 22607 Hamburg [EMAIL PROTECTED] -- Regards, Steffan Rhoads Principal SAN Architect Professional Services Inrange Technologies Corporation 714-731-5474 - Voice 877-681-2781 - 2-way Pager or [EMAIL PROTECTED] 714-832-9181 - Fax
Re: SQL-Backtrack and multiple tapes
Hallo thanks all for your help. Redefining the storagepool to filespace-based collocation and changes in the pool defs of SQL-BT has fixed the problem. Greetings from Hamburg Rolf Meyer SATISFACTORY Info Business Systems GmbH
Re: SQL-Backtrack
Does anyone have experience on the following error? This is happened during SQL_Backtrack expiring logs. [dtoexpire 43890] Object is not found: /BACKTRACK:dt_catalog_dirs /CRMPROD /datafile_9-0.3 1-12-2000.07:04:37-29204!, error msg= ANS1302E (RC2)No objects on server match query Thanks. Rosa Leung Distributed Storage Services Tel: (416) 490-5151 Fax: (416) 490-5283 [EMAIL PROTECTED] BK02/245/TOR _ IBM Global Services
Re: Antwort: Re: SQL-Backtrack and multiple tapes
Rolf What is your device class mount limit? If it isn't already set to drives you might want to set it to drives Becky Davidson Data Manager/AIX Administrator EDS/Earthgrains voice: 314-259-7589 fax: 314-877-8589 email: [EMAIL PROTECTED] -Original Message- From: Rolf Meyer [mailto:[EMAIL PROTECTED]] Sent: Monday, February 05, 2001 1:48 AM To: [EMAIL PROTECTED] Subject: Antwort: Re: SQL-Backtrack and multiple tapes Hello Steffan, client has max mount point of three, which is more as he needs. Is collocating no the right choice ? Greetings Rolf Meyer arhoads [EMAIL PROTECTED] am 02.02.2001 18:01:31 Bitte antworten an [EMAIL PROTECTED] An:[EMAIL PROTECTED] Kopie: (Blindkopie: Rolf Meyer/Satisfactory) Thema: Re: SQL-Backtrack and multiple tapes Rolf, update the client's registration parameter maximum number of mount points to 2. Steffan Rolf Meyer wrote: Hello I use TSM 4.1.2 on Solaris 8 with BMC SQL Backtrack for Oracle. Trying to do a backup of a 300G SAP DB using more than one backup stream. SQL-BT starts two sessions to TSM, one gets a tape from 3494 lib, other stays on MediaW. Both stream go to same Managementclass/Storage Pool. How should I configure TSM to let SQL-BT writing to more than one tape. Thanks for your help Rolf Meyer SATISFACTORY Info Business Systems GmbH 22607 Hamburg [EMAIL PROTECTED] -- Regards, Steffan Rhoads Principal SAN Architect Professional Services Inrange Technologies Corporation 714-731-5474 - Voice 877-681-2781 - 2-way Pager or [EMAIL PROTECTED] 714-832-9181 - Fax
Antwort: Re: Antwort: Re: SQL-Backtrack and multiple tapes
Hello Devclass mount limit is drives (we have four drives 3590E). Greetings Rolf "Davidson, Becky" [EMAIL PROTECTED] am 05.02.2001 09:08:41 Bitte antworten an "ADSM: Dist Stor Manager" [EMAIL PROTECTED] An:[EMAIL PROTECTED] Kopie: (Blindkopie: Rolf Meyer/Satisfactory) Thema: Re: Antwort: Re: SQL-Backtrack and multiple tapes Rolf What is your device class mount limit? If it isn't already set to drives you might want to set it to drives Becky Davidson Data Manager/AIX Administrator EDS/Earthgrains voice: 314-259-7589 fax: 314-877-8589 email: [EMAIL PROTECTED] -Original Message- From: Rolf Meyer [mailto:[EMAIL PROTECTED]] Sent: Monday, February 05, 2001 1:48 AM To: [EMAIL PROTECTED] Subject: Antwort: Re: SQL-Backtrack and multiple tapes Hello Steffan, client has max mount point of three, which is more as he needs. Is collocating no the right choice ? Greetings Rolf Meyer arhoads [EMAIL PROTECTED] am 02.02.2001 18:01:31 Bitte antworten an [EMAIL PROTECTED] An:[EMAIL PROTECTED] Kopie: (Blindkopie: Rolf Meyer/Satisfactory) Thema: Re: SQL-Backtrack and multiple tapes Rolf, update the client's registration parameter maximum number of mount points to 2. Steffan Rolf Meyer wrote: Hello I use TSM 4.1.2 on Solaris 8 with BMC SQL Backtrack for Oracle. Trying to do a backup of a 300G SAP DB using more than one backup stream. SQL-BT starts two sessions to TSM, one gets a tape from 3494 lib, other stays on MediaW. Both stream go to same Managementclass/Storage Pool. How should I configure TSM to let SQL-BT writing to more than one tape. Thanks for your help Rolf Meyer SATISFACTORY Info Business Systems GmbH 22607 Hamburg [EMAIL PROTECTED] -- Regards, Steffan Rhoads Principal SAN Architect Professional Services Inrange Technologies Corporation 714-731-5474 - Voice 877-681-2781 - 2-way Pager or [EMAIL PROTECTED] 714-832-9181 - Fax
Re: SQL-Backtrack and multiple tapes
I use TSM 4.1.2 on Solaris 8 with BMC SQL Backtrack for Oracle. Trying to do a backup of a 300G SAP DB using more than one backup stream. SQL-BT starts two sessions to TSM, one gets a tape from 3494 lib, other stays on MediaW. Both stream go to same Managementclass/Storage Pool. How should I configure TSM to let SQL-BT writing to more than one tape. We have done this successfully. We configured SQL-BackTrack so that it would use a different prefix for the filespace names created by each stream, and configured the TSM storage pool for collocation by filespace (as opposed to collocation by node).
Antwort: Re: SQL-Backtrack and multiple tapes
Hello Steffan, client has max mount point of three, which is more as he needs. Is collocating no the right choice ? Greetings Rolf Meyer arhoads [EMAIL PROTECTED] am 02.02.2001 18:01:31 Bitte antworten an [EMAIL PROTECTED] An:[EMAIL PROTECTED] Kopie: (Blindkopie: Rolf Meyer/Satisfactory) Thema: Re: SQL-Backtrack and multiple tapes Rolf, update the client's registration parameter maximum number of mount points to 2. Steffan Rolf Meyer wrote: Hello I use TSM 4.1.2 on Solaris 8 with BMC SQL Backtrack for Oracle. Trying to do a backup of a 300G SAP DB using more than one backup stream. SQL-BT starts two sessions to TSM, one gets a tape from 3494 lib, other stays on MediaW. Both stream go to same Managementclass/Storage Pool. How should I configure TSM to let SQL-BT writing to more than one tape. Thanks for your help Rolf Meyer SATISFACTORY Info Business Systems GmbH 22607 Hamburg [EMAIL PROTECTED] -- Regards, Steffan Rhoads Principal SAN Architect Professional Services Inrange Technologies Corporation 714-731-5474 - Voice 877-681-2781 - 2-way Pager or [EMAIL PROTECTED] 714-832-9181 - Fax
Re: SQL-Backtrack and multiple tapes
Rolf, update the client's registration parameter maximum number of mount points to 2. Steffan Rolf Meyer wrote: Hello I use TSM 4.1.2 on Solaris 8 with BMC SQL Backtrack for Oracle. Trying to do a backup of a 300G SAP DB using more than one backup stream. SQL-BT starts two sessions to TSM, one gets a tape from 3494 lib, other stays on MediaW. Both stream go to same Managementclass/Storage Pool. How should I configure TSM to let SQL-BT writing to more than one tape. Thanks for your help Rolf Meyer SATISFACTORY Info Business Systems GmbH 22607 Hamburg [EMAIL PROTECTED] -- Regards, Steffan Rhoads Principal SAN Architect Professional Services Inrange Technologies Corporation 714-731-5474 - Voice 877-681-2781 - 2-way Pager or [EMAIL PROTECTED] 714-832-9181 - Fax
TSM 4.1 Server and SQL Backtrack
Hi Everyone, We have our server on AIX 4.3.3 and planning to be migrating to TSM 4.1 from ADSM 3.1.7 this weekend. We have AIX clients and NT Clients. Some are on TSM v 3.1 and other ADSM 3.7. Did anyone have any trouble with SQL Backtrack with TSM 4.1 Any help will be greatly appreciated. Dave Pearson IS Production Support Analyst Snohomish County PUD Everett Washington [EMAIL PROTECTED] 425.347.4420
Re: TSM 4.1 Server and SQL Backtrack
When we were deciding to go to either 3.7 or 4.1, SQL-BACKTRACK was testing the 4.1 release. I believe they added 4.1 as a supported release. [EMAIL PROTECTED] 11/15/00 03:49PM Hi Everyone, We have our server on AIX 4.3.3 and planning to be migrating to TSM 4.1 from ADSM 3.1.7 this weekend. We have AIX clients and NT Clients. Some are on TSM v 3.1 and other ADSM 3.7. Did anyone have any trouble with SQL Backtrack with TSM 4.1 Any help will be greatly appreciated. Dave Pearson IS Production Support Analyst Snohomish County PUD Everett Washington [EMAIL PROTECTED] 425.347.4420
Re: TSM 4.1 Server and SQL Backtrack
Thanks for the information -Original Message- From: Lawrence Clark [SMTP:[EMAIL PROTECTED]] Sent: Wednesday, November 15, 2000 12:54 PM To: [EMAIL PROTECTED] Subject: Re: TSM 4.1 Server and SQL Backtrack When we were deciding to go to either 3.7 or 4.1, SQL-BACKTRACK was testing the 4.1 release. I believe they added 4.1 as a supported release. [EMAIL PROTECTED] 11/15/00 03:49PM Hi Everyone, We have our server on AIX 4.3.3 and planning to be migrating to TSM 4.1 from ADSM 3.1.7 this weekend. We have AIX clients and NT Clients. Some are on TSM v 3.1 and other ADSM 3.7. Did anyone have any trouble with SQL Backtrack with TSM 4.1 Any help will be greatly appreciated. Dave Pearson IS Production Support Analyst Snohomish County PUD Everett Washington [EMAIL PROTECTED] 425.347.4420
ADSM and SQL-Backtrack
We have ADSM 3.2.1 and are in the processing of implementing SQL Backtrack to backup up our Oracle databases on AIX and SQL Server 7.0 databases on NT. We know that Backtrack is pushing the backups to ADSM because when our Information Architect goes into Backtrack to do a database restore, she is successful. Also, the amount of scratch tapes in our MagStar are rapidly depleting. When we do a QUERY OCCUPANCY * * command in dsmadmc, we see two (2) names for our Database AIX node where the Oracle databases are installed called /BACKTRACK:tmp-control-dir and /BACKTRACK:oracatalog. I can see there are 30,000+ files and 240+ gig worth of data. This is my question. When I go into the ADSM gui, I see the high level file space structure of those 2 /BACKTRACK filespaces but don't see any file/directory detail. Why is this?
Re: ADSM and SQL-Backtrack
I am looking there when I am in the dsm GUI. The folder is there but when I try to expand it, it is empty. Is there another way to look at it in the dsm GUI or should I use a different ADSM tool? Thanks for your help. Lu Ann Mezera Data Center Supervisor Lab Safety Supply (608) 757-4909 voice (608) 757-4652 fax [EMAIL PROTECTED] -Original Message- From: Fluker, Tom R [mailto:[EMAIL PROTECTED]] Sent: Monday, September 18, 2000 12:02 PM To: [EMAIL PROTECTED] Subject: Re: ADSM and SQL-Backtrack look at "/BACKTRACK:oracatalog" your backups are there Tom Fluker Viasystems Technologies -Original Message- From: Lu Ann Mezera [SMTP:[EMAIL PROTECTED]] Sent: Monday, September 18, 2000 12:18 PM To: [EMAIL PROTECTED] Subject: ADSM and SQL-Backtrack We have ADSM 3.2.1 and are in the processing of implementing SQL Backtrack to backup up our Oracle databases on AIX and SQL Server 7.0 databases on NT. We know that Backtrack is pushing the backups to ADSM because when our Information Architect goes into Backtrack to do a database restore, she is successful. Also, the amount of scratch tapes in our MagStar are rapidly depleting. When we do a QUERY OCCUPANCY * * command in dsmadmc, we see two (2) names for our Database AIX node where the Oracle databases are installed called /BACKTRACK:tmp-control-dir and /BACKTRACK:oracatalog. I can see there are 30,000+ files and 240+ gig worth of data. This is my question. When I go into the ADSM gui, I see the high level file space structure of those 2 /BACKTRACK filespaces but don't see any file/directory detail. Why is this?
Re: ADSM and SQL-Backtrack
Lu Ann, Backtrack uses the ADSM API and therefore using the BA GUI will yield nothing. You can compile and use the sample API program included with the client and use that as a text interface to view objects, or, you can use the show versions command from the server admin interface. 30,000 objects seems quite a bit. I'm sure it depends on your retention and # data files. Check the # generations that your DBAs have set to make sure everything is okay. Also make sure the management class you have them bound to has: vere=1 verd=0 rete=0 reto=0 This allows the backtrack software to correctly control versioning. Otherwise, you'll have objects that take much longer to expire than what you might have envisioned. David Hendrix Lu Ann Mezera [EMAIL PROTECTED]@VM.MARIST.EDU on 09/18/2000 12:03:13 PM Please respond to "ADSM: Dist Stor Manager" [EMAIL PROTECTED] Sent by: "ADSM: Dist Stor Manager" [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Re: ADSM and SQL-Backtrack I am looking there when I am in the dsm GUI. The folder is there but when I try to expand it, it is empty. Is there another way to look at it in the dsm GUI or should I use a different ADSM tool? Thanks for your help. Lu Ann Mezera Data Center Supervisor Lab Safety Supply (608) 757-4909 voice (608) 757-4652 fax [EMAIL PROTECTED] -Original Message- From: Fluker, Tom R [mailto:[EMAIL PROTECTED]] Sent: Monday, September 18, 2000 12:02 PM To: [EMAIL PROTECTED] Subject: Re: ADSM and SQL-Backtrack look at "/BACKTRACK:oracatalog" your backups are there Tom Fluker Viasystems Technologies -Original Message- From: Lu Ann Mezera [SMTP:[EMAIL PROTECTED]] Sent: Monday, September 18, 2000 12:18 PM To: [EMAIL PROTECTED] Subject: ADSM and SQL-Backtrack We have ADSM 3.2.1 and are in the processing of implementing SQL Backtrack to backup up our Oracle databases on AIX and SQL Server 7.0 databases on NT. We know that Backtrack is pushing the backups to ADSM because when our Information Architect goes into Backtrack to do a database restore, she is successful. Also, the amount of scratch tapes in our MagStar are rapidly depleting. When we do a QUERY OCCUPANCY * * command in dsmadmc, we see two (2) names for our Database AIX node where the Oracle databases are installed called /BACKTRACK:tmp-control-dir and /BACKTRACK:oracatalog. I can see there are 30,000+ files and 240+ gig worth of data. This is my question. When I go into the ADSM gui, I see the high level file space structure of those 2 /BACKTRACK filespaces but don't see any file/directory detail. Why is this?
Re: ADSM and SQL-Backtrack
This is my question. When I go into the ADSM gui, I see the high level file space structure of those 2 /BACKTRACK filespaces but don't see any file/directory detail. Why is this? SQL-BackTrack is based on the ADSM API client. ADSM is designed so that backup/archive clients cannot obtain information about individual files backed up by API clients, API clients cannot obtain information about files backed up by the backup/archive client, and different types of API clients (for example, SQL-BackTrack and Tivoli Data Protection) cannot obtain information about each others files. Client-side query facilities for files sent to ADSM by SL-BackTrack, if they exist at all, are part of SQL-BackTrack.
Re: ADSM and SQL-Backtrack
BackTrack had a problem with expiring it's own data. Here are some scripts that we used to find more info about the particular files. Hope this will help you. Mark Adams (402) 963-8237 /* This will show all files for a particular node */ select * from contents where node_name='SQL_BACKTRACK' /* This script is designed to pull the files*/ /* for SQL_BACKTRACK node given a certain month */ /* for the year 2000*/ select filespace_name, hl_name, - ll_name from backups where - node_name='SQL_BACKTRACK' and - substr(varchar(backup_date),1,7)='2000-$1' /* This script is designed to pull the files*/ /* for SQL_BACKTRACK node given a certain month */ /* for the year 1999*/ select node_name, filespace_name, hl_name, - ll_name, backup_date from backups where - node_name='SQL_BACKTRACK' and - substr(varchar(backup_date),1,7)='1999-$1' - order by backup_date /* This script obtains all nodes and their */ /* total amount of occupancy*/ select node_name "NODE", type, sum(num_files) - "# FILES", sum(physical_mb) "PHY(MB)", - sum(logical_mb) "LOG(MB)" from occupancy - group by node_name, type order by type -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Lu Ann Mezera Sent: Monday, September 18, 2000 1:03 PM To: [EMAIL PROTECTED] Subject: Re: ADSM and SQL-Backtrack I am looking there when I am in the dsm GUI. The folder is there but when I try to expand it, it is empty. Is there another way to look at it in the dsm GUI or should I use a different ADSM tool? Thanks for your help. Lu Ann Mezera Data Center Supervisor Lab Safety Supply (608) 757-4909 voice (608) 757-4652 fax [EMAIL PROTECTED] -Original Message- From: Fluker, Tom R [mailto:[EMAIL PROTECTED]] Sent: Monday, September 18, 2000 12:02 PM To: [EMAIL PROTECTED] Subject: Re: ADSM and SQL-Backtrack look at "/BACKTRACK:oracatalog" your backups are there Tom Fluker Viasystems Technologies -Original Message- From: Lu Ann Mezera [SMTP:[EMAIL PROTECTED]] Sent: Monday, September 18, 2000 12:18 PM To: [EMAIL PROTECTED] Subject: ADSM and SQL-Backtrack We have ADSM 3.2.1 and are in the processing of implementing SQL Backtrack to backup up our Oracle databases on AIX and SQL Server 7.0 databases on NT. We know that Backtrack is pushing the backups to ADSM because when our Information Architect goes into Backtrack to do a database restore, she is successful. Also, the amount of scratch tapes in our MagStar are rapidly depleting. When we do a QUERY OCCUPANCY * * command in dsmadmc, we see two (2) names for our Database AIX node where the Oracle databases are installed called /BACKTRACK:tmp-control-dir and /BACKTRACK:oracatalog. I can see there are 30,000+ files and 240+ gig worth of data. This is my question. When I go into the ADSM gui, I see the high level file space structure of those 2 /BACKTRACK filespaces but don't see any file/directory detail. Why is this?
