Your services are now shown by engine

Modified on Wed, 2 Sep at 11:38 AM

From version 3.3, My2Cloud names each service by the technology - the "engine" - that powers it, and the menu section once called "Services" is now called "Engines". Nothing about your protection has changed; only the labels are different.

Nothing to do. This is a naming change only. Your logins, permissions, service links and any integrations continue to work exactly as before, and you will find the same views and reports in the same place under their new engine names.

What changed

Previously the left-hand menu listed your services under a heading called Services, using Assurestor's product brand names such as Backup2Cloud and DR2Cloud. From version 3.3 onward, that heading is now Engines, and each service is labelled by the underlying technology that provides it.

So Backup2Cloud now appears as Asigra, DR2Cloud as Zerto, and so on. It is the same service in every case, simply named after the engine you already know.

The new names

Here is how each old brand name maps to its new engine name:

You used to seeYou now see
Backup2CloudAsigra
DR2CloudZerto
SaaS2CloudCloudAlly
SaaS2Cloud NGHYCU
Veeam2CloudVeeam

the left-hand menu before and after the change. The "Services" heading becomes "Engines", and each brand name is replaced by the engine that powers it.

the left-hand menu before and after the change. The "Services" heading becomes "Engines", and each brand name is replaced by the engine that powers it.

Is my protection affected?

No. This is purely a change to how things are labelled. In particular:

  • It is the same data, drawn from the same accounts, shown in the same views.
  • Your reports are unchanged - the same figures, presented the same way.
  • Your logins, permissions and service links continue to work exactly as before.
  • Any integrations you rely on carry on unaffected.

You do not need to take any action. The next time you sign in you will simply see the new engine names in the menu.

Two practical notes

Bookmarks

The web address (URL) of each page now uses the engine name too. For example, a page that used to sit under a brand name now appears under a path such as /app/main/asigra or /app/main/zerto. If you have bookmarked a specific page in your browser, the old bookmark may no longer lead straight to it, so it is worth opening the page from the menu once and re-saving the bookmark.

Alert emails

Alert emails now show the engine name as well. An alert that previously referred to Backup2Cloud, for instance, will now refer to Asigra. The alert itself, and when you receive it, are unchanged.

Why we made this change

Naming each service by its engine makes My2Cloud consistent with the underlying platforms you already use, and removes any ambiguity about which technology protects each workload. When you see Zerto or Veeam in the portal, it matches exactly what you would see and hear when talking about that technology elsewhere.

Still have a question? If anything looks unfamiliar after the change, raise a ticket from Support › Tickets and our team will be happy to help.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article