Syntax

allowconnection <host name> <username> [<database>]

Specify the name of the computer you want to allow to connect to the relational data store (host name) and one of the database accounts used by the data store (username): either the data store administrator, replica owner, geodatabase administrator, or managed user (the user who publishes feature layer data), which you can obtain using the listadminusers or listmanageduser utility. You can also specify the name of the primary relational data store database but, since there is only one, this value is optional.

Example

In this example, a connection is allowed from the workcom computer to the relational data store when connecting as the hqo.n_1E7 managed user.

allowconnection workcom hqo.n_1E7

Syntax

backupdatastore [<backup file name>] [--store {relational | tileCache | spatiotemporal | graph}] [--location <backup_arguments>] [--prompt {yes | no}]

Arguments for the --location parameter are as follows and must be separated with semicolons (;):

• type=—Valid types are fs (file share), s3 (Amazon Simple Storage Service (S3) bucket), or azure (Microsoft Azure Blob storage container). You can only use file shares for graph store backups.
• name=—If you assigned names to the backup locations you configured for your data store, you can use the location name to specify where you want backup files created when running the backupdatastore utility.
• location=—If you do not specify a backup location name, you must specify the backup type and location. For file shares, provide the file path. For S3 buckets, provide the bucket name. For Azure Blob storage containers, provide the container name.

Examples

In this example, a full backup file named project1bu is created in the backup location you specified for the data store using the configurebackuplocation utility. By default, backups are created for relational data stores; therefore, in the following example, a relational data store backup is created.

backupdatastore project1bu

You are going to back up the data store. This could take some time, depending on the size of your data store.
Please do not interrupt the process once it has started.

Do you want to continue (Yes or No)?Yes

In this example, a backup file named localbu5 is created for the spatiotemporal big data store in a file share location, which you named gadbu when you configured the backup location.

backupdatastore localbu5 --store spatiotemporal --location name=gadbu

You are going to back up the data store. This could take some time, depending on the size of your data store.
Please do not interrupt the process once it has started.

Do you want to continue (Yes or No)?Yes

In this example, a backup is created of a spatiotemporal big data store in an Azure Blob storage container named blob4backups, and the backup file created is named spds311016:

backupdatastore spds311016 --store spatiotemporal --location type=azure;location=blob4backups

You are going to back up the data store. This could take some time, depending on the size of your data store.
Please do not interrupt the process once it has started.

Do you want to continue (Yes or No)?Yes

Syntax

changedatastoremode {readonly | readwrite} [--prompt {yes | no}] --store {relational | spatiotemporal}

Examples

In this example, the relational data store is placed back in read-write mode, meaning clients can resume such activities as publishing hosted feature layers to ArcGIS Enterprise, editing data through a hosted feature layer, or adding CSV files to a map viewer.

changedatastoremode readwrite --store relational --prompt no

To place a spatiotemporal big data store in read-write mode, specify spatiotemporal with the --store option as shown in the following example:

changedatastoremode readwrite --prompt no --store spatiotemporal

Syntax

changedbproperties --store {relational | tileCache | spatiotemporal} [configuration options]

The following are supported configuration options:

• disk-threshold-readonly—Used with the relational data store only.

  This setting controls when a relational data store will be placed in read-only mode to avoid loss of data due to insufficient disk space. Specify sizes in MB. The default disk space value is 1024 MB.

• max-connections—Used with the relational data store only.

  Use this parameter to specify the maximum number of connections allowed to a relational data store. Relational data stores accept up to 150 connections by default. You can use the --max-connections property with the changedbproperties utility to change the number of connections allowed.

  When determining how many connections your data store requires, take into consideration that ArcGIS Data Store internal processes can take up to five connections. Also consider how many concurrent connections your ArcGIS Data Store machine can accept and continue to perform well. If the machine running ArcGIS Data Store doesn't have a lot of memory, you may need to decrease the number of connections allowed.

  The number specified cannot be less than 10. When you change the maximum number of connections allowed, the number is changed on both the primary and standby data store machines. This parameter is not supported for spatiotemporal big data stores or tile cache data stores.

• pitr—Used with the relational data store only.

  This setting indicates whether ArcGIS Data Store creates incremental backups of the relational data store, thereby allowing you to recover the relational data store to a point in time. Possible inputs for this option are enable or disable. Point-in-time recovery is disabled by default.

  Note:

  You must enable point-in-time recovery if you will use the webgisdr utility to create incremental backups of your ArcGIS Enterprise deployment.

• enablessl—Used with the relational and tile cache data stores only.

  This parameter controls use of the Transport Layer Security (TLS) protocol when populating the tile cache data store and for communication between the relational data store and the hosting server.

  Supported options for the enablessl parameter are as follows:

  • true—This is the default option. This means that the Transport Layer Security protocol will be used when writing scene layer data to the tile cache data store when you specify --store tileCache and when communicating between the relational data store and hosting server when you specify --store relational.
  • false—Specify false and --store tileCache to use HTTP communication from the hosting server when writing to the tile cache data store. Specify false and --store relational to use HTTP communication between the hosting server and relational data store.
• heap-size—Used with the spatiotemporal big data store only.

  Use this parameter to change the amount of heap memory (in MB) used by a spatiotemporal big data store. By default, this type of data store will use half the RAM on the machine (up to 70 percent of free RAM) when it starts. You can change the heap size to an amount between 512 MB and 32,000 MB, but be sure the amount you specify does not exceed the amount available on the machine.

• rebalance—Used with the spatiotemporal big data store only.

  By default, this parameter is set to true, which means data in a spatiotemporal big data store will distribute data to other machines if any one machine is unavailable. If you need to perform maintenance on one spatiotemporal big data store machine, such as upgrading it, you can temporarily shut off rebalancing by setting this parameter to false. The rebalance operation will be suspended for the number of minutes set for the max-rebalance-off parameter.

• max-rebalance-off—Used with the spatiotemporal big data store only.

  The setting for this parameter is used when you set the rebalance parameter to false. By default, max-rebalance-off is set to 60 minutes. That means if you temporarily shut off rebalancing, it will start again after 60 minutes. If you need more or less time than that to perform the maintenance task for which you suspended rebalancing, change the time setting for max-rebalance-off.

• prompt—When you run this utility, you are prompted to confirm the action you specified. If you automate the use of this utility, set the prompt parameter to false; otherwise, the script will not proceed until you answer the prompt.

Examples

The following sections include examples of using the options available with the changedbproperties utility.

changedbproperties --store relational --disk-threshold-readonly 4000

You are changing the following database properties:
         ...disk space threshold to change relational data store into READONLY mode to 4000MB)

Changing database configurations could cause the database to restart. Please do not interrupt the process once it has started.

Do you want to continue (Yes or No)?Yes

changedbproperties --store relational --max-connections 100

You are changing the following database properties:
         ...max number of connections to 100 (on all relational data store machines)

Changing database configurations could cause the database to restart. Please do not interrupt the process once it has started.

Do you want to continue (Yes or No)?Yes

changedbproperties --store relational --pitr enable

You are changing the following database properties:
         ...enable point-in-time recovery for relational store

Changing database configurations could cause the database to restart. Please do not interrupt the process once it has started.

Do you want to continue (Yes or No)?Yes

changedbproperties --store relational --enablessl false

You are changing the following database properties:
         ...disable ssl for relational store

Changing database configurations could cause the database to restart. Please do not interrupt the process once it has started.

Do you want to continue (Yes or No)?Yes

changedbproperties --store spatiotemporal --heap-size 1600

You are changing the following database properties:
         ...heap size for spatiotemporal store to 1600MB (on current machine)

Changing database configurations could cause the database to restart. Please do not interrupt the process once it has started.

Do you want to continue (Yes or No)?Yes

changedbproperties --store spatiotemporal --rebalance false --prompt false
changedbproperties --store spatiotemporal --max-rebalance-off 30 --prompt false

Syntax

changeloglocation <directory path>

Example

In this example, log files will be created in the local directory, d:\datastorefiles\logs.

changeloglocation 'd:\datastorefiles\logs'

Syntax

changenosqldslocation <path> [--prompt {yes | no}]

Example

In this example, the databases that store scene layer caches will be created in a shared directory named dstorecache on machine server2.

changenosqldslocation \\server2\dstorecache

Syntax

changepassword <username> <new password> [--prompt {yes | no}]

Example

In this example, the password is changed for user gwi_n2Te0 to Phfl4mp!.

changepassword gwi_n2Te0 Phfl4mp

You are going to change the password for user gwi_n2Te0.
Do you want to continue (Yes or No)?Yes

Syntax

changestaginglocation <directory path>

Example

In this example, the designated staging location is \\netserver\rbustage.

changestaginglocation \\netserver\rbustage

Syntax

configurebackuplocation --location <backup_location_arguments> [options]

Use the --location option to specify where you want ArcGIS Data Store to store backup files. For tile cache data stores or spatiotemporal big data stores or to register a secondary backup location for a relational data store, specify the following arguments separated by a semicolon (;): --location type=fs|s3|azure;location=<backup_location>;[name=<backup_location_name>];[username=<AWS_access_key_ID_or_Azure_account>];[password=<AWS_secret_access_key_or_Azure_account_key>]. An explanation of each of these arguments is provided in the following list:

• type=—Specify what type of location to use for backups. You can specify s3 to store backups in an Amazon S3 bucket, azure to store backups in an Azure Blob storage container, or fs to store backups in a file share (this is the default).
• location=—For file shares, specify the file path. For Amazon S3 buckets, specify the bucket name. For Blob storage containers, specify the container name.
• name=—You can assign a name to the backup location. For example, if your backup location is a file path, such as \\sharedserver_sharedfolders_datastorebackups, you can designate a name for this location, such as dsbackups. When you run the backupdatastore, listbackups, or restoredatastore utility, provide this name instead of the full path.

  If you do not provide a name when you configure the data store backup location, ArcGIS Data Store assigns a default name.

• username=—Required if your backup location is an S3 bucket or a Blob storage container. For S3 buckets, provide the access key ID for your Amazon Web Services (AWS) account. For Azure Blob storage containers, provide the name for the Microsoft Azure storage account that can access the Blob storage container.
• password=—Required if your backup location is an S3 bucket or a Blob storage container. For S3 buckets, provide the secret key for your AWS account. For Azure Blob storage containers, provide the key for the Azure account you specified with the username argument.
• endpointsuffix=—This option allows you to indicate where your Azure Blob storage container is located. By default, the is endpointsuffix assumed to be core.windows.net. If your container is in the Microsoft Azure Government cloud environment, set endpointsuffix=core.usgovcloudapi.net. If your container is in a private cloud, set endpointsuffix to the EndpointSuffix of your Azure private cloud. This option is only used if you store your backups in an Azure Blob storage container.

Additional options you must provide with the configurebackuplocation utility are as follows:

• --store {relational | tileCache | spatiotemporal | graph}—Specify the type of ArcGIS Data Store for which you're configuring a backup location. The default value is relational.
• --operation {change | register | unregister | list | setdefault}—The default value is change. The following is an explanation of each option:
  • change—Use this option to change any of the following:
    • Specify a different shared file location for scheduled relational data store backups. The location set with the change option is always the default backup location for relational data stores.
    • Alter the name you assigned to the backup location.
    • Update the authentication information you set for backup locations on Azure or S3. For S3, you can change the information you previously specified with the username and password options. For Azure, you can change the password value.
  • register—Use this option to register a backup location. The first backup location you define for a spatiotemporal big data store or graph store is set as the default backup location. When you register another backup location for a tile cache or spatiotemporal big data store or a graph store, a secondary backup location is registered.

    When you specify the register option with a relational data store, it always registers a secondary backup location. The secondary backup location stores manual backups generated with the backupdatastore utility.

    Note:

    When you use the register option, you must provide information for the --location option.

  • unregister—Use this option to remove a secondary backup location from a data store. If only one backup location is registered, you can use the unregister option to completely remove the backup location for a tile cache or spatiotemporal big data store or a graph store.
  • list—Lists all backup locations registered for a data store.
  • setdefault—If you have multiple backup locations for a tile cache or spatiotemporal big data store, you can use setdefault to designate one of the backup locations as the default location. This location is where scheduled backups are written and is the default location used if you run the backupdatastore, listbackups, or restoredatastore utility without specifying a backup location.
• --force {true | false}—Used only with relational data stores, this option allows you to change the default backup location even if the existing default backup location is unavailable.

  When you change the default backup location for a relational data store, ArcGIS Data Store copies the existing backup files from the old location to the new location. If ArcGIS Data Store cannot access the old location, it cannot copy the files. In previous releases, this would cause the configurebackuplocation tool to fail. If you want to proceed with changing the default backup location without copying existing backup files, specify --force true.

  The default value for this option is false, which means you cannot change the default backup location if ArcGIS Data Store cannot access the existing default location.

• --prompt {yes | no}—The default value is yes.

Examples

The following sections provide examples of changing, setting, or listing backup locations for data stores.

configurebackuplocation --operation change --store relational --location \\myshare\fsdata_bu 

You are going to change the backup location of the data store. Existing backups will be copied to the new location and it could take a few moments.
Please do not interrupt the process once it has started.

Do you want to continue (Yes or No)? Yes

configurebackuplocation --operation register --store relational --location type=azure;location=mybackups;name=secondrelloc;username=myazureaccountlogin;password=zpw4myazureaccount 

You are going to change the backup location of the data store. Existing backups will be copied to the new location and it could take a few moments.
Please do not interrupt the process once it has started.

Do you want to continue (Yes or No)? Yes

