Storage location guidance
A storage location is a physical or logical storage volume used as storage for a repository associated with a Rapid Recovery Core. Storage locations can contain backup data (such as backup snapshots, replication information, or archives), repository metadata, or both types of data.
DVM repositories must include at least one storage location, and may be expanded to contain as many as 4096 extents. Regardless of the storage location associated with the repository, the Rapid Recovery Core considers the total amount of space available to be a single repository.
To be defined as a storage location for the Core, a storage volume must have at least 1GB of storage space available. For practical purposes, any Core is likely to need substantially more space; Quest recommends each Core have at least 250GB of storage space associated with the repository to be effective.
The storage location for a DVM repository must be on a local drive attached to the Core server or on a CIFS share.
Use the following guidance when planning or defining a storage location for a repository:
- For repository data, use a fast storage drive, preferably a solid-state drive (SSD) with sufficient storage space.
- For increased efficiency, store metadata for your repository on a separate fast storage drive (preferably SSD).
- After creating the DVM repository, consider modifying the location of the deduplication cache to a separate fast storage drive (preferably SSD) for increased efficiency. For more information, see Optimizing deduplication in the topic Understanding deduplication cache and storage locations.
- Disable anti-virus protection on repository folders, directories or volumes.
NOTE: Rapid Recovery employs space-saving deduplication functionality that can conflict with anti-virus software, resulting in repositories with inaccessible data. For more information, refer to Quest Knowledge Base article 117506, "Software conflicts with AppAssure and Rapid Recovery."
- Quest strongly recommends specifying a dedicated folder within the storage drive or volume to store data files. For example, to store your repository data on the E drive, specify E:\Repository\Data. To store your repository data on a CIFS drive, specify \\servername\Repository\Data.
Caution: If you define the location for your repository data at the root of the selected volume (for example, E:\ or \\servername) instead of in a dedicated folder, then if you subsequently remove the repository, other files and data stored in that root folder are deleted, which could result in catastrophic data loss.
Speed is the most critical factor for storage volumes used as repository storage locations. For information about the storage technologies supported by Rapid Recovery, see the topic Understanding repositories.
For information about creating a DVM repository, see Creating a DVM repository.
For information about expanding an existing DVM repository, see Expanding a DVM repository.
Creating a DVM repository
This process describes how to create a repository on your Core using the Deduplication Volume Manager (DVM) repository technology.
You must have administrative access to the machine on which you want to create a DVM repository. This process requires you to associate at least one volume on which to store data and metadata for the repository. For guidance, see the topic Storage location guidance.
Complete the following steps to create a DVM repository.
- Navigate to the Rapid Recovery Core Console.
- On the icon bar, click
(More), and then select
Repositories.
The Repositories page displays.
- At the top of the page, under the Repositories page title, click + Create.
The Create Repository Wizard appears.
- On the Configuration page, enter the information as described in the following table.
Table 5: Repository configuration settings Text Box Description Name Enter the display name of the repository. By default, this text box consists of the word Repository and a number, which corresponds to the number of repositories for this Core. For example, if this is the first repository, the default name is Repository 1. Change the name as needed.
Repository names must contain between 1 and 40 alphanumeric characters, including spaces. Do not use prohibited characters or prohibited phrases.
Comments
Optionally, enter a descriptive note about this repository. You can enter up to 254 characters. Examples might include a message such as DVM Repository 2 or This repository contains protected SQL Server data only.
This information can later be viewed and edited by accessing the Settings for this repository.
- Click Next.
The Storage Location page appears.
- On the Storage Location page, specify the path to a storage location on a local disk or on a CIFS shared network storage location.
NOTE: Follow the guidance described in the topic Storage location guidance.
- To add a storage location on a local disk, enter the following information:
Table 6: Local disk settings Text Box Description Location Specify the path for a local drive on which to store repository data. For example, type
E:\Repository\Data.Use only alphanumeric characters, hyphen, or period, with no spaces or special characters.
Metadata path Specify the path for a local drive on which to store repository metadata. It can be the same local volume (for example, E:\Repository\Metadata), or for more efficiency, you can specify a separate local volume (for example,F:\Repository\Metadata).When specifying the path, use only alphanumeric characters, the hyphen, and the period (but only to separate host names and domains). You can use the backslash character only to define levels in the path. Do not use spaces. No other symbols or punctuation characters are permitted.
NOTE: If you do not specify a path for metadata, then repisotory data and metadata are both stored in the Location path. Ten percent of the volume space allocated for repository data is then reserved specifically for metadata.
- To specify a storage location on a CIFS network shared location, enter the following information:
Table 7: CIFS share credentials Text Box Description Location
Specify the path for a CIFS network share location on which to store repository data and metadata.
The path must begin with \\. When specifying the path, use only alphanumeric characters, the hyphen, and the period (but only to separate host names and domains). The letters a to z are case-insensitive. Do not use spaces. No other symbols or punctuation characters are permitted.
If this location is at the root, define a dedicated folder name (for example:
\\Server12\Repository).User name
Enter the user name associated with an administrative account with access to the network share location, or to use a set of credentials saved to Credentials Vault, use the drop-down list and select a user name.
Password
Specify a password for accessing the network share location.
- To add a storage location on a local disk, enter the following information:
- Click Next.
The Space Allocation page appears.
- On the Space Allocation page, perform the following tasks:
- Specify the amount of storage space to leave unused on the repository volume. The remainder of space on the volume is dedicated to repository file storage.
NOTE: Industry best practice suggests that drive speed and performance is enhanced when 10 to 20 percent of a storage volume is left unused. While Quest makes no recommendations in this area, the default setting for reserved free space is 20 percent. You can change this amount explicitly by moving the Percentage of available space slider, or implicitly by changing the amount in GB of space in the Data setting.
- To increase the amount of free space to leave on the repository volume, move the slider from its current position to the left.
- To increase the amount of storage space on the volume to be used for repository storage, move the slider from its current position to the right.
NOTE: Quest does not recommend filling the entire volume with repository files. Consider leaving at least 10 percent of the volume free.
If the value shown on the Percentage of available space slider is set as intended, then data and metadata values are informational only. If you change the amount in GB of space in the Data setting, the slider and metadata values change accordingly.
- Optionally, you can specify in GB the amount of space on the volume to be used to store data. Before you change this setting, note the following:
- If you change the amount in GB of space in the Data setting, the slider and metadata values change accordingly.
- The metadata value always represents between 8 and 10 percent of the total space reserved to back up data in the repository.
- If you designated two separate volumes for storing data and metadata on the Storage Location page of the wizard, then the metadata value shows in GB the amount of space reserved for metadata on the specified volume. In this case, if you add the amount of free space reserved as shown in the slider with the amount of space in the Data text field, the sum equals the total amount of storage space available on the volume.
- If storing repository data and metadata on the same storage volume, the 10 percent allocation for metadata is reserved on the single repository volume. The amount shown in the Data text field represents the remaining 90 percent of the storage space allocated for the repository. In this case, if you add the amount of free space reserved as shown in the slider, the amount of space in the Data text field, and the amount in the Metadata field, the sum equals the total amount of storage space available on the volume
- Optionally, on the Space Allocation page, if you want to enter advanced options, select Show advanced options and enter the details for the advanced settings as described in the following table.
Table 8: Space allocation details Text Box Description Bytes per sector
Specify the number of bytes you want each sector to include. The default value is 512.
NOTE: Quest recommends setting the bytes per sector to match the physical sector size of the storage location in which the repository resides. For example, if the disk on the intended storage location has a 4096 byte sector size, change the bytes per sector setting to 4096.
If using multiple storage locations with different sector sizes, Quest recommends retaining the default setting of 512 bytes per sector.
Average bytes per record
Specify the average number of bytes per record. The default value is 8192.
Write caching policy
The write caching policy controls how the Windows Cache Manager is used in the repository and helps to tune the repository for optimal performance on different configurations. As of release 6.4, the default for this setting is Off.
Set the value to one of the following:
- On. If set to On, Windows controls the caching.
- Off. If set to Off, which is the default, Rapid Recovery controls the caching.
- Sync. If set to Sync, Windows controls the caching as well as the synchronous input/output.
- When you have completed your repository configuration, click Finish.
The Create Repository Wizard closes, and Rapid Recovery applies the settings to your Core. If Toast alerts are enabled, you see messages indicating that repository creation has started, and the repository is mounted. Alternatively, you can monitor the progress of the repository creation by viewing alerts on the Events page.
After a brief pause, on the Repositories page, in the DVM Repositories summary table, your new repository is listed.
- Specify the amount of storage space to leave unused on the repository volume. The remainder of space on the volume is dedicated to repository file storage.
Adding a storage location to an existing DVM repository
You can add additional storage space to your DVM repository by expanding the repository. This process is known as adding a storage location (or adding an extent). This action expands the capacity of your repository over two or more volumes. You can add up to 4096 extents to your original DVM repository.
A DVM repository must exist in your repository before you can expand it. The new disk volume must have at least 1GB free. The volume can be on the same storage technology or it can use a different supported storage technology, with speed being the most critical factor for performance.
Before expanding your repository, please refer to Storage location guidance.
|
|
NOTE: Rapid Recovery employs space-saving deduplication functionality that can conflict with anti-virus software, resulting in repositories with inaccessible data. For more information, see Quest Knowledge Base article 117506, "Software conflicts with Rapid Recovery." |
Complete the steps in the following procedure to expand your existing DVM repository.
- Navigate to the Rapid Recovery Core Console.
- On the icon bar, click
The Repositories page appears, displaying the DVM Repositories pane.
- In the DVM Repositories summary table, from the row representing the repository for which you want to add a storage location, click the
(More options) drop-down menu, and then select Expand Repository.
The Add Storage Location to [Repository Name] wizard appears, displaying the Storage Location page.
- On the Storage Location page, specify the path to a storage location on a local disk or on a CIFS shared network storage location.
NOTE: The values entered into the Location and Metadata text boxes must each represent unique paths not used for other storage locations. Follow the guidance described in the topic Storage location guidance.
- To add a storage location on a local disk, enter the following information:
Table 9: Local disk settings Text Box Description Location Specify the path for a local drive on which to store repository data. For example, type
E:\Repository\Data.Use only alphanumeric characters, hyphen, or period, with no spaces or special characters.
Metadata path Specify the path for a local drive on which to store repository metadata. It can be the same local volume (for example, E:\Repository\Metadata), or for more efficiency, you can specify a separate local volume (for example,F:\Repository\Metadata).When specifying the path, use only alphanumeric characters, the hyphen, and the period (but only to separate host names and domains). You can use the backslash character only to define levels in the path. Do not use spaces. No other symbols or punctuation characters are permitted.
NOTE: If you do not specify a path for metadata, then repisotory data and metadata are both stored in the Location path. Ten percent of the volume space allocated for repository data is then reserved specifically for metadata.
- To specify a storage location on a CIFS network shared location, enter the following information:
Table 10: CIFS share credentials Text Box Description Location
Specify the path for a CIFS network share location on which to store repository data and metadata.
The path must begin with \\. When specifying the path, use only alphanumeric characters, the hyphen, and the period (but only to separate host names and domains). The letters a to z are case-insensitive. Do not use spaces. No other symbols or punctuation characters are permitted.
If this location is at the root, define a dedicated folder name (for example:
\\Server12\Repository).User name
Enter the user name associated with an administrative account with access to the network share location, or to use a set of credentials saved to Credentials Vault, use the drop-down list and select a user name.
Password
Specify a password for accessing the network share location.
- To add a storage location on a local disk, enter the following information:
- Click Next.
The Space Allocation page appears.
- On the Space Allocation page, perform the following tasks:
- Specify the amount of storage space to leave unused on the repository volume. The remainder of space on the volume is dedicated to repository file storage.
NOTE: Industry best practice suggests that drive speed and performance is enhanced when 10 to 20 percent of a storage volume is left unused. While Quest makes no recommendations in this area, the default setting for reserved free space is 20 percent. You can change this amount explicitly by moving the Percentage of available space slider, or implicitly by changing the amount in GB of space in the Data setting.
- To increase the amount of free space to leave on the repository volume, move the slider from its current position to the left.
- To increase the amount of storage space on the volume to be used for repository storage, move the slider from its current position to the right.
NOTE: Quest does not recommend filling the entire volume with repository files. Consider leaving at least 10 percent of the volume free.
If the value shown on the Percentage of available space slider is set as intended, then data and metadata values are informational only. If you change the amount in GB of space in the Data setting, the slider and metadata values change accordingly.
- Optionally, you can specify in GB the amount of space on the volume to be used to store data. Before you change this setting, note the following:
- If you change the amount in GB of space in the Data setting, the slider and metadata values change accordingly.
- The metadata value always represents between 8 and 10 percent of the total space reserved to back up data in the repository.
- If you designated two separate volumes for storing data and metadata on the Storage Location page of the wizard, then the metadata value shows in GB the amount of space reserved for metadata on the specified volume. In this case, if you add the amount of free space reserved as shown in the slider with the amount of space in the Data text field, the sum equals the total amount of storage space available on the volume.
- If storing repository data and metadata on the same storage volume, the 10 percent allocation for metadata is reserved on the single repository volume. The amount shown in the Data text field represents the remaining 90 percent of the storage space allocated for the repository. In this case, if you add the amount of free space reserved as shown in the slider, the amount of space in the Data text field, and the amount in the Metadata field, the sum equals the total amount of storage space available on the volume.
- Optionally, on the Space Allocation page, if you want to perform the repository optimization job for the selected repository, select Run Repository Optimization Job for [Repository name].
Caution: Performing a Repository Optimization Job could take a substantial amount of time and bandwidth in your environment, based on factors such as the size of your repository, amount of data in your repository, available network bandwidth, and existing load on the input and output of your system. The only suggested use case for running this job is if your DVM deduplication cache was full and you subsequently increased the cache size.
For more information about the repository optimization job, see About DVM repository optimization.
- Optionally, on the Space Allocation page, if you want to enter advanced options, select Show advanced options and enter the details for the advanced settings as described in the following table.
Table 11: Space allocation details Text Box Description Bytes per sector
Specify the number of bytes you want each sector to include. The default value is 512.
NOTE: Quest recommends setting the bytes per sector to match the physical sector size of the storage location in which the repository resides. For example, if the disk on the intended storage location has a 4096 byte sector size, change the bytes per sector setting to 4096.
If using multiple storage locations with different sector sizes, Quest recommends retaining the default setting of 512 bytes per sector.
Average bytes per record
Specify the average number of bytes per record. The default value is 8192.
Write caching policy
The write caching policy controls how the Windows Cache Manager is used in the repository and helps to tune the repository for optimal performance on different configurations. As of release 6.4, the default for this setting is Off.
Set the value to one of the following:
- On. If set to On, Windows controls the caching.
- Off. If set to Off, which is the default, Rapid Recovery controls the caching.
- Sync. If set to Sync, Windows controls the caching as well as the synchronous input/output.
- When you have completed your repository configuration modifications, click Finish.
The Add Storage Location to [Repository Name] wizard closes, and Rapid Recovery applies the settings to your Core. If Toast alerts are enabled, you see messages indicating that repository creation has started, and the repository is mounted. Alternatively, you can monitor the progress of the repository creation by viewing alerts on the Events page.
After a brief pause, on the Repositories page, in the DVM Repositories summary table, in the DVM Repositories summary table, your new repository is listed. Optionally, expand details for the appropriate repository to see the details for the new storage location.
- Specify the amount of storage space to leave unused on the repository volume. The remainder of space on the volume is dedicated to repository file storage.
Changing DVM repository settings
This procedure assumes that your Core is already using at least one DVM repository.
In the settings for a DVM repository, you can change such settings as number of concurrent operations, and enabling or disabling deduplication or compression.
Complete the following task to change the available settings for a DVM repository.
- From the Rapid Recovery Core Console, in the icon bar, click
- On the Repositories page, from the row representing the repository you want to update, click
The Repository Settings dialog displays.
- On the Repository Settings dialog, you can change the settings described in the following table.
Table 12: DVM settings Option Description Maximum concurrent operations The number of jobs that the repository can perform at one time. The default is 64. Description Can contain and display notes or a description that you want to associate with this repository. Enable deduplication When this option is selected, Rapid Recovery Core deduplicates data so that only unique blocks are saved to the repository.
This setting is enabled by default. Clear this option and save to disable deduplication.
Enable compression When this option is selected, Rapid Recovery Core compresses data to reduce space used.
This setting is enabled by default. Clear this option and save to disable compression.
- Click Save.
The changes are applied to the repository.