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 agent into host mode, typing "/host" on the base URL of the app, and authenticate.
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.
The Host page is composed of 4 sections.
- Client section
- Access Restrictions section
- Servers section
- Portals sections
2. Go to the Servers sections
Here we see a few things, the client is currently set up for connecting to AWS S3 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 the client to backup to this server: toggles to on/off
3.) Next we're going to add a second offsite backup vault utilizing a WSBU Backup Server running on Windows Server 2016. 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 Server: "2"
- for WSBU server select: "Windows WholesaleBackup"
- for cloud bucket select: "AWS S3/Google Cloud/Wasabi"
- Server label:
- This can be anything you want: "WSBU Server 2016"
- Backup FQDN:
- for a WSBU server use its FQDN e.g): "server.backupops.com"
- for an S3/Google/Wasabi bucket: "leave the field blank",
- Registration FQDN:
- for a WSBU server use an FQDN e.g.) "server.backupops.com"
- for a S3/Google/Wasabi use bucket use "dash.backupops.com"
- Account name:
- for a WSBU Server: use the account name tied to that client: e.g) "ryan_kite"
- for an S3/Google/Wasabi bucket: use the Access Key tied to your bucket e.g) AKIAIOSFODHK7EXAMPLE
- Account password:
- for a WSBU Server use the password tied to the client that client e.g) "averymysteriouspassword"
- for an S3/Google/Wasabi bucket use the Secret Access Key tied to your bucket e.g) wJalrXUtnFEdg/K7MDENG/bPxRfiCYEXAMPLEkeY
- click to Allow the client to backup to this server: "True"
4.) Next click Save and (re-Register). The client will connect and register the account in the new location and provision of the new offsite vault.
5.) Now we will run a quick throughput test on each of the offsite backup vaults. Enter /expert mode and perform a Throughput and Firewall test. The new Vault is listed.
When the next backup process is launched, the client will sync the backup data across all of the available remote vaults.