configurebackuplocation --operation register --store graph 
--location type=fs;location=\\sharedmachine\g_bu;name=fshare

configurebackuplocation --operation register --store spatiotemporal --location type=azure;location=myblobs;name=mazloc;username=myazureaccountlogin;password=zpw4myazureaccount

configurebackuplocation --operation register --store spatiotemporal 
--location type=s3;location=mybucket;name=awsloc;username=abcdefg1234567;password=z9y8x7w6v5u4t3s2r1q0

configurebackuplocation --operation setdefault --store spatiotemporal --location name=awsloc

configurebackuplocation --operation list --store spatiotemporal
Backup locations for spatiotemporal big data store:
================================================================
Name             Type     Location                     isDefault
================================================================
fsshare          fs       \\sharedmachine\ge_bu        false
awsloc           s3       mybucket                     true
mazloc           azure    myblobs                      false

Syntax

configuredatastore <ArcGIS Server admin URL> <ArcGIS Server administrator> <ArcGIS Server administrator password> <data directory> [--stores {relational | tileCache | spatiotemporal | graph | object}] [--mode {primaryStandby | cluster}] [--machines <machine names>]

• <ArcGIS Server admin URL>—This is the GIS Server site that is used or will be used as the ArcGIS Enterprise hosting server. The ArcGIS Server admin URL is in the format https://gisserver.domain.com:6443. Note that even if your GIS Server site uses a web adaptor or load balancer, you must provide the URL in the aforementioned format.
• <ArcGIS Server administrator>—Provide the username for a built-in (not organization-specific) user who has administrator privileges in the GIS Server site.
• <ArcGIS Server administrator password>—Provide the password for the account used above.
• <data directory>—The data directory is the location on the local machine where you want the data store files to be created.
• {relational | tileCache | spatiotemporal | graph | object}—Specify the type of data store to create. Though it is not recommended, you can configure more than one type of data store on the same machine by specifying each store type separated by a comma (no spaces). For example, to configure both relational and tile cache data stores on the same machine with a shared data store directory, specify --stores relational,tileCache. Esri strongly recommends that you run spatiotemporal big data stores and graph stores on machines separate from other data stores or software. Failing to do so can result in poor performance, or even render the data store unusable.
• --mode—This optional operation applies to tile cache data stores and object stores only. By default, tile cache data stores and object stores are created in primaryStandby mode.

  Tile cache data stores created in primaryStandby mode can contain two machines. The standby tile cache data store contains the same data as the primary. If the primary data store fails, the standby becomes the primary tile cache data store. If you need to store large numbers of scene layer caches and, therefore, you need your tile cache data store to scale to include three or more machines, create a tile cache data store in the cluster mode. You can use the mode operation to switch the tile cache data store from primaryStandby mode to cluster mode.

  Object stores created in primaryStandby mode can contain only one machine currently. If you need multiple machines in the object store to provide high availability, you can deploy the object store in cluster mode. When used in cluster mode, the object store must contain at least three machines. See Add machines to a data store for details.

Examples

In this example, a data store for hosted feature layer data (relational data store) is created. The URL for the GIS Server site that will use the data store is https://gisserver.domain.com:6443, the site administrator username and password are admin and Iph33l$ik, respectively, and the data directory for the data store is C:\datastore\data\.

configuredatastore https://gisserver.mydomain.com:6443 admin Iph33l$ik c:\datastore\data\ --stores relational

In the following example, an existing tile cache data store (primary-standby) is changed to cluster mode:

configuredatastore https://gisserver.mydomain.com:6443 portaladmin S00perSecret c:\datastore\scenedata\ --stores tileCache --mode cluster

Syntax

configureserviceaccount [--username <Windows account>] [--password <account password>] [--readconfig <user configuration file>] [--writeconfig <user configuration file>]

Example

In this example, configureserviceaccount sets the mynetwork\datastore account to run the ArcGIS Data Store service and grants this account the privileges required on ArcGIS Data Store system folders and files.

configureserviceaccount --username mynetwork\datastore --password SewL0ng

In this example, a group managed service account is used for the ArcGIS Data Store account:

configureserviceaccount --username mydomain\datastore-gmsa$ --writeconfig c:\temp\domainaccountconfig.xml

Note that changing the account under which the service runs causes the service to restart.

In this example, the ArcGIS Data Store account is changed, and the account information is written to a file (adsainfo) at C:\adminfiles.

configureserviceaccount --username mynetwork\datastore --password SewL0ng --writeconfig C:\adminfiles\adsainfo.xml

In this example, ArcGIS Data Store is installed on a different machine, and the administrator runs the configureserviceaccount utility to set the same account using the file created in the previous example.

