ArcGIS Data Store 10.5 makes it easier to configure and manage each type of data store. It includes an expanded configuration wizard, the ability to backup and restore all data store types, safeguards against data loss due to insufficient disk space, and improvements to several utilities.
Configure specific data store types
Different data store types serve different purposes. You configure different types of data stores depending on the functionality you need and the clients you will use. The Data Store Configuration wizard has changed at 10.5 to make this process simpler and more apparent. Now you specify which type of data store to create and register with your GIS Server site. You can choose to configure a relational, tile cache, or spatiotemporal big data store.
In previous releases, the wizard always configured both a relational and tile cache data store, and it could not be used to create a spatiotemporal big data store.
Backup and restore all types of data stores
Automatic and manual backups are now possible for all data store types. Use the new configurebackuplocation utility to configure a shared network location for each data store. You must configure a shared network location for spatiotemporal big data store backups using the register operation of the configurebackuplocation utility. Use the configurebackuplocation utility with the change operation to specify a shared network location for tile cache and relational data store backups.
Once you've set a backup location, you can use the backupdatastore utility to create a manual backup of relational, tile cache, or spatiotemporal big data stores. When run on a relational data store, the backupdatastore utility creates a full backup.
As with previous releases, automatic backups are created for relational data stores by default. For tile cache and spatiotemporal big data stores, you can now run the updatebackupschedule utility to set a backup schedule after you've set a shared network backup location for these data stores.
The first spatiotemporal big data store backup created manually or automatically is a full backup. Since spatiotemporal big data stores can be very large, subsequent backups create a backup file containing only the changes since the initial full backup.
Similarly, the first time a manual or automatic backup is created for a tile cache data store, backup copies are made of all existing tile cache data store databases. Subsequent manual or automatic backups create backup copies of any tile cache data store databases created since the last time a backup was created.
The restoredatastore utility has also been expanded to allow you to restore any data store type for which you have backup files.
Read-only mode for relational data stores
If the machine on which you created your relational data store runs out of disk space, the data store becomes unusable and you can lose data. This is more likely to happen if you do not follow the recommended practice of configuring relational data store automatic backups to be created in a remote, shared directory, but can happen if your data store grows very large or you created the relational data store on a machine with little free disk space.
To prevent the loss of data, the primary relational data store is placed in read-only mode when the disk space of the machine on which it is running drops below a specific size. By default, that size is 1024 MB, but you can change this using the changedbproperties utility with the disk-threshold-readonly operation. Once in read-only mode, clients will not be able to complete operations—such as publishing hosted feature layers—that would result in data being copied to the relational data store.
Prior to its being placed in read-only mode, warnings appear in the log files of the hosting server indicating that relational data store disk space is getting low. By default, these messages begin appearing in the logs when the primary relational data store machine reaches 10 GB of remaining space. ArcGIS Data Store checks the disk size every hour; consequently, messages are logged hourly.
When the remaining disk space drops below 1024 MB or the size you specified using the changedbproperties utility, the relational data store is placed in read-only mode.
Once you have added disk space to the primary data store machine, run the changedatastoremode utility to set the relational data store back to read-write mode, and run the updatebackupschedule utility to re-establish automatic backups for the relational data store.
You can also use the changedatastoremode utility to place the primary relational data store in read-only mode while you perform maintenance tasks on the machine.
The describedatastore utility returns an additional line of information when run on the primary relational data store machine to indicate whether the data store is in read-only or read/write mode.
Disk space monitoring for tile cache and spatiotemporal big data stores
ArcGIS Data Store also monitors the remaining disk space on tile cache and spatiotemporal big data store machines. When remaining disk space drops below 10 GB, warnings are logged to let you know you need to add disk space. Once the disk space on the data store drops below 1024 MB, the data store shuts down to avoid data loss.
Once you have added disk space to the data store machine, you can either restart the ArcGIS Data Store service on that machine (if there is only one type of data store installed on the machine), or sign in to the ArcGIS Server Administrator Directory for the hosting server and use the start REST function to restart the tile cache or spatiotemporal big data store machine.
Changes to ArcGIS Data Store command utilities
Most of the changes made to command utilities were done to improve administration of all three types of data stores.
As part of the improvements to clarify and simplify administration of different data store types, new options were added to the unregisterdatastore and removemachine utilities to allow you to specify which type of data store you want to unregister or remove. This is useful if you have more than one type of data store installed on the same machine—you can unregister, for example, the tile cache data store without unregistering the relational data store. Similarly, you can remove one spatiotemporal big data store machine without affecting any other data stores.
Since you can now create a backup of all data store types, the listbackups utility can return information on backups made for each type of data store.
The output from the describedatastore utility has been expanded and modified to better represent information for each type of data store.
The listmanageduser utility now returns the user name and password for the data owner for all three types of data stores.
The following changes have been made to the changedbproperties utility:
- You can now specify which data store type to configure when you run the changedbproperties utility.
- The disk-threshold-readonly operation was added to allow you to control when your relational data store machine is placed in read-only mode due to disk space size constraints.
- Two options specific to spatiotemporal big data stores were renamed: the reallocation option is now rebalance and the max-allocation-off option is now max-rebalance-off. These new names more accurately reflect the action the spatiotemporal big data store is taking when these properties are set.
- The default value for max-rebalance-off is 30 minutes instead of 60 minutes.
The new changedatastoremode utility allows you to place a relational data store in a read-only state and put it back in a read-write state when you are ready to allow clients to write data to, or edit data in, the relational data store again.
The changebackuplocation utility has been deprecated. Although the changebackuplocation utility is still present to allow existing scripts to function, you should now use the configurebackuplocation utility instead.