Knowledge Base


Expand allClose all

Backup Exec 2010 Exchange Database not found


The backup of Exchange 2010 fails with no byte count.


The following error message is displayed on failure:

0xe0000391 – Backup Exec attempted to back up an Exchange database according to the job settings. The database was not found, however. Update the selection list and run the job again.


1.This failure may occur if there are two different exchange servers in the environment. For e.g. ( Exchange 2003 & Exchange 2010) OR (Exchange 2007 & Exchange 2010) and the System logon account of Backup exec will have an active mailbox on the first exchange server but not on the second. Specifically on Exchange 2010.
2.If Exchange 2010 is newly configured to backup. There has been a recent update on Backup Exec..
3.A database has been renamed recently.
4.Backup Exec Remote Agent Utility has entry of mulitiple Media Server in publishing tab which do not exists.
5.The Log on type for the Beremote service on the Exchange server was changed from the default of “Local System Account” to a specific account.


First of all, Restart Remote agent service on the Exchange servers and then attempt Backup Again. If not working, do steps below.

Solution 1 :

1. Create a new account and add the user to the following groups:

Domain Admin.


Local Administrator on all the nodes of the Exchange including the CAS Servers.

2. Make sure that the new account of Backup exec has a mailbox in Exchange 2010 and it is activated.

3. Ensure that the Backup Exec logon account is a member of the “Organization Management” Role Group in Exchange 2010.

For more information refer the document :-

4. Make the newly created account as the System Logon account and the Backup exec service account in Backup exec.

5. Restart the Backup Exec services.

6. Also make sure the remote agent is updated on the exchange server.

The Exchange Logon Account Requirements :

7. Test the backup job.

Solution 2 :

1. Make sure the remote agent has been updated on all Exchange server nodes.

2. Uninstall the Remote Agent for Windows System (RAWS) on the exchange server from Control Panel -> Add/Remove programs.

3. Push install the RAWS from the media server.

4. Re-try the backup.

Solution 3 :

If the database/s renamed and/or moved, need to reboot the Exchange server before running the backup job.

Solution 4 :

1. Access the Remote Agent Utility on the Exchange Server.

2. Access the “Publishing” Tab.

3. Modify the list to add existing Media Server and remove the entries for non-existing Media Server.

(Add the IP address of the Media Server in case the hostname is already added.)

4. Restart the Backup Exec Remote Agent Service.

Solution 5 :

1. Open Windows Services on the Exchange server in “Server Manager” or the services.msc snap-in.

2. Locate and right click the “Backup Exec Remote Agent for Windows Systems” service and select properties.

3. Go to the “Log On” tab and change the “Log on as:” to ‘Local System Account’.

4. Restart the Remote Agent service

5. Rerun the backup

The above mentioned issue is resolved by hotfix180429 for BE2010 R3

Mark as helpful. 0

The backup of the item is bad” (a000fe2d HEX or e000fe2d HEX) Backup Exec


“The backup of the item is bad” (a000fe2d HEX or e000fe2d HEX) is reported during a failed Legacy Microsoft Exchange mailbox backup.


The backup of the item is bad

Warning: %Email message% is a corrupt file. The file cannot verify

Unable to backup the attachment data associated with one or more messages. Some messages and their attachments may have been deleted while the backup was already in progress.


The suggested backup method is to use Granular Restore (GRT) backup methods instead of Legacy (Brick Level) backup methods. The Legacy method is only supported for Exchange 2003 using BE 11 to 2010. BE 2012 no longer supports the Legacy method. The GRT method uses only the backup of the Information store with the backup job selected to enable GRT. Thus the Legacy selection can be removed from the selection list.

For the Legacy Method: To potentially resolve this issue, perform the following steps:

1. Verify if any emails are quarantined. If so, those e-mails need to be excluded from the backup.

2. If any users are selected for backup whose mailboxes no longer exist, deselect these users from the backup job.

3. Make sure the Antivirus Application is not improperly scanning the file system on the Exchange Server and that the Spam Filter is configured properly. For more information on this, review the following document:

Microsoft Exchange mailboxes backed up via the Microsoft Exchange Agent hang in random locations within the backup set if Anti-virus and/or Spam Filtering Applications are not configured properly.

4. If using Advance Open File Option (AOFO), backup just Exchange in a separate job without AOFO.

5. Verify if the option “Enable single instance backup for message attachments (for mailbox and public folder backups only)” is enabled. If yes, uncheck and verify the results. For more information, refer to the Related Documents Section below.

