Veritas NetBackup™ OpsCenter Administrator's Guide
- Overview of NetBackup OpsCenter
- About OpsCenter
- About OpsCenter components
- About starting the OpsCenter console
- About OpsCenter console components
- About the View pane
- Sizing the Content pane
- About using tables
- Installing OpsCenter
- About planning an OpsCenter installation
- Installing OpsCenter on Windows and UNIX
- About OpsCenter upgrade on Windows and UNIX
- About post-installation tasks
- About uninstalling OpsCenter on Windows and UNIX
- About clustering OpsCenter
- Getting started with OpsCenter
- Administering OpsCenter
- About the services and processes used by OpsCenter
- OpsCenter server scripts on Windows and UNIX
- About OpsCenter database administration
- About backup and restore of OpsCenter and OpsCenter Analytics
- About communication ports and firewall considerations in OpsCenter
- About OpsCenter log files
- Understanding OpsCenter settings
- Setting user preferences
- About managing licenses
- Configuring the data purge period on the OpsCenter Server
- Configuring SMTP server settings for OpsCenter
- Adding host aliases in OpsCenter
- Merging objects (hosts) in OpsCenter
- Modifying tape library information in OpsCenter
- Copying a user profile in OpsCenter
- Setting report export location in OpsCenter
- About managing Object Types in OpsCenter
- About managing OpsCenter users
- About adding AD / LDAP user groups in OpsCenter
- About managing recipients in OpsCenter
- About managing cost analysis and chargeback for OpsCenter Analytics
- Understanding data collection
- About configuring data collection for NetBackup
- About the Breakup Jobs option
- Viewing primary server details and data collection status
- About configuring data collection for NetBackup
- Managing OpsCenter views
- About OpsCenter views
- About managing OpsCenter views
- Managing static views
- Managing dynamic views
- View filters in OpsCenter
- Monitoring NetBackup using OpsCenter
- Controlling the scope of Monitor views
- About monitoring NetBackup using the Overview tab
- About monitoring NetBackup jobs
- Monitor > Services view
- About monitoring Audit Trails
- Managing NetBackup using OpsCenter
- About managing alert policies
- About creating (or changing) an alert policy
- About managing NetBackup storage
- About managing NetBackup devices
- About Operational Restore and Guided Recovery operations
- About Operational Restores from OpsCenter
- About Guided Recovery
- Troubleshooting Guided Recovery
- About managing NetBackup Hosts
- About managing NetBackup Deployment Analysis
- Data compilation for the Capacity License report
- Generating a Capacity Licensing report
- Supporting Replication Director in OpsCenter
- Understanding and configuring OpsCenter alerts
- About using SNMP
- About using SNMP
- Reporting in OpsCenter
- About OpsCenter reports
- Report Templates in OpsCenter
- About managing reports in OpsCenter
- Creating a custom report in OpsCenter
- About managing My Reports
- About managing My Dashboard
- About managing reports folders in OpsCenter
- About managing report schedules in OpsCenter
- About managing time schedules in OpsCenter
- Appendix A. Attributes of NetBackup data
- Appendix B. Man pages for CLIs
- Appendix C. Creating views using CSV, TSV, and XML files
- Appendix D. Error messages in OpsCenter
Guided Recovery post-clone operations
Perform the following after the cloning operation has completed:
On Windows systems, if the cloning operation fails, use the dbca utility to delete the database. dbca sometimes removes directories, so verify before retrying the operation.
On UNIX systems, update the
oratab
file with the appropriate instance information.On UNIX systems, if the cloning operation fails, do the following cleanup:
If the database is active, shut down the database.
Remove init<SID>.ora, spfile<SID>.ora, and any other files that are associated with the SID being used, from the <$ORACLE_HOME>/DBS directory.
Remove all data files.
If a cloned Oracle database contains read-only tablespaces or data files, you must make them read-write before RMAN backs them up, or RMAN cannot restore them. After the backup (cloning operation), you can return the items to read-only.
The following shows an example of the sequence of steps in the process:
Back up Oracle database A which contains read-only tablespace TABLE1.
Clone database A to database B.
Use the Oracle alter tablespace command to make tablespace TABLE1 read-write. You may revert to read-only if you want.
Back up database B.
Use RMAN to restore database B.