Follow

Backing up customer data to multiple offsite vaults

Here we'll cover how to add a second offsite backup vault or endpoint to your backup clients.

The client allows for backing up to 7 different endpoints or offsite vaults.

This works really well for ensuring user data is synchronized across multiple remote vaults for added data redundancy.

How to implement multiple offsite remote vaults:

1.) Open the backup client in host mode, using the "-host" flag on the executable, apply the change and launch the client.

open-client-in-host-mode.JPG

The client will prompt for the host build password. (The one used when you created the backup client in the web console) enter it in and proceed.

enter-host-password.JPG

A new "HOST" tab is available - click to open it.

go-to-host-tab.JPG

2.) Next click on the Servers tab. Here we see a few things, the client is currently setup for connecting to a Windows Server as the primary remote storage vault, using Remote Server slot 1. 

  • Remote Server:  dropdown with 7 slots available
  • Protocol: dropdown with various endpoints 
  • Server label: serves as an ID or alias in GUI's and reports
  • Backup FQDN: e.g) backups.wholesalebackup.com or IP and Port
  • Registration FQDN:  e.g) backups.wholesalebackup.com or IP and Port
  • Account name: the account name
  • Account password: the account password
  • Allow client to backup to this server: toggles to on/off

overview-of-host-tab.JPG

3.) Next we're going to add a second offsite backup vault utilizing cloud storage on Amazon S3. Feel free to use another Windows Server, Amazon S3 or Google Cloud storage for this step.

First select Remote Server dropdown and select '2'

then fill in the following fields 

  • Remote Server2
  • Protocol: Amazon S3 / Google Storage 
  • Server label: e.g) Your Brand S3 Vault
  • Backup FQDN: S3 and Google leave empty.
  • Registration FQDNdash.backupops.com
  • Account name: AWS Access Key ID e.g) AKIAIOSFODHK7EXAMPLE
  • Account password: AWS Secret Access Key e.g) wJalrXUtnFEdg/K7MDENG/bPxRfiCYEXAMPLEkeY

            [don't have those? it's covered in step 2 here]

  • Allow client to backup to this server: on / true

setup-second-remote-vault-to-s3.JPG

4.) Next click Save and (re-Register). The client will connect and register the account in the new location and provision the new offsite vault. 

account-registration-successful-on-second-vault.JPG

5.) Now we will run a quick throughput test on each of the offsite backup vaults. Save and close the client. Open the client in Expert mode using the "-expert" flag on on the exe. Apply and launch the app.

testing-throughput-to-vaults.JPG

Click on the Expert Settings tab and then click Test Throughput button, the client will run a quick test and print the results.

We see the newly added Amazon S3 vault in addition to the Windows Server vault. 

result-of-throuput-test.JPG

 

Success!

When the next backup process is launched, the client will sync the backup data across all of the available remote vaults. 

 

The process works the other way around for clients configured to S3 or Google

For example if you have a backup client that uses Google Cloud or Amazon S3 as it's primary backup endpoint which is utilizing Remote Server slot 1.

You can easy add your own Hosted Windows Backup Server as a second remote vault under Remote Server slot 2.

here is what that would look like: 

adding-windows-server-as-a-second-vault-to-google-cloud.JPG

 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk