I have been working to set up a SQL Anywhere v17 High Availability mirrored server system. In particular I'd like server logs and have a couple of questions:
1) I am using the -o option to create server message logs. We can cause some confusion if the log files are all just placed in a ./Logs directory. Are there any "best practices" for how to "segregate" log files here:
A) ./Logs/Primary, ./Logs/Mirror and ./Logs/Arbiter
B) Place a ./Logs directory in the each of the three (Primary, Mirror and Arbiter) database directories
2) Is there any recommended size for the -os option in the dbsrv17 launch command to limit the size of the log file before a new log file is created?
asked 21 Mar, 16:43
(1) There is no "best practices" other than "avoid confusion" which you already understand.
IMO the -o files should be named [whatever].txt because they are text files, not database.log files.
IMO the -o files should go in the same folders as the *.db files.
IMO the creation of extra folders increases confusion. For example, if the *.db, *.log and *.txt files are all going to be placed on the same drive, put them in the same folder. Of course, if the *.db and *.log files are being placed on different drives for performance, they must go in different folders.
(2) Choose a -os value depending on the program used to browse the files. For example, if memory serves, Wordpad has problems with files larger than 10M.
(3) Congratulations on using -o and -os! ...they are very important in a production environment.