Defining a strong backup plan and ensuring that it is executed properly is probably the most important step to remember, not only when configuring your initial database, but on a regular and ongoing basis.
Your SchoolLeader database will quickly become the backbone of your daily operations. Because of this, ensure that your backup plan is clearly defined, and that the database backups are working properly. It is your responsibility to take care of your database. Disasters can -- and do -- happen. Fire, lightning strikes, and burglary can all severely impact your business computer operations, however, with your data safely secured, you can feel confident that a computer disaster will have minimal impact on your business.
SchoolLeader provides two ways to capture backups of your data
The easiest and quickest way to obtain a backup is to perform a Backup directly from FrontDesk Manager.method to perform a database backups built into the FrontDesk manager program. From FrontDesk Manager, you can click on File, then Backup/Export, and instruct SchoolLeader where to save your database backup (e.g. CD, USB Memory stick, etc). Regardless of the destination for your local backup, you always get the additional option to send your backup to the SchoolLeader DataVault for off-site storage purposes. To find out more about backing up your database to the SchoolLeader DataVault, contact us at 800- 858 8570.
We recommend that your SchoolLeader Backup/Export be initiated from the Server PC for reliability and performance reasons. Also, we highly recommend that you backup your database to a device that is separate from your database hard drive, and that you take a copy of this database backup off-site at least once per week.
The SchoolLeader Backup Manager window is accessed from the DB-Support program and allows you to do two simple tasks. First, it lets you define the location of where your backups are copied after an export, and second, it allows you to setup an automatic backup plan.
This defines the temporary storage location SchoolLeader will use for creating exports. It also will be the default location for any exports or manual backups a user creates. From your SchoolLeader server, click on Temp Location button to display the following "Choose Folder" window. You can set the default location of where to store the backups using this window.
If you want to be able to perform EXPORTS from remote workstations then you must define your backup location using UNC naming conventions. This means using the \\ServerName format rather then Drive Letter format. An example might be \\FrontDeskServer\C\Kressa\SchoolLeader\Backups.
Once you start typing the directory location, the folder display box (lower left) will automatically reveal the folder structure under the directory typed so far. This allows you to type the first part of the directory path and then tab off the field to reveal the remaining contents in the view below. You can finish drilling down to the backup location by double clicking folders in the second box.
This allows you to define the rules for how the automatic Database Monitoring service will run each day. This "DBMonitor" tool runs in the background on the SchoolLeader server and monitors and maintains the health of your SchoolLeader database.
Roll off old backups after X days: Set the number of days you wish to keep your backups. The default is 3 days and effectively will always keep 3 copies for restoring in the event of an emergency. You can increase this if you prefer but be certain you have enough disk space to hold extra copies of the database. These databases can be very large and storing many days or weeks of backups can quickly fill up your disk.
Start DB Maintenance and Backup daily at: Set the time of day the maintenance process should run. Depending on the size of your database, the 5 maintenance steps will typically take between 2 minutes and 15 minutes. You should schedule during a quiet time such as the middle of the night. Be sure it's not scheduled to run when other nightly maintenance backups or cleanups are scheduled.
Backup Log Report grid: Displays all the maintenance reports currently available for review. The available history will depend on how many days you choose to keep. Double click on any report to see the process logs. These logs show you all the details for each step performed. The example below is the log report for a successful backup.
Tips for preparing a reliable backup plan
Regardless of your ultimate method for performing backups, certain criteria are critical of any successful plan. First, database backups should be taken on a daily basis, and/or when significant changes have occurred. As a general rule, you should back up your database before one of these events:
the end of each day
before posting recurring fees for the period
before closing the accounting period on the ledger
Here are some additional suggestions for a successfully backup plan:
Ensure you have adequate and reliable backup media available, such as multiple zip disks, CD-ROMS, tapes, etc. Replace older media with new media on a regular basis per manufacturers recommendations.
From your server, perform a daily backup (either through SchoolLeader's FILE EXPORT process, or with your own Backup software). Backup your data to an external device, such as a removable USB Memory stick, a tape drive, CD-ROM, etc. Do NOT simply leave it on the same hard-drive with the active Database. If the hard-drive fails, you would loose both copies.
Each week, or even each day, rotate your backup media to an off-site location, such as your home or alternate office. If you don't have the means to perform off-site backups, consider using the SchoolLeader DataVault service to "electronically" ship the database off-site. Taking your backup copy to a physically separate location protects you against catastrophes such as fires or burglaries.
After performing the backup, verify that the backup worked. This last suggestion is obvious but often ignored. The worst time to discover that your backup process hasn't been working for the last 2 months is when you need it after a system failure. Remember, backup processes can fail too. The software gets corrupted, the backup media wears out, etc. Test it each week!