Backing Up Databases
If you encounter a problem while working in GoldMine that causes data loss or data corruption, the problem can be internal or external to your system. Ensure data availability in the event of data loss or corruption using a regular program of data backup.
To maintain an optimal backup system, make a separate backup on each day for a 2-week cycle. That is, your backup system should include 10 to 14 individual backups. Two weeks of backups are recommended because data corruption might not be discovered for several days. Only 1 or 2 backups might contain corrupted data. Use tape or diskettes as a backup medium.
For added security and recovery, keep a backup in secure offsite location (a bank deposit). Ensure you periodically update the backup.
NOTE: Maintain regular backups of GoldMine contact data, setup data, and program files. To back up contact data in GoldMine on an MSSQL database, use a utility designed to back up SQL data.
Backing Up SQL Databases
With an SQL database, the files needed for a backup can be copied to another directory, another drive, a disk, or an external drive. It is recommended that you keep a daily backup on a 2-week cycle, as hardware failures or unforeseen problems can cause you to lose your data.
NOTE: It is highly recommended that you create a database backup using SQL Server Management Studio.
A full backup of GoldMine on SQL Server requires you to back up the GoldMine system files and the SQL database. To perform a manual backup of your SQL database, the following GoldMine system files and their typical locations (listed in the table below) must be copied to create a safe backup file.
|
Location |
Files |
|
|
|
|
|
|
|
|
|
|
All other subdirectories of \GoldMine |
|
For complete information, see the SQL Server Online Help and SQL Books Online.
