MARS/Microsoft Azure Backup - The media is write protected (0x80070013)

[Garacesh]

Looking to replace DPM and have our servers backup directly to Azure

 

I've installed the MARS agent (MARSAgentInstaller.exe), joined it to our Vault with the .VaultCredentials file, set up a suitably complex encryption key, and modified the backup schedule.

 

Amongst everything else, GatewayProvider0Curr contains the following:

1C58	1F28	09/26	08:11:25.116	83	CommunicationClient.cs(1190)				NORMAL			Service Request | Params: {URL = https://pod01-ecs1.ne.backup.windowsazure.com/services/MonitoringService/resources/[REDACTED]/containers/[REDACTED]/syncEventObjects?api-version=2016-06-01.1.0}{APIVersion = 1.0}{Method = POST}{PostData = {"SyncData":{"Alerts":[{"SyncObjectID":"REDACTED-GUID","ParsedSyncObject":null,"SyncObject":{"JobID":"REDACTED-GUID","Job":{"JobType":1,"JobStatus":{"StartTime":"\/Date(1664179850591)\/","DataSourceStatus":[{"DataSource":{"DataSourceId":REDACTED,"DataSourceName":"C:\\","DSType":0,"PolicyId":0,"LogicalPath":"","State":0},"JobState":9,"FileProgress":{"Changed":0,"Failed":0,"Progress":0,"Total":0,"CurrentFile":""},"ByteProgress":{"Changed":0,"Failed":0,"Progress":0,"Total":0},"ErrorInfo":{"DetailedErrorCode":-2147024877,"ErrorCode":536900934,"DetailedErrorSource":null}}],"JobState":9,"FailedFileLog":"","ErrorInfo":{[b]"DetailedErrorCode":-2147024877[/b],"ErrorCode":536900934,"DetailedErrorSource":null},"EndTime":"\/Date(1664179877193)\/","RecoveryPointDateTime":"\/Date(-11644473600000)\/"}},"DetailedError":{"DlsErrorCode":30022,[b]"DetailedErrorCode":"The media is write protected (0x80070013)"[/b],"Success":false,"Problem":"","Resolution":"","ExceptionDetails":"","RecommendedAction":0}},"ObjectType":"Alerts","Operation":"Add"}]},"IsAsync":false,"Resync":true,"AgentDetails":{"BackupEngineInfo":{},"ContainerType":"OBS","GatewayProviderVersion":{"Major":2,"Minor":0,"Build":9249,"Revision":0,"MajorRevision":0,"MinorRevision":0}},"SyncGroupName":"AlertSyncGroup","PreviousCheckpoint":"","CurrentCheckpoint":"26/09/2022 09:11:25","SyncTime":"\/Date(1664179885022)\/"}}{PostData length = 1416}{x-ms-client-request-id = 5c7387f8-6007-4e88-b676-8fa45af80e03}

 

Checking the Backup log in Azure corroborates this information:

Error details
Error Code: [NULL]
Error Code: The media is write protected (0x80070013)
Recommended action: [NULL]

 

CBEngineCurr also shows a multitude of similar entries:

2248	20FC	09/26	10:03:41.643	18	FileWriter.cpp(693)		DC197CBE-C829-4627-BD23-58F8932CE837		WARNING	Failed: Hr: = [[b]0x80070013[/b]] SetFileInformationByHandle on file  \\?\Volume{50efa3ad-66e1-492c-8df9-65b855e11ad1}\ failed
2248	20FC	09/26	10:03:41.643	18	FSWrapper.cpp(672)	[000002ABF885F160]	DC197CBE-C829-4627-BD23-58F8932CE837		WARNING	Failed: Hr: = [[b]0x80070013[/b]] : Encountered Failure: : lVal : ::SetFileInformationByHandle( hFile, FileInformationClass, lpFileInformation, dwBufferSize)
2248	20FC	09/26	10:03:41.643	32	FSReserver.cpp(116)	[000002ABF885F160]	DC197CBE-C829-4627-BD23-58F8932CE837		WARNING	Failed: Hr: = [[b]0x80070013[/b]] : Encountered Failure: : lVal : CFSWrapper::SetFileInformationByHandle( hFile, FileInformationClass, lpFileInformation, dwBufferSize )
2248	20FC	09/26	10:03:41.643	18	FSWrapper.cpp(116)	[000002ABF885F160]	DC197CBE-C829-4627-BD23-58F8932CE837		WARNING	Failed: Hr: = [[b]0x80070013[/b]] BackupWrite Failed for handle: 0x1c88
2248	20FC	09/26	10:03:41.643	18	MtfDirectory.cpp(558)	[000002ABF8619AA0]	DC197CBE-C829-4627-BD23-58F8932CE837		WARNING	Failed: Hr: = [[b]0x80070013[/b]] SetNextBuffer failed on : \\?\Volume{fe1484e0-f9c8-405e-af81-5655525a0a28}\.
2248	20FC	09/26	10:03:41.643	70	ContinueOnFailureHandler.cpp(474)	[000002ABF76C7BA0]	DC197CBE-C829-4627-BD23-58F8932CE837		WARNING	CContinueOnFailureHandler :: SetNextFailedFile entered ( hrReason:[b]0x80070013 [/b], dsmStatus:10, Logical File File Path:\\?\Volume{fe1484e0-f9c8-405e-af81-5655525a0a28}\, Physical file Path: (null), File Info Type:0, FileId: 0)
2248	20FC	09/26	10:03:41.643	70	ContinueOnFailureHandler.cpp(495)	[000002ABF76C7BA0]	DC197CBE-C829-4627-BD23-58F8932CE837		WARNING	Can't continue for this failure
2248	283C	09/26	10:13:35.296	71	async.cpp(1040)		30FD6CC3-A572-4678-B5E4-8EA33761FE9B		FATAL	Hr: = [[b]0x80070013[/b]] DoAsync operation failed.

 

• The device has appeared under $Vault\Backup Items\Azure Backup Agent, with Last backup state logged as Failed. Makes sense.
  
• I increased the Scratch size to 25GB/7% (MS recommend it be between 5 and 10%). There is more than 25GB empty space on the local disk. I also excluded the scratch location from the backup (C:\Program Files\Microsoft Azure Recovery Services Agent\Scratch)
  
• I found some chatter about OneDrive being the issue, initially I tried excluding the C:\Users folder but that proved fruitless, next I entirely uninstalled OneDrive from the machine, still no change.
  
• Other servers from another school in the trust are backing up successfully.
  
• The hostname for this machine is unique.
  
• This test machine has not previously been backed up by DPM, so there is no potential conflict with previous backups being taken via a different method.
  
• GPResult /scope:computer tells me that the "Fixed Data Drives": "Deny write access to fixed drives not protected by Bitlocker" GPO is not set
  

 

Has anybody encountered this one before?

Edited September 26, 2022 by Garacesh