Backup using instinctive preferred server order list (PSOL)

• US 10,095,588 B1
• Filed: 04/24/2017
• Issued: 10/09/2018
• Est. Priority Date: 07/08/2014
• Status: Active Grant

• Current Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Original Assignee: Emc IP Holding Company LLC (Dell Technologies Inc.)
• Inventors: Chopra, Shelesh, Chandrakandi, Shoukathali, Raghunathan, Gajendran, Gonugunta, Sainath
• Primary Examiner(s): Coby, Frantz
• Application Number:
  US15/495,807
• Time in Patent Office: 533 Days
• Field of Search: 707770, 707640, 707769, 707704, 707649, 707650, 707652, 707653, 709203, 709226, 709222, 714 41, 714 473
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/1453 using de-duplication of the data
• CPC Class Codes: G06F 11/1456 Hardware arrangements for backup
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 11/202 where processing functionality is redundant redundant communication control functionality G06F11/2005, redundant storage control functionality G06F11/2089
• CPC Class Codes: G06F 11/2035 without idle spare hardware
• CPC Class Codes: G06F 16/128 Details of file system snapshots on the file-level, e.g. snapshot creation, administration, deletion use of snapshots for error detection or correction G06F11/14, G06F11/16
• CPC Class Codes: G06F 16/2379 Updates performed during online database operations; commit processing
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 2201/80 Database-specific techniques

Abstract

In one example, a method for data backup includes surveying a database availability group (DAG) that includes multiple nodes which are each associated with one or more databases, to determine a distribution of the databases across the nodes. Next, federated logic is used to create a profile of the DAG based on the survey, and the profile is used to generate a dynamic preferred server order list (PSOL). Load balancing for the DAG is performed using the dynamic PSOL, and the dynamic PSOL is updated based on results of the load balancing. Finally, a federated backup of the databases is performed based on the updated dynamic PSOL.

Claims

1. A method, comprising:

surveying a database availability group (DAG) that includes a plurality of nodes which are each associated with one or more databases, to determine a distribution of the databases across the nodes;

using federated logic to create a profile of the DAG based on the survey;

using the profile to generate a dynamic preferred server order list (PSOL);

performing load balancing for the DAG using the dynamic PSOL;

updating the dynamic PSOL based on results of the load balancing; and

performing a federated backup of the databases based on the updated dynamic PSOL.

2. The method as recited in claim 1, wherein the profile includes an identification of a node with maximum ownership of databases.

3. The method as recited in claim 1, wherein the dynamic PSOL is based on the profile, a last activation preference for one of the databases, and a failover preference for one of the databases.

4. The method as recited in claim 1, wherein one of the databases is a passive database.

5. The method as recited in claim 1, wherein the dynamic PSOL is generated without manual intervention by a user.

6. The method as recited in claim 1, wherein one of the backed up databases is associated with a node that comprises an email server.

7. The method as recited in claim 1, further comprising:

receiving a notification of a change affecting one or more nodes and/or databases; and

automatically updating the dynamic PSOL based upon the occurrence of the change.

8. The method as recited in claim 7, wherein the change comprises one of a failover event, a change in the PSOL, a change in the last activation preference for one of the databases, and a change in a failover preference for one of the databases.

9. The method as recited in claim 1, wherein the federated backup generates a single saveset that spans all nodes of the DAG.

16. The non-transitory storage medium as recited in claim 1, wherein the processes further comprise:

receiving a notification of a change affecting one or more nodes and/or databases; and

automatically updating the dynamic PSOL based upon the occurrence of the change.

17. The non-transitory storage medium as recited in claim 16, wherein the change comprises one of a failover event, a change in the PSOL, a change in the last activation preference for one of the databases, and a change in a failover preference for one of the databases.

10. A non-transitory storage medium having stored therein computer-executable instructions which, when executed by one or more hardware processors, implement data backup in an environment, wherein the implementation of data backup comprises performing the following processes:

surveying a database availability group (DAG) that includes a plurality of nodes which are each associated with one or more databases, to determine a distribution of the databases across the nodes;

using federated logic to create a profile of the DAG based on the survey;

using the profile to generate a dynamic preferred server order list (PSOL);

performing load balancing for the DAG using the dynamic PSOL;

updating the dynamic PSOL based on results of the load balancing; and

performing a federated backup of the databases based on the updated dynamic PSOL.

11. The non-transitory storage medium as recited in claim 10, wherein the profile includes an identification of a node with maximum ownership of databases.

12. The non-transitory storage medium as recited in claim 10, wherein the dynamic PSOL is based on the profile, a last activation preference for one of the databases, and a failover preference for one of the databases.

13. The non-transitory storage medium as recited in claim 10, wherein one of the databases is a passive database.

14. The non-transitory storage medium as recited in claim 10, wherein the dynamic PSOL is generated without manual intervention by a user.

15. The non-transitory storage medium as recited in claim 10, wherein one of the backed up databases is associated with a node that comprises an email server.

18. The non-transitory storage medium as recited in claim 10, wherein the federated backup generates a single saveset that spans all nodes of the DAG.

19. A physical backup server, wherein the physical backup server comprises:

one or more hardware processors;

non-transitory computer readable media; and

computer-executable instructions stored on the non-transitory computer readable media and which, when executed by one or more of the hardware processors, implement data backup in an environment, wherein the implementation of data backup comprises performing the following processes;

surveying a database availability group (DAG) that includes a plurality of nodes which are each associated with one or more databases, to determine a distribution of the databases across the nodes;

using federated logic to create a profile of the DAG based on the survey;

using the profile to generate a dynamic preferred server order list (PSOL);

performing load balancing for the DAG using the dynamic PSOL;

updating the dynamic PSOL based on results of the load balancing; and

performing a federated backup of the databases based on the updated dynamic PSOL.

20. The physical backup server as recited in claim 19, wherein the processes further comprise:

receiving a notification of a change affecting one or more nodes and/or databases, wherein the change comprises one of a failover event, a change in the PSOL, a change in the last activation preference for one of the databases, and a change in a failover preference for one of the databases; and

automatically updating the PSOL based upon the occurrence of the change.