I feel you DAG client configuration may be wrong. You said that you have created the Physical clients with Backup IP, but the DAG might not have Backup IP and while you are creating the client for DAG it would be trying to look for the clients with the Actual DNS Names. You can check by creating the clients with the Actual DNS names.
Client configuration looks perfect. EMC engineers already check it couple of times
What else I can check on DAG end to make this configuration work.
I understand the VLAN are different for PROD and BACKUP but both have inter trust. so the communication between both VLANs is perfect. (No Firewall in picture)
On DAG end has the access to use backup IP for communication.
I completely agree, that I need to create clients by using PROD name if this configuration doesn't work
I m wondering if I could make this work as per this configuration.
Not sure about the below point.
Can I assign backup IP for DAG name : I am expecting answer as no, but if it's yes how it will work with networker and Exchange communication.
I don't think you can assign Backup IP to the Cluster. I am not really certain that the current configuration would work, You can check with Support. We have configured backup for a similar configuration for a customer where we created Clients with the PROD names and then let DDBoost ifgroup route the backups using the backup Network.
Nitesh_Turkar
32 Posts
0
July 18th, 2016 07:00
ERROR message on NMC : New
APPLICATIONS:\Microsoft Exchange 2013: Backup of [APPLICATIONS:\Microsoft Exchange 2013] failed
_vss_save: DB EURCWSMDBEU004
99145:nsrsnap_vss_save: DB EURCWSMDBEU003
99145:nsrsnap_vss_save: DB EURCWSMDBNA005
99145:nsrsnap_vss_save: DB EURCWSMDBNA006
99145:nsrsnap_vss_save: DB EURCWSMDBNA004
99145:nsrsnap_vss_save: DB EURCWSMDBEU002
99145:nsrsnap_vss_save: DB EURCWSMDBNA002
99145:nsrsnap_vss_save: DB EURCWSMDBNA001
99145:nsrsnap_vss_save: DB EURCWSMDBEU009
99145:nsrsnap_vss_save: DB EURCWSMDBEU001
63320:nsrsnap_vss_save:NMM has detected that no valid saveset entries have been requested.
nsrsnap_vss_save: Exchange federated .. backup did not complete and no data was backed up.
07/18/16 14:10:55.728936 Unregistered session id:2, fd:2104, idx:1, ssn_max_pollfd:1, 1(512)
97614:nsrsnap_vss_save:nsrsnap_vss_save: Exchange federated .. createInstantBackup failed with error 0xc0000001 Fatal error and cannot continue.
nsrsnap_vss_save(382): Entering SendRecoverJobFailure().
Internal error.
07/18/16 14:10:55.734940 Unregistered session id:1, fd:1004, idx:0, ssn_max_pollfd:0, 0(512)
nsrsnap_vss_save(394): Exiting SendBackupJobFailure().
nsrsnap_vss_save: Sending backup status to nsrsnap
102333 1468843855 3 0 0 39032 51848 0 eurcwsmsg104.cws.sasol.com nsrsnap_vss_save NSR error 21 Exiting with failure. 0
07/18/16 14:11:05.012767 Unregistered session id:1, fd:1924, idx:0, ssn_max_pollfd:0, 0(512)
Nitesh_Turkar
32 Posts
0
July 18th, 2016 13:00
All DBs are in Healthy state and mounted.
gautamgp
226 Posts
0
July 19th, 2016 09:00
Nitesh Bhai,
I feel you DAG client configuration may be wrong. You said that you have created the Physical clients with Backup IP, but the DAG might not have Backup IP and while you are creating the client for DAG it would be trying to look for the clients with the Actual DNS Names. You can check by creating the clients with the Actual DNS names.
Nitesh_Turkar
32 Posts
0
July 21st, 2016 09:00
Hey
Client configuration looks perfect. EMC engineers already check it couple of times
What else I can check on DAG end to make this configuration work.
I understand the VLAN are different for PROD and BACKUP but both have inter trust. so the communication between both VLANs is perfect. (No Firewall in picture)
On DAG end has the access to use backup IP for communication.
I completely agree, that I need to create clients by using PROD name if this configuration doesn't work
I m wondering if I could make this work as per this configuration.
Not sure about the below point.
Regards
gautamgp
226 Posts
0
July 21st, 2016 20:00
I don't think you can assign Backup IP to the Cluster. I am not really certain that the current configuration would work, You can check with Support. We have configured backup for a similar configuration for a customer where we created Clients with the PROD names and then let DDBoost ifgroup route the backups using the backup Network.