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.

Remote Data Protection - On-Demand Webinar


Remote Backup

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.

Server-Side Network Configuration

Port Forwarding is a standard mechanism to redirect connections on a specific port from one IP to another. Retrospect Backup requires two ports:

  • Port 497: multicast and remote backup broadcast

  • Port 22024: on-demand requests

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 Remote backup will not work unless the ports are open.

Retrospect Backup Configuration

Retrospect Backup utilizes the following features for Remote Backup:

  • Public/Private Keypair Authentication: This authentication automatically and securely identifies the remote endpoint as a trusted client without a password.

  • ProactiveAI Backup: This backup script will automatically starts a backup for any remote endpoint that notifies the Retrospect Backup instance of its availability.

  • On-Demand Restore: This restore workflow allows remote employees to restore files themselves without IT assistance.

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

  1. In the backup server’s page, scroll down to see "Deploy Retrospect clients for endpoint protection".

  2. 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".

  3. 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.

  4. 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.

  1. Under Preferences > Clients, create a public/private keypair.

  2. Locate the public key file.

  3. Copy the public key file into the Retrospect Client installer’s "public_key" folder. You can download the Retrospect Client installer from Retrospect Downloads.

  4. Create a file called "server.txt" in the following location with the public DNS/IP address of the Retrospect Backup instance.

    Win: In the same folder as Retrospect Client MSI file.
    Mac: In the same folder as "Retrospect Client Installer".
    Sample `server.txt` File
  5. Compress the new installer and send it to your remote employee to install.

Now that the Retrospect Client agent can connect to the Retrospect Backup instance, let’s create a ProactiveAI backup script.

  1. In Retrospect Backup, go to Preference then Clients and check "Automatically add clients using public keys".

  2. Create a ProactiveAI script. This is under ProactiveAI on Windows and under Scripts on Mac.

  3. Add a backup set as a destination. This can be either local storage or a cloud storage location.

  4. Add "Remote Backup Clients" as the source. This is under Volumes on Windows and under Tags on Mac.

  5. After you save, Remote Backup will be configured.

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.

Qué hay de nuevo en Retrospect – Retrospect Backup 19 + Retrospect Virtual 2022 + Retrospect Cloud Storage  

Protección de datos para cada entorno.