| Oracle® Secure Backup Reference Release 10.2 Part Number E05410-02 |
|
|
View PDF |
| Oracle® Secure Backup Reference Release 10.2 Part Number E05410-02 |
|
|
View PDF |
Oracle Secure Backup defaults and policies are configuration data that control how Oracle Secure Backup operates within an administrative domain. These policies are grouped into several policy classes. Each policy class contains policies that describe a particular area of operations.
The policy classes are as follows:
See Also:
"Policy Commands" to learn about the obtool policy commandsThese policies control aspects of the behavior of daemons and services. For example, you can specify whether logins should be audited and control how the index daemon updates the catalog.
The daemon policies are as follows:
Use the auditlogins policy to audit attempts to log in to Oracle Secure Backup.
Enables the policy. All attempts to log in to Oracle Secure Backup are logged by the administrative observiced to its log file.
Disables the policy (default).
Use the obixdmaxupdaters policy to specify the maximum number of catalog update processes that can operate concurrently.
The Oracle Secure Backup index daemon (obixd) is a daemon that manages the Oracle Secure Backup catalogs for each client. Oracle Secure Backup starts the index daemon at the conclusion of each backup and at other times throughout the day.
Specifies the number of concurrent obixd daemons to allow. The default is 2.
Use the obixdrechecklevel policy to control the level of action by the Oracle Secure Backup index daemon to ensure that a host backup catalog is valid before making it the official catalog.
Specifies that the index daemon should verify that the structure of the catalog is sound after any updates to a backup catalog (default). This verification is a safeguard mechanism and is used to by the index daemon to double-check its actions after a catalog update.
Specifies that the index daemon should verify that the structure and content of the catalog is sound after any updates to a backup catalog. This is the most time-consuming as well as the most comprehensive method.
Specifies that the index daemon should take no extra action to affirm the soundness of the catalog after updates to the backup catalog. This is the fastest but also the least safe method.
Use the obixdupdaternicevalue policy to set the priority at which the index daemon runs. The higher the value, the more of the CPU the index daemon yields to other competing processes. This policy is not applicable to Windows hosts.
Specifies the index daemon priority. The default is 0, which means that the index daemon runs at a priority assigned by the system, which is normal process priority. You can use a positive value (1 to 20) to decrease the priority, thereby making more CPU time available to other processes. To give the daemon a higher priority, enter a negative number.
Use the webautostart policy to specify whether the Apache Web server automatically starts when you restart observiced.
Enables the policy.
Note:
The installation process sets
webautostart to yes, which is not the default value.Disables the policy (default).
Use the webpass policy to specify a password to be passed to the Web server.
If the Web server's Secure Sockets Layer (SSL) certificate requires a password (PEM pass phrase), then entering it in this policy enables observiced to pass it to the Oracle Secure Backup Web server when it is started. The password is used when decrypting certificate data stored locally on the administrative server and never leaves the computer.
Specifies the password. By default no password is set.
Note:
The installation script configures a password for thewebpass policy. You can change this password, although in normal circumstances you should not be required to do so.Use the windowscontrolcertificateservice to specify whether Oracle Secure Backup should attempt to put the Windows certificate service in the appropriate mode before backing up or recovering a certificate service database.
Specifies that Oracle Secure Backup should start the certificate service prior to a backup, stop it, and then restart the certificate service for a restore.
Disables the policy (default).
These policies control how a tape device is automatically detected during device discovery as well as when tape device write warnings are generated.
The device policies are as follows:
Use the discovereddevicestate policy to determine whether a tape device discovered by the discoverdev command is immediately available for use by Oracle Secure Backup.
Specifies that discovered tape devices will be immediately available to Oracle Secure Backup.
Specifies that discovered tape devices are not available to Oracle Secure Backup until explicitly placed in service (default).
Use the errorrate policy to set the error rate. The error rate is the ratio of recovered write errors that occur during a backup job per the total number of blocks written, multiplied by 100. If the error rate for any backup is higher than this setting, then Oracle Secure Backup displays a warning message in the backup transcript.
Specifies the error rate to be used with the tape device. The default is 8.
Disables error rate checking. You can disable error rate checking to avoid warning messages when working with a tape drive that does not support the Small Computer System Interface (SCSI) commands necessary to check the error rate.
Use the maxdriveidletime policy to set how long a tape can remain idle in a tape drive after the conclusion of a backup or restore operation. When this set time is up, Oracle Secure Backup automatically unloads the tape from the tape drive.
You cannot specify this parameter on a drive-by-drive basis. You must have the modify administrative domain's configuration right to modify this policy.
Specifies the length of time that a tape can remain idle before Oracle Secure Backup unloads it. Refer to "duration" for a description of the duration placeholder. The default is 5minutes, which means that Oracle Secure Backup unloads a tape when it has been idle for five minutes.
Note:
Theduration placeholder must be specified by some combination of seconds, minutes and hours only.The minimum value that can be specified is 0seconds. The maximum value is 24hours. A duration of 0 results in an immediate tape unload at the conclusion of any backup or restore operation.
Specifies that a tape remains in the tape drive at the conclusion of a backup or restore operation. The tape will not be unloaded automatically.
This policy applies only to StorageTek Automated Cartridge System Library Software (ACSLS) systems. Use the maxacsejectwaittime policy to set how long an outstanding exportvol request waits for the ACS cartridge access port to be cleared.
Specifies the length of time that Oracle Secure Backup waits for an ACS cartridge access port to be cleared before cancelling an exportvol request.
Manual operator intervention is required to remove the tapes from the cartridge access port after an ACS exportvol operation has finished. Access to the ACSLS server is denied until the tapes are removed or a period of time greater than maxacsjecetwaittime has passed. Oracle recommends that you schedule exports only when a human operator is locally available and that you batch export operations such that multiple volumes are specified for each exportvol operation.
Refer to "duration" for a description of the duration placeholder. The default is 5minutes.
Note:
Theduration placeholder must be specified by some combination of seconds, minutes and hours only.The minimum value that can be specified is 0seconds. The maximum value is forever.
Specifies that Oracle Secure Backup never cancels an exportvol request while waiting for an ACS cartridge access port to clear.
These policies control how Oracle Secure Backup generates and manages the catalog. For example, you can specify the amount of elapsed time between catalog cleanups.
The index policies are as follows:
Use the asciiindexrepository policy to specify the directory where ASCII index files are saved prior to being imported into the Oracle Secure Backup catalog by the index daemon.
Specifies the path name for the index files. The default path name is the admin/history/host/hostname subdirectory of the Oracle Secure Backup home.
Use the autoindex policy to specify Oracle Secure Backup whether backup catalog data should be produced for each backup it performs.
Specifies that catalog data should be produced for each backup (default).
Specifies that catalog data should not be produced for each backup.
Use the earliestindexcleanuptime policy to specify the earliest time of day at which catalog information should cleaned up. Cleanup activities should take place during periods of lowest usage of the administrative server.
Specifies the time in hour and minutes. Refer to "time" for a description of the time placeholder. The default value is 23:00.
Use the generatendmpindexdata policy to specify whether Oracle Secure Backup should produce backup catalog information when backing up a client accessed through Network Data Management Protocol (NDMP).
Specifies that catalog data should be produced for backups of NDMP clients (default).
Specifies that catalog data should not be produced for backups of NDMP clients.
Use the indexcleanupfrequency policy to specify the amount of elapsed time between catalog cleanups.
Typically, you should direct Oracle Secure Backup to clean up catalogs on a regular basis. This technique eliminates stale data from the catalog and reclaims disk space. Catalog cleanup is a CPU-intensive and disk I/O-intensive activity, but Oracle Secure Backup performs all data backup and restore operations without interruption when catalog cleanup is in progress.
Specifies the frequency of catalog cleanup operations. Refer to "duration" for a description of the duration placeholder. The default is 21days, which means that Oracle Secure Backup cleans the catalog every three weeks.
Use the latestindexcleanuptime policy to specify the latest time of day at which index catalogs can be cleaned up.
Specifies the latest index cleanup time. Refer to "time" for a description of the time placeholder. The default value is 07:00.
Use the maxindexbuffer policy to specify a maximum file size for the local index buffer file.
Backup performance suffers if index data is written directly to an administrative server that is busy with other tasks. To avoid this problem, Oracle Secure Backup buffers index data in a local file on the client during the backup, which reduces the number of interactions that are required with an administrative server. This policy enables you to control the maximum size to which this buffer file can grow.
Specifies the buffer size in blocks of size 1 KB. The default value is 6144, which is 6 MB. Setting the buffer size to 0 causes Oracle Secure Backup to perform no local buffering.
Use the saveasciiindexfiles policy to determine whether to save or delete temporary ASCII files used by the index daemon.
When Oracle Secure Backup performs a backup, it typically generates index information that describes each file system object it saves. Specifically, it creates a temporary ASCII file on the administrative server in the admin/history/index/client subdirectory of the Oracle Secure Backup home. When the backup completes, the index daemon imports the index information into the index catalog file for the specified client.
Directs Oracle Secure Backup to retain each temporary ASCII index file. This option might be useful if you have written tools to analyze the ASCII index files and generate site-specific reports.
Directs Oracle Secure Backup to delete each temporary ASCII index file when the backup completes (default).
These policies control historical logging in the administrative domain. For example, you can specify which events should be recorded in the activity log on the administrative server: all, backups only, restore operations only, and so forth.
The log policies are as follows:
Use the adminlogevents policy to specify the events to be logged in the activity log on the administrative server. Separate multiple event types with a comma. By default this policy is not set, which means that no activity log is generated.
Logs all backup events.
Logs command-line backups that specify files to be backed up on the command line.
Logs scheduled backup operations.
Logs restore operations.
Logs everything specified by the preceding options.
Use the adminlogfile policy to specify the path name for the activity log on the administrative server.
Specifies the path name of a log file, for example, /var/log/admin_srvr.log. By default this policy is not set, which means that no log file is generated.
Use the clientlogevents policy to specify the events to be logged in the activity log on the client host.
See the values for the adminlogevents policy. By default this policy is not set.
Use the jobretaintime policy to set the length of time to retain job list history.
Retains the job history for the specified period. The default is 30days. Refer to "duration" for a description of the duration placeholder.
Use the logretaintime policy to set the length of time to retain Oracle Secure Backup log files.
Several components of Oracle Secure Backup maintain log files containing diagnostic messages. This option lets you limit the size of these files, which can grow quite large. Oracle Secure Backup periodically deletes all entries older than the specified duration.
Retains the diagnostic logs for the specified period. The default is 7days. Refer to "duration" for a description of the duration placeholder.
Use the transcriptretaintime policy to specify the length of time to retain Oracle Secure Backup job transcripts.
When the Oracle Secure Backup scheduler runs a job, it saves the job output in a transcript file. You can specify how long transcript files are to be retained.
Retains the job transcripts for the specified period. The default is 7days. Refer to "duration" for a description of the duration placeholder.
Use the unixclientlogfile policy to specify the path name for log files on UNIX client hosts. Oracle Secure Backup logs each of the events selected for clientlogevents to this file on every UNIX client.
Specifies the path name for the log files on UNIX clients. By default this policy is not set, which means that no log file is generated.
Use the windowsclientlogfile to specify the path name for log files on Windows client hosts. Oracle Secure Backup logs each of the events selected for clientlogevents to this file on each Windows client.
Specifies the path name for the log files on Windows clients. By default this policy is not set, which means that no log file is generated.
These policies control domain-wide media management. For example, you can specify a retention period for tapes that are members of the null media family.
The media policies are as follows:
Use the barcodesrequired policy to determine whether every tape is required to have a readable barcode.
By default, Oracle Secure Backup does not discriminate between tapes with readable barcodes and those without. This policy ensures that Oracle Secure Backup can always solicit a tape needed for restore by using both the barcode and the volume ID. Use this feature only if every tape drive is contained in a tape library with a working barcode reader.
Requires tapes to have readable barcodes.
Does not require tapes to have readable barcodes (default).
Use the blockingfactor policy to define the size of every tape block written during a backup or restore operation. You can modify this value so long as it does not exceed the limit set by the maxblockingfactor policy.
See Also:
Oracle Secure Backup Administrator's Guide for more information on blocking factorsSpecifies the block factor in blocks of size 512 bytes. The default value is 128, which means that Oracle Secure Backup writes 64 KB blocks to tape.
Use the maxblockingfactor policy to define the maximum size of a tape block read or written during a backup or restore operation. Blocks over this size are not readable.
See Also:
Oracle Secure Backup Administrator's Guide for more information on maximum blocking factorsSpecifies the maximum block factor in blocks of size 512 bytes. The default value is 128, which represents a maximum block size of 64 KB. The maximum setting is 4096, which represents a maximum tape block size of 2 MB. This maximum is subject to further constraints by tape device and operating system limitations outside of the scope of Oracle Secure Backup.
Use the overwriteblanktape policy to specify whether Oracle Secure Backup should overwrite a blank tape.
Overwrites blank tapes (default).
Does not overwrite blank tapes.
Use the overwriteforeigntape policy to specify whether Oracle Secure Backup should overwrite an automounted tape recorded in an unrecognizable format.
Overwrites tapes in an unrecognized format (default).
Does not overwrite tapes in an unrecognized format.
Use the overwriteunreadabletape policy to specify whether Oracle Secure Backup should overwrite a tape whose first block cannot be read.
Overwrites unreadable tapes.
Does not overwrite unreadable tapes (default).
Use the volumeretaintime policy to specify a retention period for tapes that are members of the null media family.
Retains the volumes for the specified period. The default is disabled, which means that the volumes do not automatically expire. You can overwrite or unlabel the volume at any time. Refer to "duration" for a description of the duration placeholder.
Use the writewindowtime policy to specify a write-allowed time for tapes that are members of the null media family.
Retains the volumes for the specified period. The default is disabled, which means that the write window never closes. Refer to "duration" for a description of the duration placeholder.
This class contains a single policy, which specifies a WINS server for the administrative domain.
The naming policy is as follows:
Use the winsserver policy to specify an IP address of a Windows Internet Name Service (WINS) server. The WINS server is used throughout the administrative domain.
Oracle Secure Backup provides the ability for UNIX systems to resolve Windows client host names through a WINS server. Setting this policy enables Oracle Secure Backup to support clients that are assigned IP addresses dynamically by WINS.
Specifies a WINS server with the IP address wins_ip. By default this policy is not set.
These policies specify Network Data Management Protocol (NDMP) data management application (DMA) defaults. For example, you can specify a password used to authenticate Oracle Secure Backup to each NDMP server.
The NDMP policies are as follows:
Use the authenticationtype policy to specify the means by which the Oracle Secure Backup Network Data Management Protocol (NDMP) client authenticates itself to an NDMP server.
You can change the authentication type for individual hosts by using the --ndmpauth option of the mkhost and chhost commands.
Specifies the authentication type. Refer to "authtype" for a description of the authtype placeholder. The default is negotiated, which means that Oracle Secure Backup determines (with the NDMP server) the best authentication mode to use. Typically, you should use the default setting.
Use the backupev policy to specify backup environment variables. Oracle Secure Backup passes each variable to the client host's Network Data Management Protocol (NDMP) data service every time it backs up NDMP-accessed data.
Note:
NDMP environment variables are specific to each data service. For this reason, specify them only if you are knowledgeable about the data service implementation.You can also select client host-specific environment variables, which are sent to the NDMP data service each time data is backed up from or recovered to the client host, by using the --backupev and --restoreev options of the mkhost and chhost commands.
Specifies a backup environment variable name and value, for example, VERBOSE=y. By default the policy is not set.
Use the backuptype policy to specify a default backup type. Backup types are specific to Network Data Management Protocol (NDMP) data services; a valid backup type for one data service can be invalid, or undesirable, for another. By default Oracle Secure Backup chooses a backup type appropriate to each data service.
You can change the backup type for individual hosts by using the --ndmpbackuptype option of the mkhost and chhost commands.
Specifies a default backup type. Refer to "ndmp-backup-type" for a description of the ndmp-backup-type placeholder.
Use the password policy to specify a password used to authenticate Oracle Secure Backup to each Network Data Management Protocol (NDMP) server.
You can change the NDMP password for individual hosts by using the --ndmppass option of the mkhost and chhost commands.
Specifies a password for NDMP authentication. By default this policy is not set, that is, the default password is null.
Use the port policy to specify a TCP port number for use with Network Data Management Protocol (NDMP).
You can change the TCP port for individual hosts by using the --ndmpport option of the mkhost and chhost commands.
Specifies a TCP port number. The default value for port_num is 10000.
Use the protocolversion policy to specify a Network Data Management Protocol (NDMP) version.
Typically, you should let Oracle Secure Backup negotiate a protocol version with each NDMP server (default). If it is necessary for testing or some other purpose, then you can change the NDMP protocol version with which Oracle Secure Backup communicates with this server. If an NDMP server is unable to communicate using the protocol version you select, then Oracle Secure Backup reports an error rather than using a mutually supported version.
You can change the NDMP protocol version for individual hosts by using the --ndmppver option of the mkhost and chhost commands.
Specifies a protocol number. Refer to "protover" for a description of the protover placeholder. The default is 0, which means "as proposed by server."
Use the restoreev policy to specify restore environment variables. Oracle Secure Backup passes each variable to the client host's Network Data Management Protocol (NDMP) data service every time it recovers NDMP-accessed data.
You can also select client host-specific environment variables, which are sent to the NDMP data service each time data is backed up from or recovered to the client host, by using the --backupev and --restoreev options of the mkhost and chhost commands.
Note:
NDMP environment variables are specific to each data service. For this reason, specify them only if you are knowledgeable with the data service implementation.Specifies a backup environment variable name and value, for example, VERBOSE=y. By default the policy is not set.
Use the username policy to specify the name used to authenticate Oracle Secure Backup to each Network Data Management Protocol (NDMP) server.
You can change the NDMP username for individual hosts by using the --ndmpuser option of the mkhost and chhost commands.
Specifies a username for authentication on NDMP servers. The default is root.
These policies control various backup and restore operations. For example, you can set the amount of time that a Recovery Manager (RMAN) backup job waits in the Oracle Secure Backup scheduler queue for the required resources to become available.
The operations policies are as follows:
Use the autohistory policy to specify whether Oracle Secure Backup updates backup history data every time a client host is backed up. This history data is used to form file selection criteria for an incremental backup.
Updates backup history data when a client host is backed up (default). This history data is used to form file selection criteria for incremental backups.
Does not update backup history data when a client host is backed up.
Use the autolabel policy to specify whether Oracle Secure Backup creates a volume label and a backup image label for a new backup image whenever it backs up data.
Enables label generation (default).
Disables label generation. You should not disable label generation unless directed by Oracle Support Services.
Use the backupimagerechecklevel policy to specify whether Oracle Secure Backup performs block-level verification after each backup section is completed.
Oracle Secure Backup can optionally reread each block that it writes to tape during a backup job. It provides a second verification that the backup data is readable. The first check is performed by the read-after-write logic of the tape drive immediately after the data is written.
Performs block-level verification after each backup section is completed. Oracle Secure Backup backspaces the tape to the beginning of the backup section, reads the contents, and performs one of the following actions:
Leaves the tape positioned at the end of the backup section if it was the last section of the backup
Continues with volume swap handling if it has more data to write
Caution:
Choosingblock substantially increases the amount of time it takes to back up data.Performs no verification (default).
Use the backupoptions policy to specify additional options to apply to backups dispatched by the scheduler. Whenever the scheduler initiates a backup, it supplies the specified command-line options to obtar. For example, you can turn on diagnostic output mode in obtar by setting this value to -J.
These options apply only to backups initiated by the Oracle Secure Backup scheduler, not through the obtool command-line interface.
Specifies user-supplied obtar options. See "obtar Options" for details on obtar options. By default no options are set.
Note:
Whatever you enter is passed directly to obtar, so be sure to specify valid options. Otherwise, your backup or restore jobs will fail to run.Use the databuffersize policy to control the size of the shared memory buffer used for data transfer in a local file system backup or restore operation. It is expressed as a number of tape blocks, and the default value is 6. The default size of this shared memory, therefore, is 6 times the current tape block size.
You can use this policy to tune backup performance. It is relevant only to file system backup and restore operations where the client and the media server are collocated.
See Also:
"blockingfactor" for more information on tape block sizeUse the fullbackupcheckpointfrequency policy to specify checkpoint frequency, that is, how often Oracle Secure Backup takes a checkpoint during a full backup for restartable backups.
Takes a checkpoint after every n MB transferred to a volume.
Takes a checkpoint after every n GB transferred to a volume. By default, Oracle Secure Backup takes a checkpoint for every 8 GB transferred to a volume.
Use the incrbackupcheckpointfrequency policy to specify checkpoint frequency, that is, how often Oracle Secure Backup takes a checkpoint during an incremental backup for restartable backups.
Takes a checkpoint after every n MB transferred to a volume.
Takes a checkpoint after every n GB transferred to a volume. By default, Oracle Secure Backup takes a checkpoint for every 2 GB transferred to a volume.
Choose the period at which Oracle Secure Backup will take a checkpoint during an incremental backup for any backup that is restartable. The value is represented in volume of bytes moved. (In the default case, a checkpoint is taken for each 8 GB transferred to a volume.)
Use the mailport policy to specify the TCP/IP (Transmission Control Protocol/Internet Protocol) port number to which Oracle Secure Backup sends email requests from Windows hosts.
Specifies a TCP/IP port number. The default value is 25.
Use the mailserver policy to specify the name of the host to which Oracle Secure Backup sends email requests from Windows hosts.
Specifies a host name. The default value is localhost.
Use the maxcheckpointrestarts policy to specify the maximum number of times Oracle Secure Backup attempts to restart an operation from the same checkpoint. If this limit is reached, then Oracle Secure Backup discards the checkpoint and restarts the backup from the beginning.
Specifies the maximum number of restarts. The default value is 5.
Use the positionqueryfrequency policy to specify a frequency at which Oracle Secure Backup obtains position information from the tape drive.
When obtar generates an index while creating or indexing a backup image, it periodically obtains information from the tape drive. Oracle Secure Backup uses this information during subsequent restore jobs to rapidly position a tape to the requested files.
Specifies the position query frequency in terms of KB transferred. The default value is 1024 (1 MB), which means that information is obtained after each 1 MB (1024*1024) of data is written to tape.
Use the restartablebackups policy to specify whether the restartable backups feature is enabled. This feature enables Oracle Secure Backup to restart certain types of failed backups from a mid-point rather than from the beginning.
Enables restartable backups (default).
Note:
If you use the restartable backups feature, then ensure that the /tmp directory on the administrative server is on a partition that maintains at least 1 GB of free space.Disables restartable backups.
Use the restoreoptions policy to specify additional options to apply to restore operations dispatched by the scheduler. Whenever the scheduler initiates a restore operation, it supplies the specified command-line options to obtar. For example, you can turn on diagnostic output mode in obtar by setting this value to -J.
Specifies user-supplied obtar options. See "obtar Options" for details on obtar options. By default no restore options are set.
Note:
Whatever you enter is passed directly to obtar, so be sure to specify valid options. Otherwise, your backup or restore jobs will fail to run.Use the rmanresourcewaittime policy to select the duration to wait for a resource.
When a Recovery Manager (RMAN) job has been started and requires certain resources, the resources might not be available immediately. The rmanresourcewaittime policy controls the amount of time that the job waits in the Oracle Secure Backup scheduler queue for the required resources to become available. If the resources are unavailable at the end of the wait time, then the job fails with an error message. If the resources become available within the specified time, then the job completes successfully.
Specifies the time to wait for a resource. Refer to "duration" for a description of the duration placeholder. Note that all values are valid except disabled. The default is forever.
Use the rmanrestorestartdelay policy to select the amount of time to wait before starting a restore operation after a restore request has been received. You can use this delay to queue all requests and optimize the retrieval of data from tape.
Specifies the time to delay. Valid values are a number followed by seconds, minutes, or hours. The default is 10seconds.
Use the tcpbufsize policy to specify the size of TCP/IP (Transmission Control Protocol/Internet Protocol) buffers used in performing backups over the network, for hosts for which no buffer size has been specified directly using mkhost or chhost. The default value for tcpbufsize is the system default.
This policy is used in tuning backup performance.
Use the windowsskipcdfs policy to determine whether Oracle Secure Backup should back up Windows CD-ROM file systems (CDFS).
Does not back up CDFS file systems (default).
Backs up the contents of CDFS file systems.
Use the windowsskiplockedfiles policy to determine whether Oracle Secure Backup logs an error message when it encounters a locked Windows file. Files are locked when in use by another process.
Skips locked files and does not write a message to the transcript or archive's index file.
Logs an error message to the transcript and to the archive's index file (default).
These policies control the behavior of the scheduler. For example, you can specify a frequency at which the scheduler attempts to dispatch backup jobs.
The scheduler policies are as follows:
Use the applybackupsfrequency policy to specify a frequency at which the Oracle Secure Backup scheduler attempts to dispatch jobs.
Specifies how often the scheduler dispatches jobs. Refer to "duration" for a description of the duration placeholder. Note that the forever and disabled values are not legal. The default value is 5minutes, that is, Oracle Secure Backup attempts to dispatch jobs every five minutes.
Use the defaultstarttime policy to specify the default start time for each new trigger. See the Oracle Secure Backup Administrator's Guide for more information on triggers.
Specifies the default trigger start time. Refer to "time" for a description of the time placeholder. The default value is 00:00 (midnight).
Use the maxdataretries policy to specify the maximum number of times to retry a failed client backup.
While attempting to back up a client, certain errors can occur that cause the backup to fail. (See the Oracle Secure Backup Administrator's Guide for a description of triggers.) Retryable failures include those caused by the client being unavailable because it is out of service or down, unable to communicate through the network, or has insufficient disk space for temporary backup files.
Specifies the maximum number of times to retry. The default value is 6.
Use the pollfrequency policy to specify the frequency at which Oracle Secure Backup scans the contents of the scheduler catalog for manual changes.
Specifies the scheduler catalog polling frequency. Refer to "duration" for a description of the duration placeholder. Note that the forever value is not legal. The default value is 30minutes.
Use the retainbackupmetrics policy to specify whether Oracle Secure Backup saves a summary of metrics produced by each backup operation in the client host's observiced log.
Saves a metric summary.
Does not save a metric summary (default).
These policies control aspects of domain security. For example, you can enable Secure Sockets Layer (SSL) encryption for backup data in transit or set the key size for each host identity certificate.
The security policies are as follows:
Use the trustedhosts policy to control whether or not Oracle Secure Backup restricts certain operations to trusted hosts only. These operations include:
Use of obtar commands
Direct access to physical devices and libraries
Access to encryption keys
The restricted operations can be run only from an administrative server or media server. If one of the restricted operations is attempted from a host that has only the client role, then the attempt fails with an illegal request from non-trusted host error.
The restricted operations can be run from any host in the administrative domain.
See Also:
Oracle Secure Backup Installation and Configuration Guide for more information on trusted hostsUse the autocertissue policy to indicate whether observiced on the administrative server will transmit signed certificates (certificate response messages) over the network as part of the mkhost command processing.
Transmits signed certificates over the network during host creation (default).
Does not transmit signed certificates over the network during host creation.
Use the certkeysize policy to indicate the key size to be used when creating the public key/private key pair used in every identity certificate in the administrative domain. Certification Authorities typically choose key sizes of 1024 or 2048.
Specifies the size of the key in bytes. Valid values are 512, 768, 1024 (default), 2048, 3072, or 4096. Key sizes of 512 or 768 are not regarded as secure; 1024 or 2048 are regarded as secure; and 3072 or 4096 are regarded as very secure.
Use the encryptdataintransit policy to enable Secure Sockets Layer (SSL) encryption for file system and unencrypted Recovery Manager (RMAN) backup data before it passes over the network. This policy does not enable or disable encryption for data at rest, that is, data stored on disk or tape.
If RMAN backup data is already encrypted by RMAN, then this policy does not encrypt it again.
Enables encryption for bulk data transferred over the network.
Disables encryption for bulk data transferred over the network (default).
Use the loginduration policy to specify the amount of time a login token remains valid in obtool after it is created.
Oracle Secure Backup creates a login token each time you log in through the obtool. If a valid token exists when you invoke either tool, then you do not have to log in again.
Specifies the duration of the login token. Refer to "duration" for a description of the duration placeholder. The default value is 15minutes.
Use the securecomms policy to specify whether daemon components will utilize Secure Sockets Layer (SSL) for authentication and message integrity.
Enables SSL encryption for authentication and message integrity (default).
Disables SSL encryption for authentication and message integrity.
These policies control how Oracle Secure Backup performs backup encryption. For example, you can specify whether backups must be encrypted for the entire administrative domain or for specific clients in the domain, as well as which encryption algorithm to use for encryption, and how keys are managed.
The global algorithm, global keytype, and global rekeyfrequency policies are used to provide default values to newly created clients. The client algorithm, client keytype, and client rekeyfrequency policies define the actual values used for a given client.
The encryption policies are as follows:
Use the encryption policy to specify whether data written to tape backups must be encrypted by default.
This policy can be set as a global policy for the administrative domain. It can also be overridden at the client level, using the --encryption option of the mkhost and chhost commands.
Note:
If a database backup is encrypted at the Recovery Manager (RMAN) level, then Oracle Secure Backup always writes the backup to tape in the encrypted form provided by RMAN, regardless of the setting for theencryption policy. If encryption is set to required, then Oracle Secure Backup does not encrypt the data a second time.Encrypt all backups, regardless of policy settings on specific clients or jobs. If this policy is enabled at the administrative domain level, then all backup data written to tape is encrypted, regardless of other policies for specific clients or settings for specific jobs. If this policy is defined at the client level, then all backup data written to tape from this client is encrypted, regardless of settings for specific jobs.
Backups written to tape are not encrypted, unless the policy set on a client or the settings for a job specify encryption. This is the default.
Use the algorithm policy to specify the algorithm used in encrypting backups written to tape.
At the administrative domain level, the algorithm policy specifies the default algorithm for all backups. At the client level, it specifies the default algorithm for backups from this client.
Note:
The algorithms available are the same as those available in Recovery Manager (RMAN).Use AES 128-bit encryption. This is the default.
Use AES 192-bit encryption.
Use AES 256-bit encryption.
Use the keytype policy to specify the method for generating the encryption key.
Keys are randomly generated using the Oracle Random Number Generator as a seed for the key. The keys are stored in the Oracle wallet. This is the default.
Keys are generated based upon a backup administrator-supplied passphrase.
Note:
chhost command. Until the passphrase is set, backups are encrypted in transparent mode.If the passphrase is lost or forgotten, then backups created with it cannot be restored.
Use the rekeyfrequency policy to manage how often new keys are generated. Older keys are retained in a wallet-protected key store.
The rekeyfrequency policy can be defined at the global level for an entire administrative domain. The global policy can be overridden at the client level.
Specifies the frequency of generating new keys for transparent mode encryption. Refer to "duration" for a description of the duration placeholder.
A new key is automatically generated at midnight on the day when the specified duration expires. This new key is then added to the wallet and is used on subsequent backup operations. Older keys are retained in the wallet for restoring older backups.
Note:
If the keytype policy is set to passphrase, then the administrator is responsible for managing key regeneration.The default value is 30days, which means new keys are generated after thirty days. Minimum duration is 1 day.
New keys are generated for each backup. Older keys are retained in the wallet for restoring older backups.
New keys are not automatically generated at regular intervals.
Valid only as a client-based policy. Specifies that this host should use the current administrative domain policy.
These policies control how Oracle Secure Backup performs vaulting.
The vaulting policies are as follows:
Use the autovolumerelease policy to automatically release recalled volumes when restore jobs requiring those volumes have completed. Only volumes automatically recalled by Oracle Secure Backup are released.
Use the customeridstring policy to define the default customer ID string used in reports generated by Oracle Secure Backup. You can override this policy for an individual location.
Use the minwritablevolumes policy to specify the minimum number of writable volumes that must be available in each tape library at all times. If the number of writable volumes in a tape library drops below this value, then Oracle Secure Backup initiates early rotation of volumes in that tape library.
You can override this policy for an individual location.
Specifies the minimum number of writeable volumes for each tape library.
Use the reportretaintime policy to define how long vaulting reports (pick/distribution) are retained.
Specifies how long vaulting reports are retained. Refer to "duration" for a description of the duration placeholder. The default value is 7days.
These policies control how Oracle Secure Backup performs volume duplication.
The volume duplication policies are as follows:
Use the duplicateovernetwork policy to control whether Oracle Secure Backup is allowed to duplicate a volume to a different media server than the one containing the original volume being duplicated. Oracle Secure Backup does not duplicate between tape devices attached to different media servers by default, because it requires heavy use of network bandwidth.
Allow duplication between tape devices attached to different media servers.
Disallow duplication between tape devices attached to different media servers. This is the default value.
Use the duplicationjobpriority policy to specify the priority of volume duplication jobs relative to other jobs.
Specifies the priority of the job. Default: 200.
Note:
By default, backup jobs are scheduled with a priority of 100. As a result, backup jobs take precedence over volume duplication jobs by default.
|
 Copyright © 2006, 2008, Oracle. All rights reserved. Legal Notices |
|