SnapCenter Software 5 Manuals ( CA08871-403 )

You should have defined your restore and recovery strategy.

The SnapCenter administrator should have assigned you the storage virtual machines (SVMs) for both the source volumes and destination volumes if you are replicating Snapshot copies to a mirror or vault.

If archive logs are pruned as part of backup, you should have manually mounted the required archive log backups.

If you want to restore Oracle databases that are residing on a Virtual Machine Disk (VMDK), you should ensure that the guest machine has the required number of free slots for allocating the cloned VMDKs.

You should ensure that all data volumes and archive log volumes belonging to the database are protected if secondary protection is enabled for that database.

You should ensure that the RAC One Node database is in "nomount" state to perform control file or full database restore.

If you have an ASM database instance in NFS environment, you should add the ASM disk path /var/opt/snapcenter/scu/clones/*/* to the existing path defined in the asm_diskstring parameter to successfully mount the ASM log backups as part of recovery operation.

In the asm_diskstring parameter, you should configure AFD:* if you are using ASMFD or configure ORCL:* if you are using ASMLIB.

You should configure the static listener in the listener.ora file available at $ORACLE_HOME/network/admin for non ASM databases and $GRID_HOME/network/admin for ASM databases if you have disabled OS authentication and enabled Oracle database authentication for an Oracle database, and want to restore the datafiles and control files of that database.

You should increase value of SCORestoreTimeout parameter by running the Set- SmConfigSettings command if the database size is in terabytes (TB).

You should ensure that all the licenses required for vCenter are installed and up to date.

You should ensure that the LUN is not mapped to the AIX host using iGroup consisting of mixed protocols iSCSI.