Hi! We have Navision 2.60 with its own database on a windows nt 4.0 server running. In the Navision Client under Database Information I see the following database details: datbase occupied (KB) 14562720 databse size (KB) 32768000 license size (KB) 32818000 One time in the month I make a bakup from my database in the navision client (all mandants - complete database) - that are 3 *.fbk files. These are 3 fbk files with about 2 GB size. Then I want to import these backup files in a other windows 2000 testserver with also navision 2.60 on it. This computer is a Pentium III/800 computer with 512 RAM Memory. The original system is a Pentium III/733 with two processors and 2 GB Ram. My problem is that my import on the testserver is running about 15 hours. Very long running is the creation of the different keys of the tables. Now my question: Could I with a faster cpu or more memory speed up this import. Or has anybody an other idea how I could make that proces faster? Thanks
Of course a faster CPU would increase the performance! But a “Bottleneck” could also be the network-connection between the client, where the FBK are located, and the Testserver! To compare, here our TecData: NF DE2.60.D Server: WinNT, 2 x P3/500Mhz, 2GB RAM Network: Gigabit Ethernet Client: WinNT, P3/733Mhz, 128MB RAM Database: ~30GB, occupied ~20GB Backup: 5 Files, ~8GB (total) BackupTime: ? RestoreTime: ~4 Hours Regards, Jörg Joerg A. Stryk Apollo-Optik, IT/ERP
Hi! The network could not be the “Bottleneck” because I have my fbk files which I import local on my testserver lying. Make you also the backup from one of your client computers with the navision client software with the ‘extra’ menu item? My Backuptime: about 1 hour Restoretime: on testserver about 15 hours!! Greetings from Fritz Rebernik
quote:
Originally posted by stryk: Of course a faster CPU would increase the performance! But a “Bottleneck” could also be the network-connection between the client, where the FBK are located, and the Testserver! To compare, here our TecData: NF DE2.60.D Server: WinNT, 2 x P3/500Mhz, 2GB RAM Network: Gigabit Ethernet Client: WinNT, P3/733Mhz, 128MB RAM Database: ~30GB, occupied ~20GB Backup: 5 Files, ~8GB (total) BackupTime: ? RestoreTime: ~4 Hours Regards, Jörg Joerg A. Stryk Apollo-Optik, IT/ERP
Yes, of course! We make our Backups with “Extras - Datensicherung erstellen”, not “HotCopy” or anything else! The “Structure” of our Backup-Process is this:
- We run 2 identical NAVISION-Server, one active, the other as Backup, containing the Datas of the last evening.
- We create a Evening-Backup (before Batch/Night-Processing, this one will be restored) and a Morning-Backup (after Batch, before Day-Business).
- The Evening-Backup is created local on the Backup-Server, which has Gigabit access to the Active-Server. (~8GB FBK, ~1.5 Hours)
- The FBK are restored to the Backup-Server (~4 Hours)
- The Morning-Backup is created on a Client which has Gigabit-access to the Active-Server (~8GB FBK, ~3 Hours)
Regards, Jörg Joerg A. Stryk Apollo-Optik, IT/ERP
Backup time is determined primarily by the amount of data, not including keys, in the database tables, Lessor speed effects come from the speed of the disk, and CPU of the hardware. When you do a backup, none of the key data is included in the backup, only the key definitions. During a Restore, all the keys are rebuilt from scratch. This is the primary time consumed during a Navision Restore. The four factors having the largest effect on this time are a) the size of the database being restored b) the number of keys and key records being created during the Restore c) the database memory cache size available d) the amount of work (empty) space available in the defined database to which the fbk is being restored. Lessor, but significant, factors are the speed of the CPU and disk of the Restore machine. To speed up a restore on the configuration you describe, maximize the amount of database cache assigned and make sure your empty database is at least twice the size of the expected data plus keys requirement. To improve speed somewhat and inexpensively, you could add memory to the system and increase the cache size. You might see some speed increase by splitting the new database across disk drives, but I’ve not tested this. Dave Studebaker das@libertyforever.com Liberty Grove Software A Navision Services Partner
Hi! I have now a question to the database memory cache size available. How large should that be when I have on my server 512 MB (1024 MB)Memory? How could I see (chnage) the size of my database cache size? Thanks!
quote:
Originally posted by daves: Backup time is determined primarily by the amount of data, not including keys, in the database tables, Lessor speed effects come from the speed of the disk, and CPU of the hardware. When you do a backup, none of the key data is included in the backup, only the key definitions. During a Restore, all the keys are rebuilt from scratch. This is the primary time consumed during a Navision Restore. The four factors having the largest effect on this time are a) the size of the database being restored b) the number of keys and key records being created during the Restore c) the database memory cache size available d) the amount of work (empty) space available in the defined database to which the fbk is being restored. Lessor, but significant, factors are the speed of the CPU and disk of the Restore machine. To speed up a restore on the configuration you describe, maximize the amount of database cache assigned and make sure your empty database is at least twice the size of the expected data plus keys requirement. To improve speed somewhat and inexpensively, you could add memory to the system and increase the cache size. You might see some speed increase by splitting the new database across disk drives, but I’ve not tested this. Dave Studebaker das@libertyforever.com Liberty Grove Software A Navision Services Partner
See the attached for general information on Server cache. This information was exerpted from the Navision manual “Installation and Server Management - Navision Server”. See either this manual or the equivalent Navision manual for SQL Server installation for additional information. …My attachment upload didn’t work (twice) so just check the manuals. Dave Studebaker das@libertyforever.com Liberty Grove Software A Navision Services Partner Edited by - daves on 2002 Aug 05 16:43:48