Best practices for reducing backup and restore times

Last Updated : Oct 02, 2024 |
Prolog information
Metadata
Keywords:
If you do not take steps to optimize your CMS backup and restore times, you might experience performance issues. Your CMS system performance drops if the backup continues to run when call center activity increases. Due to higher capacity limits and fewer database restrictions, the maintenance backup time can take longer with each new CMS release. In rare extreme cases, maintenance backups could take more than 24 hours.
To reduce the amount of time it takes to backup or restore data, you can:
  • Select the maximum interval time that meets your data collection needs.
  • Select the minimum data storage times that meets your data collection needs for all the historical database tables.
  • Run reports when the CMS system is not actively backing up or restoring data.
  • Schedule each ACD to back up at a different time.
  • Schedule routine backups to occur at a different time than data archiving.
  • Schedule routine backups to occur when CMS system activity is low.
  • Use the binary backup method. A binary backup does not support table level restore and data migration. This backup method is also a good alternative for disaster recovery.
  • Upgrade your CMS system to add additional memory and CPUs.