If the issue still occurs after performing the steps above, the registry can be modified per the following steps, to prevent jobs from failing on files which Backup Exec believes to be corrupt:

Warning: Use of this registry key will result in the successful status of job operations that otherwise would have qualified as being failed operations. Ordinarily, successful job status indicates that 100% of the targeted data has been protected and recorded to media. After this registry key has been enabled, a successful job status will indicate a primarily successful backup operation with exceptions. When this key has been enabled, Symantec recommends that an inspection of job log files is performed to make note of any possible exceptions that may have occurred during a backup operation.

Warning: Incorrect use of the Windows registry editor can have disastrous results on a server operating system. 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.


2. Browse to the following key:

Backup Exec 9.x and 10.x: HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Backup Exec\Engine\Backup
Backup Exec 11d and 12.x: HKEY_LOCAL_MACHINE\SOFTWARE\SYMANTEC\Backup Exec\Engine\Backup

3. In the right window, double-click Fail Jobs on Corrupt Files (Figure 2)

4. In the DWORD Editor dialog box, change the Value Data to 0 (zero) (Figure 3)

5. Click OK

6. Exit Regedt32

7. Recycle Backup Exec services.

Mark as helpful. 0

vRanger – File is larger than the maximum size supported by datastore


VMFS datastores can be created with different block sizes, resulting in different maximum VMDK sizes. A VM with multiple VMDKs on different datastores, formatted with different block sizes may result in datastore size errors when performing vRanger backups.

VMware Block Size Limitations: (VMFS3)

Block Size Largest VMDK/File Size
—————- ———————————–
1 MB block size = 256 GB maximum filesize
2 MB block size = 512 GB maximum filesize
4 MB block size = 1024 GB maximum filesize
8 MB block size = 2048 GB maximum filesize

An example for a multi-VMDK VM:

VMDK1 (50GB) stored on a 1MB block size datastore (A)
VMDK2 (300GB) stored on a 2MB block size datastore (B)

Typically, the VM’s .vmx file is located on the same datastore as the VM’s 1st VMDK and the vRanger snapshots are stored on the
same datastore as the .vmx. Because a snapshot is created for each VMDK, the snapshot for VMDK2 would be stored on datastore (A).
As this snapshot would be larger than the block size limitation for datastore (A) an error condition is encountered.

There are 2 possible solutions:

1. Perform a VMware Storage vMotion to move the VMDK on the 1MB formatted datastore to another datastore with a larger block size.

References include VMware KBs 1004040 and 1005544.

2. Reformat the datastore. There is no way to change the block size of a VMFS datastore once it has been created. The datastore must be reformatted with the required block size.

This would require moving the VMs/VMDKs located on the datastore to another location, then reformatting the datastore.

Mark as helpful. 0

Vice Versa 256 character limit

It is quite rare to exceed 259 characters for a file path name. If that is needed, ViceVersa PRO 2 now supports long path names exceeding 259 chars.

To enable this in a specific folder use the prefix “\\?\”.
For example, to allow paths longer than 259 characters in c:\folder\backup\ use \\?\c:\folder\backup\ as source (or target, or archive folder) in ViceVersa PRO.
Using “\\?\” permits a maximum path length of approximately 32,000 characters composed of components up to 255 characters in length.

To specify a UNC path, use the “\\?\UNC\” prefix.
For example, “\\?\UNC\\“.

Mark as helpful. 0

How to Re-register Volume Shadow Copy Service (VSS) Components on Windows 2003/Windows 2008

If an Exchange Backup Job is performed with AOFO and Sybari Antigen product is installed in ESE mode, the error: “AOFO: Initialization failure on: \\servername\Microsoft Information Store\First Storage Group Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS)” may occurHow to Re-register Volume Shadow Copy Service (VSS) Components on Windows 2008/Windows 2003.


How to Re-register Volume Shadow Copy Service (VSS) Components on Windows 2008/Windows 2003.


VSS may not be working in one or more of the following ways:

1. Volume snapshots may fail with errors.
2. Backups using VSS may fail.
3. One or more VSS writers are missing when running the following command:
•vssadmin list writers

4. Using Backup Exec for Window Servers, backup jobs may:
•fail with VSS or snapshot errors.
•hang at snapshot processing.

5. Using Backup Exec System Recovery, backup jobs may:
•fail at 5%.
•appear to be progressing, reach 90% or higher then fail.

Re-registering VSS in Windows 2008 & testing is done in 2 parts:

