How To Backup Collect!

The safest and easiest way to back up Collect! is to simply copy the contents of the Collect! folder to another location when none of the files are in use. We will describe 2 methods below for backing up the Collect! folder.

Method 1 - SQL Backup With Management Studio

This method does not requires any down time for your server while the backup process runs.

When restoring this type of backup, you do not want to restore any of the SQL database files (.MDF & .LDF files) as the backup process will create .BAK files for each of the databases. It is those files that you will use for the restoration process, which will create the appropriate .MDF and .LDF files.

1. Open MS SQL Management Studio.
2. Right-click each database, select Tasks, then select Backup. You may control the backup location here. The default backup location will be the MS SQL Server directory in the Program Files folder.
3. Copy the Collect! folder to another drive, preferably off-site. If you left the backup files in the Default MS SQL Server, you will need to copy those files to the backup medium as well.
4. In Management Studio, Attach all the databases.

For simplicity, this process can be scripted using batch files and the Windows Scheduler. Contact us or a Microsoft Certified Technician for more information.

Method 2 - SQL Backup With Batch File

This method does not requires any down time for your server while the backup process runs.

When restoring this type of backup, you do not want to restore any of the SQL database files (.MDF & .LDF files) as the backup process will create .BAK files for each of the databases. It is those files that you will use for the restoration process, which will create the appropriate .MDF and .LDF files.

1. In the Collect!\bin folder, run the file backupSQL.bat. This file will create a .BAK of each of the database files, then compress the files into a .TAR file, then into a .TAR.GZ file located in the Collect!\snapshots folder.
2. Copy the Collect! folder to another drive, preferably off-site.

For simplicity, this process can be scripted using batch files and the Windows Scheduler. Contact us or a Microsoft Certified Technician for more information.

In Collect!, if you go to the File menu, then to Maintenance, the Snapshot button will run this script.

Method 3 - Detach Databases

This method requires down time for your server while the backup process runs.

When restoring this type of backup, you may have to take ownership of all the SQL database files (.MDF & .LDF files) as the file security on the files from the old server will have been the registered user for MS SQL Server, not your Administrator account.

1. Open MS SQL Management Studio.
2. Right-click each database, select Tasks, then select Detach. You may have to select the "Drop" option if there are still connections to the database.
3. Copy the Collect! folder to another drive, preferably off-site.
4. In Management Studio, Attach all the databases.

For simplicity, this process can be scripted using batch files and the Windows Scheduler. Contact us or a Microsoft Certified Technician for more information.

Summary

Ultimately, the backup strategy that you use is up to you. There are lots of tools available such as RAID and ROBOCOPY to mirror your drive to another drive. You can then copy that drive to an off-site medium.

A good backup can mean the difference between a successful disaster recovery and having to close your business.