• Substantial number of assets with significant Historical information per asset
• Many images are attached to assets. The program stores picture files directly in the Asset Database. It can take a long time to retrieve and compress into the backup file
• Running the backup process over a VPN or WAN connection

The backup procedure can take anywhere from a few minutes to several hours depending on the size of the database. The procedure appears to 'freeze' at around 18% (Book Parts) and 43% (Event log) and at 56% (Images). Under the Windows Task Manager, it will appear as if the program is 'Not Responding' but this isn’t necessarily the case. Let it run uninterrupted for an extended period before intervening. The process will either complete, or error out.

To prevent slowdown during backup:

• Backup up the database to the hard drive of the local machine
• Reduce the distance between the location of the database and where you're running the backup. For example, making the backup on a client that's installed on the server
• Don’t use Special Characters in the backup File Name