Adding a new site for Cross Updating
This procedure is best run at night or over a weekend
Note:
- x_send is run via option 1 on xmenu
- x_check is run via option 2 on xmenu
On the new machine:
Make sure there is a working vet system with the correct branch number set in master.dev and within the vet software. You must be able to transfer e-mail between sites.
Make sure call_info is set correctly (xmenu opt a, opt a).
Keep x_send disabled until you are ready to use the system for genuine work.
If you have been adding 'play' work on this machine please get support to make sure the play work will not be transferred to the main machine. Or, if doing this out of hours remove v6lf and UUCP.log (from the main vet data directory if they exist) and kill any queued work (xmenu opt a, opt i) for the main machine.
Log into the existing branch machine(s) and run x_send
This makes sure that any work added on these machines is queued for the master machine.
On the master machine:
- Run x_send
Ensures any work is queued out to the remote sites.
- Force a connection to the remote sites (xmenu opt 4)
Picks up any queued work on the brach machines and sends current work.
- Switch off the modem
This will stop incomming work from the remote machines while the backup is being made.
- Run x_check
Collects any work just received from the remote machines and moves it to where the vet system is located.
- Login and integrate any work
Update the master database with any incomming work.
- Stop users adding work to the master machine
We don't want to miss anything on the backup, additionally backing up while adding data can corrupt the files.
- Allocate some clients (say 200) for the new site
Make sure when the new branch goes live it can add some clients.
- Run x_send
Queue the new clients for the existing sites.
- Add the new site name to call_info
Tells the cross updating module that it should send to the new site.
- Transfer the clinical files.
Use xmenu option 5, then option 3 to prepare a copy of full clinical files. When the files are ready you will be given the option of how to transfer them. The system will have estimated the modem transfer time, if this is less than it would take you to physically go there then pick modem else pick tape.
Note: Make sure you are using compatible tapes.
- Modem Transfer:
This will have queued the files to go to ALL sites, you will have
to delete the work for existing sites. To do this:
Run the command: uustat -a
This will list ALL the work that is queued, look for lines containing /tmp/tran3.Z, this is the clinial files. The job number will be given on the left of the line. Ignoring the line for the new branch type:
uustat -k <job-number>
e.g. uustat -k bdsediN12ea
Repeat the command for all existing branch machines.
Now switch the modem back on and force a transfer to the new machine, xmenu option 4. This ensures the work is sent straight away to the new site. Users can now start using the master machine.
- Tape transfer:
Take the tape to the new branch, run xmenu option 5 then option R which will extract the files from the tape.
- On the branch machine run x_check.
This will move the files into the correct location
- Log into the branch machine and check that the work is there and
all the records are accessible.
- Make sure the modem is switched back on at the main machine.
- Contact support who will check out the work and switch on x_send so work is automatically sent.
NOTE: If anything goes wrong with either the transfer you will have to re-run the procedure from the start again.