Re: Recovery Manager vs. SQL Back Track
SQL-Backtrack was a good product at one time. In theory it still is. Here's the problem though. When Data Tools sold SQL-Backtrack to BMC, it seems that anyone that knew anything about the product left. There is no one in tech support that can help you beyond the menu items. There is no one there that knows how to run their product from the command line. Some recovery scenarios require command line operation, and wouldn't you know, we lost a database at a former employer for that very reason. Jared On Tue, 3 Apr 2001, Yttri, Lisa wrote: Hi everyone - Currently we are doing backups manually, periodic cold backups, and hot backups in between - we are running in archivelog mode. We are running 8.1.5 and 8.1.6 (soon to be 8.1.7) on Sun Solaris. Today there are only a few small production servers (2 - 5 GB), but we are anticipating a couple large ones (~200GB), and a data warehouse (anticipated to be around 500GB). We have started playing around with Recovery Manager. Our Sybase DBAs are telling us we should look at SQL BackTrack instead. For those of you who are using either one, I'd appreciate your comments on how well you like / don't like it and any "gotcha's" that you have run into. Other than the cost factor, what would you recommend? Thanks very much - Lisa Jared Still [EMAIL PROTECTED] -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
Recovery Manager vs. SQL Back Track
Title: Recovery Manager vs. SQL Back Track Hi everyone - Currently we are doing backups manually, periodic cold backups, and hot backups in between - we are running in archivelog mode. We are running 8.1.5 and 8.1.6 (soon to be 8.1.7) on Sun Solaris. Today there are only a few small production servers (2 - 5 GB), but we are anticipating a couple large ones (~200GB), and a data warehouse (anticipated to be around 500GB). We have started playing around with Recovery Manager. Our Sybase DBAs are telling us we should look at SQL BackTrack instead. For those of you who are using either one, I'd appreciate your comments on how well you like / don't like it and any gotcha's that you have run into. Other than the cost factor, what would you recommend? Thanks very much - Lisa
Re: Recovery Manager vs. SQL Back Track
I have used rman exclusively since I became an Oracle DBA because it was there and I needed a backup strategy. It has gotten better with later releases. We are now on 8.0.6. It used Oracle internals so that is an advantage. It comes free with Oracle so that is another advantage. I can send you a paper on why to love rman written by Francis Sanchez of Oracle Corp. if you need it. I can't send an attachment through the list. Regards, Ruth - Original Message - To: "Multiple recipients of list ORACLE-L" [EMAIL PROTECTED] Sent: Tuesday, April 03, 2001 10:45 AM Hi everyone - Currently we are doing backups manually, periodic cold backups, and hot backups in between - we are running in archivelog mode. We are running 8.1.5 and 8.1.6 (soon to be 8.1.7) on Sun Solaris. Today there are only a few small production servers (2 - 5 GB), but we are anticipating a couple large ones (~200GB), and a data warehouse (anticipated to be around 500GB). We have started playing around with Recovery Manager. Our Sybase DBAs are telling us we should look at SQL BackTrack instead. For those of you who are using either one, I'd appreciate your comments on how well you like / don't like it and any "gotcha's" that you have run into. Other than the cost factor, what would you recommend? Thanks very much - Lisa -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Ruth Gramolini INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
Re: Recovery Manager vs. SQL Back Track
Send it through the list. I would like to see it also. Thanks. [EMAIL PROTECTED] 04/03/01 11:56AM I have used rman exclusively since I became an Oracle DBA because it was there and I needed a backup strategy. It has gotten better with later releases. We are now on 8.0.6. It used Oracle internals so that is an advantage. It comes free with Oracle so that is another advantage. I can send you a paper on why to love rman written by Francis Sanchez of Oracle Corp. if you need it. I can't send an attachment through the list. Regards, Ruth - Original Message - To: "Multiple recipients of list ORACLE-L" [EMAIL PROTECTED] Sent: Tuesday, April 03, 2001 10:45 AM Hi everyone - Currently we are doing backups manually, periodic cold backups, and hot backups in between - we are running in archivelog mode. We are running 8.1.5 and 8.1.6 (soon to be 8.1.7) on Sun Solaris. Today there are only a few small production servers (2 - 5 GB), but we are anticipating a couple large ones (~200GB), and a data warehouse (anticipated to be around 500GB). We have started playing around with Recovery Manager. Our Sybase DBAs are telling us we should look at SQL BackTrack instead. For those of you who are using either one, I'd appreciate your comments on how well you like / don't like it and any "gotcha's" that you have run into. Other than the cost factor, what would you recommend? Thanks very much - Lisa -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Ruth Gramolini INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Gene Sais INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
Re: Recovery Manager vs. SQL Back Track
We currently use SQL BackTrack on both Solaris boxes where our interface to tape software is netware. To put it mildly, netware sucks. When we were going to disk SQL BackTrack worked like a charm. On our other system - AIX - our interface is ADSM. It too has worked like a charm. If you can stay away from using SQL BackTrack with netware's obsi interface, go for it. Otherwise, stay as far away as you can. Terry "Yttri, Lisa" wrote: Hi everyone - Currently we are doing backups manually, periodic cold backups, and hot backups in between - we are running in archivelog mode. We are running 8.1.5 and 8.1.6 (soon to be 8.1.7) on Sun Solaris. Today there are only a few small production servers (2 - 5 GB), but we are anticipating a couple large ones (~200GB), and a data warehouse (anticipated to be around 500GB). We have started playing around with Recovery Manager. Our Sybase DBAs are telling us we should look at SQL BackTrack instead. For those of you who are using either one, I'd appreciate your comments on how well you like / don't like it and any "gotcha's" that you have run into. Other than the cost factor, what would you recommend? Thanks very much - Lisa -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Terry Ball INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
RE: Recovery Manager vs. SQL Back Track
Title: RE: Recovery Manager vs. SQL Back Track I have worked with manual scripting, EBU, RMAN, and SQLBackTrack. If you can afford it, use SQLBackTrack. It's idiot proof for both backup and restore if you set it up right. (trust me). If you have other questions email me direct. Brian P. Mac Lean Oracle DBA/OCP v8/OMC Vcommerce Corp. 6262 N. Scottsdale Rd., Suite 110 Scottsdale, AZ 85250 480.922.9922 - Main 480.778.8449 - Direct 480.922.9921 - Fax [EMAIL PROTECTED] - Email vc_bmaclean - Yahoo Messenger http://www.vcommerce.com -Original Message- From: Yttri, Lisa [mailto:[EMAIL PROTECTED]] Sent: Tuesday, April 03, 2001 7:46 AM To: Multiple recipients of list ORACLE-L Subject: Recovery Manager vs. SQL Back Track Hi everyone - Currently we are doing backups manually, periodic cold backups, and hot backups in between - we are running in archivelog mode. We are running 8.1.5 and 8.1.6 (soon to be 8.1.7) on Sun Solaris. Today there are only a few small production servers (2 - 5 GB), but we are anticipating a couple large ones (~200GB), and a data warehouse (anticipated to be around 500GB). We have started playing around with Recovery Manager. Our Sybase DBAs are telling us we should look at SQL BackTrack instead. For those of you who are using either one, I'd appreciate your comments on how well you like / don't like it and any gotcha's that you have run into. Other than the cost factor, what would you recommend? Thanks very much - Lisa
