Included here are FAQs that don't pertain to a specific
version of the system.
What is and is not a backup?
It is extremely important that you backup your Summit data on a daily
basis. If a regular backup is not done, you can lose all data entered since the
last backup. Use a multi-generation tape or removable media system (CD, Zip
etc.) to back up the Summit data directory. Do full backups only, not
incremental or differential.
Backing up to diskette or to a hard disk is not acceptable - if you have
an error on a diskette or on the hard disk, your backup is unusable and you lose
your data. Do your really want to re-enter all your Summit data from
scratch?.
See your Windows documentation on how to do backups or refer to your backup
software documentation.
We strongly recommend a 6 set daily backup rotation and a 4 set monthly
backup rotation.
All of the Summit
systems are client/server applications. Client/server refers to the relationship of
actually sharing the workload between client and server applications on the network.
Client/server applications go beyond simply sharing file and print resources. In this
environment, clients ask servers to perform services on their behalf, typically returning
results back to the clients. Part of the computing effort takes place on the client, and
part takes place on the server.
In a client/server system, the local database engine (the "client" part of
client/server) formats a request for a specific set of data and passes this
"generic" request to the database server (the "server" part of
client/server). The local database engine has no idea of where the data is physically
stored, nor does it care. It's up to the database server to process the request and pass
the data back to the client.
Why is client/server better? With client/server applications, you can request exactly
what you want. With file-server applications, you have a much higher level of granularity.
Also, by isolating all database files under the control of one database engine (for
instance, the server) and one physical machine, the server can provide advanced
functionality that can't be furnished with a file-server architecture. Features like
online backup via log files, advanced hardware support such as uninterruptible
power
supplies or hot swappable disk drives, and multiprocessor machines can all be added to the
server with no changes to the client machines.
If you are printing a manual log: The 2:00 a.m. hour is not played at all.. Master
Control plays the 1:00 a.m. - 2:00 a.m. program and then skips to the 3:00 a.m. program.
If you are Automated: The computer should be programmed for daylight savings time and will
automatically set the clock one hour ahead, hence the automation will skip the 2:00 a.m.
hour. Billing: Auto-reconciliation will place the spots scheduled in the 2:00 a.m. hour in
makegoods or if they are fillers it will not acknowledge that they ran. If you manually
edit your log you will need to place the spots that were scheduled in the 2:00 a.m. time
slot to makegoods or cancel.
|
