GRT backup of Exchange Information Stores to TAPE fails with error: "VFF Open Failure. This can be caused by low memory or disk resources."

Article:TECH127758  |  Created: 2010-01-22  |  Updated: 2014-06-02  |  Article URL http://www.symantec.com/docs/TECH127758
Article Type
Technical Solution

Product(s)

Issue



GRT (Granular Recovery Technology) backup of an Exchange Information Store to tape fails with error: Unable to complete the operation for the selected resource using the specified options for the following reason: VFF Open Failure.  This can be caused by low memory or disk resources.


Error



V-79-57344-759 - Unable to complete the operation for the selected resource using the specified options for the following reason: VFF Open Failure. This can be caused by low memory or disk resources.

-543 The required log files for recovery are missing.

800705AA Insufficient system resources exist to complete the requested service

V-79-57344-75 - E000004B - Unable to complete the operation for the following reason: VFF Open Failure


Cause



Due to how Backup Exec handles mapping the Exchange database in memory, some databases (typically large databases, or databases with a large amount of logs) require more virtual memory than a 32bit server can provide. These limitations can be avoided when using a x64 bit server, and as such may require Backup Exec to be installed onto a x64bit Windows server.


Solution



 
1. Add the following registry key on the Exchange server(s):

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

Key : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VirtFile
Value: VFF Extended Timeout
Type: DWORD
The Maximum value is (Decimal) 600 seconds.
Start out at 240 seconds at first. If error still occurs then 480, before going to 600.
Restart all the Backup Exec Services for the changes to take effect.

If step 1 doesn't resolve the issue, please move to step 2.

2. Add the following registry key to the Exchange server:
 
- This step is taken directly from from Microsoft KB article 304101 (see acknowledgements).  It is applied to the Exchange server.
* For this change to take effect, the Exchange Server must be rebooted.
 
STEPS TO ADD THE REGISTRY SETTING 
  1. Click Start, click Run, type regedit in the Open box, and then click OK.
  2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
  1. On the Edit menu, point to New, and then click DWORD Value.
  2. Type PoolUsageMaximum as the entry name, and then press ENTER.
  3. Right-click PoolUsageMaximum, and then click Modify.
  4. Click Decimal.
  5. In the Value data box, type 60, and then click OK.

    Important
  • Use 60 as your initial value. If your backup does not succeed, use 40 as your value. If that does not work, you must change the behavior of your backup program to reduce the demand of paged pool. If the value works, you may want to increase the value by approximately 25 percent until the backup does not work. If the backup is unsuccessful, use the second registry setting that is described in this article.
  • Make sure that the value for this registry setting is not more than 60.
  • If you are using the /3GB switch, use 40 as your initial setting. Note that this value is a percentage value.

   

How to Apply the 3GB Switch

To Set the /3GB Startup Switch in Windows Server 2003

1.      Right-click My Computer and select Properties. The System Properties dialog box will appear.

2.      Click the Advanced tab.

3.      In the Startup and Recovery area, click Settings. The Startup and Recovery dialog box will appear.

4.      In the System startup area, click Edit. This will open the Windows boot.ini file in Notepad.

5.      In the [Operating Systems] section, add the following switches to the end of the startup line that includes the /fastdetect switch: /3GB

6.      Save the changes and close Notepad.

7.      Click OK two times to close the open dialog boxes, and then restart the computer for the change to take effect.

 To Set the /3GB Startup Switch in Windows 2000 Advanced Server or Windows 2000 Datacenter Server.

1.      In Windows Explorer, navigate to the system partition. This is the partition that holds hardware specific Windows files such as Boot.ini and NTLDR.

2.      If you cannot see the Boot.ini file, it could be because the folder options are set to hide protected operating system files. If this is the case, in the Explorer window, click Tools, Folder Options, and then click View. Clear the Hide protected operating system files (Recommended) check box. When prompted, click Yes.

3.      After the Boot.ini file is visible in Explorer, right-click the file, click Open With, and then click Notepad to open the file.

4.      Add the /3GB switch to the end of the line starting with "multi" under the [Operating Systems] section.

5.      Save the changes and close Notepad.

6.      Restart the computer for the change to take effect.

Note: in some occasions this can cause a Windows based system to bluescreen. Testing is required if you are setting the PAE boot.ini switch. 
  1. Quit Registry Editor.
  2. Restart your computer.
Because you must test these settings during the most stressful backups, you may have to wait a month for a whole backup cycle to complete if you are not sure which backup consumes the most resources. Because of this situation, Microsoft recommends that you test low values first.
 

 If the issue still persists after making these adjustments please contact Symantec support for further troubleshooting.


Supplemental Materials

SourceUMI
ValueV-79-57344-759
Description

Unable to complete the operation for the selected resource using the specified options for the following reason: VFF Open Failure. This can be caused by low memory or disk resources.


SourceUMI
ValueV-79-57344-75
Description

 V-79-57344-75 - E000004B - Unable to complete the operation for the following reason: VFF Open Failure



Legacy ID



347659


Article URL http://www.symantec.com/docs/TECH127758


Terms of use for this information are found in Legal Notices