Can these new-school statements (or ones like it) ALTER MIRROR SERVER xxx12A AS PARTNER log_file = 'C:\xxx\xxx12A.mlog'; ALTER MIRROR SERVER xxx12B AS PARTNER log_file = 'C:\xxx\xxx12B.mlog'; be used to add HA debugging to dbsrv12 engines that were set up with these options? (or is there some way to add *.mlog files to a 24x7 old-school setup?) -n xxx12A -o "C:\xxx\xxx12ALog.txt" -su nfr -x tcpip(port=55500;dobroadcast=no) -xf "C:\xxx\xxx12AState.txt" -gl All -ti 0 "C:\xxx\xxx.db" -sn xxxPri -sm xxxSec -xp partner=(eng=xxx12B;links=tcpip(host=localhost;port=55599;timeout=2));mode=sync;autofailover=YES;auth=xxx;arbiter=(eng=xxx12;links=tcpip(host=localhost;port=55501;timeout=2)) -n xxx12B -o "C:\xxx\xxx12BLog.txt" -su nfr -x tcpip(port=55599;dobroadcast=no) -xf "C:\xxx\xxx12BState.txt" -gl All -ti 0 "C:\xxx\xxx.db" -sn xxxPri -sm xxxSec -xp partner=(eng=xxx12A;links=tcpip(host=localhost;port=55500;timeout=2));mode=sync;autofailover=YES;auth=xxx;arbiter=(eng=xxx12;links=tcpip(host=localhost;port=55501;timeout=2)) |
If you are using the SQL Anywhere 11 compatible -xp, then you can use the logfile=C:\xxx\xxx12A.mlog parameter. For example: -xp partner=(eng=xxx12B;links=tcpip(host=localhost;port=55599;timeout=2));mode=sync;autofailover=YES;auth=xxx;logfile=C:\xxx\xxx12A.mlog;arbiter=(eng=xxx12;links=tcpip(host=localhost;port=55501;timeout=2)) Mixing -xp and CREATE/ALTER MIRROR server is NOT recommended and can lead to unexpected results. Kind regards, Ian |