Before you configure a protection policy for asset protection, observe the following points and perform the following actions:
For each database that you add as an asset in a protection policy, ensure that the database has only one hostname. A single database must not have more than one hostname.
When you create protection policies for RAC databases, ensure that all nodes in the RAC environment are powered on and registered at the time of the protection policy creation. Otherwise the protection might fail.
For Oracle Instance Group assets, ensure that the maximum length of the hostname plus storage unit is 59 characters. There are no special character limitations. For example,
oracle_database_department_123_accounts.
Review the configuration file requirements for connections to local databases.
Notes
You can only protect an asset with one policy at a time. If the asset type supports protection rules, assets can move between protection policies depending on the protection rule priorities. Protection rules do not automatically move assets that were manually added to a policy to a different policy.
Before scheduling weekly, monthly, or yearly backups, set the
PowerProtect Data Manager time zone to the local time zone. Otherwise, the backup still runs but is triggered based on the
PowerProtect Data Manager time zone.
Policy-level credentials are mandatory. Credentials that you set at the asset level and host level take precedence over the credentials that you set at the protection policy level. Asset-level credentials have the highest precedence.
For database backups,
PowerProtect Data Manager chains the dependent backups together. For example, the incremental or transaction log backups are chained to their base full backup. The backups do not expire until the last backup in the chain expires. As a result, all incremental and transaction log backups are recoverable until they have all expired.
NOTE:Ensure that the database is open so that the log backups can be part of the dependency chain. Otherwise, the full backup copies are reported as partial copies without an archive log in the
PowerProtect Data Manager UI.
When a new asset is added to an existing policy, you must run an ad hoc full backup for the newly added asset.
When a new asset is added to a protection policy during a scheduled backup window, the backup starts right away. However, if an asset is added to a protection policy outside of the scheduled backup window, the backup does not start until the next time that backups are configured to run.
If a new asset is added to a protection policy that has a weekly or monthly backup schedule and the current time is within the scheduled
Start and
End times, the backup runs right away, regardless of the date. If the current time is not within the scheduled
Start and
End times, the backup does not start until the next time that backups are configured to run.
Initial configuration
Enable the Oracle database asset source.
Review the authentication requirements for an Oracle database.
Add any required Oracle database credentials.
Register the application hosts with
PowerProtect Data Manager.
Perform a discovery of the application hosts.
Where applicable, configure any necessary Service Level Agreements (SLAs). The
PowerProtect Data Manager Administrator Guide provides instructions.
Assign a preferred node in the Oracle RAC environment.
Objectives
To move a backup or replica to
Cloud Tier, the corresponding
objectives must have a retention time of 14 days or more.
If you want to replicate only specific backups, perform a manual replication of these backups in advance.
Storage
Add protection storage.
The
PowerProtect Data Manager Administrator Guide provides more information about working with storage units, such as the relationships between storage units and policies, security considerations, and applicable limitations.
Before you add a replication
objective, add remote
protection storage for the replication target.
Before you add a
Cloud Tierobjective,
PowerProtect Data Manager requires:
Protection storage set up for
Cloud Tier, with the system passphrase set.
The discovery of
protection storage with a configured Cloud unit.
A configured and running data movement schedule on the cloud storage unit.
The
DDOS Administration Guide provides more information.
NOTE:PowerProtect Data Manager does not support the automatic retention lock (ARL) setting on the
DD system. The option to create a storage unit during protection policy configuration does not support compliance mode retention locking, only governance mode. To use compliance mode retention locking, create and configure a storage unit before you configure an associated protection policy. If you activate retention locking and select a storage unit where the retention lock mode is
None, the retention lock defaults to governance mode. The
PowerProtect Data Manager Administrator Guide provides more information.
Networking
If applicable, complete all of the virtual network configuration tasks before you assign any virtual networks to the protection policy. The
PowerProtect Data Manager Administrator Guide provides more information.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\