|
The most important technical component in a SAP environment is always the
database. If all fails, and you succeed in restoring your database, all other
SAP components can be reconstructed in a worst-case scenario with a
re-install of the SAP instances.
In your setup, put the Oracle database in suspend mode. When done, all I/O
is suspended.
As long as the database is in suspend mode, SAP is in reconnect mode. As
such, both SAP and database are 'waiting' and nothing is written to the
database and SAP application file systems.
At that point, split the mirrors in both NAS and SAN and start your backup
on the mirrors. If you resume the database, all activities continue as if
nothing happened in between.
In addition, if you disable file system buffering at the OS level, all I/Os are
written to the disks at database commit time. File system buffering is no
longer used. This guarantees consistent backups.
Consult your OS documentation on the disabling of file system buffering. For
the suspend/resume feature, consult the Oracle documentation.
For more information on backup/recovery from SAP, see
http://service.sap.com/atg --> backup/restore.
|
