They serve different needs, in regards to the Native database this is my view of the major differences.
Hotcopy is much faster to recover, because you just have to copy files back to original location, and you are back up andrunning. but, there is no compression, so you need just as big a drive to hold hot copy as original database. Now you also have to copy files back to same location, so you can't easily use it to restore say to a test company, because it won't have same name and file location.
Navision backup, compresses data, but takes a long time to restore database. But it also test the database on backup and restore so you can get consistency checks performed on the database. And it re-indexes everything when you restore it. Which is what takes most of the time. And you can restore it to a different database.
Navision backup, compresses data, but takes a long time to restore database.
I am not sure it compresses data. But I am sure it doesn't backup secondary indexes. This is the big reason the backup is a lot smaller (if you don't believe me, take T32 with a few 100.000 records, optimize the table and check the size, then delete the secondary indexes and recheck the size) and the fact it takes a lot of time to restore, because Navision has to recreate the indexes.
Regards,Alain Krikilion No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
Navision backup, compresses data, but takes a long time to restore database.
I am not sure it compresses data. But I am sure it doesn't backup secondary indexes. This is the big reason the backup is a lot smaller (if you don't believe me, take T32 with a few 100.000 records, optimize the table and check the size, then delete the secondary indexes and recheck the size) and the fact it takes a lot of time to restore, because Navision has to recreate the indexes.
I said it reindexes everything when you restore it, that is what takes so much time. the documentation I have says it compresses that data. Here is the help topic on it.
You can make backups by copying the database directly with an operating system command, but there are four main advantages to using the Navision Financials backup function:
· The program tests the database for errors, so useless information is not copied to a backup.
· The data is packed so it takes up as little space as possible.
· The program calculates how much space the backup will use.
· A message will appear when a diskette is full, telling you to insert a new one.
Kriki, I am wondering what your post contributed to this discussion.
Comments
Regards
Hotcopy is much faster to recover, because you just have to copy files back to original location, and you are back up andrunning. but, there is no compression, so you need just as big a drive to hold hot copy as original database. Now you also have to copy files back to same location, so you can't easily use it to restore say to a test company, because it won't have same name and file location.
Navision backup, compresses data, but takes a long time to restore database. But it also test the database on backup and restore so you can get consistency checks performed on the database. And it re-indexes everything when you restore it. Which is what takes most of the time. And you can restore it to a different database.
Just my opinion.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
You can make backups by copying the database directly with an operating system command, but there are four main advantages to using the Navision Financials backup function:
· The program tests the database for errors, so useless information is not copied to a backup.
· The data is packed so it takes up as little space as possible.
· The program calculates how much space the backup will use.
· A message will appear when a diskette is full, telling you to insert a new one.
Kriki, I am wondering what your post contributed to this discussion.