You’re offline. This is a read only version of the page.
Is it normal for database when it reaches 2,097,152KB to create another file? As this is what is happening. Backups are now usually in 2 files.
*This post is locked for comments
Hi fkirui,
NAV increases the file name only, the backup is full regardless of data (by year). It is better to name backup file ending with order number, such as 16-05-2017_01.fbk -> NAV will generate next file named 16-05-2017_02.fbk, ...
It depends on the name that you keep for that particular backup file.
If you keep Backup file as NAVBackup_16052016, it will increase the last digit and hence it would become 16052017.
Avoid giving numeric digit at the last and you would not see such file name. It would be more of _1, _2, _3 etc.
Vishal,
is it also normal for the files to have different years. Coz our backup naming system is per the date and the second file usually picks the next year. For instance one file will be 16-05-2016.fbk and the incremental file will be 16-05-2017.fbk
Thanks for the feedback.
Much appreciated
Hi fkirui,
It is normal. NAV splits the backup (.fbk file) in to 2GB file. When you restore the backup, put all files in same folder and browse the first file.
Yes it is normal.
If you are taking NAVISION Backup (.fbk), it would create separate file for every 2 GB of file size.
If you take sql database backup, it would create single file.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (