The following features and enhancements are now available with the release of Bocada 20.1.2:
LiveVault Enterprise Cloud Backup
Expanded visibility into cloud backup with LiveVault backup and storage reporting, providing visibility and insight into backup status, storage utilization and trends, consumption forecasting, and capacity alerting.
ServiceNow Incident Integration
Expanded capabilities to allow automated population of any incident field present in the ServiceNow instance, including backup error messages, assignment groups, affected assets and other information to further automate the ticket management workflow.
Commvault Client Computer Group Support
Added Commvault Client Computer Group to the Bocada data field, “Job Group” to better identify jobs in reports and enhance automation when assigning client to zones via rules.
Commvault Storage Policy Support
Added Commvault Storage Policy Name to the Bocada data field, “Job Group” to better identify jobs in reports and enhance automation when assigning client to zones via rules.
Avamar Policy Name Support
Added Avamar Policy Name to the Bocada data field, “Job Group” to better identify jobs in reports and enhance automation when assigning clients to zones via rules.
Avamar Contact and Zoning with Contact Rules
Avamar Contact information is now collected with backup metadata and presented in backup and client reports alongside jobs. Additionally, the contact filter in Bocada Rules enables clients to be assigned to zones based on names or partial names of contacts.
Streamlined Criteria Builder
Continued to improved user experience by rolling out the streamlined criteria builder within an additional 23 reports.
Regional Date Settings for Trends Reports
Added capability to view the Job Trends, Consecutive Failures, and Failure Trends reports as DD/MM in addition to the default MM/DD format.
Scheduled Report Email
Added the capability to specify an email subject and message text for reports scheduled for automated email distribution.
Microsoft SQL Server Backup
Added visibility into each file backed up during the database backup by splitting out each file into separate jobs, as reported in MSSQL.
Improved the report by ignoring no attempts on current day when considering failure. Because the day is typically not complete, this previously introduced unwanted noise.