configureserviceaccount --readconfig C:\adminfiles\adsainfo

Syntax

deletebackup <backup name> [--prompt {yes | no}]

Example

deletebackup featuresMarchbu
You are attempting to delete backup 'featuresMarchbu'. This operation is irreversible.

Do you wish to continue (Yes or No)?yes

Operation completed successfully

Syntax

describedatastore

Example

The describedatastore utility returns general information that applies to all data stores on a machine and returns separate sections that contain information specific to each type of data store.

You should have different data stores on different machines, but to allow you to see the information returned for each type, the following output shows a machine that has all ArcGIS Data Store types on the same machine. The first section (General Information) is always returned. The data store sections returned by describedatastore vary depending on what type of data store is present on the machine.

describedatastore

General Information of ArcGIS Data Store on machine.domain.com
==============================================================
ArcGIS Data Store release....11.0.0.1234
Staging location.............C:\arcgisdatastore\staging
Log location.................C:\arcgisdatastore\logs
Free disk space..............174.00GB
Threshold for READONLY mode..2048MB

Information for relational data store ds_sthiu0_5T
==============================================================
Backup location...........\\nwshare\dsbackups
Is backup folder shared...true
Backup schedule...........{"schedule-starttime":"00:00:00","schedule-frequency":"Every 7 DAYS"}
Days backup retained......31
Data store status.........Started
SSL enabled...............true
Last failover.............20150130190334005
Member machines...........MACHINE1.DOMAIN.COM, MACHINE4.DOMAIN.COM
Maximum connections.......150
Owning system URL.........https://gisserver_webadaptor.domain.com/server
Portal for ArcGIS URL.....https://portal_webadaptor.domain.com/portal
Number of connections.....8 connection(s) to managed database
Data Store mode.....................READWRITE
Is Point-in-time recovery enabled...No
Query optimizer enabled.............Yes

