Abstract: An embodiment may involve server devices arranged into pods, each server device hosting computational instances, and a central computational instance configured to: (i) obtain per-pod lists of the instances hosted by the pods; (ii) determine a maximum number of the instances to arrange into batches; (iii) determine a group size for groups of the instances that are to be placed into the batches; (iv) execute a first phase that involves removing per-pod groups from the per-pod lists and adding them to the batches, until less of the instances than the group size remains in each of the per-pod lists; (v) execute a second phase that involves removing one of the instances from the per-pod lists and adding it to the batches, until none of the instances remains in any of the per-pod lists; and (vi) schedule one or more of the automations to take place in the data center.

Abstract: An embodiment may involve server devices arranged into pods, each server device hosting computational instances, and a central computational instance configured to: (i) obtain per-pod lists of the instances hosted by the pods; (ii) determine a maximum number of the instances to arrange into batches; (iii) determine a group size for groups of the instances that are to be placed into the batches; (iv) execute a first phase that involves removing per-pod groups from the per-pod lists and adding them to the batches, until less of the instances than the group size remains in each of the per-pod lists; (v) execute a second phase that involves removing one of the instances from the per-pod lists and adding it to the batches, until none of the instances remains in any of the per-pod lists; and (vi) schedule one or more of the automations to take place in the data center.

Abstract: Input information comprising an identifier of a production instance is received. The input information indicating a given time a live database from the production instance is to be restored to in a temporary copy of the production instance. Based at least on the input information, backup data associated with the live database from production instance is identified. Based on the backup data, it is determined whether resource capacity is available for restoring the backup data to the temporary copy of the production instance. In response to determining the resource capacity is available, the temporary copy of the production instance is generated. The backup data is restored to the temporary copy of the production instance to represent a state of the live database from the production instance at the given time.

Abstract: Input information comprising an identifier of a production instance is received. The input information indicating a given time a live database from the production instance is to be restored to in a temporary copy of the production instance. Based at least on the input information, backup data associated with the live database from production instance is identified. Based on the backup data, it is determined whether resource capacity is available for restoring the backup data to the temporary copy of the production instance. In response to determining the resource capacity is available, the temporary copy of the production instance is generated. The backup data is restored to the temporary copy of the production instance to represent a state of the live database from the production instance at the given time.