We want to share an upcoming change applicable to Metallic customers who are using VM V1 indexes. If you see an in product notification about this upgrade then this FAQ is applicable to your environment.
This is a backend upgrade process with no direct impact to customer operations. This upgrade greatly improves the overall backup and restore efficiency. Below is an FAQ regarding the upcoming V1 to V2 migration plus links to additional documentation.
What is the purpose of this update?
Customers were asking for better control of operations with individual VMs, configuration of security settings for individual VMs, and other related VM improvements. VM V2 indexed client will enable those improvements for the customers.
Please see the documentation for additional details on the V2 indexing feature.
What is changing with this update?
The Metallic team is migrating the indexes of V1 hypervisor clients on all Metallic rings to V2. This is a backend upgrade process with no direct impact to any customers day-to-day operations.
As you can see in the picture below, the upgraded VM group keeps the existing name and the old group is renamed with suffix “_V1”. All the backup operations and clients are automatically transferred to the upgraded VM group. The backups on the old VM group have been disabled and will be visible until all the older backups expire. The same behavior is reflected for the hypervisors as well.
What is the impact to customers?
Existing VM V1 customers will be switched to the new hypervisor automatically. So, there is no impact to the day-to-day operations. The original VM group will be disabled, and older backups will naturally age based on their set retention. This will be done automatically so that no changes are necessary from the customer side.
NOTE: The first backup after migration will run as full, which may take longer time than usual depending on the size and number of VMs in the VM group.
When will this change happen?
The changes will occur beginning April 19, 2023, and will be executed on a ring-by-ring basis for Metallic customers using VM V1 indexes. Once live, impacted customers will also receive an in-product notification. Since this is a backend upgrade process, customers will not notice anything other than what is documented here. However, should you require further information, see the documentation, and post any questions here in the community or contact your CSM.