System & Component Backup Pruning/Deleting Deep Dive
MarcoZobbi 1100007WWM Visits (3688)
Here is the documentation for backup and restore on PureApplication System:
PureApplication System offers 2 types of backups: System Backup and Component Backup. Note that the actual work
System/Component Backup basically copies the content from PureApplication to an external backup server.Typically this external backup server is a Linux server that accessible by PureApplication.
The requirements for this server includes:
- SCP access enabled, either using username/password or SSH keys
- at least 1TB free space available
- accessible from PureApp, the faster the network connection to this server the faster the backup is performed
Is recommended that both types of backup should be configured. These backup could be scheduled to run at specific times and daily,monthly or weekly.
The System/Component backup feature in IBM PureApplication System captures the system’s configuration, its cloud environment’s configuration and workload catalog.
The System Backup copy the internal data from the management nodes, and the catalog content (scripts, images, ptypes, etc) and we could consider as a snapshot in time on the content on the rack.
For the System Backup, the first backup is what we call a "full" or initial backup, any subsequent backups to the same location and using the same firmware are "incremental" backups (i.e. they backup only the delta from the initial full backup) so they are a lot smaller and faster.
The Component Backup copy only the catalog's contents, and allows customer to select which components they want backup (script packages, virtual images, ptypes, system plugins, environment profiles, ....).
For the Component Backup, the first one exports all the selected components,after that, only components that are new/updated are backup, so it's also a lot smaller and faster.
The purpose of this backup types is quite different. The restore of System Backup restore all contents and the rack looks like the time when the backup was taken, note that customers could not restore themselves and need IBM support, the restore not work if both management nodes have failed. The restore of Component Backup does not rollback the rack to a specific point in time, instead customer could restore themselves the desired component for example a script package was deleted by accident they could select to restore just that script package.
It is not supported for the user to manually prune/delete any data from the backup server, it is very easy to corrupt the backup and make them unusable.
Instead, the customer should have to configure a new backup location from PureApplications console under section "Management/Backup & Restore" or via CLI, for more informations: http
For the System Backup, this will create a new initial backup, and the scheduled backup will be incremental. Similarly, do the same for the Component Backup. Once you are comfortable that do not need the backups, you can then purge completely the old backup location. However, the creation of a new backup location means the customer does need to have sufficient free storage, or a different server.
For the System Backup, the restore only works on the same PureApplication version. So when the rack is upgraded to a new fixpack level, the first backup taken after the upgrade is a new base backup for the new PureApplication version, additional space is required for this initial backup, the backups from the old PureApplication versions may be deleted. So if the customer has backups from prior releases those are safe to delete. You would feel more comfortable to delete the old backups only after a new initial backup has completed successfully after the upgrade, in case need it to help with debugging.
Each backup location (/backup in my example below), there is directory for each PureApplication version, the version number is based on the backup component. For the corresponding PureApplication version, replace the "5" with "2". Within each 5.1.1.x is a System Backup for that PureApplication release. The directories are created automatically by the backup. If the rack is upgraded to 126.96.36.199, a new initial backup is taken and stored under the 188.8.131.52 directory. Within each version directory, there is one initial backup and all incrementals backups. So it is not supported to cleanup by removing contents from a version directory. However, in the example below, it is safe to delete 184.108.40.206 and 220.127.116.11 directory. Those backups could only be used for restored if the rack build level is rolled-back to that version.
18.104.22.168 22.214.171.124 126.96.36.199 backupSecurity backupStorage
backup.json docroot facets globalcontext key scripts security templates vault virtual