What is JobR?

JobR mines all your backup processes looking for potential data loss events, i.e. backup job failures, and empowers you to remediate these immediately. JobR highlights failed backup jobs from multiple domains and vendor technologies, so you can quickly get back to business as usual.

Unlike the vendor-provided management consoles or monitoring tools, JobR proactively seeks out failure events through Process Mining and highlights these for your urgent action. Rules and automated remediations can be rapidly applied to immediate failed events and all future ones (should you wish to).

With JobR in play, Backup Admins are freed from repetitive, low-value tasks to focus on more strategic, high-value activities that contribute to the overall business objectives.

Key Features:

• Define the Backup Servers that you want to be monitored
• Use out-of-the-box remediations and define your own
• A single view of all your backup jobs, supporting multiple vendor technologies
• Create rules to automate actions when job failures occur, e.g. restart job, without logging into the vendor's backup console.

JobR isn't just another monitoring tool; it's proactive Process Mining designed specifically for Backup and Recovery processes. Proactively managing your backup job failures means that business users can rest assured that their data will always be backed up and available, and Backup Admins.

• Can mitigate data loss situations and rectify the situation immediately
• Can create rules so JobR can automate repetitive tasks, thus freeing up time to do higher-value activities
• Federate all your Backup technologies into a single view and management layer.

System Requirements/Prerequisites

• MId Server. You must have a working Windows MID Server on the instance. When you create a new Data Source, you will have the option to specify which MID Server to use. Please see the section on MID Security Policy. The MID Server must be able to access the servers you wish to collect data from.
• For each data protection system that will be included in JobR, the relevant admin must provide credentials for an admin account and the REST API URL
• JobR supports Azure Backup Vaults, it uses API v2023-02-01. It requires the configuration of a Service Principal in Azure with access to the required Backup Vaults. The REST API URL will be https://management.azure.com/subscriptions/[subscriptionid]/resourceGroups/[ResourceGroup]/providers/Microsoft.RecoveryServices/vaults/[VaultName]
• JobR supports Veritas NetBackup (minimum version:8.3), Veeam Enterprise Manager (minimum version:11), Commvault (v11.26.18 and above), and Cohesity (v6.6 and above).
• NetBackup, It is recommended to use API Key authentication. The NetBackup admin must obtain the API key for an administrator-level account and provide the REST API URL (typically https://masterserverURL)
• Veeam Enterprise Manager: JobR supports Veeam, version 11 and above. It is recommended to use basic authentication. The Enterprise Manager REST API URL (typically https:/VeeaEMURL:9398) is required along with credentials (user ID and password) for an administrator-level account.
• Commvault: It is recommended to use basic authentication. The core Commvault URL (typically https://cellname) is required along with credentials (user ID and password) for an administrator-level account. The password needs to be base64 encoded, you can use an online encoding site like Base64 Encode and Decode - Online
• Cohesity: It is recommended to use basic authentication. The core Cohesity URL (typically https://clustername) is required along with credentials (user ID and password) for an administrator-level account. 
• Rubrick CDM: JobR supports Rubrik CDM v6 and above. It is recommended to use basic authentication. The core Rubrik URL (typically https://node) is required along with credentials (user ID and password) for an administrator-level account.
• A Data Management administrator may be required to provide additional information.