Doug,
I would strongly recommend using the NetWorker Module for SAP R/3 on Oracle. It
ensures database integrity and high-availability. It also protects data at both
the database and transaction log levels. Your command invokes save, which does
not have any hooks into the database environment. You are also not taking
advantage of the online backup processes, which ensures business (application)
continuity. This solution also provides you with 2 different methods of backing
up the data (depending on which you are more comfortable with).
The NWM for SAP uses a utility called brbackup, which passes LGTO and
application environment relevant information to the SAP tools utility
(backint). You can also direct SAP to use Oracle's RMAN (which a lot of dba's
are already used to). Either way, the data can be backed up while the
application is live, and you shouldn't have to worry about corruption issues.
We are using the NM for SAP here, and have ran into extremely long recover
times, but worked with LGTO to resolve those, and we are now happy with the
products performance.
Btw, what is the -O switch do with the save command? I checked the MAN PAGE and
don't see it listed. I thought it was a savegrp switch.
HTH,
-Sean
-----Original Message-----
From: Doug Phillips [mailto:dphillips AT CSENERGY.COM DOT AU]
Sent: Monday, September 16, 2002 1:51 AM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: [Networker] W2K and large file (> 9GB) corruption
Hi
Is anyone aware of an issue with Legato 6.1.1 saving files > 9GB?
I have an Oracle database file that has been saved as part of an offline
backup. The command that is used to backup these files is listed below:
save -O 4G -f C:\Temp\.nsr.backint.CEP -LL -N backint:CEP -b SAPdata -i -s
sappdb.csenergy.com.au G:\oracle\CEP\sapdata1\ES46CD_1\es46cd.data1 2>&1
This is a SAP database using the backint interface to backup the database
to the Legato server. I have recovered the file several times and it is
reported as being corrupt by the Oracle DBV tool.
I will be trying to determine if it is the backup that was used is
stuffed. However, if anyone has any knowledge of limitations etc your help
would be greatly appreciated.
Regards
Doug Phillips
--
Note: To sign off this list, send a "signoff" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
**********************************************************************
This e-mail is the property of Enron Corp. and/or its relevant affiliate and
may contain confidential and privileged material for the sole use of the
intended recipient (s). Any review, use, distribution or disclosure by others
is strictly prohibited. If you are not the intended recipient (or authorized to
receive for the recipient), please contact the sender or reply to Enron Corp.
at enron.messaging.administration AT enron DOT com and delete all copies of the
message. This e-mail (and any attachments hereto) are not intended to be an
offer (or an acceptance) and do not create or evidence a binding and
enforceable contract between Enron Corp. (or any of its affiliates) and the
intended recipient or any other party, and may not be relied on by anyone as
the basis of a contract by estoppel or otherwise. Thank you.
**********************************************************************
--
Note: To sign off this list, send a "signoff" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
|
