Data backup and retention
Regular backups are taken for all customer environments for VMs and databases. Backups are performed using a disk-to-disk copy.
BMC tests its backup and restore procedures at least annually. If you have purchased an additional environment, its backup and retention schedule will be the same as the Development schedule seen below. Customers may request a database restore at any time by submitting a new case through Support Central.
Backup data is encrypted only if the active data at rest is encrypted. See Data encryption for details. For file transfer protocol (FTP) retention periods, please visit File transfer process.
Backup and retention schedules are as follows:
VM backups
For services deployed on a virtual machine, BMC uses the following schedule:
| Environments | Frequency | Type | Retention | Media | Storage location |
|---|---|---|---|---|---|
Production | Daily | Incremental | 14 days | Disk | Primary and secondary sites |
| Daily | Incremental | 7 days | Disk | Primary site |
Production | Weekly | Full | 14 days | Disk | Primary and secondary sites |
| Weekly | Full | 7 days | Disk | Primary site |
Important
If you are a customer on containerized applications, the current state of the objects is backed up when changes are made. Historical configurations are retained indefinitely.
Database backups
For database backups, BMC uses the following schedule:
| Environments | Frequency | Type | Retention | Media | Storage location |
|---|---|---|---|---|---|
| Production | Daily | Incremental | 14 days | Disk | Primary and secondary sites |
| Production | Weekly | Full | 14 days | Disk | Secondary site |
| Production | Monthly | Full | 90 days | Disk | Secondary site |
| Daily | Incremental | 7 days | Disk | Secondary site |
| Weekly | Full | 7 days | Disk | Secondary site |
Was this page helpful? Yes No
Submitting...
Thank you
Comments
Log in or register to comment.