Configuration requirements for snapshot backups with NetBackup for Oracle
Each agent has its own hardware requirements, software requirements, compatibility with certain features, and the snapshot methods that are supported. Special requirements apply for specific types of backups. See the Cohesity Support website for more information. Familiarize yourself with this information before you configure any snapshot backups.
The following list highlights some of the requirements that pertain to database agents:
Snapshot Client backups do not back up all database objects. Your backup configuration must include schedules to perform snapshot and stream-based backups. This configuration ensures that the entire database can be restored successfully.
On UNIX, the user identification and group identification numbers (UIDs and GIDs) associated with the files to be backed up must be available. The UID and GID must be available to both the primary client and the alternate backup client. The UID on the primary client and the alternate backup client must be the same. Similarly, the GID on the primary client and the alternate backup client must be the same.
Note:
The UID number can be different than the GID number.
Allocate different areas for data files, archived redo logs, and the control file for database activities. Write the data files to their own repository because it is required for an instant recovery point-in-time rollback. Only data files can exist on the volume or the file system that you want to restore.
The hardware and software that is required for the appropriate snapshot method must be installed and configured correctly.
NetBackup Snapshot Client must be installed and configured correctly, and the license for this option must be registered.
To perform off-host backups, perform any special configuration that is required.
See About configuring Snapshot Client with NetBackup for Oracle.
More Information