Retrospect Management Console allows you to monitor and manage every Retrospect engine in your organization and managed organizations. Starting in Retrospect Backup 16.5, customers can view and manage individual engine’s information, including scripts, sources, sets, and activities, for every engine. Starting with Retrospect Backup 18, the Management Console Add-on is included with every edition of Retrospect to allow seamless aggregation and management for every business.
The new Retrospect Management Console interface is optimized for managing larger scale environments. We have moved the list of organizations and servers onto the left for easy navigation.
Retrospect Management Console now displays activities, sources, and backup sets for customers to drill down on.
Retrospect Management Console can also display scripts (only available with Retrospect Backup 16.5 engines).
Retrospect Management Console now lets customers create and edit ProactiveAI scripts for individual engines, and those changes are sent to each engine every minute. Customers can create destinations as well, including local disk sets, NAS disk sets, and cloud sets. Note that you cannot yet do file-level adjustments.
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.
Retrospect Backup engines contact the Retrospect Management Console every 60 seconds to provide real-time status updates and fetch any management instructions. The Retrospect Management Console does not initiate or maintain an active connection to the engines.
Note that as of March 5, 2019, deployment options are limited to ProactiveAI scripts with standard source containers ("All sources", "All local", "All clients", "All network", "All email") to cloud destinations with simple scheduling options. Support for local sources, local destinations including disk, scheduled scripts, and more extensive scheduling options will be available soon.
Using the same license on multiple engines will have unexpected consequences on Retrospect Management Console, including data switching back and forth between machines and deploying scripts to both machines.
Once you deploy a script to a machine using a cloud destination, you cannot change the name of the backup server, as it is used as part of the path in the cloud destination.
Real-Time Monitoring - See a real-time view of backups, including live activities and predictive storage usage.
Access Anywhere - Monitor an entire backup infrastructure or multi-tenant client base from any desktop or mobile device, with your own portable Backup-Operations-Centre.
Every Retrospect Edition - Retrospect Management Console supports every edition of Retrospect Backup, from Solo to Multi Server Premium.
Dashboard Aggregation - Analyze the status of the entire organization’s Retrospect engine infrastructure with engine and organization aggregation.
Organization Drilldown - Create different organizations for separate business locations or corporate clients to partition the engine information and enable organization-level drilldown.
Distributed Management - Deploy new backup configurations to every Retrospect engine or only a specific subset. See details.
You can move a machine (engine) between organizations with the following steps:
In Retrospect Management Console, navigate to the list of machines.
Delete the machine you would like to move.
Navigate to the organization you would like to move the machine to.
Copy its UUID.
In Retrospect Backup, open Preferences and navigate to Retrospect Management Console preferences.
Add the new UUID to the "Organization UUID" field.
The "Machine UUID" will update on the next sync with Retrospect Management Console, and your engine’s data will show up under the new organization.
If you receive the error "The management console requires an organization UUID and so the option was turned off." on Windows, please check that you added both the Organization UUID and the backup server name.
If you see a red error icon in the dashboard, it means that your Retrospect instance is sending too much data. Please contact Support to diagnose the issue.
For Retrospect Backup:
Go to Preferences.
Go to Management Console.
Uncheck "Enable Management Console".
For Retrospect Virtual:
Go to your folder with
Retrospect_Virtual_Web_Integration_Unregister and select "Run as Administrator".
The Retrospect Management Console uses the organization UUID to link a Retrospect Backup instance to the correct organization. Within the organization, the Retrospect Backup application license is used to uniquely identify the data for that instance. If the application license is used by more than one instance (for example, re-using a trial license), then the data from the most recent communication from one of those instances will appear.