Skip Open Document In Backup

[#1]

A best practice is to make sure the db is backed up every day.  

However, ACT, pay attention here ...

It is not uncommon that, during the process of the day, a document or two had been left open during the day.  When the scheduled backup starts it fails b/c the user did not close the document(s).

Can the development team give consideration to modifying the backup process with a notice to the user that because a document was left open, no attachments were backed up. 

There could be a number of reasons why a document was open; however, the backup should be completed without attachments.  The reason it should be skipped is because the db doesn't know if the document is in the process of being changed or just open for reading.  

The necessity of the core db being backed up is critical.

And if you are not backing up every day, please adopt this best practice to schedule an automatic daily backup.

[#2]

The backup.log file in Seagate Manager and Maxtor Manager will report only on files that are skipped or encounter problems during a backup. Keep in mind these errors are generally related to individual files, and not entire folders. There are many files that are typically skipped during a backup, see the information below to help interpret the various error messages that may show in the log.

[#3]

Did you forget to add something?  There was nothing here to see below.