Space Requirements for a Multi-TB SharePoint Migration using DocAve 6

Details:

Background
 
How much temporary space needs to be allocated to support a multi-TB SharePoint migration using DocAve 6 (including the space required in the target farm for the copied content and the space needed for SQL log files)?
Since DocAve 6 uses a data stream to migrate the data to the destination, migration data is not temporarily stored in the Agent temp directory like it used to be with DocAve 5. If a Migration database is not used, the DocAve Agent logs will grow depending on the size of the migration. It is difficult to estimate how large these can grow, but generally speaking, it is not too large.
Regarding the Migration database, there is no hard number on a recommended size for a multi-TB migration. However, the following test results will be of help.
 
DocAve Migration Database
The Migration database is not required for a migration. The setting can be disabled when you run the migration job. Accordingly, nothing will be written to the database. If you do enable the Migration database, note that the Migration database does not store much data. The following factors can affect the size of the Migration database:
·         The number of the migration data (files & items).
·         The length of the source item’s URL.
·         The number of exception items in a migration data transaction.
 

Test Results and Observations

From the test result below (SharePoint 2007 to SharePoint 2010 Migration), we can see that 10,000 documents use about 16 MB space in DocAve Migration database. The increase is nearly linear.
Refer to the following table and screenshot for more information.

​	ENV1​	​ENV2	ENV3​	ENV4​
Document Number​	​10,000	​50,000	​90,000	​130,000
Migration Database Size (MB)​	​16	​73	​129	​189

 

Figure 1: Diagram of Migration database size changes.