65 Posts

February 5th, 2016 13:00

the best option may be to open a support ticket or even a chat for a speedy response time.  I am not familiar with a setup that does not use the external IP addresses to connect to the DR cluster but that doesn't necessarily mean that is wrong but, I would ask what is the plan when/if you need fail over? wouldn't we need that up anyway? My experience with SyncIQ (somewhat limited) is that it uses the external IP's to actually connect.

articles that may help based on your OneFS version:

https://support.emc.com/docu65070_OneFS-8.0.0-Backup-and-Recovery-Guide.pdf?language=en_US

https://support.emc.com/docu60094_OneFS-7.2.1-Backup-and-Recovery-Guide.pdf?language=en_US

https://support.emc.com/docu56055_OneFS-7.2.0-Backup-and-Recovery-Guide.pdf?language=en_US

https://support.emc.com/docu50233_OneFS-7.1.0-Backup-and-Recovery-Guide.pdf?language=en_US

I dont think this to be your actual problem but it is good info if you have firewalls between source and target it lists the ports that OneFS uses

https://support.emc.com/kb/89545

2 Intern

 • 

205 Posts

February 5th, 2016 17:00

It may also be that the primary cluster has no static IP pools set up. I ran into this awhile back; apparently on newer versions of OneFS, synciq requires a statically allocated IP pool, rather than dynamically allocated. This can of course be a separate pool from your dynamic pool. I ended up setting up a pool specifically for synciq. Doesn't need a smartconnect zone or anything, just a pool of IPs in a routable subnet.

39 Posts

February 9th, 2016 00:00

Hello,

Do you have different smartconnect zone for synciq ?

What is preffered gateway for the zone ?

Did you tried giving a node ip in synciq policy and see if that works ?

Thanks

Chughh

No Events found!

Top