跳转到主内容

Why doesn't SCO create a Snapshot on the storage for the db control files ?

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

 

Applies to

SnapCenter Plug-in for Oracle (SCO)

Answer

To provide backups in SCO with a less strict storage usage policy compared to SnapManager (SMO/SMSAP), SnapCenter puts a copy of the binary
control files on the table space storage for the time of the snapshot, and a backup-to-trace ascii copy in a way that depends on whether or not ASM is used:

  • Using NFS or filesystem LUNs formatted with standard Linux filesystem, SCO puts the backup-to-trace file with the copy of the control files
  • Using ASM on either NFS or raw LUNs in RAC, a copy on ASM is not possible, so SCO stores the backup-to-trace content in SnapCenter's NSM repository

Additional Information

With Oracle RAC on ASM, it's recommended to backup your NSM database regularly (see Administration Guide on how to do this), since a manual clone or restore under these circumstances is problematic.

Snapshot are always created for the database files and archive logs, which are required to be on NetApp storage, with a Snapshot on the redo logs only when using DataGuard.