Skip to main content
NetApp Knowledge Base

The SnapCenter Plug-in for Oracle does not backup oracle home when coming from SMSAP

Views:
223
Visibility:
Public
Votes:
0
Category:
snapcenter
Specialty:
snapx
Last Updated:

Applies to

SnapCenter Plug-in for Oracle (SCO)

Issue

Migrating from SnapManager for SAP (SMSAP) to SnapCenter fails to include the copy of the control files and undo logs used by SAP:
  • /oracle/<SID> - oracle home, mounted on a NetApp volume orahome, no longer keeps a copy of the control files
    • /oracle/<SID>/mirrorlog - copy of the undo logs inside orahome
    • The copy of the Oracle control files for SAP usage, within the orahome mounted volume
  • /oracle/<SID>/sapdata - oracle database/tablespaces with its own mount on NetApp storage oradata, included in a snapshot by SCO
    • /oracle/<SID>/sapdata/cntrl - active control files, inside the sapdata file system and part of the snapshot on oradata
  • /oracle/<SID>/origlog - undo logs a.k.a. the redo logs with their own mount on NetApp storage, which are only included in a snapshot when DataGuard is used
  • /oracle/<SID>/archlog - archive logs with their own mount on NetApp storage oraarch, included in a snapshot by SCO
Restoring the database from that backup using SnapCenter will not match up with SAP usage, causing integration issues.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.