Part 1 – Create and Execute a batch file named, FIXVSS08.BAT:
Please note the following:
•Run the batch file as Administrator.
•This is only for Windows 2008, not Windows 2003.

After running the .bat file, reboot the server to bring all of the writers into a stable state.
Copy and paste the following into Notepad, then click Save As and save it as FIXVSS08.BAT.



net stop “System Event Notification Service”

net stop “Background Intelligent Transfer Service”

net stop “COM+ Event System”

net stop “Microsoft Software Shadow Copy Provider”

net stop “Volume Shadow Copy”

cd /d %windir%\system32

net stop vss

net stop swprv

regsvr32 /s ATL.DLL

regsvr32 /s comsvcs.DLL

regsvr32 /s credui.DLL

regsvr32 /s CRYPTNET.DLL

regsvr32 /s CRYPTUI.DLL

regsvr32 /s dhcpqec.DLL

regsvr32 /s dssenh.DLL

regsvr32 /s eapqec.DLL

regsvr32 /s esscli.DLL

regsvr32 /s FastProx.DLL

regsvr32 /s FirewallAPI.DLL

regsvr32 /s kmsvc.DLL

regsvr32 /s lsmproxy.DLL

regsvr32 /s MSCTF.DLL

regsvr32 /s msi.DLL

regsvr32 /s msxml3.DLL

regsvr32 /s ncprov.DLL

regsvr32 /s ole32.DLL

regsvr32 /s OLEACC.DLL

regsvr32 /s OLEAUT32.DLL

regsvr32 /s PROPSYS.DLL

regsvr32 /s QAgent.DLL

regsvr32 /s qagentrt.DLL

regsvr32 /s QUtil.DLL

regsvr32 /s raschap.DLL

regsvr32 /s RASQEC.DLL

regsvr32 /s rastls.DLL

regsvr32 /s repdrvfs.DLL

regsvr32 /s RPCRT4.DLL

regsvr32 /s rsaenh.DLL

regsvr32 /s SHELL32.DLL

regsvr32 /s shsvcs.DLL

regsvr32 /s /i swprv.DLL

regsvr32 /s tschannel.DLL

regsvr32 /s USERENV.DLL

regsvr32 /s vss_ps.DLL

regsvr32 /s wbemcons.DLL

regsvr32 /s wbemcore.DLL

regsvr32 /s wbemess.DLL

regsvr32 /s wbemsvc.DLL

regsvr32 /s WINHTTP.DLL

regsvr32 /s WINTRUST.DLL

regsvr32 /s wmiprvsd.DLL

regsvr32 /s wmisvc.DLL

regsvr32 /s wmiutils.DLL

regsvr32 /s wuaueng.DLL

sfc /SCANFILE=%windir%\system32\catsrv.DLL

sfc /SCANFILE=%windir%\system32\catsrvut.DLL

sfc /SCANFILE=%windir%\system32\CLBCatQ.DLL

net start “COM+ Event System”

Part 2 – Testing VSS by performing a System State Backup:
•You must first open a command prompt by right-clicking on Command Prompt and select Run As Administrator.

The command to start a System State Backup is:

Wbadmin start systemstatebackup -backuptarget:F:

Additional Notes:
•F: is the target drive where you wish to store the system state backup.
•This shouldn’t be a drive that is hosting any of the files included with System State.
•For Windows 2003, please refer to the following article:

For additional details, refer to the following Microsoft Technet article:

Mark as helpful. 0

Install Backup Exec 2012 License

Go to add and remove programs and click on Change for Symantec Backup Exec to find the option to add licenses


Symantec Backup Exec 2012 is shown as being in Trial version even after installing the serial numbers.


1. During the install of Backup Exec 2012, “Maintenance” serial numbers are entered, but the the actual “Product” serial numbers were not entered. Figure 1.

Figure 1


2. If “Product” serial numbers were entered, but not selected in “Select the products to install on this computer, Backup Exec will still be installed in Trial mode. Figure 2.

Figure 2




1.  Run the installation again and verify  which serial numbers were installed.  The “Product Name/Description” will indicate which ones are “Maintenance serial numbers” and which ones are “Product” serial numbers. Figure 3.

Figure 3


2. Click “Next” and the “Select the product to install on this computer” screen will show whether the “Product” serial number was selected to be installed on the local computer.  If nothing is checked, then Backup Exec 2012 was installed as a Trial version. Figure 4.

Figure 4


3.  To get Backup Exec installed as a licensed version, select the “Serial numbers” and continue the installation. Figure 5.

Figure 5

Mark as helpful. 0