Unsolved
This post is more than 5 years old
1 Rookie
•
2 Posts
0
1718
July 8th, 2018 14:00
FLR fails for vProxy and Data Domain with NAT
Hi All
We are running a trial on Networker and are attempting to do a file level restore from VM that was backed up up to a Data Domain. The Data Domain is on a different network behind firewalls and NAT is used.
From the vProxy logs we see the nfs add from the Data Domain but its using hard codes IP addresses.
2018/07/06 14:43:59 TRACE: [@(#) Build number: 194] Output of 'nfs add /data/col1/kdc-nsrvf1/FLR-IRTTENVP01-00e3c487-b721-45d6-9789-83be01dacb44 10.33.160.75 fe80::250:56ff:fe93:2ec0 10.97.167.48 fe80::225:b5ff:fe03:22c (rw,no_root_squash,no_all_squash,secure)' on host 'kdc-dd1.bus':
2018/07/06 14:43:59 TRACE: [@(#) Build number: 194] NFS export for "/data/col1/kdc-nsrvf1/FLR-IRTTENVP01-00e3c487-b721-45d6-9789-83be01dacb44" added.
It then fails to create the datastore I'm assuming because the Data Domain knows nothing about those IPs as they are real addresses - not the NATed ones that would be expected on the Data Domain network side.
2018/07/06 14:43:59 INFO: [@(#) Build number: 194] Removing NFS export at 'kdc-dd1.bus:/data/col1/kdc-nsrvf1/FLR-IRTTENVP01-00e3c487-b721-45d6-9789-83be01dacb44'
2018/07/06 14:44:01 TRACE: [@(#) Build number: 194] Output of 'nfs del /data/col1/kdc-nsrvf1/FLR-IRTTENVP01-00e3c487-b721-45d6-9789-83be01dacb44 10.33.160.75 fe80::250:56ff:fe93:2ec0 10.97.167.48 fe80::225:b5ff:fe03:22c' on host 'kdc-dd1.bus.unisys.net.nz':
2018/07/06 14:44:01 TRACE: [@(#) Build number: 194] Deleted 4 NFS clients.
2018/07/06 14:44:01 TRACE: [@(#) Build number: 194] (End of command output)
2018/07/06 14:44:01 INFO: [@(#) Build number: 194] Unmounting after mount failure: Unable to create datastore 'EMC-FLR-IRTTENVP01-1525389553' using 'kdc-dd1.bus:/data/col1/kdc-nsrvf1/FLR-IRTTENVP01-00e3c487-b721-45d6-9789-83be01dacb44': ServerFaultCode: An error occurred during host configuration.
2018/07/06 14:44:01 TRACE: [@(#) Build number: 194] Entering doUnmount
2018/07/06 14:44:01 TRACE: [@(#) Build number: 194] Connecting to backup device 'kdc-dd1.bus'
2018/07/06 14:44:02 NOTICE: [@(#) Build number: 194] DD Model = "DD6300", DDOS Version = "Data Domain OS 6.1.0.21-579789", DD Boost Version = "3.4.0.4-569771".
2018/07/06 14:44:02 INFO: [@(#) Build number: 194] Releasing datastore '' ()
2018/07/06 14:44:02 INFO: [@(#) Build number: 194] Removing NFS export at 'kdc-dd1.bus:/data/col1/kdc-nsrvf1/FLR-IRTTENVP01-00e3c487-b721-45d6-9789-83be01dacb44'
2018/07/06 14:44:03 ERROR: [@(#) Build number: 194] Unable to remove NFS export at 'kdc-dd1.bus.unisys.net.nz:/data/col1/kdc-nsrvf1/FLR-IRTTENVP01-00e3c487-b721-45d6-9789-83be01dacb44': Unable to run SSH command, error Unable to get command output of 'nfs del /data/col1/kdc-nsrvf1/FLR-IRTTENVP01-00e3c487-b721-45d6-9789-83be01dacb44 ', error Process exited with: 34. Reason was: ()
We want the vProxy to use the hostnames - not the IPs. Does this suggest the vProxy is not supported for NAT. I can't find anything in the documentation on this?
Any help would be appreciated.
Thanks
Craig
Gruchmen
1 Message
0
September 13th, 2018 07:00
I suppose the NAT shouldn't be blamed, because I have the similar LAB environment like you, but all on the same network segment, with no NAT nor routers/firewalls and got exactly the same issue.
murfcraig
1 Rookie
•
2 Posts
1
September 16th, 2018 14:00
For us it definitely was the NAT between the vProxy and the Data Domain. I got official word from EMC support stating " as this configuration has not been tested by EMC it is not supported". Interesting response and certainly no indications in any documentation.
We managed to remove the NAT eventually and this fixed the issue. Successfully doing FLRs now.