Forum Discussion

PoNuts's avatar
PoNuts
Level 3
10 years ago

Backup cluster in a smartway

! Backing up a file cluster in a smart way

! Lets say that you have 3 clusters with 6nodes totally.

The setup

HostA1 HostA2 with ClusterA3 with three instance (not so sure about the terms here)

  • HostAClusterDBorange I:\
  • HostAClusterDBred J:\
  • HostAClusterDBblue K:\

HostB1 HostB2 with ClusterB3

  • HostBClusterDBblack I:\
  • HostBClusterDBgrey G:\
  • HostBClusterDBwhite Z:\

HostC1 HostC2 with ClusterC3.

  • HostCClusterDBgreen I:\
  • HostCClusterDByhellow J:\
  • HostCClusterDBmagenta H:\

The policys

Traditionally is that there will be in the policy configuration:

PolicyAHosts

  • HostA1
  • HostA2

PolicyAClusterOrange

  • HostAClustrerOrange

PolicyAClousterRed

  • HostAClusterRed

PolicyAClusterblue

  • HostAClusterBlue

... and next

... PolicyBHost... and so on..

There will be a lots of policys and as for me, Im not the DBa or who invent all those cluster adresses and so on.. so in some "fantasy" way I would like

One policy for the system host  (that could be done even in the above example). One policy for the instance like SQLinstances with target "all local drives".

Example:

PolicyClusterNodes ( here is no problem today, except that one is using c: and the other using C and D as system drives)

  • Host A1
  • Host A2
  • Host B1
  • Host B2
  • Host C1
  • Host C2

PolicyClusterDrives

  • HostAClusterDBorange I:\
  • HostAClusterDBred J:\
  • HostAClusterDBblue K:\
  • HostBClusterDBblack I:\
  • HostBClusterDBgrey G:\
  • HostBClusterDBwhite Z:\
  • HostCClusterDBgreen I:\
  • HostCClusterDByhellow J:\
  • HostCClusterDBmagenta H:\

(Here comes the problem in if i spec "Backup Selection" then i need to put in I,J,K,I,G,Z and so on... then i get an error like cant find the Z drive for hostA adn B). In the later scenario i got two policys to manage instead of our consultant who put up with like 300000 thousands of policys.. (a bit extremed).

 

 

  • Looking at your examples, the assumption is that the cluster virtual hostnames are:

    ClusterA3

    ClusterB3

    ClusterC3

    These virtual hostnames make the drive letters and/or Instances available to users and applications no matter on which physical nodes they are online, right?

    So, you need 3 policies (no scripting needed):

    1. ClusterA3 
    Client name: ClusterA3 
    Backup Selection: I:\ J:\ K:\

    2. ClusterB3 
    Client name: ClusterB3 
    Backup Selection: I:\ G:\ Z:\

    3. ClusterC3 
    Client name: ClusterC3 
    Backup Selection: I:\ J:\ H:\

     

    If these are hosting databases, your policy type should be for the appropriate DB agent with the backup script path in Backup Selection. Script should be on one of the shared drives.

     

1 Reply

  • Looking at your examples, the assumption is that the cluster virtual hostnames are:

    ClusterA3

    ClusterB3

    ClusterC3

    These virtual hostnames make the drive letters and/or Instances available to users and applications no matter on which physical nodes they are online, right?

    So, you need 3 policies (no scripting needed):

    1. ClusterA3 
    Client name: ClusterA3 
    Backup Selection: I:\ J:\ K:\

    2. ClusterB3 
    Client name: ClusterB3 
    Backup Selection: I:\ G:\ Z:\

    3. ClusterC3 
    Client name: ClusterC3 
    Backup Selection: I:\ J:\ H:\

     

    If these are hosting databases, your policy type should be for the appropriate DB agent with the backup script path in Backup Selection. Script should be on one of the shared drives.