Replication Data Protection includes integrated WAN optimized replication. BrickStor SP supports block and file level replication. Only the changed data is transmitted to shorten replication windows and reduce bandwidth usage. BrickStor SP replication supports bandwidth throttling. BrickStor SP Replication supports pause and resume as well as resume from bookmarks when interrupted by network outages and disruption. BrickStor SP supports block level replication to other BrickStor SP devices. RackTop’s data replication and backup capabilities enable customers to take advantage of a hybrid cloud strategy and use the cloud provider of their choice. Replication Best Practices When setting up replication, especially for larger datasets where data is being written, snapshots should be set to run more frequently than ran during normal operation. Each snapshot becomes a replication job, and since more frequent snapshots will be smaller, there is less likely to be a failure to replicate due to network errors or latency. Any replication retransmits are also more likely to be successful. In cases where an encrypted dataset is being replicated, keys should be exported from the local BrickStor SP and imported on the remote BrickStor SP so that the data can be recovered there. Use the advanced configuration parameters to optimize replication: Priorities can be set to determine which datasets will replicate first. Bandwidth throttling can be configured to optimize how much bandwidth is used and at what times of day. Optimize snapshot retention periods on both ends. On the local system, ensure that snapshots are not aging out before they are replicated. On the remote system, longer retention will consume more storage. Replication peers should be on an appropriate data network that will be available and not interfere with other network traffic. Setup email notifications. Understanding Peers BrickStor SP supports block replication between two or more pools within the same system or across systems. To set up replication between two systems, Establish a peer relationship with the target system from the origin system. Once the peer relationship is created set up replication between pools on a per-data set basis. Configuring a Peer Relationship To configure a peer relationship, complete the following steps: In the Connections pane, select the appliance level. In the details pane, click the *Replication tab. Click on the Add Peer Button by clicking the + beside "Locations". If peers already exist on the system, navigate to the Add Peer button by clicking the + button beside the word Locations. In the Add Peer dialog box, enter an IP address or hostname for the desired peer. Replication 2.0 now supports replicating to an HA cluster through the resource group. This will allow replication to continue operating even after a fail over. The BrickStor SP OS will coordinate sharing keys between the cluster nodes. If replicating to an HA cluster, ensure the use of the destination resource group’s address (VNIC) in this step. Enter the username and password for the desired peer. Click Add Peer. The added peer appears under the Replication Peers label. The new peer will remain greyed out until a target has been added to that peer. Repeat this process in order to replicate in the reverse direction on the other host. Understanding Peer Status The following table describes peer status messages that may be encountered. Table 1. Peer Status This… Means the peer is… Healthy No Backlog Configured without replication targets enabled for Peer Unreachable and has a Problem, such as the target pool is not imported and will show up as [unk] or the target pool is out of space. Data Protection Replication Data will be replicated to the target pool under the Replication Container. Through the GUI the source Hostname and IP will be visible along with the original dataset name. This information is stored in file system metadata on the replication target. It will not match the exact path name if an admin is browsing the file system on the pool. Data Replication Hierarchy on File System Pool name global replication Serial number of source BrickStor SP GUID of source dataset Data Protection Policy Configurations Data Replication Priorities Each replicated dataset has a priority assigned to it. The priority determines the order that replicated datasets are sent. The possible priorities are: Critical High Medium Low Background Critical priority datasets are always sent before datasets of any other priority. Datasets with a priority of Background are always sent after any datasets of any other priority have been sent. For High, Medium, and Low priority datasets, the order chosen depends on a combination of factors such as: The amount of data to transfer. The success of past replication attempts of this dataset. The replication priority is combined with these factors to determine a 'fair' replication order to allow all datasets to make progress replicating (when possible). Consequently, a High replication cannot indefinitely preempt replication of a Medium or Low priority dataset. Likewise, a Medium priority dataset cannot indefinitely preempt replication of a Low priority dataset. Configure the Data Protection Policy for a Storage Profile Managing Replication Details Manage replication details for a peer from the Replication Details page, to include: Set replication window settings for bandwidth throttling and peak business hours. View and configure replication targets. Enable/Disable targets. Set inheritance (whether to inherit replication parameters from the parent). View timing and transfer status. Export a replication report. Show the history of replication jobs by clicking the Open History button. Accessing the Replication Details page Clicking on a Peer’s IP address will navigate to the replication details page. Replication Transfer History You can view the details of transfers. This list can be filtered and exported. Details include: Time Duration Source/Destination Size Speed Success Status Auto Snapshot Data Protection Within the selected dataset, click on the Auto Snapshot Data Protection tab. Set a custom profile protection policy under the Auto Snapshot Creation section and filter as needed. Choose whether to have the same or alternate retention under Auto Replicated Snapshots. To the right (the Auto Snapshot Compliance area(), includes the number of snapshots retained and desired, as well as the latest snapshot and next snapshot time for all rolling, interval, weekly, monthly, and yearly snapshots. The snapshot stats display shows the count, users, latest and oldest snapshots, max expiration, holds, and user holds. Further to the right (the Snapshot Indexing area), displays the following information and allows the user to toggle the on and off switch for indexing snapshots. Snapshot Indexing also gives the option to regenerate the index, which will prompt the user with a time consumption warning. Further to the right under reports, click Auto Snapshot Creation: Policies. Here, set the minimum and maximum policy by selecting them with the toggle button. Once selected, the user can filter and add the needed specifications. There may be a prompted alert if too many or too few snapshots are selected.