u must run utconfig on all servers, and configure failover ( specifying that server is on a group), and use the same group key (group signature).

Then u must specify hierarchy, running ./utreplica -p secondary-server1 secondary-server2 ...  ( on primary server). ( -p gives primary role to that server, and u specify who are the secondary servers)

And finally u run ./utreplica -s primary-server  (on each secondary server) ( -s gives secondary role to that server, and u specify who is the primary)

"  utreplica -l  "  will show current administration configuration.

Sorry my bad english.. Im spanish native.

Hope that works for u.

PD: Use rdate <primary-host>, preferably with crontab, to synchronize secondary servers with their primary server.


Ives, Keith-P59429 escribió:
Failover with SRSS 4

My past experience has been up thru SRSS 3.1 on sparc. I have been setting up failover groups with no problems.
Now, with 4.0, patched to 127554 (x86) it seems to be more challenging.
The replication step complains "…unable to determine replication status…"
This message occurs from either box.
Has the configuration of failover groups changed any that the documentation has not "caught up" ?
The 4.0 SRSS Admin Guide utadm example shows secondary server specifying primary as auth server…
        - is this now a hard rule…
        - does the primary have to reference the secondary anytime before "utreplica" is run
Another observation is that 4.0 now asks if I want kiosk mode which I now decline; when in the past I simply answered the questions for # of users… and the system would configure # pseudo accts in password and shadow, so my question is:

        - when do I need kiosk mode… we do not use smart cards, nor do we do hot-desking
My config:
Primary NICs on same network  (same switch)
Secondary NICs on same dedicated network (same switch)



__________ Información de NOD32, revisión 3981 (20090401) __________

Este mensaje ha sido analizado con NOD32 antivirus system
http://www.nod32.com

_______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users


__________ Información de NOD32, revisión 3981 (20090401) __________

Este mensaje ha sido analizado con  NOD32 antivirus system
http://www.nod32.com

  


--



Diego Naufel
Soporte Sun Microsystems

AR-TEC S.A.
San Martin 198 P.3 Of.2
Godoy Cruz - Mendoza - CP 5547
Phone +54 261 422-0442/6861
Email [email protected]
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users

Reply via email to