Reckon Desktop Automatic Backups

What happens if a user is logged in when it's time for the automatic backups run?

Does Reckon kick them out or does the backup fail?

Accepted answers

If a user is logged in when an automatic backup is scheduled to run, Reckon does not kick the user out; instead, the backup simply does not run. Backups set to run will only occur once the file is actually closed, so if someone is still logged in, the backup is skipped until the next qualifying file close. Once the file has been closed, the backup will be generated. Reckon never forces a logout or closes the company file automatically.

All comments

Reeta

Hi @Joanne O'Sullivan ,

Joanne O'Sullivan

I have a further question regarding this, when backup fails Reckon is prompting (a non-admin user) to remove the scheduled backup tasks. Is there is a way that this can be disabled eg, stop asking users if they want to remove the scheduled backups?

If there is no way to do so, what would happen if the user clicked yes? eg, would it immediately remove the scheduled backups, would there by further warning prompts, or would they be blocked from doing it due to not being an ‘admin’ user?

PhuongDo

Hi all,

Not sure if this helps, but I recall creating a script in the past that used a copy tool to duplicate the QBW file even while it was in use. This allowed a scheduled copy of the file to be taken automatically.

From a practical point of view, as long as you have a reliable backup, I don’t think it makes a big difference whether it’s a QBW or a QBB file.

Thanks,

Phuong

Datarec

Using the built-in backup function allows for the inclusion of a file verification to be performed to the company data file (QBW) just prior to the backup itself being created.

This allows the software to check the file for any detectable issues which really should be addressed before a backup is made.
If there are issues, have them investigated and addressed by putting the file through the built-in file rebuild function.
Then once more attempt to create a backup (QBB) using the built-in backup function.
If no further issues, then great.
You now have a compressed backup copy of the company file that has been tested and found to be error-free at that time.
If the initial issue is resolved but additional problems surface then addressing those is vital.

Simply making a copy of a company data file (QBW) is a reasonably good alternative to making use of the built-in backup function under ideal conditions.

It is certainly a faster process than the built-in backup function, but it does not include that very important file verification.
Therefore, if one chooses to simply copy a file, it is a very good idea to periodically make use of the built-in file integrity checking functions of the software (Verify Data / Rebuild Data).
How often you perform that manual file verification with respect to how often you make a copy of the file to serve as a secondary/backup copy is highly dependent on your appetite for risk.