Data360 Analyze: Cannot process request because a system backup is in progress.

This article describes what to do if you cannot access the system because a backup is in progress. For more information on backups, see how backups work

There are two types of messages that you can get...

1. 

This suggests that the backup is taking longer than expected to complete. It will eventually disappear and users will be able to access the system, but you should take some preventative measures to avoid a reoccurrence, see further down this article.

2. 

This suggests that a backup process has hit an issue and cannot complete. 

At this time, the only way to resolve the error is to restart the Analyze services / processes. We have a Jira in place to create a better resolution; LAE-24990, which will be coming in the 3.7.x series of releases.  Below are some measures you can take to avoid encountering the error. 

FAQ's & PREVENTATIVE MEASURES:

* what time do backups take place at by default?

Backups, by default are executed at 02:00. This setting can be changed. (See the help section on configuring backups - here)

*  is it possible to monitor the backup process?

The log file lae-webapp.log indicates the start, status & end of the backup progress. It can be found under <DataDirectory>/site-7731/logs

*  what would cause a backup to fail, or hang?

Depending on how far along it is, the scheduled job will either not get kicked off, or it will be allowed to run until a place where it is "suspendable", then the system will "suspend" it - nodes continue to execute on the server, but the webapp stops processing the results (no database updates), until the backup is done when the scheduled job is "resumed". 

However, if no long running jobs are in place and you're still seeing that error, then we'll need to investigate further. Please raise a Support ticket and attach the log files from your system. 

*  what can I do to keep the database tidy? Are there any system tables that need cleaning? 

As long as you set the retention parameters (under Settings > Scheduling > Cleanup of Scheduled Runs), the database itself doesn't need a lot of cleanup.

The thing that you will have to watch is for temp files that aren't removed when you might expect them to.  The attached dataflow can be used to monitor disk space - you'll have to adjust it to your specific installation.
You may also wish to create some task to periodically archive the log files - they can get quite large over time. The trick to that is that a few log files (specifically lae-audit.log) are necessary to determine system usage - you'll need to balance how much disk space they use versus how far back in history you want usage statistics.