Retrospect Backup provides complete protection for every major operating system, virtual environment, application, and email service–with seamless integration to our hosted service, Retrospect Management Console.
Remote employees pose a significant challenge to legacy backup systems. Their endpoint needs data protection, but with ubiquitous cloud services like Office 365 and Dropbox, those employees don't need to log into the VPN on their laptop to get work done. Without a VPN, legacy backup systems cannot back up these desktops and laptops because the agents are behind firewalls and routers with network address translators (NATs).
With Retrospect Backup, every employee's data can be protected. Retrospect Backup provides multiple solutions, depending on the optimal configuration for your business: VPN Backup, Remote Backup and Cloud Backup.
Optimized for remote employees on VPN that you want to protect with an on-site Retrospect Backup instance. Retrospect Backup works seamlessly with virtual private networks (VPNs) with automatic agent discovery and protection capabilities for remote employees, and you can quickly onboard new remote employees using Automatic Onboarding on Retrospect Management Console.
Optimized for remote employees not on VPN that you want to protect with an on-site Retrospect Backup instance. Retrospect Backup allows you to protect remote employee endpoints outside of your VPN without any client-side router changes using Remote Backup, with full support for on-demand restore for employees to get files back without assistance and seamless Automatic Onboarding for easy deployment.
Optimized for remote employees that you want to back up directly to the cloud. Retrospect Backup Solo Premium protects a computer and any connected device, and you can easily deploy it to all of your remote employees using Automatic Onboarding on Retrospect Management Console.
Remote Data Protection - On-Demand Webinar
Optimized for remote employees outside of VPN that you want to protect with an on-site Retrospect Backup instance.
With Remote Backup, remote employee endpoints can be automatically added to a Retrospect Backup instance inside the corporate firewall and protected with a ProactiveAI script. There are no router changes needed on the employees side, and the IT administrator can make a simple change on the corporate firewall to forward inbound connections to Retrospect Backup. Remote employees are able to use on-demand restore to get files fast without assistance. Automatic Onboarding is a great way to deploy the Retrospect Client agent to your remote employees.
Remote Backup is designed specifically for endpoint protection and is not supported for server protection.
For Remote Backup to work, the Retrospect Client agent needs to be able to make a network connection the Retrospect Backup instance.
We’ll walk through each step.
Port Forwarding is a standard mechanism to redirect connections on a specific port from one IP to another. Retrospect Backup requires two ports:
You need to set up your public-facing router/NAT/firewall to forward these ports to the IP address of the computer running your Retrospect Backup instance. With this networking change, a remote endpoint running the Retrospect Client agent will be able to make a connection to the Retrospect Backup instance, even though the computer running the Retrospect Backup instance is running on the internal network.
For guidance on enabling port forwarding, please refer to the hardware’s manual. The process varies by manufacturer.
You can verify that the ports are open using https://www.yougetsignal.com/tools/open-ports/. Remote backup will not work unless the ports are open.
Retrospect Backup utilizes the following features for Remote Backup:
Let’s walk through the steps with Automatic Onboarding on Retrospect Management Console.
Retrospect Backup for Windows: Onboard a new server or endpoint
Retrospect Backup for Mac: Onboard a new server or endpoint
In the backup server’s page, scroll down to see "Deploy Retrospect clients for endpoint protection".
Upload the server’s public key. Retrospect Backup 17 enables you to automatically upload it to Retrospect Management Console. Simply go to Preferences. The public key file is located on the engine under /Library/Application Support/Retrospect/pubkey.dat on Mac and C:/ProgramData/Retrospect/pubkey.dat on Windows. Find it with "Upload Key" and then click "Upload".
Enter the IP address or DNS name of the Retrospect Backup server under "Remote Backup", so that remote computers can connect to the port-forwarded public IP/DNS address.
Under "Retrospect client installers", there is a link to share with end users. They can download the Retrospect Client for Windows, Retrospect Client for Mac, or Retrospect Client for Linux installers with the public key and remote backup address bundled in.
Let’s walk through setting these up in Retrospect Backup without Retrospect Management Console.
Now that the Retrospect Client agent can connect to the Retrospect Backup instance, let’s create a ProactiveAI backup script.
On-demand restore will automatically work using public key authentication.
If you encounter any issues, please see further details in our User’s Guide: Retrospect Backup for Windows or Retrospect Backup for Mac.
Optimized for remote employees that you want to bypass corporate network and back up to the cloud.
With Cloud Backup, remote employees can use Retrospect Backup to back up their corporate data to a cloud storage provider. Retrospect Management Console supports Automatic Onboarding to deliver a Retrospect Backup download and license to remote employees, and IT administrators can then configured a Shared Script on Retrospect Management Console to automatically deploy to those new instances. The endpoint will use the script to back itself up to a per-configured cloud storage location. Retrospect Backup Solo Premium is a great subscription license for this scenario, covers a computer and any connected device.
Let’s walk through setting up a new Retrospect Backup server and then using Shared Scripts to deploy a cloud backup sript to it.
Retrospect Backup for Windows: Onboard a new backup server
Retrospect Backup for Mac: Onboard a new backup server
Under Settings > Organizations, you will see our new Onboarding Assistant. Click "Onboarding Assistant".
Enter a name for your new backup server.
Click "Add License…", type in your license, and click "Add".
Your custom installer should now be visible. Click "Download".
Unzip the download.
For Mac, run "Install Retrospect". At the end, Retrospect will be launched.
For Windows, run "Install Retrospect" and select "Install Retrospect". After it completes, launch Retrospect.
Retrospect is now licensed and connected to Retrospect Management Console under your account.
The Retrospect Management Console supports mass deployment of scripts through its Shared Scripts workflow. With Shared Scripts, IT administrators or partners can update a set of Retrospect Backup engines with a common ProactiveAI script to a single cloud destination. See the following step-by-step guide.
Log into your Retrospect Management Console account and click on "Settings" to access your account at the top right of the screen.
Click on "Scripts". You will see a list of Shared Scripts with a summary of each, including deployments.
Click on "New Shared Script". You will be able to select which source containers you want to include, which cloud destination, and the schedule.
For the "Destination", you can select between Amazon S3 compatible providers and B2. For a B2 cloud destination, enter the bucket name. For an Amazon S3 compatible provider, use the entire URL with bucket name.
After you save the script, select that script's deployment options. Select the engines that you would like to deploy this Shared Script to and click "Save". The script will then be deployed to those engines.
All Shared Scripts are use AES-256 encryption. You will find the encryption key in the "Deployments" tab under "Security Code". Each backup set will be named 'Destination Name-Engine Name' to ensure the separate Storage Groups do not use the same destination path.