If you changed it there, then I guess it is changed. It seems as if something is not yet changed (or cached). You may wish to take advantage of current DD DR session going at Ask the Expert: Using Data Domain Storage in your Disaster Recovery Plan and explain in detail what you had, what you did and what was the outcome. Though that session is not intended to do technical troubleshooting, from the steps made they might be able to spot what has been missed or what needs to be changed/checked.
Thanks for the suggestion I will look at that site.
I have one more finding, it could be the problem, but I still don't know how to fix it.
Our NetBackup Master Server for example the name of the cluster service is NBMSBCK (which is also the name of of the EMMSERVER) during the normal production it will reside on nbmspd01 server (hostname) during the DR it will reside on nbmsdr01 (hostname). And this is our finding:
on the Data Domain on the production and DR site:
During the normal Production
dd01bck# ddboost show connections
Active Clients: 2
Clients: Client Idle CPUs Memory(MiB) Plugin Version OS Version Application Version -------- ---- ---- ----------- -------------- -------------------------------------------------------------------- ------------------- XXXbck NO 24 16,373 2.5.0.3-314845 Microsoft Windows Server 2008 Service Pack 2 (build 6002), 64-bit NetBackup: 7.5.0.4 nbmspd01 NO 4 7,874 2.5.0.3-314845 Linux 2.6.32-131.0.15.el6.x86_64 x86_64 NetBackup: 7.5.0.4 YYYY YES 24 32,768 2.5.0.3-314845 Microsoft Windows Server 2008 R2 Service Pack 1 (build 7601), 64-bit NetBackup: 7.5.0.4 -------- ---- ---- ----------- -------------- -------------------------------------------------------------------- -------------------
During the DR (test)
dd01bck# ddboost show connections
Active Clients: 2
Clients: Client Idle CPUs Memory(MiB) Plugin Version OS Version Application Version -------- ---- ---- ----------- -------------- -------------------------------------------------------------------- ------------------- XXXbck NO 24 16,373 2.5.0.3-314845 Microsoft Windows Server 2008 Service Pack 2 (build 6002), 64-bit NetBackup: 7.5.0.4 nbmspd01 NO 4 7,874 2.5.0.3-314845 Linux 2.6.32-131.0.15.el6.x86_64 x86_64 NetBackup: 7.5.0.4 YYYY YES 24 32,768 2.5.0.3-314845 Microsoft Windows Server 2008 R2 Service Pack 1 (build 7601), 64-bit NetBackup: 7.5.0.4 -------- ---- ---- ----------- -------------- -------------------------------------------------------------------- -------------------
As you can see the active connection on normal Production and DR is going to nbmspd01 which is production server. Logically during the DR the connection should go to client nbmsdr01.
Obviously something wrong here. Is there any configuration need to change during the DR?
Thanks for the suggestion I will look at that site.
I have one more finding, it could be the problem, but I still don't know how to fix it.
Our NetBackup Master Server for example the name of the cluster service is NBMSBCK (which is also the name of of the EMMSERVER) during the normal production it will reside on nbmspd01 server (hostname) during the DR it will reside on nbmsdr01 (hostname). And this is our finding:
on the Data Domain on the production and DR site:
During the normal Production
dd01bck# ddboost show connections
Active Clients: 2
Clients:Client Idle CPUs Memory(MiB) Plugin Version OS Version Application Version
XXXbck NO 24 16,373 2.5.0.3-314845 Microsoft Windows Server 2008 Service Pack 2 (build 6002), 64-bit NetBackup: 7.5.0.4
nbmspd01 NO 4 7,874 2.5.0.3-314845 Linux 2.6.32-131.0.15.el6.x86_64 x86_64 NetBackup: 7.5.0.4
YYYY YES 24 32,768 2.5.0.3-314845 Microsoft Windows Server 2008 R2 Service Pack 1 (build 7601), 64-bit NetBackup: 7.5.0.4-------- ---- ---- ----------- -------------- -------------------------------------------------------------------- -------------------
As you can see the active connection on normal Production and DR is going to nbmspd01 which is production server. Logically during the DR the connection should go to client nbmsdr01.
Obviously something wrong here. Is there any configuration need to change during the DR?
I'm not so familiar with NB to be able to give you qualified answer, but it seems odd that it shows active connection to server which should be off. If I would need to guess, I would say nbmsdr01 IP is resolved to nbmspd01and this is why DD unit is reporting it this way. You did say DNS change was done so could it be that this is the reason? Eventually, you can check what does traceroute and nslookup do against nbmspd01 from DD unit.
ble1
4 Operator
•
14.4K Posts
0
January 27th, 2014 00:00
Is it possible that hosts records still show old IP?
iwantam
4 Posts
0
February 11th, 2014 17:00
Hi Hrvoje Crevlin,
How to check it? On the Data Domain I changed the master server IP manually.
ble1
4 Operator
•
14.4K Posts
2
February 12th, 2014 02:00
If you changed it there, then I guess it is changed. It seems as if something is not yet changed (or cached). You may wish to take advantage of current DD DR session going at Ask the Expert: Using Data Domain Storage in your Disaster Recovery Plan and explain in detail what you had, what you did and what was the outcome. Though that session is not intended to do technical troubleshooting, from the steps made they might be able to spot what has been missed or what needs to be changed/checked.
iwantam
4 Posts
0
February 12th, 2014 18:00
Hi Hrvoje Crvelin ,
Thanks for the suggestion I will look at that site.
I have one more finding, it could be the problem, but I still don't know how to fix it.
Our NetBackup Master Server for example the name of the cluster service is NBMSBCK (which is also the name of of the EMMSERVER) during the normal production it will reside on nbmspd01 server (hostname) during the DR it will reside on nbmsdr01 (hostname). And this is our finding:
on the Data Domain on the production and DR site:
During the normal Production
dd01bck# ddboost show connections
Active Clients: 2
Clients:
Client Idle CPUs Memory(MiB) Plugin Version OS Version Application Version
-------- ---- ---- ----------- -------------- -------------------------------------------------------------------- -------------------
XXXbck NO 24 16,373 2.5.0.3-314845 Microsoft Windows Server 2008 Service Pack 2 (build 6002), 64-bit NetBackup: 7.5.0.4
nbmspd01 NO 4 7,874 2.5.0.3-314845 Linux 2.6.32-131.0.15.el6.x86_64 x86_64 NetBackup: 7.5.0.4
YYYY YES 24 32,768 2.5.0.3-314845 Microsoft Windows Server 2008 R2 Service Pack 1 (build 7601), 64-bit NetBackup: 7.5.0.4
-------- ---- ---- ----------- -------------- -------------------------------------------------------------------- -------------------
During the DR (test)
dd01bck# ddboost show connections
Active Clients: 2
Clients:
Client Idle CPUs Memory(MiB) Plugin Version OS Version Application Version
-------- ---- ---- ----------- -------------- -------------------------------------------------------------------- -------------------
XXXbck NO 24 16,373 2.5.0.3-314845 Microsoft Windows Server 2008 Service Pack 2 (build 6002), 64-bit NetBackup: 7.5.0.4
nbmspd01 NO 4 7,874 2.5.0.3-314845 Linux 2.6.32-131.0.15.el6.x86_64 x86_64 NetBackup: 7.5.0.4
YYYY YES 24 32,768 2.5.0.3-314845 Microsoft Windows Server 2008 R2 Service Pack 1 (build 7601), 64-bit NetBackup: 7.5.0.4
-------- ---- ---- ----------- -------------- -------------------------------------------------------------------- -------------------
As you can see the active connection on normal Production and DR is going to nbmspd01 which is production server. Logically during the DR the connection should go to client nbmsdr01.
Obviously something wrong here. Is there any configuration need to change during the DR?
Regards,
Iwan
iwantam
4 Posts
0
February 12th, 2014 19:00
Hi Hrvoje Crvelin ,
Thanks for the suggestion I will look at that site.
I have one more finding, it could be the problem, but I still don't know how to fix it.
Our NetBackup Master Server for example the name of the cluster service is NBMSBCK (which is also the name of of the EMMSERVER) during the normal production it will reside on nbmspd01 server (hostname) during the DR it will reside on nbmsdr01 (hostname). And this is our finding:
on the Data Domain on the production and DR site:
During the normal Production
dd01bck# ddboost show connections
Active Clients: 2
Clients:Client Idle CPUs Memory(MiB) Plugin Version OS Version Application Version
-------- ---- ---- ----------- -------------- -------------------------------------------------------------------- -------------------
XXXbck NO 24 16,373 2.5.0.3-314845 Microsoft Windows Server 2008 Service Pack 2 (build 6002), 64-bit NetBackup: 7.5.0.4
nbmspd01 NO 4 7,874 2.5.0.3-314845 Linux 2.6.32-131.0.15.el6.x86_64 x86_64 NetBackup: 7.5.0.4
YYYY YES 24 32,768 2.5.0.3-314845 Microsoft Windows Server 2008 R2 Service Pack 1 (build 7601), 64-bit NetBackup: 7.5.0.4-------- ---- ---- ----------- -------------- -------------------------------------------------------------------- -------------------
During the DR (test)
dd01bck# ddboost show connections
Active Clients: 2
Clients:Client Idle CPUs Memory(MiB) Plugin Version OS Version Application Version
-------- ---- ---- ----------- -------------- -------------------------------------------------------------------- -------------------
XXXbck NO 24 16,373 2.5.0.3-314845 Microsoft Windows Server 2008 Service Pack 2 (build 6002), 64-bit NetBackup: 7.5.0.4
nbmspd01 NO 4 7,874 2.5.0.3-314845 Linux 2.6.32-131.0.15.el6.x86_64 x86_64 NetBackup: 7.5.0.4
YYYY YES 24 32,768 2.5.0.3-314845 Microsoft Windows Server 2008 R2 Service Pack 1 (build 7601), 64-bit NetBackup: 7.5.0.4-------- ---- ---- ----------- -------------- -------------------------------------------------------------------- -------------------
As you can see the active connection on normal Production and DR is going to nbmspd01 which is production server. Logically during the DR the connection should go to client nbmsdr01.
Obviously something wrong here. Is there any configuration need to change during the DR?
Regards,
Iwan Tamimi
ble1
4 Operator
•
14.4K Posts
0
February 13th, 2014 01:00
I'm not so familiar with NB to be able to give you qualified answer, but it seems odd that it shows active connection to server which should be off. If I would need to guess, I would say nbmsdr01 IP is resolved to nbmspd01 and this is why DD unit is reporting it this way. You did say DNS change was done so could it be that this is the reason? Eventually, you can check what does traceroute and nslookup do against nbmspd01 from DD unit.