Premvet 5 Manual Pages
Cross Updating
The Mirror option allows you to have one central server with a copy
of each site's data on it. Each remote site has it's own directory - that
is you do not have specific clients cross updating to other sites. This
allows for geographically spread practices to maintain a central database.
This allows for:
- Security Copy in case of failure at site level
- You can combine the data into one DataMajor database
- You can send OUT Stock/AP and definition files to allow for a common
data set at site level.
- You only need to access one server and you have acces to all site data - No more dialing into multiple sites.
As the checking program has a little more to do on a mirror site it has
been split from the standard x_check. On
mirror servers you need to run /usr/utilities/x_checkm instead.
If you forget don't worry - if the system detects a mirror in use it
will NOT let you run the standard x_check program and vise versa on
non-mirror'ed machines you will not be allowed to run x_checkm.
In call_info you add:
MIRROR=/somewhere
The remote site data should then be copied into the mirror area. The mirror
area is 'What is MIRROR set to' / 'Name of site' / 'What is VETSYS set to'.
So if we have:
MIRROR=/v/mirror
VETSYS=/u/vetdata
SITES="pluto venus"
The location of pluto's data will be /v/mirror/pluto/u/vetdata.
The location of venus's data will be /v/mirror/venus/u/vetdata.
It will be this area that is updated when work is received from remotes.
You will have your 'common' area in VETSYS, this is where you add
your stock, AP codes and make changes to definition files. When x_send
is run work in VETSYS will be sent to all the remote sites.
When the system is setup as a Mirror the following applies:
- The Logfile in the 'common' area (VETSYS) will NOT be sent.
- Files specified in EXTRA will be sent from VETSYS
- Any XUD Compare files will NOT be sent
- Stock and AP transfer files WILL be sent
- Client, Animal and Stock Data sheets WILL be transferred
- Automatic Transfers will take place, it is advisable to add
v6users.sys to the x_ignore file to avoid sending password changes from the common area.
- The custom.chk script will NOT be processed if present.
- Files specified in SUBFILES and DIRECTORIES will NOT be sent
