V-79-57344-883 – Failed to create the list item for
Error writing file data.
The maximum size of an individual SharePoint file that Backup Exec can restore is limited by the SQL server settings on the server that hosts the SharePoint content database being restored.
The SQL server can be configured to support restoring larger SharePoint files in two ways.
Increase the packet size setting
By default, the packet size is set to 4K. The default packet size setting can be temporarily increased to process large restore jobs. Once the restore job is completed, change the packet size back to default. Using a larger packet size setting can cause adverse performance for jobs which restore smaller files.
Use SQL’s Native Client 10.0 as the ODBC driver to increase the supported file size
SQL Server Native Client 10.0 is installed by default for SQL 2008 and SQL 2008 R2. It can also be downloaded and installed on Native Client 10.0 on SQL 2005 servers. Ensure that Native Client 10.0 is installed by checking the Drivers tab in the ODBC Data Source Administrator utility. [Administrative Tools > Data Sources (ODBC)] If using SQL 2005, download the SQL Native Client 10.0 from the Microsoft SQL 2008 Feature Pack or Microsoft SQL Server 2008 R2 Feature Pack download page. Search for “native client 10.0 download.”
The tables below list the maximum supported file size for different possible configurations:
SQL 2008 and SQL 2008 R2
|
SQL Packet Size
|
ODBC Driver
|
Maximum SharePoint file size supported for restore jobs
|
|
4K
|
SQL Server
|
63MB
|
|
4K
|
Native Client 10.0
|
2047MB
|
|
32K
|
SQL Server
|
508MB
|
|
32K
|
Native Client 10.0
|
2047MB
|
|
SQL Packet Size
|
ODBC Driver
|
Maximum SharePoint file size supported for restore jobs
|
|
4K
|
SQL Server
|
63MB
|
|
4K
|
Native Client 10.0
|
255MB
|
|
32K
|
SQL Server
|
508MB
|
|
32K
|
Native Client 10.0
|
2035MB
|
To increase the packet size setting:
1. Run REGEDT32.EXE on the SQL server that hosts the SharePoint content database.
Warning: Incorrectly using the Windows registry editor may prevent the operating system from functioning properly. You should take great care when you make changes to the Windows registry. Veritas recommends that you make a complete backup of the registry and SQL server before you make any registry changes.
2. Highlight the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\veritas\Backup Exec For Windows\Backup Exec\Engine\SharePoint
3. Click Edit, and then click New.
4. Click DWORD Value.
5. Type SQL_PACKET_SIZE for the name of the new value.
6. Highlight SQL_PACKET_SIZE.
7. Click Edit, and then click Modify.
8. In the Value Data field, type 8000 for the hexadecimal value or 32768 for the decimal value, for the new packet size.
The SQL Server default is 4K (4096). Veritas recommends setting the packet size to the maximum value, 32K (32768) to complete the restore job. When the restore job is complete, either change the value back to the default or remove the SQL_PACKET_SIZE value.
9. Click OK.
To enable Native Client 10.0 as the ODBC driver:
1. Run REGEDT32.EXE on the SQL server that hosts the SharePoint content database.
Warning: Incorrectly using the Windows registry editor may prevent the operating system from functioning properly. You should take great care when you make changes to the Windows registry. Veritas recommends that you make a complete backup of the registry and SQL server before you make any registry changes.
2. Highlight the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\veritas\Backup Exec For Windows\Backup Exec\Engine\SharePoint
3. Click Edit, and then click New.
4. Click DWORD Value.
5. Type NEW_DRIVER for the name of the new value.
6. Highlight NEW_DRIVER.
7. Click Edit, and then click Modify.
8. In the Value Data field, type 2.
9. Click OK.