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.
You can also keep backups 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 both housed in a building that lost power), you still have a backup you can restore.
Backup modes
You can create different types of backups with the webgisdr utility using the following backup modes:
Backup
Introduced at 10.9, the backup mode is intended to back up the state of the organization, including the portal content, published services, the relational data store, and the tile cache data store if you specified it in the properties file. This also includes any data store references registered as portal items or directly through the ArcGIS Server Manager. You cannot use backup mode to back up any of your referenced data unless the data was copied to the site as part of the publishing process.
Full
The full mode works similarly to the backup mode and includes the same content. It is intended to facilitate a combined full and incremental backup schedule and remove the transaction log limit to allow for incremental backup and recovery. If you decide not to use incremental mode as part of your backup strategy, you must use backup mode instead.
Incremental
The incremental mode contains a collection of changes that occurred since the last full backup. It is especially useful in geographic replication, where shorter backup and restore times are advantageous for keeping the deployments in close synchronization. The incremental mode backup file only includes changes to the portal content, published services, data copied to the federated server sites, the relational data store, and the tile cache data store if you specified it in the properties file. If a new data store is registered with the ArcGIS Server site or an existing connecting string is updated, a backup using the full mode and a subsequent restore is required before you can continue with replication using the incremental mode.
Note:
To create or restore incremental backups, ArcGIS Data Store must be configured to automatically create backups of relational data stores.
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
- The relational data store and tile cache data store
You can create incremental backups between full backups to reduce the total backup size. See Backup modes for more information on the differences between full and incremental backups.
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.
- Referenced data sources for 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 and graph store backups—If you have a spatiotemporal big data store or graph store (or both) registered with your hosting server, create backups of each using the ArcGIS Data Store backupdatastore utility.
- Federated ArcGIS Mission Server or ArcGIS Notebook Server sites—If you have either of these, create backups by following the instructions in the ArcGIS Mission Server documentation and the ArcGIS Notebook Server documentation. To restore them using the webgisdr utility, follow the instructions in Restore ArcGIS Enterprise.
- ArcGIS GeoEvent Server site configuration—Follow the instructions in the ArcGIS GeoEvent Server documentation to create a backup of it.
Note:
To create incremental backups with the webgisdr utility, you must enable point-in-time recovery, or the utility will fail.
Also note that the webgisdr utility must have access to at least one of the machines in each federated server site through the ArcGIS Server Administrator Directory URL and the primary data store to succeed. To determine whether the URL is accessible, open the ArcGIS Server Administrator Directory from a browser on the machine where you will run the webgisdr utility.
Since 10.4, the list of items and settings that must be identical across your source and target deployments when running the webgisdr utility has been shortened. The following table summarizes these changes across recent versions of Portal for ArcGIS and ArcGIS Server:
Must this item or setting be identical across deployments when running the webgisdr utility?
| Item or setting | 10.4.x | 10.5.x, 10.6 | 10.6.1 and later |
|---|---|---|---|
Public portal URLs | Yes | Yes | Yes |
Services URL for federated servers | Yes | Yes | Yes |
Registered data stores other than ArcGIS Data Store | Yes | Yes | Yes |
Account credentials for the ...webgisdr.properties file | Yes | Yes | Yes |
ArcGIS Server directory paths (for example, arcgisjobs) | Yes | Yes | No |
Security information (LDAP URLs, proxy information) | Yes | Yes | No |
Deployment type (single machine or highly available) | Yes | No | No |
Private portal URL | Yes | No | No |
Admin URL for federated servers | Yes | No | No |
Machine names | Yes | No | No |
Portal content directory storage type | Yes | Yes | Yes |
Portal content directory path (if using the file system) | No | No | No |
Portal content directory credentials (if using cloud storage) | No | No | No |
ArcGIS Server configuration store | No | No | No |
Networking requirements
For the webgisdr utility to function, it needs access to specific URLs that are part of your deployment and connect directly to the component that is being backed up. Depending on your configuration, they may not match the URLs used to configure the ArcGIS Enterprise deployment, such as the privatePortalURL property in the portal, or the URLs used to federate the portal and server. The URLs are as follows:
- The 7443 endpoint of the portal machine or machines if the deployment is highly available. If your portal is running on a machine named portal.domain.com, the webgisdr utility must be able to reach https://portal.domain.com:7443/arcgis.
- The 6443 endpoint of at least one ArcGIS Server machine in each federated server site. If ArcGIS Server is running on a machine named server.domain.com, the webgisdr utility must be able to reach https://server.domain.com:6443/arcgis. This also applies to any other machine that's part of that site.
- The 2443 endpoint of any ArcGIS Data Store machine registered to the hosting server site. If ArcGIS Data Store is running on a machine named datastore.domain.com, the webgisdr utility must be able to reach https://datastore.domain.com:2443/arcgis.
How often to back up an 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 can affect network performance. It is recommended that you 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 the staff's lunch hour. You can run the webgisdr tool as a cron job within a Linux environment. Additionally, the tool can be moved to and run from a different machine than the portal installation, as long as communication is open between the machine where the tool is run and the ArcGIS Enterprise components.
- 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 to 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 can 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.
Note:
The webgisdr utility records the software versions of the ArcGIS Enterprise components when you create a backup. The deployment to which you restore must be at the same version it was when you created the backup. Additionally, you must restore to the same type of operating system. For example, you cannot create a backup of an ArcGIS Enterprise deployment on Linux and restore it to Windows machines.