Add a Local Data Store

This section provides information about how to add a local data store as a destination. You can add multiple data stores to a recovery point server.

Note: If the status of a data store shows The Data Store is experiencing an issue. Please try restarting the "Arcserve UDP RPS Data Store Service" to see if the problem is resolved. after you create or import a data store, then refresh the data store status from the Actions drop-down list and check if it changes to Running. If the status still does not update to Running, contact Arcserve Support.

Follow these steps:

1. On the Protect screen, do one of the following:
From the Recovery Point Servers View
1. Navigate to Destinations > Recovery Point Servers.
2. From the list of recovery point servers, click the Action drop-down list of a specific recovery point server, and then select Add Data Store.
3. The Add Data Store screen appears with a name of the specified recovery point server.
From the Data Store View
1. Navigate to Destinations > Data Stores.
2. On the Data Stores page, click Add Data Store, and then select Add Data Store.
3. The Add Local Data Store screen appears.
2. Specify the following details:
• Recovery Point Server: From the drop-down list, select the RPS as needed.
• Note: If you have chosen the Recovery Point Server view to add a local data store, or you have a single Recovery Point Server, the Recovery Point Server is selected by default.
• Data Store Name: Type a name for the data store.
• For Concurrent Active Sources Limit to: Specify the maximum concurrent jobs on the data store. The default value for concurrent jobs is 4.
• Data Store folder: Do the following:
1. Type the folder path in the following format or click Browse to select the desired folder.
2. \\Hostname\share
3. If the path provided is valid, the Connect button gets enabled.
2. Click Connect.
3. The Connect dialog appears.
3. Type the username and password of the provided hostname, and then click OK.
• Note: For non-deduplication and deduplication data store, the destination path must be an empty folder.
• Enable Deduplication: Specifies that deduplication is enabled for this data store. Arcserve Cloud Console 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. By default, the Enable Deduplication check box is selected.
• Deduplication Block Size: By default, the deduplication block size is selected as 64 KB.
• Hash Memory Allocation: Type the amount of physical memory that you want to 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 Cloud Console calculates the available free memory at this time. Assume that the available free memory is X GB at present. Arcserve Cloud Console 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%).
• Hash destination is on a Solid State Drive (SSD: Specifies that the hash folder is on a solid state drive.
• Note: Configure the hash destination on local SSD if the Hash destination is on a Solid State Drive(SSD) check box is selected.
• Index Destination: Defines the index destination folder to store the index files. Select a different disk to improve the deduplication processing.
• Note: The Index Destination path must be an empty folder.
• Hash Destination: Defines the path to store the hash database. Arcserve Cloud Console uses the SHA1 algorithm to generate the hash for source data. The hash database manages the hash values. Selecting a high speed Solid State Drive (SSD) increases the deduplication capacity and requires a lower memory allocation. For better hash performance, we recommend you that format the SSD volume as NTFS file system with 4 KB volume cluster size.
• Note: The Hash Destination path must be an empty folder.
• Notes:
• You cannot specify the same path for the following folders: Data Store folder, Index Destination, and Hash Destination.
• Remote or network share paths are not supported for AWS, Azure, or Google Cloud data stores.
• If you do not want to enable deduplication for a data store, uncheck the Enable Deduplication check box.
• Enable Compression: Specifies that the data compression settings are enabled.
• Compression Type: Specifies whether to use the Standard or Maximum as the 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.
• 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 UDP 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.

A password is not required when you are attempting to restore to the computer from which the backup was performed. However, when you attempt to restore to a different computer, a password is required which is set in the policy and not the password set in the data store.

3. Click Save.
4. Note: After the data store is created, you cannot enable or disable Deduplication, Compression, or Encryption.
5. The local data store is created successfully.