Manage the Configuration Archive
Depending on your user privilege level, or privileges set for the User Group to which you belong, you can manage the configuration archive.
A configuration can exist on every node of a device cluster. When a configuration file is pulled from a device by a node, the file is sent to all cluster nodes. See Security Manager in the Oracle Communications Session Element Manager if you need to change your privileges to allow you to manage the configuration archive.
Note:
For Oracle Enterprise products, the Configuration Archive supports only the Enterprise Session Border Controller (ESBC) and the Enterprise Communications Broker (ECB).Note:
When R226 compliance is set as enabled upon installation, the OCSDM hides LI and SIPREC attributes, however, they still exist in the datadoc.Add a Backup Schedule
Use this task to schedule automatic configuration backup for a device or a device group to run once, daily, weekly, or monthly automatically. You can also configure a backup to run on demand. The following actions occur when you create a backup:
- A new directory is created for each device using its device name in the AcmePacket/ConfigBackups directory.
- An entry is added to the database for the configuration file.
- The set purge policy is applied.
Note:
For Oracle Enterprise products, the following procedure supports only the Enterprise Session Border Controller (ESBC) and the Enterprise Communications Broker (ECB).Restore a Configuration Backup
The purge policy or existing configuration backups are not affected when a backup is restored for a device.
Note:
For Oracle Enterprise products, the following procedure supports only the Enterprise Session Border Controller (ESBC) and the Enterprise Communications Broker (ECB).- On the Configuration Manager slider, select Configure archive, Archive configuration.
- Select a backed up configuration from the table, and click Restore.
- In the confirmation dialog, click Yes to restore the backed-up configuration.
View a Backup Schedule
Note:
For Oracle Enterprise products, the following procedure supports only the Enterprise Session Border Controller (ESBC) and the Enterprise Communications Broker (ECB).Rename a Configuration
You can rename any backed up configuration file to make its name more meaningful. The actual file name on the system does not change and continues to adhere to the set file naming policy. This configuration name only appears within the context of Oracle Communications Session Element Manager.
Note:
For Oracle Enterprise products, the following procedure supports only the Enterprise Session Border Controller (ESBC) and the Enterprise Communications Broker (ECB).Manage Purge Policies
You can select a purge policy for devices or device groups. You can customize the purge policy to define the number of backup configurations to store per device, to configure the purge schedule for devices or device groups, and to purge them immediately.
Note:
For Oracle Enterprise products, purge policies support only the Enterprise Session Border Controller (ESBC) and the Enterprise Communications Broker (ECB).Purge Configurations On-Demand
You can select the purge policy you set earlier or target all backed up configurations on a device or group. You can select multiple devices or multiple groups to purge at one time.
Note:
For Oracle Enterprise products, the following procedure supports only the Enterprise Session Border Controller (ESBC) and the Enterprise Communications Broker (ECB).Search the Archive for a Configuration
Use this task to search for a configuration in the configure archive for an existing configuration backup.
- Standard wild card
* and
? characters are
supported.
- * matches 0 or more characters.
- ? matches 1 character.
- Search filters containing wild card characters must be enclosed in double quotes: “fo*”.
- Search filters containing no wild card characters result in an exact match.
-
Wild card characters cannot be used outside of double quotation marks in combination with an exact match search.
“A*1” is a valid search filter.
“A*”* is not a valid search filter.
Note:
For Oracle Enterprise products, the following procedure supports only the Enterprise Session Border Controller (ESBC) and the Enterprise Communications Broker (ECB).