PowerProtect Data Manager 19.12 Microsoft SQL Server User Guide

ddbmsqlsv: BackupVirtualDeviceSet::SetBufferParms: Request large buffers failure on backup device 'EMC#6f1e7adf-678f-4ceb-88fb-248211218add'. Operating system error 0x8007000e (Not enough storage is available to complete this operation.).

ddbmsqlsv SYSTEM critical Unable to allocate memory: Not enough space
ddbmsqlsv PowerProtect Data Manager critical BackupVirtualDeviceSet::SetBufferParms: Request large buffers failure on backup device 'EMC#77002120-0a31-4f53-98b1-3311f997e8ac'. Operating system error 0x800705af (The paging file is too small for this operation to complete.).

To prevent or resolve these backup issues, use any of the following procedures:

• Increase the RAM size on the Microsoft SQL Server host.

• Increase the virtual paging value (swap size) on the Microsoft SQL Server host by completing the following steps:

  1. Select Control Panel > System and Security > System.
  2. Select Advanced system settings to display the system properties of the Microsoft SQL Server host.
  3. In the System Properties dialog box, select the Advanced tab.
  4. Under Performance, select Settings.
  5. In the Performance Options dialog box, select the Advanced tab.
  6. Under Virtual memory, select Change.

  7. In the Virtual Memory dialog box:

     1. Clear the default setting, Automatically manage paging file size for all drives.
     2. Select the drive for which you want to change the paging file size.
     3. Select Custom size.
     4. Set the Initial size to the same value as the Currently allocated size.
     5. Set the Maximum size required for the paging file, based on the recommended size for the Microsoft SQL Server host system. To ensure system stability, Windows restricts the paging file size to three times the value of the installed RAM.

• On the Infrastructure > Assets page in the PowerProtect Data Manager UI, reduce the stripe value for all databases. Enable multi-stream backups for Microsoft SQL Server protection policy provides details about how to set the stripe value.

  NOTE If the stripe value is decreased to 1, full and differential backups can take longer to complete, depending on the size of the database.
• If the backup schedule results in overlapping backups that run at the same time, such as concurrent FULL and LOG backups, modify the backup schedule to prevent the overlapping backups.

• If possible, create multiple protection policies with fewer databases that have non-overlapping schedules.

  NOTE A Microsoft SQL Server database asset may be included in only one protection policy.