By default, AppAssure is configured to perform 3 concurrent actions. So let’s say you have a schedule in place for snapshots of 7 servers to be taken at the same time. Three of those snapshots will be taken simultaneously; fourth (fifth, sixth and seventh) server snapshot will be queued and executed later.

To modify this setting (change the number of concurrent tasks AppAssure will run), click on the Configuration tab, then select Settings on the left, and hit Change in the Transfer Queue section.

image

image

Please be advised that modifying (increasing) this value will cause AppAssure to consume additional bandwidth thus impacting your network. As of this writing, there is no way to throttle the bandwidth used for backups, so AppAssure will consume as much as it can get. One possible way of solving this problem is to outfit all of the servers you are protecting with a 2nd NIC, and basically configure it for “out of band” backup.


To setup replication of backups with a remote AppAssure instance (Replay Core) you’ll need to submit the request for a Replication license. You can do so by completing and submitting a form at http://software.dell.com/appassure. In the bottom left of the page, under Support for This Product section, click on the Support Portal link.

Download the AppAssure installer package and install it on the server you’ll be using as a replication target. Once installed, you’ll be prompted to enter in a license key. Use the Replication License key you have just obtained.

image

Provision a storage repository from the Home tab, by clicking on the Add New Repository.

In our example we’ll be using a 2TB Virtual Disk we’ve created on a Dell VRTX. It’ll show up as a disk in Disk Management on the Windows server we’ll be using. We’ve formatted the drive and assigned it a drive letter. Then we’ve created folders that are required by AppAssure – APPASSURE BACKUP; and two subfolders within it – DATA and METADATA.

image

Specify the repository name, then click on Add Storage Location.

image

Specify the Storage Locations you’ll be using. In our specific example the Metadata Path will be Z:\APPASSURE BACKUP\METADATA and the Data Path will be Z:\APPASSURE BACKUP\DATA. Also, in the Details section, specify the size of the Storage Repository. Again, in our specific example the size will be 2 TB.

image

Then click on the Save button.

Now we’ll have to configure the replication target (Remote Core) back on the source AppAssure appliance. Using the web interface navigate to the Replication tab, then click on the Actions button, and select Add Remote Core from the drop down menu.

image

Click on the radio button next to I have my own remote Core I wish to replicate to then specify the IP address (or a FQDN) of the Remote Core as well as the credentials for the appropriate domain account you’ll be using. Click on Continue.

image

In the next window, select Add a new Coe to replicate to, then select which servers you’d like to replicate as well as which storage repository replicas should be placed in on the Remote Core.

image

Please note that AppAssure as of this writing (version 5.3.7.68) does not have the ability to throttle bandwidth used for replication. What this means is that every time replication occurs AppAssure will consume as much bandwidth as it can. Biggest hit your WAN circuits will take is during the initial replication of resources. To work around this you can check the box next to Use a seed drive to perform initial transfer, which will export the replicas of the selected servers to a seed drive which can be say a external USB hard drive. You can then physically transport the drive to the remote location and then “consume” (import) the data on the Remote Core side.

Once you select the appropriate servers to replicate and click on the Start Replication button, you will see the the status under the Replication tab.

image

Another thing to note is that there is no replication schedule you can configure. As soon as the snapshot of a server is created on the source AA core it will be automatically replicated to the target AA core.

On the target AA core (Remote Core) you will now see this server listed under Replicated Machines.

image

%d bloggers like this: