ABLETM
Advanced Bindery Library
Exchange
Reference
Guide
Volume 16
Preventive Maintenance
Version 6.6.1
ABLEä Ventures, LLC
Copyright by ABLEä Ventures, LLC
This reference guide is copyrighted and all rights are
reserved. This document may not, in
whole or in part, be copied, photocopied, reproduced translated, reduced to any
electronic medium or machine readable form without prior consent, in writing,
from the ABLEä
Ventures, LLC.
The information in this document is subject to change without notice. The ABLEä Ventures, LLC assumes no responsibility for errors that may appear in this document.
For more information visit the ABLEä web site: http://www.programmingconcepts.com/able/
Or contact,
ABLEä Ventures, LLC
c/o Paul Parisi
ACME Bookbinding
100 Cambridge Street
Charlestown, MA 02129
(800) 242-1821
For technical support contact:
Programming
Concepts, Inc.
web site: http://www.programmingconcepts.com/able/
e-mail: able_support@programmingconcepts.com
telephone: 631-563-3800 x230
fax: 631-563-3898
ABLEä
Ventures, LLC
Acme Bookbinding
Information Conservation, Inc.
Kater-Crafts Bookbinders
Lehmann Bookbinding
Mekatronics Inc.
National Library Binding of Georgia
Ocker & Trapp Library Bindery Inc.
Programming Concepts, Inc.
ABLEä
is a trademark of Mekatronics, Inc. / Bendror International Inc. 1987-2001
2. Library and Bindery Maintenance Schedule
2.1.1 Incremental or Full Backup
2.3.1 System Disk Defragmentation and Cleanup
Release Notes
V6.0 Preliminary release for review.
V6.01 Changes for ABLEä release 6.01.
V6.02 Changes for ABLEä release 6.02.
V6.4 Changed copyright.
The ABLEä Reference Guide is comprised of multiple volumes. The collection of volumes describes the functional and operational characteristics of ABLEä. The volumes are:
|
Volume |
Reference Guide |
File Name |
|
1 |
r6-intro.htm |
|
|
2 |
Library User |
r6-library-user.htm |
|
3 |
r6-user.htm |
|
|
4 |
r6-title.htm |
|
|
5 |
R6-style.htm |
|
|
6 |
r6-report.htm |
|
|
7 |
r6-control.doc |
|
|
9 |
r6-maint.htm |
|
|
10 |
r6-transfer.htm |
|
|
12 |
R6-emboss.htm |
|
|
13 |
r6-help.htm |
|
|
15 |
r6-bill.htm |
|
|
16 |
r6-pm.htm |
|
|
19 |
R6-s3.htm |
|
|
20 |
r6-linstall.htm |
|
|
21 |
r6-binstall.htm |
|
|
22 |
r6-ezcut.htm |
|
|
23 |
r6-ftp.htm |
|
|
24 |
r6-alink.htm |
|
|
25 |
r6-zlink.htm |
|
|
27 |
r6-file-import.htm |
The Preventive Maintenance volume of the ABLEä Reference Guide provides procedures for maintaining ABLEä systems. The maintenance procedures include scheduled activities that the ABLEä System Manager must utilize to maintain proper system performance and integrity of the system.
ABLEä is user friendly, flexible, and comprehensive. This complexity, however, has placed a burden on the system manager. In particular, due to sheer file size and database complexities, the performance of ABLEä is dependent on the proper system maintenance.
ABLEä is a database intensive system running under a complex environment. It supports multiple workstations accessing many shared files across a network or Internet to a file server. The sizes of these files are very large.
The scheduled maintenance schedule is summarized in the following table.
D A I L Y W E E K L Y M O N T H L Y
|
Incremental or Full Backup |
1. Full Backup 2. File Maintenance Purge
|
1. Full Backup 2. File Maintenance Purge 3. File Optimization and Defragmentation 4.
Clean Workstations |
To maintain day to day data integrity, data loss must be guarded against. Data loss results from unpredictable occurrences such as power failures, system crashes and disk crashes. The ABLEä system software is designed to handle many failure conditions BUT you should take no unnecessary chances.
Backup includes incremental and full backups. Incremental backups should be done on a daily basis. Incremental backups provide a means to store the current day's work on a separate secured backup tape.
Incremental backups, however, are always done in conjunction with a Full backup. One effective method is to maintain four sets of backup tapes, one for each week of the month. Each set in turn contains a FULL backup tape(s) and an INCREMENTAL backup tape(s). At the end of the week, choose the oldest set of backup tapes and perform the FULL backup for the next work week. Then for each day subsequent to the FULL backup and prior to the next FULL backup, perform the INCREMENTAL backup.
Refer to the SQL Server 2000 documentation on setting up a Backup schedule.
To restore data from an incremental backup tape follow the directions for your OS and tape drive.
Full Backup and File Maintenance Purge are done on a weekly basis.
Full backups are used to maintain week to week data integrity, and to provide the basis for subsequent incremental backups described above.
To restore data from a full backup tape follow the directions of your OS and tape manufactures instructions.
Data stored for Lots, Jobs, Pieces, and Items is basically temporary. The data is used so long as the work for that Job/Lot is still in progress. Once the work has been completed for a Job/Lot and the contractual agreement for that job/lot has been fulfilled on both sides (bindery and library), the data stored in the database for that Job/Lot is no longer needed. In fact it is detrimental to keep it around for too long as it takes up file space, slows down the system, and ties up Lot/Job Id's that can be used for subsequent work.
The File Maintenance Purge provides the means of purging old data. File Maintenance Purge purges according to Job/Lot creation date. There is a global variable Purge Months (PMONTHS) that determines, system wide, how old (in months) a Job/Lot must be before it can be purged.
The purge program then uses Purge Months to purge the database using the following rules:
1. All empty Jobs (except HOLD) in ABLEä Bindery and all empty Lots are purged.
2. Non-empty Jobs and their associated Lots are purged if they were created Purge Months prior to the current date. Be careful that your error jobs are not also purged.
3. The HOLD Job in ABLEä Bindery is never purged, unless selected.
4. A Job's date is the date the Job was created in the Bindery.
The procedure for File Maintenance Purge follows:
1. Make sure no other clients are using the Account being purged against.
2. Select File MaintenanceàPurge from the Windows menu on the ABLEä Title screen.
3. Start the purge.
The Hold Job should be periodically
purged. If
These monthly procedures are described in this section. The procedures should be once for about every 40,000 pieces processed. The Daily or Weekly Backup, System Purge, File Maintenance Purge, File Optimization, and Disk Defragmentation should be performed monthly.
Before proceeding on to optimization, perform the daily INCREMENTAL or weekly FULL backup as described above. This will ensure a secured means of error recovery.
Before proceeding on to optimization, also perform the File Maintenance purge described above. This will enable the optimization routines to recapture and optimize the space held by the purged data.
The File Maintenance Purge purges ABLE files of not needed data. It does not, however, purge the system disk of unwanted files. The Windows Check Disk utility check for disk integrity and cleans up the disk.
The workstations on the bindery floor require cleaning since the environment is dirty. Remove the cover on the workstation and vacuum the internal components.
(Filters should also be installed to reduce the dirt build-up.)