A historical full snapshot from a couple of years ago was taken without properly activating the system lockout and then restored to the site. Is there a method by which the site can generate a safe snapshot? Is this something that Acumatica Services needs to perform? I have rebuilt indexes and optimized the db then scheduled a lockout in attempt to take a safe snapshot but still receive the following notice:
Best answer by Kandy Beatty
View original
+16
HI
You need to put the instance in Maintenace mode. The below may help you:
Hello Patrick,
It is my understanding that an unsafe snapshot was already restored, therefore any further snapshots taken may have that warning due to an unsafe snapshot being restored previously.
As Kandy Beatty mentioned above, maintenance mode does indeed allow a snapshot to be safe, however that warning indicates your newest snapshot may also contain corrupted data, therefore it continues to warn about that even with new snapshots.
There is another method, one can try a combination of “Hide Warning” as indicated in the tenant screen, and also use maintenance mode for any further snapshots.
Once a safe snapshot has been restored, I predict no further issues with the warning will appear? Definitely update us if that is any different.
https://help-2022r2.acumatica.com/Help?ScreenId=ShowWiki&pageid=3f8ba9f5-9e04-4568-a93e-862ba7b92c2b
| Hide Warning | Hides the warning about unsafe snapshot restoration in the Tools > About box. This warning appears after you have restored (or another administrator has restored) a snapshot that was not taken in maintenance mode. This button is available when the system is showing the warning about unsafe snapshot restoration in the Tools > About box. |
A historical full snapshot from a couple of years ago was taken without properly activating the system lockout and then restored to the site. Is there a method by which the site can generate a safe snapshot? Is this something that Acumatica Services needs to perform? I have rebuilt indexes and optimized the db then scheduled a lockout in attempt to take a safe snapshot but still receive the following notice:
Very very helpful even when this post is 4 years old.
This is one of those areas where Acumatica should do a better job of helping out the user. When you go to create a snapshot, it should give you the option of locking out the site (assuming you have proper permissions to do that of course). It is tribal knowledge that you have to go a totally different area to lockout the site before taking a safe snapshot, and then you have to remember to remove the site from lockout mode or no one will be able to login. Not the best usability-wise.
Seconding
In the ideal case, you would want to prompt the operator requesting the snapshot whether or not they want to “enable maintenance mode”; If they decline to do so, double-confirm that “This will result in an unsafe snapshot being created. Proceed anyway?” In doing this, you also gain access to the context necessary for basic automatic lock/unlock for maintenance. By proceeding with lockout, you could reliably enable the lockout before snapshot creation and automatically end lockout when the snapshot is complete and any optional next steps (ex. prep for export) begin.
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
