To create the destination, the recovery point server needs data stores. The data store specifies where the backup data is stored. You can add multiple data stores to a RPS.
Follow these steps:
The Destinations: Recovery Point Servers page is displayed.
A list of options is displayed.
The Add a Data Store page is displayed with the name of the specified recovery point server.
Defines the name of the data store.
Defines the location of the folder where the data store is created.
Note: For non-deduplication and deduplication data store, the backup destination path should be an empty folder.
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.
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 coming after five backup jobs waits in the queue, but you can submit another job such as File System Catalog.
Notes:
Specifies whether to enable data encryption. 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.
Specifies whether to enable data deduplication. 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.
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.
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.
Defines the path to store the hash database. Selecting a high speed Solid State Drive (SSD) can increase the deduplication capacity with a low memory allocation required.
Note: The Hash Destination path should be a blank folder.
Specifies if the hash folder is on a solid state drive.
Specifies the amount of physical memory that you allocate to keep hashes.
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 4KB to 8KB, the Deduplication capacity estimations double. Increasing the deduplication block size can decrease the deduplication percentage.
Note: You cannot specify the same path for the following four folders: Backup Destination folder, Data Destination, Index Destination, and Hash Destination.
These options help to estimate the capacity of a Deduplication data store.
The data store is created and gets displayed on the center pane. Click the data store to view the details in the right pane.
|
Copyright © 2015
|
|