Symantec: fails with 0xe0008105 - Invalid Volume Identifier

[guest]

Problem

Restore of emails from a disk based GRT backupset of a Microsoft Exchange 2010 Server Mailbox Database fails with 0xe0008105 - Invalid Physical Volume Library Media Identifier.





Error

V-79-57344-33029 - Error - Mount failed.
Invalid Physical Volume Library Media Identifier.

V-79-57344-33029 - Unable to acquire device for the specified pool and media

Debug Monitor(see related articles below) Log shows the following:

BENGINE: [date time] [thread-ID] [loops] - This BSD requires PDI restore. Checking to see if FS supports it
BENGINE: [date time] [thread-ID] [loops] -NDMPRAHostRestoreEngine::IsPDIRestoreSupported( ) - Querying application server(Exchange-CA-Server) for PDI support.
BENGINE: [date time] [thread-ID] [loops] -NDMPRAHostRestoreEngine::IsPDIRestoreSupported( ) - Querying application server(Exchange-CA-Server) for PDI support.
BENGINE: [date time] [thread-ID] [loops] - Applicationserver(Exchange-CA-Server) supports PDI
BENGINE: [date time] [thread-ID] [loops] - Querying PDIdata store server(MediaServer) for PDI support.
BENGINE: [date time] [thread-ID] [loops] - Querying PDIdata store server(MediaServer) for PDI support.
BENGINE: [date time] [thread-ID] [loops] - Could notconnect to the PDI data store server
BENGINE: [date time] [thread-ID] [loops] - FS does notsupport PDI restore
BENGINE: [date time] [thread-ID] [loops] - This BSD doesnot require PDI restore. Performing traditional backup
BENGINE: [date time] [thread-ID] [loops] -NDMPAgentConnector::EndConnection(): Data Server = Exchange-CA-Server
BENGINE: [date time] [thread-ID] [loops] -NDMPAgentConnector:SetupConnection(): Data Server = Exchange-CA-Server
BENGINE: [date time] [thread-ID] [ndmp\ndmpclient] - NDMP version 3 connection CONNECTED
PVLSVR: [date time] [3008] AdammSession::Execute(ADAMM_SESSION_EXECUTE_SESSION_SET_TARGET_DEVICE_HOST )
Session ={FFBD1BEE-C256-47C5-823E-92B9BD2555C5} Device Host = "Exchange-CA-Server"
BENGINE: [date time] [thread-ID] [server] - Job::Mount:acquired device
BENGINE: [date time] [thread-ID] [server] - Job::Mount:mounting tape
PVLSVR: [date time] [3008] AdammSession::CheckTargetDeviceStatus()
Session = {FFBD1BEE-C256-47C5-823E-92B9BD2555C5} Job ={32C76B6B-0EE5-4BFB-81DA-A53051E67A20}, "Restore 00302"
TargetDevice = {2F48C514-AFB6-4CAC-A73B-87019C267379}, "B2D-Name"
State = 0003, ReservationID = 0000, AvailableMovers = 0006
PVLSVR: [date time] [3008] AdammSession::Execute(ADAMM_SESSION_EXECUTE_MOVER_MOUNT_SPECIFIC )
Session ={FFBD1BEE-C256-47C5-823E-92B9BD2555C5} ERROR = 0xE0008105
(E_PVL_INVALID_MEDIA_ID)
BENGINE: [date time] [thread-ID] [loops] - Querying PDI data store server(MediaServer) for PDI support.
BENGINE: [date time] [thread-ID] [loops] -NDMPAgentConnector:SetupConnection(): Data Server = MediaServer
BEREMOTE: [date time] [4264] [ndmp\ndmpcomm] - ndmpRun: Control connection accepted : connection established between end-points 127.0.0.1:10000 and 127.0.0.1:50308
BEREMOTE: [date time] [8184] [ndmp\ndmpsrvr] - sslOpen() : Opening SSL for: 00000000E7B6F92F
BENGINE: [date time] [thread-ID] [ndmp\ndmpclient] - NDMP version 3 connection CONNECTED
BEREMOTE: [date time] [8184] [ndmp\ndmpsrvr] - sslOpen(): certinfo = 00000001270CAF1F ; sslConn = 00000000ECDEB61F
BENGINE: [date time] [thread-ID] [loops] -NDMPAgentConnector::AuthenticateClient(): Using Default Account for proxy
Authentication
BESERVER: [date time] [6908] -1 Client 'MediaServer' connected('','SNCT\123backup'): 0x9a5e540
BENGINE: [date time] [thread-ID] [loops] -NDMPEngine::SetupNDMPConnection(): Using the system default logon account
BENGINE: [date time] [thread-ID] [ndmp\ndmpclient] -connectClientAuth(): agent is on local loopback, skipping SSL connection...
BEREMOTE: [date time] [8184] [ndmp\ndmpsrvr] -ndmpdConnectClientAuth(): agent is on local loopback, skipping SSL connection...
BEREMOTE: [date time] [8184] [ndmp\ndmpsrvr] - Username for Logon: Domain\UserName
BEREMOTE: [date time] [8184] - LogonType set =[LOGON32_LOGON_BATCH][0x4]
BEREMOTE: [date time] [8184] - LogonUser failed: Logon failure: unknown user name or bad password.
BEREMOTE: [date time] [8184] [ndmp\ndmpsrvr] - LogonuserError: 1326
BEREMOTE: [date time] [8184] [ndmp\ndmpsrvr] - LogonUser failed for user: Domain\UserName
BENGINE: [date time] [thread-ID] [ndmp\ndmpcomm] - ERROR: 69 Error: Windows LogonUser API failed.
BENGINE: [date time] [thread-ID] [ndmp\ndmpclient] - ***getLastNDMPError Calling to get last NDMP Error.
BEREMOTE: [date time] [8184] [ndmp\ndmpsrvr] - In ndmpdGetLastError:: Callback to get last NDMP Error.
BEREMOTE: [date time] [8184] [ndmp\ndmpsrvr] - sslClose() :Closing SSL for: 00000000E7B6F92F
BENGINE: [date time] [thread-ID] [loops] - Could not connect to the PDI data store server
BENGINE: [date time] [thread-ID] [loops] - FS does not support PDI restore
BENGINE: [date time] [thread-ID] [loops] -NDMPAgentConnector::EndConnection(): Data Server = Exchange-CA-Server



Cause

Backup Exec server is not a part of Domain.This issue occurs if a local user account on the media server (i.e computername\username) is set as default.

Even though the backup job is configured to use "domain\username", the SGMON log shows that Logon attempted was for user "computername\username" account and cause the backup job to fail.



Solution

Workaround:

Use Exchange Recovery Storage Database (RSG) to restore (redirected) the emails.

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.