Crash recovery techniques
Unfortunately, even the best software applications crash on rare occasions. If you have any unsaved edits in a file when your application crashes, you may have to spend valuable time reproducing all your unsaved work. The Asta Enterprise system has been designed to recover from a client or server crash with most, if not all, of your data intact. The Enterprise server keeps a copy of all work in progress on Asta Powerproject clients, and each client keeps a copy of their own work. This means that if the Enterprise server or a client crashes, you can restart the program and continue from where you left off. If either the server or a client crashes, you can restart the program that has crashed and continue working.
If a client crashes
A client crash is when the Asta Powerproject client terminates abnormally. After communication between the server and the client has been lost, the server keeps a copy of that client's work in progress. You can specify the length of time for which work is kept by setting the timeout duration. If a user restarts the client and logs back onto the same project within this time frame, the server is able to restore the previous edits to the client. If the user does not restart the client and log back onto the same project within this time frame, the server discards its copy of the client's work in progress and the user will be unable to retrieve these unsaved edits.
When a user restarts the client after a client crash, a dialog appears enabling the user to choose whether to resume work on the project that was abandoned, or whether to start a new project. If the user chooses to resume work on the project that was abandoned, the project is opened in exactly the same state that it was in just before the client crashed.
If the server crashes
A server crash is when the Enterprise server terminates abnormally. When the server crashes a message is displayed to any clients that were running, informing them that the client has lost its connection to the server. You must restart the server. You do not need to shut down the client while you wait for the server to load. When the server loads, if the client is still open it will automatically connect to the server and reload the project that was open at the time when the server crashed.
If your connection to a Microsoft SQL Server® database is lost, a message is displayed to any clients that were running, informing them that the client has lost its connection to the database. This message is repeated at a frequency that you can define until the connection to the database is restored. Users are warned to save their work when the connection to the database is restored.