Hi! we have a production attain 3.60 own database with 32 GB (67% percent full). We have also a attain 3.60 testserver. when we bring our testserver to the newest database state we do it so: first we delete all companies on our testserver. then we export all objects in the object designer of the real system. then we import all these objects in the testserver. then we make a navision own backup (without application) objects on the real server. then we import these *.fbk files (4) on my navision attain 3.60 testserver. very long needs the creation of the table keys. how could I make that whole more faster? who has ideas? more memory? (we have 512 MB) faster disks? raid controller raid1? Thanks!
I wonder why you are exporting and importing the objects seperate from the backup file? Does not make much sense, I think. I don’t know if this is the cause for the long time needed to build the keys (never tried it this way myself), but may be you should try to import a backup including the objects. But some time is always needed to build the keys, and this rebuild takes longer the bigger your tables are and the more keys you have defined. You can speed up this process with more disks (no raid, except for security!) and more memory, but from the distance I can’t tell what really slows the rebuild down and what you need.
Hi, I completely agree with Alex, to make a full copy (incl. data) of your Db you only need to make a backup from within Navision. Hope this helps a little.
quote:
… to make a full copy (incl. data) of your Db you only need to make a backup …
As far as I know, objects are not replaced by a restore of a FBK, even if it contains them. [:0] The objects will be just imported if a new DB is created. But you can import objects from a FBK (not FOB!) via “Object Designer”: Same like importing FOB, just choosing the (first) FBK. In every case: If objects were changed, you allways have to import them before starting a restore, except when creating a new DB! Best regards, Jörg
I too agree with Alex and Sven, there’s no need to separate objects and data. When we set up our test system, we simply create a completely new, empty database on the test server and then import the daily backup of our production server. Creating keys takes a long time for us too, longer than the actual import. To my knowledge, you can only speed things up by buying faster hardware, as you already mentioned [;)]. From inside Navision, there’s only the option to interrupt the import, identify the tables that have the most records, and delete all those records you deem unnecessary for the test system. You might also choose to deactivate those keys that might not be needed - you can always activate them again later. Then, you can start the import again, usually it proceeds from where you interrupted it [:D]
quote:
Originally posted by stryk
As far as I know, objects are not replaced by a restore of a FBK, even if it contains them. [:0]
Yup, right - but I think table definitions will be replaced during a restore (imagine a new field has been added and filled with data - these data must be stored somewhere!). In any case, it’s quite easy to produce a real mess when importing objects and data into a non-empty database [xx(]. That’s the reason why I mentioned creating a completely new database for the test system…
quote:
table definitions will be replaced during a restore
No way. The restore ends with an error. Sad but true [V]
Hotcopy is perfect for creating a test database. You get copies of the database files and don’t need to restore keys.
Well… it seems that you’re loosing a lot of time on the process… first deleting all the companies takes usually more time when having lots of data (and more steps) than just creating and empty database from scratch. When creating a new empty database, you can use a full backup from the real server to restore on the new database (it will take some time on making the backup… time you can use for creating again the test database and then just use a full restore (data, data common to all companies and objects) on the new created test database. I think that the hotcopy (usually a fast way for copying databases without having to restore keys and so) won’t work on you, as you say you’re handling a 32 GB database… so you’ll probably have the database split in different files, and unless you’re keeping the same folder structure for keeping the files on the testserver you’ll get in trouble when trying to open the database if just copied the files to the test server. Regards,
i forgot to say that if you restore the database using a local session instead of a client/server connection it will go faster …
quote:
I think that the hotcopy (usually a fast way for copying databases without having to restore keys and so) won’t work on you, as you say you’re handling a 32 GB database
We are handling a 32GB database with HotCopy very well [^] We are running HotCopy and ExpandIT parallel (to get a “combat ready” DB and to save the FBK on Tape), the whole process takes 10 hours (while running a automated night-batch, too!). Regards, Jörg