Ransomware Detection and the ServiceNow integration were covered in last month’s Druva bulletin. This one picks up everything else that has shipped since — the client versions, the agent builds, and two changes that will quietly break a workflow if nobody reads them.
Check your eDiscovery client version first
Two items here, and they belong together.
Versions below 2.4.0 are missing the useful bit. eDiscovery Download Client 2.4.0 can download Legal Hold custodian data — both metadata and custodian data — directly to NAS. Previously administrators had to pull large datasets down to local storage and then move them. For GB- and TB-scale legal-hold collections that removes local disk capacity as the limiting factor, which is usually the thing that makes a collection take two days instead of one.
Versions below 2.3.0 are end of life. Druva has deprecated eDiscovery Download Client versions older than 2.3.0 because of the transition to new DigiCert G2 root CA certificates. This is a certificate-chain change, so an old client does not degrade gracefully — it stops working. If legal hold is part of what you sell, audit client versions before someone needs a collection urgently.
inSync Client 8.1.5
Windows. Released with minor bug fixes, rolling out in phases.
macOS. Version r110985, adding support for macOS 27 (Golden Gate).
One requirement to carry into any macOS deployment: Druva needs Location Services permissions granted to both inSync Client and inSyncDataplane so it can properly regulate network connections for backup activity. If you push the client through MDM without that permission in the profile, backups will behave unpredictably and the cause will not be obvious.
New workload agents and proxies
| Workload | September version | Change |
|---|---|---|
| OpenStack | 7.0.0-1056138 | New feature |
| Proxmox | 7.0.0-1039288 | Enhancement |
| TurboTier | 6.3.4-1047411 / 6.3.4-1046038 | Updated versions |
Druva recommends upgrading agents and proxies to the latest versions for performance and compatibility. If you have customers running Proxmox or OpenStack, these are the two to action.
The Salesforce restore UI has been renamed around you
Druva has redesigned the Salesforce backup and restore experience, and the navigation has moved as well as the labels:
| Previously | Now |
|---|---|
| Environment Hub | Organization Hub |
| Restore & Seeding | Seeding |
| Data Archival | Archival |
| Restore templates | Standalone execution |
Restore workflows now start from the Backup tab, and existing Data Restore workflows may need to be migrated to the new restore workflow. That is the sentence to act on. Any runbook or recovery document that names the old screens is now wrong, and a restore is the worst moment to find that out.
Export device mappings to CSV
Administrators can export the complete device-mapping inventory to CSV from the Endpoints console. Useful for audit, compliance, device inventory, user and device mapping, troubleshooting, and customer reporting — particularly if you have been assembling that list by hand each quarter.
30-day trials for three more workloads
Druva has added the ability to start 30-day free trials for Okta, Active Directory and Microsoft Dynamics 365. Both prospective and existing customers can evaluate them, subject to regional availability. If you have been having the identity-backup conversation without a way to let a customer try it, that gate is now open.
FedRAMP GovCloud: Centralized Reporting
Centralized Reporting is now the primary reporting experience for FedRAMP GovCloud. Workload information is reached through the unified Druva Cloud Platform Console under Global Navigation → Reports, giving consolidated workload visibility and audit-oriented reporting.
Dark mode
The Cloud Console now offers Dark, Light or System Default. Small, but the people who live in that console all day will notice.
Want help with the version audit?
Arrosoft manages Druva environments for partners and their customers across APAC and North America. If you would like us to check which eDiscovery and inSync client versions your estate is running before the EOL bites, or plan the Salesforce restore-workflow migration, get in touch.