How To Recover SuperCluster Components that were Backed Up with osc-config-backup
(Doc ID 1934130.1)
Last updated on SEPTEMBER 28, 2023
Applies to:Oracle SuperCluster M7 Hardware - Version All Versions to All Versions [Release All Releases]
Solaris Operating System - Version 11.3 to 11.4 [Release 11.0]
Oracle SuperCluster T5-8 Full Rack - Version All Versions to All Versions [Release All Releases]
Oracle SuperCluster T5-8 Half Rack - Version All Versions to All Versions [Release All Releases]
Oracle SuperCluster M8 Hardware - Version All Versions to All Versions [Release All Releases]
Oracle Solaris on SPARC (64-bit)
Provide information on recovering SuperCluster components that were backed up with the osc-config-backup tool for T5-8, M6-32, M7 and M8 based SuperCluster products.
Also highlights any critical issues and workarounds which SuperCluster administrators should be aware of before attempting a recovery scenario, and finally provides detailed instructions on how to use the ZFS Stream recovery process on a T5-8 server.
This article provides links to the relevant documents required to effectively restore SuperCluster components from osc-config-bakup data stored on the internal ZFS Storage Array.
Note that backing up any data from Exadata Storage cells and servers is not covered, and also that this article does not cover ASM instance or Exadata storage server recovery.
The osc-config-backup utility is supported on these SuperCluster models as long as the system also meets the prerequisites:
- Oracle SuperCluster T5-8
- Oracle SuperCluster M6-32 (starting Jan 2017 QFSDP)
- Oracle SuperCluster M7
- Oracle SuperCluster M8
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Possible recovery scenarios|
|Known Issues and Workarounds|
|Recover T5-8 Domains Using ZFS streams|