You need to do that only if you want to backup selected company. You need to have on mind, that NAV backup will never do backup of specialities connected to MS SQL like views and other things. IF you are using something like this, you need to use the SQL backup and not the NAV backup, else you will be not able to restore the db...
NAV backups are not necessary to maintain database integrity or anything if that's what you're asking. You can completely restore a NAV database using a SQL Server backup. Using SQL Server to implement a comprehensive backup strategy gives you the flexibility to schedule them without having to purchase 3rd party products, AND you can restore back to the second you lost the database, provided that the backup strategy is set up correctly for that purpose.
Well a long time ago I heard that you can still have a valid SQL backup and yet still have a db that is corrupted from Navision's perspective (obviously the odds are very small).
So I usually have my clients do 1 Navision backup a weekend. As far as I knew when taking a Navision backup, Navision checks the integrity of the database from its own perspective so that way the backup routine is for me more of a way of ensuring validity from Navision perspective as well.
Are you saying you completely do not need it anymore?
Well a long time ago I heard that you can still have a valid SQL backup and yet still have a db that is corrupted from Navision's perspective (obviously the odds are very small).
So I usually have my clients do 1 Navision backup a weekend. As far as I knew when taking a Navision backup, Navision checks the integrity of the database from its own perspective so that way the backup routine is for me more of a way of ensuring validity from Navision perspective as well.
Are you saying you completely do not need it anymore?
If at some point you've done data import and let's say for example in your CODE field lowercase values where imported - you will successfully be able to do SQL backups. However, while doing NAV backup you will get errors. Therefore, sometimes it's good to do a NAV backup, just to be sure everything is fine.
Comments
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
RIS Plus, LLC
But a simple yes or no would've answered by question.
AP Commerce, Inc. = where I work
Getting Started with Dynamics NAV 2013 Application Development = my book
Implementing Microsoft Dynamics NAV - 3rd Edition = my 2nd book
So I usually have my clients do 1 Navision backup a weekend. As far as I knew when taking a Navision backup, Navision checks the integrity of the database from its own perspective so that way the backup routine is for me more of a way of ensuring validity from Navision perspective as well.
Are you saying you completely do not need it anymore?
RIS Plus, LLC
If at some point you've done data import and let's say for example in your CODE field lowercase values where imported - you will successfully be able to do SQL backups. However, while doing NAV backup you will get errors. Therefore, sometimes it's good to do a NAV backup, just to be sure everything is fine.
Dynamics NAV Enthusiast