Exchange backup to tape fails with "The volume that is used for the staging location must be a writable NTFS volume that is local to the Backup Exec server"

Article:TECH211138  |  Created: 2013-10-01  |  Updated: 2013-10-01  |  Article URL http://www.symantec.com/docs/TECH211138
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution


Issue



When backing up Microsoft Exchange 2010 on a Small Business Server to a local tape device the backup may fail with the errors below.


Error



Job log Error: The volume that is used for the staging location must be a writable NTFS volume that is local to the Backup Exec server. Also, the volume must not be shared through Distributed File System. See the job log for more details.

Debug Log Errors:
VFF Process ModuleName 8: C:\Program Files\Symantec\Backup Exec\beremote.exe

Starting Persistent Virt VFF id (35816-00008BE8) 2.0.98.0

CheckVirtOpen:Unable to see I/O in GRT directory :C:\TEMP\Backup Exec\IMG#\vdb_DATE STAMP\Mailbox Database.edb.Virt___0
The most likely cause of this problem is that the path is on a DFS share. Suggest using a local drive or non-DFS share.

CheckVirtOpen:Unable to see I/O in GRT directory :C:\TEMP\Backup Exec\IMG#\vdb_DATE STAMP\Mailbox Database.edb.Virt___0
The most likely cause of this problem is that the path is on a DFS share. Suggest using a local drive or non-DFS share.

Virt Session aborted prematurely (7)

Error on Virt thread start up (35816) (time = 29)

Error Aborting OpenVirt (35816)

EndDriverSessionThread:SetEvent-ShutDownRequest failed, lastError = 00000006, The handle is invalid.

Closing Persistent Virt VFF id (35816-00008BE8) with: Total Bytes Read=00000000:00000000, Written=00000000:00000000

Closing Session [ThreadId=35816, Major=0, Minor=0, Index=0, Last=00000006].
[fsys\jet]           - OpenVirt FAILED, but didn't say why!

SessionStatus returned invalid not found.
[fsys\mb2]           - FILTER DRIVER OPEN SESSION FAILED: Unspecified error
[fsys\mb2]           - MB2_Chgdir:Logon returned e000fea9


Solution



Workaround: Perform non GRT backups of the Microsoft Databases

 

Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns. For information on how to contact Symantec Sales, please see http://www.symantec.com

Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.


Supplemental Materials

Value3328332
Description

EXCH: GRT backup fails with virtfile failure (Virt Session aborted prematurely (7))


SourceUMI
ValueV-79-57344-4626
Description

The volume that is used for the staging location must be a writable NTFS volume that is local to the Backup Exec server. Also, the volume must not be shared through Distributed File System. See the job log for more details.



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


Terms of use for this information are found in Legal Notices