When I do a backup of both Data and Application objects, sometimes the backup crash. Is it because there are users performing posting actions inside the application?
:?:
That may well be the case if it's only occasionally happening.
What happens when you start a backup is that the backup-procedure takes a snap-shot of the data in the database and locks that snapshot to ensure the integrity of the backup. While the backup is running any new entries or alterations in existing data will be written in the free space of the database. In other words. It will not re-use the space in the database that is used by "old" data because these "old"-data are about to be backed up. What could happen is that you run out of free space and then the db-engine WILL start using the space occupied by the old data and thus your backup-procedure will halt with an error message stating something along those lines. I can't remember the exact message right now!
So you could try to expand the database and then maybe you will have better luck running the backup while there are users on the system.
Tommy, Afonso is using MS SQL => SQL increase size of database automaticaly (if free space is available and is not limit for size]...
On SQL is problem, that there is no snapshot but TableLocking. We have same experience with Navision backup with MS SQL. We are using SQL backup. But there are situations when you need native backup - best is switch database into single user mode and make backup. Or make backup when there are no users in Navision (or their activity is very low)...
:?
Comments
What happens when you start a backup is that the backup-procedure takes a snap-shot of the data in the database and locks that snapshot to ensure the integrity of the backup. While the backup is running any new entries or alterations in existing data will be written in the free space of the database. In other words. It will not re-use the space in the database that is used by "old" data because these "old"-data are about to be backed up. What could happen is that you run out of free space and then the db-engine WILL start using the space occupied by the old data and thus your backup-procedure will halt with an error message stating something along those lines. I can't remember the exact message right now!
So you could try to expand the database and then maybe you will have better luck running the backup while there are users on the system.
Tommy
On SQL is problem, that there is no snapshot but TableLocking. We have same experience with Navision backup with MS SQL. We are using SQL backup. But there are situations when you need native backup - best is switch database into single user mode and make backup. Or make backup when there are no users in Navision (or their activity is very low)...
:?
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
Ahh yes. I overlooked that fact. Too bad
Tommy