SQL server backup vs. Navision backup

ta5

Hi
Is there a reason to use navision backup when using sql server option?
Of course a navision backup offers the possibility to restore companywise or only objects, etc. But is it also needed to detect data corruption or anything else (as I've heard)? I guess no, but your opinion is appreciated.

Thanks
Thomas

bbrown

I see no reason to use Navision backup for normal operations. In fact, little reason to use them at all. As far as data corruption/intergrity checking, this can be accomplished using the available SQL DBCC commands. The NAV SQL Installation guide outlines the association between the various database test and the related DBCC commands.

ta5

Thanks!
Thomas

garak

Read also this:

viewtopic.php?f=33&t=35427

ta5

Hi Garak
Interesting thread. The link to How_to_backup_navision.pdf seems to be broken, do you have the new link?
By the way, do you know the document form ExpandIT, where they say nevertheless a Navision Backup is a kind of must because sql backup does not know the internal structures of navision?
Here is the link, sorry in german only:
http://www.ctm-computer.de/ctm/produkte ... herung.pdf

Regards
Thomas

David_Singleton

bbrown wrote:

As far as data corruption/intergrity checking, this can be accomplished using the available SQL DBCC commands.

I wouldn't totally agree with that. :-k

I can easily corrupt a Navision database that you could then backup with SQL, and SQL would show the database to be fine even though it was a corrupt database. Flow fields are the first candidate, but there are lots more. Simply putting a lower case non ascii character of the wrong code page into a text field like Customer name. The old bug in Navision where a flow field could overflow, can't be done in Navision now but could be replicated in SQL. Those are simple examples, but there are many more, and often the only way to fix them is to clean up the SQL create an FBK and restore it.

I understand that these are generally circumstances where someone played with the back end in SQL direct, but I do still see some use for an FBK. I wouldn't use one as my primary recovery plan in a production environment, but I still generally encourage clients to make and FBK backup once per month and restore it. Especially if they have any external process linking into Navision.

garak

ta5 wrote:

ctm-computer

:-) ctm :-) My old employer :-D

Yes i know this document ;-)

for me, the link http://www.geocities.com/navision_attai ... vision.pdf work

ta5

Thanks David. Circumstances like these were the reason for my original question. Actually this is quite scary, isnt't?

Regards
Thomas