EA ist required for this setup. You'll have to start with a reinstallation of CUA on the target, then setting up EA. Failover is a manual task. Failing back is troublesome in the way that the ancient primary needs to be configured as ea standby for the secondary. Then fail back , then configure the ea again pointing to the secondary site.
See the Centera Universal Access Monitor & Admin Guide. There is a good chapter on CUA EA in there.
In order to have a fail over CUA in the DR you need to configure EA between the active CUA in the main site & a CUA in the DR site, you cannot have two active CUAs at the same time & sync between them. You can also point the DR CUA to the DR Centera pre & during fail over
holgerjakob_c0722c
2 Intern
•
337 Posts
1
January 29th, 2016 06:00
Hi dsuarez
EA ist required for this setup. You'll have to start with a reinstallation of CUA on the target, then setting up EA. Failover is a manual task. Failing back is troublesome in the way that the ancient primary needs to be configured as ea standby for the secondary. Then fail back , then configure the ea again pointing to the secondary site.
See the Centera Universal Access Monitor & Admin Guide. There is a good chapter on CUA EA in there.
Holger
omarelmazny
19 Posts
1
January 29th, 2016 06:00
Hello dsuarez
In order to have a fail over CUA in the DR you need to configure EA between the active CUA in the main site & a CUA in the DR site, you cannot have two active CUAs at the same time & sync between them. You can also point the DR CUA to the DR Centera pre & during fail over
Dr.diSousa
1 Rookie
•
97 Posts
0
February 8th, 2016 05:00
Hi, reading Centera Universal Access Monitor & Admin Guide
What I'm worried about is that DR CUA can see data in DR CENTERA in a failover situation.
Customer wrote in DR CUA but luckly there is not too much data and is being copied back to main CUA, so I can destroy DR CUA and reconfigure for EA.
I'll be back for any doubts after reading doc.
Thanks in advance for you both!!