Data and configuration integrity checking post-rollback using backups in virtualized computing environments

Patent metadata

Field	Value
Publication number	US-11567672-B2
Application number	US-202117349936-A
Country	US
Kind code	B2
Filing date	Jun 17, 2021
Priority date	Jun 17, 2021
Publication date	Jan 31, 2023
Grant date	Jan 31, 2023

Abstract

A rollback can be performed after completing an upgrade to components of a virtualized computing environment. When the upgrade is performed, an upgrade bundle having rollback scripts is provided to edges, hosts, and managers in the virtualized computing environment that are to be upgraded. When a rollback is to be performed, the rollback scripts are executed, and the components are rolled back in a reverse order relative to their upgrade order. Data and configuration checking are performed to validate the results of the rollback.

First claim

We claim:

1. A method to perform integrity checking for a rollback in a virtualized computing environment having an edge, a host, and a manager, the method comprising:
in response to a request to perform an upgrade, from a first version to a second version, of the edge, the host, and the manager, making a pre-upgrade backup of data and configuration files of the edge, the host, and the manager;
after the upgrade is completed and in response to a rollback from the second version to the first version, making a post-rollback backup of data and configuration files of the edge, the host, and the manager;
comparing the pre-upgrade backup with the post-rollback backup to determine an amount of matching between the pre-upgrade backup with the post-rollback backup; and
validating post-rollback integrity of the data and configuration files in the edge, the host, and the manager, in response to the amount of matching meeting a threshold level of confidence.

2. The method of claim 1 , wherein in response to the amount of matching failing to meet the threshold level of confidence, generating an alert to perform investigation of differences between the backups.

3. The method of claim 1 , further comprising preventing the upgrade from proceeding, in response to a failure to make the pre-upgrade backup.

4. The method of claim 1 , further comprising storing the pre-upgrade backup at a backup server that separately manages node-level backups from cluster-level backups.

5. The method of claim 4 , wherein:
the node-level backups include data and configuration files of individual hosts, edges, and managers,
the cluster-level backups include data and configuration files of clusters of edges, managers, and controllers, and cluster policies, and
the backup server further stores inventory files at node and cluster levels.

6. The method of claim 1 , wherein making the pre-upgrade backup and making the post-rollback backup are performed in response to user selection of an integrity checking option.

7. The method of claim 1 , further comprising providing a user interface that enables:
selection of configuring periodic backup or one-time backup; and
tracking of rollback and validation.

8. A non-transitory computer-readable storage medium that includes instructions which, in response to execution by a processor, cause the processor to implement a method to perform integrity checking for a rollback in a virtualized computing environment having an edge, a host, and a manager, wherein the method comprises:
in response to a request to perform an upgrade, from a first version to a second version, of the edge, the host, and the manager, making a pre-upgrade backup of data and configuration files of the edge, the host, and the manager;
after the upgrade is completed and in response to a rollback from the second version to the first version, making a post-rollback backup of data and configuration files of the edge, the host, and the manager;
comparing the pre-upgrade backup with the post-rollback backup to determine an amount of matching between the pre-upgrade backup with the post-rollback backup; and
validating post-rollback integrity of the data and configuration files in the edge, the host, and the manager, in response to the amount of matching meeting a threshold level of confidence.

9. The non-transitory computer-readable storage medium of claim 8 , wherein the operations further comprise:
in response to the amount of matching failing to meet the threshold level of confidence, generating an alert to perform investigation of differences between the backups.

10. The non-transitory computer-readable storage medium of claim 8 , wherein the operations further comprise:
preventing the upgrade from proceeding, in response to a failure to make the pre-upgrade backup.

11. The non-transitory computer-readable storage medium of claim 8 , wherein the operations further comprise:
storing the pre-upgrade backup at a backup server that separately manages node-level backups from cluster-level backups.

12. The non-transitory computer-readable storage medium of claim 11 , wherein:
the node-level backups include data and configuration files of individual hosts, edges, and managers,
the cluster-level backups include data and configuration files of clusters of edges, managers, and controllers, and cluster policies, and
the backup server further stores inventory files at node and cluster levels.

13. The non-transitory computer-readable storage medium of claim 8 , wherein making the pre-upgrade backup and making the post-rollback backup are performed in response to user selection of an integrity checking option.

14. The non-transitory computer-readable storage medium of claim 8 , wherein the operations further comprise:
providing a user interface that enables:
selection of configuring periodic backup or one-time backup; and
tracking of rollback and validation.

15. A computer system, comprising:
a processor; and
a non-transitory computer-readable storage medium coupled to the processor and that includes instructions which, in response to execution by the processor, cause the processor to perform operations for integrity checking for a rollback in a virtualized computing environment having an edge, a host, and a manager, wherein the operations comprise:
in response to a request to perform an upgrade, from a first version to a second version, of the edge, the host, and the manager, make a pre-upgrade backup of data and configuration files of the edge, the host, and the manager;
after the upgrade is completed and in response to a rollback from the second version to the first version, make a post-rollback backup of data and configuration files of the edge, the host, and the manager;
compare the pre-upgrade backup with the post-rollback backup to determine an amount of matching between the pre-upgrade backup with the post-rollback backup; and
validate post-rollback integrity of the data and configuration files in the edge, the host, and the manager, in response to the amount of matching meeting a threshold level of confidence.

16. The computer system of claim 15 , wherein the operations further comprise:
in response to the amount of matching failing to meet the threshold level of confidence, generate an alert to perform investigation of differences between the backups.

17. The computer system of claim 15 , wherein the operations further comprise:
prevent the upgrade from proceeding, in response to a failure to make the pre-upgrade backup.

18. The computer system of claim 15 , wherein the operations further comprise:
store the pre-upgrade backup at a backup server that separately manages node-level backups from cluster-level backups.

19. The computer system of claim 18 , wherein:
the node-level backups include data and configuration files of individual hosts, edges, and managers,
the cluster-level backups include data and configuration files of clusters of edges, managers, and controllers, and cluster policies, and
the backup server further stores inventory files at node and cluster levels.

20. The computer system of claim 15 , wherein the operations to make the pre-upgrade backup and to make the post-rollback backup are performed in response to user selection of an integrity checking option.

21. The computer system of claim 15 , wherein the operations further comprise:
providing a user interface that enables:
selection of configuring periodic backup or one-time backup; and
tracking of rollback and

Assignees

• Vmware Inc

Inventors

• Shelke Prashant
• Bhatewara Dipesh
• Gole Suraj
• Dhakate Neha Pratik

Classifications

• G06F9/45558

  Hypervisor-specific management and integration aspects · CPC title

• G06F3/067

  Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS] · CPC title

• G06F3/0664

  at device level, e.g. emulation of a storage device or system · CPC title

• G06F3/065

  Replication mechanisms · CPC title

• G06F3/0619 Primary

  in relation to data integrity, e.g. data losses, bit errors · CPC title