Adding and Managing Destinations › How to Manage a Data Store › Modify a Data Store

Modify a Data Store

You can modify an already existing data store, however, there are some restrictions and you cannot modify the following details of a data store:

• Compression details
• Non-deduplication data store to a deduplication data store or deduplication data store to a non-deduplication data store.
• Deduplication options: Deduplicate Data and Deduplication Block Size.

Considerations before you modify a data store:

• If you change the path of the data store or the encryption password, all jobs running in that data store, including the jobs waiting in queue are canceled. Any change in the data store name, hash memory size, or concurrent active nodes number does not impact the running jobs.
• For non-deduplication data store: To change the data store path, keep the backup destination folder empty.
• For deduplication data store: To change the data store path, keep the following folders empty:
  • Backup Destination folder
  • Data Destination
  • Index Destination
  • Hash Destination
• The Encryption Password options are editable only if you selected the Encrypt Data option while creating the data store.

Follow these steps:

1. From the Console, click the resources tab.
2. From the left pane, navigate to Destinations, and click Recovery Point Servers.

   The Destinations: Recovery Point Servers page displays the list of available recovery point servers.

3. Expand a recovery point server.

   You can see the list of data stores associated with the recovery point server.

4. Perform one of the following actions:
   • Right-click the data store name.
   • Select the data store, and from the center pane click the Actions drop-down list.
   • Select the data store, and from the right pane click the Actions drop-down list.

   A list of options is displayed.

5. Click Modify.

   The Modify a Data Store page is displayed.

6. Update the required fields and click Save.

   Data Store Name

   Defines the name of the data store.

   Recovery Point Server

   Defines the recovery point server where the data store is created. The recovery point server is already added by default.

   Backup Destination Folder

   Defines the location of the folder where the data store is created. Click Browse to select the destination folder.

   Note: For non-deduplication and deduplication data store, the backup destination path should be an empty folder.

   Enable Deduplication

   Specifies that deduplication is enabled for this data store. Arcserve UDP supports both types of deduplication: Source-side deduplication and Global deduplication. Source-side deduplication prevents duplicate data blocks to move across network from a particular agent. Global deduplication eliminates duplicate data across all client machines based on the volume cluster level.

   Deduplication Block Size

   Defines the deduplication block size. The options are 4 KB, 8 KB, 16 KB, and 32 KB. The deduplication block size also impacts the Deduplication capacity estimation. For example, if you change the default 4 KB to 8 KB, the Deduplication capacity estimations double. Increasing the deduplication block size can decrease the deduplication percentage.

   Hash Destination is on a Solid State Drive (SSD)

   Specifies if the hash folder is on a solid state drive.

   Hash Memory Allocation

   Specifies the amount of physical memory that you allocate to keep hashes. This field is pre-filled with a default value. The default value is based on the following calculation:

   If the physical memory of the RPS is smaller than 4 GB (or is identical to 4 GB), the default value of Hash Memory Allocation is identical to the physical memory of the RPS.

   If the physical memory of the RPS is greater than 4 GB, Arcserve UDP calculates the available free memory at this time. Assume that the available free memory is X GB at present. Arcserve UDP further checks the following conditions:

   • If (X * 80%) > = 4 GB, the default value of Hash Memory Allocation is (X * 80%).
   • If (X * 80%) < 4 GB, the default value of Hash Memory Allocation is 4 GB.

     Example: Consider the RPS has 32 GB of physical memory. Assume that operating system and other applications use 4 GB memory while creating the data store. So, the available free memory at this time is 28 GB. Then, the default value of Hash Memory Allocation is 22.4 GB (22.4 GB = 28 GB * 80%).

   Data Destination

   Defines the data destination folder to save the actual unique data blocks. Use the largest disk to store data as that contains the original data blocks of source.

   Note: The Data Destination path should be a blank folder.

   Index Destination

   Defines the index destination folder to store the index files. Choose a different disk to improve the deduplication processing.

   Note: The Index Destination path should be a blank folder.

   Hash Destination

   Defines the path to store the hash database. Arcserve UDP uses the SHA1 algorithm to generate the hash for source data. The hash values are managed by the the hash database. Selecting a high speed Solid State Drive (SSD) increases the deduplication capacity and requires a lower memory allocation.

   Note: The Hash Destination path should be an empty folder.

   Note: You cannot specify the same path for the following four folders: Backup Destination folder, Data Destination, Index Destination, and Hash Destination.

   Enable Compression

   Specifies that the data compression settings are enabled.

   Compression Type

   Specifies whether to use the standard compression type.

   Compression is often selected to decrease the usage of the disk space, but also has an inverse impact on your backup speed due to the increased CPU usage. Based on your requirement, you can select one of the three available options.

   Note: For more information, see Compression Type.

   Enable Encryption

   Specifies that encryption settings are enabled. When you select this option, you must specify and confirm the encryption password.

   Data encryption is the translation of data into a form that is unintelligible without a deciphering mechanism. The Arcserve Unified Data Protection solution uses secure, AES (Advanced Encryption Standard) encryption algorithms to achieve maximum security and privacy of your data. For data stores, encryption or No encryption is supported. For Encryption, only AES-256 is available.

   Concurrent Active Nodes

   Specifies the maximum concurrent jobs on the data store.

   No Limit: The default means that all jobs in this Data Store are started immediately.

   Limit to: Refers to a value from 1 to 9999. The value indicates the number of jobs that can concurrently run. If the running jobs meet the number, another job is placed in to the queue and job can only start when one of the running job completes. The completed job could mean a finished, canceled, or a failed job.

   The number applies to the Job Types but not to the Server nodes. For example, number 5 indicates that five backup jobs are running. Any job scheduled after five backup jobs waits in the queue, but you can submit another job such as File System Catalog.

   Note: Limit to number only impacts the replication outbound job, not the replication inbound job. Limit to number does not impact the Restore or BMR jobs. Such jobs are not placed in a queue.

The data store is updated.