SnapManager 3.4.2 for Oracle
Installation and Setup for UNIX for Clustered Data ONTAP
Product overview
Preparing for deployment
Configuring databases
Setting up SnapManager
Preparing storage systems for SnapMirror and SnapVault replication
Backing up and verifying your databases
Installation and Setup for UNIX for Data ONTAP Operating in 7-mode
Product overview
Preparing for deployment
Configuring databases
Setting up SnapManager
Backing up and verifying your databases
Administration for UNIX
Product overview
Recommended general database layouts and storage configurations
Support for ASM databases without ASMLib
Deploying and running the scripts
Limitations when working with SnapManager
Limitations related to Oracle Database
Recommended general database layouts and storage configurations
Support for ASM databases without ASMLib
Deploying and running the scripts
Limitations when working with SnapManager
Limitations related to Oracle Database
Upgrading SnapManager
Post-upgrade tasks
Upgrading SnapManager hosts by using rolling upgrade
What a rollback is
Configuring SnapManager
SnapManager configuration parameters
Security and credential management
About role-based access control
Clearing user credentials for all hosts, repositories, and profiles
Deleting credentials for individual resources
Managing profiles for efficient backups
Backing up databases
What full and partial backups are
Creating database backups
What AutoSupport is
Changing the backup retention policy
Scheduling database backups
Resuming backup schedules
Restoring database backups
What database restore is
Guidelines for when you can use fast restore
Restore files from an alternate location
Restore backups from an alternate location overview
Cloning database backup
Creating clone specifications
Considerations for cloning a database to an alternate host
Splitting a clone
Introduction to data protection in SnapManager
Configuring and enabling policy-driven data protection
Considerations for performing data protection
Restoring protected backups from secondary storage
SnapManager for Oracle uses Protection Manager to protect a database backup
Protected backup configuration and execution
Database restoration from backup
Performing management operations
Configuring an email notification
Configuring email notification for a new profile
Configuring email notification for an existing profile
Creating task specification file and scripts for SnapManager operations
Creating pretask, post-task, and policy scripts
Updating storage system name and target database host name associated with a profile
Maintaining history of SnapManager operations
SnapManager for Oracle command reference
Troubleshooting SnapManager
Dump files
Installation and Setup for Windows
What SnapManagerfor Oracle is
Advantages of using SnapManager
What the SnapManager for Oracle architecture is
SnapManager for Oracle deployment considerations
Requirements for running SnapManager
Database version support and configuration overview
Installing SnapManager for Oracle
Preparing to install SnapManager for Oracle
Upgrading SnapManager
Post-upgrade tasks
Upgrading SnapManager hosts by using rolling upgrade
What a rollback is
Configuring SnapManager
SnapManager configuration parameters
Starting SnapManagerfor Oracle
Accessing SnapManager
Starting the SnapManager host server
Verifying the environment
Creating repositories
Security and credential management
Clearing user credentials for all hosts, repositories, and profiles
Deleting credentials for individual resources
Managing profiles for efficient backups
Backing up databases
What full and partial backups are
Creating database backups
What AutoSupport is
Changing the backup retention policy
Scheduling database backups
Restoring database backups
What database restore is
Restore files from an alternate location
Restore backups from an alternate location overview
Cloning database backup
Creating clone specifications
Considerations for cloning a database to an alternate host
Introduction to data protection in SnapManager
Considerations for performing data protection
Protecting database backups by using postscripts
Creating or updating the post scripts
Creating post-processing, task-specification files
Performing management operations
Configuring an email notification
Configuring email notification for a new profile
Configuring email notification for an existing profile
Creating task specification file and scripts for SnapManager operations
Creating pretask, post-task, and policy scripts
Updating storage system name and target database host name associated with a profile
Maintaining history of SnapManager operations
SnapManager for Oracle command reference
Troubleshooting SnapManager
Dump files
Contributors
Download PDF of this page
Administrators have the option to resume the suspended backup schedule.
If you try to resume the active schedules, you might encounter the error message: "Cannot resume: schedule <schedulename> already in resume state".
To resume the suspended backup schedule, enter this command: smo schedule resume -profile profile_name-schedule-nameschedulename [-quiet | -verbose]
Edit on GitHub