Information for tile cache data store ds_wztxj7um
==============================================================
Data location.......................C:\arcgisdatastore\nosqldata
Data store status...................Started
Backup location............\\mybackups\scenebackup
Backup schedule............{schedule-frequency":"Every 1 DAYS"}
Is backup folder shared.............true
Mode................................cluster
Member tile cache machines.....................MACHINE1.DOMAIN.COM, MACHINE2.DOMAIN.COM, MACHINE3.DOMAIN.COM
Registered tile cache machines.................MACHINE1.DOMAIN.COM, MACHINE2.DOMAIN.COM, MACHINE3.DOMAIN.COM
Owning system URL...................https://gisserver_webadaptor.domain.com/server
Portal for ArcGIS URL...............https://portal_webadaptor.domain.com/portal

Information for spatiotemporal data store ds_qpko99Cl
==============================================================
Max rebalance off time..............60 minutes
Automatic rebalance ................On
Machines in spatiotemporal cluster..MACHINE1.DOMAIN.COM, MACHINE2.DOMAIN.COM, MACHINE3.DOMAIN.COM
Current coordinator in cluster...MACHINE1.DOMAIN.COM
Registered spatiotemporal machines..MACHINE1.DOMAIN.COM, MACHINE2.DOMAIN.COM, MACHINE3.DOMAIN.COM
Owning system URL...................https://gisserver_webadaptor.domain.com/server
Portal for ArcGIS URL...............https://portal_webadaptor.domain.com/portal
Data Store mode.....................READWRITE

Information for graph store x2b7s0n
==============================================================
Deployment mode................................singleInstance
Access endpoint................................MACHINE1:9829
Registered graph store machines................MACHINE1.DOMAIN.COM
Owning system URL...................https://gisserver_webadaptor.domain.com/server
Portal for ArcGIS URL...............https://portal_webadaptor.domain.com/portal

Information for object store w1tiknx
==============================================================
Deployment mode................................primaryStandby
Access endpoint................................MACHINE1:9900
Registered object store machines...............MACHINE1.DOMAIN.COM
Owning system URL...................https://gisserver.domain.com:6443/server/admin
Portal for ArcGIS URL...............https://portal_webadaptor.domain.com/portal

Syntax

diskcleanup

Example

To run the diskcleanup utility, you must confirm that you want to proceed.

diskcleanup

You are attempting to cleanup some archived data generated as part of ArcGIS Data Store upgrades or backup-restore operations. Once removed, this data can't be recovered. Do you want to continue (Yes or No)?

Syntax

listadminusers

Examples

In this example, listadminusers is run on a machine where only a relational data store is installed.

listadminusers

Admin users for relational data store ds_abcd1234
=================================================
Database Admin User.... adm_32ret / tT30sbYk22jF
Database Repl User..... dsrepuser / uWn/MV0678h4
GDB Admin User......... sde / iO=Qst751epb

In this example, listadminusers is run on a machine where only a spatiotemporal big data store is installed.

listadminusers

Admin users for spatiotemporal big data store bds_abcd1234
=================================================
Store admin user.... els_321ret / B1as70fF1

In this example, listadminusers is run on a machine where only a graph store is installed.

listadminusers

Admin users for graph store s2t0ic1
=================================================
Store admin user....root / ypz5kx2c5tk4fequ

In this example, listadminusers is run on a machine where only an object store is installed.

listadminusers

Admin users for object store w1tiknx
=================================================
Store admin user....n6o96nl53vzkm36d / bpvifyjz73xwhot4

Syntax

listbackups [--store {relational | tileCache | spatiotemporal | graph}] [--location <location_arguments>]

If you do not specify a data store type, the utility defaults to relational and returns the backups for the relational data store running on that machine.

The location parameter is used with spatiotemporal big data stores and relational data stores. Arguments are as follows:

• name=: The name of the backup location. You specified this name when you configured the backup location or, if you didn't specify a name, ArcGIS Data Store assigned a default name.
• location=: Either the path to the shared file directory, S3 bucket name, or Blob storage container name.

Examples

In this example, backups are listed for a relational data store:

listbackups --store relational

Backup_Name                  Status           Backup_Time         Mode
==========================================================================
phase1proj_bu               BackupComplete   2014-03-08 14:12    manual
phase2proj_bu               BackupComplete   2014-06-21 11:43    manual
ds_gdt1oomh-201411030300    BackupComplete   2014-11-01 03:00    scheduled

Backups located at: '\\myserver.net.com\dsbackups'

In this example, spatiotemporal big data store backups are listed for the backup location named sbdsbu:

listbackups --store spatiotemporal --location name=sbdsbu

Backup_Name                 Status           Backup_Time         Mode
=======================================================================
backup1						               BackupComplete   2016-07-11 09:47    manual

Backups located at: '\\myserver.net.com\spatiotemporal'

Syntax

listdatasources

Example

Run the listdatasources utility at a command prompt to return a list of GeoEvent Server map services.

listdatasources

Syntax

listmanageduser

Examples

In the following example, listmanageduser is run on a machine that contains a relational and tile cache data store. The machine is the primary relational data store.

listmanageduser

Managed user for relational data store ds_abcd1234
===================================================
UserName     Password       Database
gwi_n2Te0    4cXddhZhve=Y   db_qv5e1

Managed user for tile cache data store tcs_e41f0rj2
===================================================
UserName     Password
usr_n8778    y47ccno913

In this example, listmanageduser is run on a spatiotemporal big data store machine.

listmanageduser

Managed user for spatiotemporal big data store bds_6udbx4321
=============================================================
UserName     Password
fmr_o1He3    5vZggkPbaw+T

In the following example, listmanageduser is run on a graph store machine.

listmanageduser

Managed user for graph store s2t0ic1 
================================================ 
UserName   Password 
mu_vwmp8c6 m5c2so76y3b0qczf

In the following example, listmanageduser is run on an object store machine.

listmanageduser

Managed user for object store w1tiknx
=============================================================
Store credential........n6o96nl53vzkm36d / bpvifyjz73xwhot4

Syntax

registerdatastore <ArcGIS Server URL> <ArcGIS Server site administrator username> <ArcGIS Server site administrator password> --stores {relational | tileCache | spatiotemporal | graph | object}

Though not recommended, if you have multiple different types of data stores installed on the same machine, you can register them at the same time by specifying the data store type separated by a comma (no spaces); for example, type --stores relational,tileCache.

Example

In this example, a relational data store is reregistered to a GIS Server site with the URL https://gisserver.domain.com:6443. The ArcGIS Server primary site administrator username is agsadmin with the password Tan$p0n.

registerdatastore https://gisserver.domain.com:6443 agsadmin Tan$p0n --stores relational

Syntax

removemachine <machine name> --store {relational | tileCache | spatiotemporal} [--force {true | false}] [--prompt {yes | no}]

--force—By default, this is set to false. Specify true with this option only if the registered ArcGIS Server site is unavailable.

--prompt—By default, this is set to yes. If you do not want to confirm the action, specify no with this option.

Examples

In this example, the spatiotemporal big data store machine, gefour, is removed from the data store.

removemachine gefour --store spatiotemporal

In this example, the hosting server site is unavailable and the relational data store machine, fsdata, is removed from the data store.

removemachine fsdata --store relational --force true

Syntax

restoredatastore [options]

Supported options are as follows:

• [--store {relational | tileCache | spatiotemporal | graph}]—Indicates the type of data store you want to restore.
• [--target {most-recent | <yyy-mm-dd-hh:mm:ss> | <name of backup file>}]—All data store types support the backup file name with the target option. A time stamp and most-recent are only supported for relational data stores.
• [--source-loc <parent directory of the source backup file location>]—This is the top-level directory where the backup files you want to use to restore the data store are located. This will be the path to a file share location, a backup location name, or an Amazon S3 or Azure Blob storage backup location. Only file share locations are supported for graph stores.

  Tip:

  You can run the describedatastore utility to obtain the backup source location. If you cannot run describedatastore—for example, if the data store machine crashed and you are restoring to a new machine to recover the data store—you can identify the correct backup source location by the presence of a file named agsds_backup_sig.

• [--bound {true | false}]—The --bound option is only supported with relational data stores.
• [--data-dir <new data store directory>]—This is the ArcGIS Data Store directory on the machine where you are restoring the database. Only use --data-dir if you are restoring the data store to a new machine. When restoring to a new machine, you must also specify the --source-loc option.
• [--server-url <ArcGIS Server URL registered with data store>]—If you specify --bound true to keep the data store registered with the same GIS Server site it was registered with when you created the backup, specify the URL of that GIS Server site. If you specify --bound true and have moved your services to a new GIS Server site, use the --server-url option to specify the URL of the new GIS Server site. Note that if you specify a new site URL and have not moved the services to this new server, the data in the data store will not be accessible.
• [--server-admin <username of ArcGIS Server admin>]—This option is required if you specify --bound true or do not specify the --bound option. Supply the username of the ArcGIS Server administrator.
• [--server-password <password of ArcGIS Server admin>]—This option is required if you specify --bound true or do not specify the --bound option. Supply the password for the ArcGIS Server administrator.
• [--loaddata {true | false}]—Supported with tile cache and spatiotemporal big data stores and graph stores. Set this option to false when you need to restore the data store to a new set of machines, but the data will not fit on the first machine. This allows you to restore the data store's schema, add more machines to the data store to accommodate all the data, and then run the restoredatastore utility again with --loaddata set to true to restore the data. By default, this option is set to true.
• [--replicatedata {true | false}]—Supported with tile cache data stores. Set this option to true when you need to rebalance scene cache data after adding a machine to the tile cache data store.
• [--mode {primaryStandby | cluster}]—When you restore a tile cache data store to a new machine, specify whether you want a two-machine tile cache data store for high availability (primaryStandby) or a scalable multimachine tile cache data store (cluster).
• [--prompt {yes | no}]

When restoring after a crash or to move the relational data store, specify --target most-recent. If restoring a relational data store to a point in time, specify the date and time (in UTC) to which you want to restore the data store. If you have a specific backup file you want to restore, specify the backup file name instead. If you do not specify a target, the most recent backup is restored.

By default, the restored data store is associated (bound) with its GIS Server site. Only specify --bound false if you want to restore the data store without maintaining the association with the data store's GIS Server site. You would only do this as a last resort if the previous GIS Server site was lost and could not be recovered; you could restore the data store unbound and configure it with a new federated GIS Server site. However, the layers that used the data in the data store would no longer exist. You would have to connect to the data store database to extract the data to another format and republish it to ArcGIS Enterprise.

Examples

In this example, the most recent backup is in a backup location named rdsbackups and will be restored to the existing data store. Because the default store type is relational, and it remains bound by default to the GIS Server site with which it was registered, you do not have to specify --store relational or --bound true. However, you do have to specify the GIS Server URL and administrator credentials.

restoredatastore --target most-recent --source-loc rdsbackups --server-url https://gisserver.domain.com:6443 
--server-admin siteadmin --server-password $Aup.4s

You are attempting to restore the data store from a data store backup. This process could take a long time, 
depending on the size of your data. Please do not interrupt the process once it has started.

Do you want to continue (Yes or No)?Yes

In this example, a relational data store that has point-in-time recovery enabled is restored from the relational data store backup location on a network share to the state it was in at 2:30 p.m. (UTC) on July 17, 2014.

restoredatastore --target 2014-07-17-14:30:00 --source-loc \\sharedserver\entbackups\relds --server-url https://gisserver.domain.com:6443 
--server-admin siteadmin --server-password $Aup.4s

You are attempting to restore the data store from a data store backup. This process could take a long time, 
depending on the size of your data. Please do not interrupt the process once it has started.

Do you want to continue (Yes or No)?Yes

In this example, the relational data store is restored to a new machine using a backup file named movedatastore. When you restore to a new machine, you must specify the location of the backup file and the location of the new ArcGIS Data Store data directory. Because the hosted feature services are still running on the same GIS Server site with which the relational data store is registered, --bound true is not required, but the GIS Server URL and administrator credentials are required.

restoredatastore --target movedatastore --source-loc \\buserver\data\backups --data-dir C:\datastore 
--server-url https://gisserver.domain.com:6443 --server-admin siteadmin --server-password $Aup.4s

You are attempting to restore the data store from a data store backup. This process could take a long time, 
depending on the size of your data. Please do not interrupt the process once it has started.

Do you want to continue (Yes or No)?Yes

In the following example, the tile cache data store is restored to a new machine. When you restore to a new machine, you must specify the location of the backup file and the location of the new ArcGIS Data Store data directory. Because the scene services are still running on the same GIS Server site with which the tile cache data store is registered, --bound true is not required, but the GIS Server URL and administrator credentials are required.

restoredatastore --store tilecache --source-loc \\buserver\scenedata\backups --data-dir C:\datastore --server-url https://gisserver.domain.com:6443 --server-admin siteadmin --server-password $SAup.4s

You are attempting to restore the data store from a data store backup. This process could take a long time, 
depending on the size of your data. Please do not interrupt the process once it has started.

Do you want to continue (Yes or No)?Yes

In this example, the tile cache data store is restored from a file named mybackupfilename to rebalance scene cache data after a new machine is added to the tile cache data store.

restoredatastore --store tilecache --target mybackupfilename --serverurl https://gisserver.domain.com:6443 --server-admin siteadmin --server-password myAdminPWd! --replicatedata true

You are attempting to restore the data store from a data store backup. This process could take a long time, 
depending on the size of your data. Please do not interrupt the process once it has started.

Do you want to continue (Yes or No)?Yes

In the following example, a spatiotemporal big data store backup file (bds1) is restored from a named backup location (awsloc).

restoredatastore --target bds1 --store spatiotemporal --source-loc name=awsloc --server-url https://gisserver.domain.com:6443 --server-admin siteadmin --server-password $Aup.4s

You are attempting to restore the data store from a data store backup. This process could take a long time, 
depending on the size of your data. Please do not interrupt the process once it has started.

Do you want to continue (Yes or No)?Yes

See Recover a data store for steps and an example of restoring a spatiotemporal big data store after hardware failure.

Syntax

revokeconnection <host name> <username> [<database>]

Example

In this example, the data store database will no longer accept connections from the workcom machine when logged in as user hqo.n_1E7.

revokeconnection workcom hqo.n_1E7

Syntax

unregisterdatastore --stores {relational | tileCache | spatiotemporal | graph | object} [--prompt {yes | no}]

If you have more than one type of data store installed on the same machine and want to unregister more than one at a time, specify each data store type separated by a comma (no spaces). For example, to unregister a relational and tile cache data store, type --stores relational,tileCache.

Example

Here, the unregisterdatastore utility is run to unregister the relational and tile cache data stores from the GIS Server site. A prompt is returned, which is the default behavior. To suppress the prompt, specify --prompt No.

unregisterdatastore --stores relational,tileCache

You are going to unregister the data store.
Do you want to continue (Yes or No)?Yes

Syntax

updatebackupretaindays <number of days>

Example

In the following example, backup file retention time is changed to 10 days:

updatebackupretaindays 10

Syntax

updatebackupschedule [--store {relational | tileCache | spatiotemporal | graph}] [--starttime <local server time>] --frequency <number of days>

If you do not specify a new start time, the existing start time setting does not change. If you do not specify a data store type, relational data store is assumed.

Examples

In this example, full backups of a relational data store will take place at 11 p.m. (local server time) every 10 days:

updatebackupschedule --starttime 23:00:00 --frequency 10

In this example, a backup schedule is set for a tile cache data store. After the initial backup copy of all tile cache data store databases, ArcGIS Data Store copies newly created data store databases to the location specified with the configurebackuplocation every 14 days.

updatebackupschedule --store tileCache --frequency 14

Syntax

updatesslcertificate <source certificate file name with path> <password for the source certificate file> <alias for the certificate>

Example

After you receive a CA-signed certificate file, run updatesslcertificate to replace the ArcGIS Data Store self-signed certificate.

updatesslcertificate C:\myfiles\mysignedcert.pfx ps4mycert dsmachinename

Syntax

upgradedatasource [<service name>]

Examples

In this example, all GeoEvent Server map service sources are upgraded:

upgradedatasource

In this example, the upgradedatasource utility will update the indexes used by the GeoEvent Server map service recon. The service name was determined using the listdatasources utility.

upgradedatasource recon