cancel
Showing results for 
Search instead for 
Did you mean: 

How to take backup in cluster environment.

Mehul_Pal
Level 5

Hi,

 

we have 2 nodes for 1 cluster

the problem is last week there were more than tb;s of backup however this week full backup was lesser than last week in gbs

 

We have configured the nodes like this

 

DFSR in a different policy 

Drive paths in single policy

 

6 REPLIES 6

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

How is DFSR policy configured?

What is in Backup Selection?
Ensure that all DFSR data is selected in SCC path.

What is in Clients tab?
Virtual hostname should be selected, not nodename(s)

 

Yes we are taking node level backup

Backup selection for dfsr policy


Shadow Copy Components:\User Data\Distributed File System Replication\DfsrReplicatedFolders

For the other policy in which we are taking per drive basis backup

 

NEW_STREAM
C:\
NEW_STREAM
D:\
NEW_STREAM
E:\
NEW_STREAM
G:\
NEW_STREAM
K:\
NEW_STREAM
L:\
NEW_STREAM
M:\
NEW_STREAM
O:\
NEW_STREAM
System State:\

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

As per my previous post - for DFSR policy the Client name should be Vritual Hostname.

yes the client name for dfsr is the node name

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Client name for DFSR policy should NOT be the nodename.

I've been trying to tell you that the client name should be the Virtual hostname associated with the Cluster Group.... 

If the nodename is used in DFSR policy, you will you or NetBackup know when a failover has taken place and that backup should be taken from another node?

This is why we cluster applications and why a Virtual IP and Hostname is assigned to the cluster. When failover happens, the Virtual IP and hostname also fails over to the new node and end users or applications can still access the clustered data with the same hostname/IP. 

 

Hi,

 

Both the nodes are active in the cluster I checked it with wintel

few drives are assigned to Node 1 , others on Node 2