Configuring backup settings for the Developer Portal subsystem
You can use the apicup
utility to configure backup settings for the
Developer Portal subsystem
Before you begin
About this task
- During an initial installation, use these steps to configure the backup settings prior to creating the initial management ISO.
- You can configure scheduled backups, or generate manual (on-demand) backups.
- When you specify a filepath in a backup setting, be sure to escape any blank spaces in the path.
- Version 10.0.3.0 or later: OpenSSH key authentication for SFTP is supported.
The default Developer Portal backup schedule is once every 24 hours, but the schedule can be changed in the backup settings. The Developer Portal saves all system and site backups locally, and also saves them remotely based on the configured SFTP and s3 settings.
The local backups are automatically maintained so that the latest three backups of each site and of the system are kept, and older backups are removed. This maintenance means that the Developer Portal retains the latest three backups for each site and for the system however old they are, but there is no deletion of the old backups on the remote server. If a site is deleted, then all of the local backups for that site are also deleted, as otherwise the backup volume might become full of old site backups. For remote backups, you can configure a retention policy on your remote server to remove the old backup files as required.
portalbackup
list that have a CR TYPE
of
record
, there might be a slow down in system performance, including during Developer Portal upgrades. Although there is no upper limit to how many portal backups you can have, it is
recommended that you prune your remote backups so that the number of rows does not become
excessively large. One portalbackup
row of type record
,
corresponds to one backup file on the configured remote backup server. For more information, see
Overview of the Developer Portal backup resources.