You can create backups of your ArcGIS Enterprise deployment and restore the most recent backup in the event of a failure or corruption. This allows you to recover the portal items, services, and data that existed at the time you created the backup.
Restoring backups to recover your deployment is a good option if your users will accept some amount of downtime and possible data loss, and your organization does not have the infrastructure or resources to devote to a highly available deployment.
Backups can also be kept even if you implement other disaster recovery strategies. They provide extra insurance that you can recover your deployment if your primary strategy fails. For example, if you maintain a replicated deployment and both your primary and replicated deployments fail at the same time (perhaps they were running on servers in the same building and the building loses power or there's an electrical surge that wipes out both servers), you still have a backup to which you can resort.
What's included in the backup?
Use the webgisdr utility to export backup files of the following components of your ArcGIS Enterprise deployment:
- Your portal items and settings
- GIS services and settings
- If using ArcGIS Data Store, your managed database (relational data store) and hosted scene layer cache databases (tile cache data store)
You have the option to create incremental backups between full backups. When you create an incremental backup, the backup file contains all changes made since the last full backup.
Note that the backup created with the webgisdr utility does not include the following:
- Map service cache tiles and hosted tile layer caches—If you have either of these, make a backup copy of all directories where your cache tiles are stored (for example, the entire arcgiscache directory under C:\arcgisserver\directories\ or <ArcGIS Server installation directory>/arcgis/server/usr/directories). These directories contain the cache tiles and the tiling scheme file conf.xml. The cache directories may also contain a file geodatabase, status.gdb, which contains information about what tiles have been built. When you restore the site, move or copy the information back to the original arcgiscache directory.
- Data sources for nonhosted web services—For file-based data sources, you need to make backup copies of those files. For data stored in a database, use the tools of your database management system to create database backups.
- Spatiotemporal big data store backups—If you have a spatiotemporal big data store registered with your hosting server, you must manually create backups using the ArcGIS Data Store backupdatastore utility.
How often should I back up my ArcGIS Enterprise deployment?
The more frequently you create backups, the less data loss you incur if your primary deployment fails. However, it is not practical (or, often, even possible) to do continual backups. Keep the following in mind when deciding how frequently to create backups of your deployment:
- Each backup takes time to create. The amount of time it takes increases as the amount and size of your content increases. You can decrease that time by doing incremental backups between full backups.
- Backup creation is a network-intensive process and could affect network performance. It would be best to perform full backups while there is less traffic on your network, such as at night, and perform incremental backups during periods of lower traffic during the day, such as during staff's lunch hour.
- Even though backup files are compressed, they still take storage space. You have to maintain enough space in your secure backup location to store your backup files.
How long should I keep backup files?
Deciding how long to keep backup files depends on the amount of free disk space you have and how much flexibility you require for recovery options. If you won't need to restore to a time before the last full backup, you can keep the last full backup and the incremental backups created since then. Incremental backups created with the webgisdr tool are cumulative; you can apply the most recent incremental backup to the last full backup. Therefore, at minimum, you need to retain the last full backup and the most recent incremental backup created since that full backup.
You could also move a few sets of older backups to another location, such as storage media. That way, if you discover that key data and services were deleted prior to the last full backup, you'll still have the files available.