My2Cloud 3.1 Release Notes

Release: 3.1 
Date: July 2026 
Platforms: Backup2Cloud (Asigra), DR2Cloud (Zerto), SaaS2Cloud (CloudAlly), Veeam2Cloud (Veeam)

My2Cloud 3.1 builds on the 3.0 platform with two headline capabilities: self-service DS-Client and account lifecycle management for Backup2Cloud, and a SaaS2Cloud billing forecast. It also extends multi-factor authentication to protect destructive actions, hardens data collection, and adds a round of portal polish.

The notes below group every new and changed feature by area.

Backup2Cloud (Asigra) - DS-Client and account management

• New DS-Client Management for Backup2Cloud, mirroring the actions in the Asigra NOC: Lock, Unlock, Deactivate, Reactivate, Reset Hardware Token and Remove a DS-Client, and Lock, Unlock and Remove an account.

• Gated by a new DS-Client Management feature and per-action permissions, with a separate Destroy permission for the irreversible removes, so a tenant chooses exactly which users can manage and which can remove.

• State-aware menus: each action is only offered when it is valid for the target's current state (Unlock only when locked, Remove a DS-Client only when deactivated, Remove an account only when it has no DS-Clients).

• Lock padlocks surfaced in the DS-Clients list and the DS-Client detail modal header, with a locked-only / deactivated badge set, so state is clear at a glance.

• Every management action is re-checked server-side (the target must belong to the caller's tenant) and written to the audit log, with the confirming credential excluded from the log.

• Reset Hardware Token opens a re-registration window with a configurable timeout and is treated as a benign, self-healing action that does not require re-confirmation.

• Friendly NOC error handling: a DS-NOC rejection surfaces the NOC's own reason text rather than a raw fault, and the create / remove paths were hardened with clearer AMC errors.

SaaS2Cloud (CloudAlly) - Billing Forecast

• New Billing Forecast for SaaS2Cloud, both live and analytics, showing the CloudAlly next-payment forecast by account: billable quantities only, with no pricing exposed anywhere in the API or UI.

• A daily collector captures the forecast per account and service line (reseller and distributor-direct) into the analytics history.

• A dedicated Billing Forecast page under Services, grouped by account with expandable per-service rows (Service, Total quantity, Billable quantity), account and subscription-type filters, and a Monthly / Annual pill with a next-renewal tooltip.

• A Billing Forecast tab on the SaaS2Cloud analytics dashboard and the host Tenant Usage dashboard, showing the peak billable quantities over the selected range.

• Gated behind a Billing Forecast feature (under the SaaS2Cloud feature) and permission, so a tenant enables it per edition and grants it per user or role; the host always sees it. A dashboard tab whose widgets are all gated out is now hidden rather than left blank.

• SaaS2Cloud "Users" are renamed "Accounts" throughout the UI to match CloudAlly's terminology.

Security and multi-factor authentication

• Enhanced authenticator (MFA) experience: a modern six-box code entry in the Assurestor brand colours, used consistently across sign-in, setup and verification, with the enable / disable flow corrected so the two-factor state and login enforcement stay in step.

• Destructive Backup2Cloud actions now confirm with the acting user's authenticator code when they have two-factor enabled, falling back to their password when it is off. The rule is enforced server-side, so the API applies it however it is called, and the authenticator code (like the password) is never written to the audit log.

Data collection and observability

• The data collectors were split into a clear per-vendor structure for maintainability, with each collector reviewed for stability and logging.

• The Backup2Cloud collector always fetches fresh data from the NOC - it never serves cached data into the analytics history - so scheduled snapshots are always current.

• Extended vendor-API tracking: every outbound vendor call, including Freshdesk and Zoho Books, is timed and its cache use recorded, so slow or heavily-called endpoints can be reviewed.

• Backup2Cloud region names are resolved dynamically from the NOC rather than hard-coded, so a NOC region rename is picked up automatically.

Tenant provisioning

• The tenant create and edit modals can assign the Zoho Books customer and the Freshdesk company for a tenant, and only offer the billing and support selectors when the tenant's edition grants the corresponding feature.

Dashboards and interface polish

• Standardised on brand outline pills and a shared storage bullet-bar across the service views and dashboard widgets.

• Corrected the Backup2Cloud default dashboard widget order, and brought outline pills to the host Last Data Collection tooltip.

• Sub-header bar refined for a comfortable, consistently-centred height, and the fixed header and footer separated cleanly from scrolling content.

• Service and analytics pages now use the Assurestor service-brand names in their URLs (backup2cloud, dr2cloud, saas2cloud, veeam2cloud) in place of the vendor names.

Fixes

• Fixed a crash when creating a new role, and an error when logging in as a tenant from the host.

• Notifications modal and Clear Web Logs refinements, and host Recent / Failed Logins widgets.

Internationalisation

• Every new and reworded string is present in all locale files, seeded with the English source and ready for translation.

Platform

• Application version updated to 3.1 across the back end and front end.