Data exchange - Creation of initial image for distributed infobase subordinate node

Hello,
Is there a faster way of creating the original image of an infobase other than using the standard mechanism (managed form)? I've made some tests and the standard mechanism can take some time for large databases.

I intend to create an initial image for an infobase containing tens of gigabytes of data, so I need to accomplish this in the most optimal way possible. The infobase works in server mode - MS SQL Server architecture.
I was thinking maybe to simply backup the corresponding database from SQL Server Management and restore it in a new database. But in the end I will have a problem with 1C:Enterprise seeing this new database as a distributed infobase subordinate node.

Daniel, the initial image is created with processing of data in infobase as only data belonging to a specific node will be exported. In your case it should contain entire the data but in other cases it is not.

Maybe you could limit data for your node as in case of problems when you will need to restore the distributed infobase, this will take a long time.

So the standard mechanism would be the only way of creating the initial image of a specific node.

When you talk about limiting the data for the node you refer at filtering the data which is sent fr om master to slave node?

In my case, the data will need to be send just in one direction, from main to backup infobase. At first, I will need to create the initial image for backup node, after which the new/changed data from main infobase will be send to backup infobase periodically. But almost all of the metadata objects from the configuration must be part of the exchange plan (AutoRecord enabled), so I don't think I will can lim it the data to be sent.

Alexey, after creating the initial image of the main infobase, data older than a certain date will be deleted from the main infobase in order to work only with recent data (for better performance). But this deletions will not be recorded for backup node, so that the old data could be found at any time in the backup infobase. I don't know if the database mirroring mechanism can allow me to implement such scheme, haven't used it before.

It will be more useful to create new infobases yearly, for example and keep there opening balances and catalog items only. In that case you will have as backups fully functional infobases with data by years.
If you would sign a partnership with 1C Company, you could have an Extended TechSupport option and our specialist could assist you with performance issues of your infobase.

Thanks for all the suggestions.