%3CLINGO-SUB%20id%3D%22lingo-sub-369153%22%20slang%3D%22en-US%22%3ELesson%20Learned%20%2355%3A%20Azure%20SQL%20Managed%20Instance%20-%20Backup%20failed%20for%20Server%20%22servername%22.%20Failed%3A%201117%20-The%20request%20could%20not%20be%20performed%20because%20of%20an%20I%2FO%20device%20error%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-369153%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3EFirst%20published%20on%20MSDN%20on%20Jan%2013%2C%202019%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20Hello%2C%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20I%20found%20several%20service%20requests%20that%20our%20customers%20are%26nbsp%3Btrying%20to%20proceed%20with%20a%20backup%20of%20a%20Azure%20SQL%20Managed%20Instance%20to%20Azure%20Storage%20Account%20and%20they%20are%20facing%20an%20error%2C%20after%26nbsp%3Breaching%26nbsp%3B40%25%3A%20Backup%26nbsp%3Bfailed%26nbsp%3Bfor%26nbsp%3BServer%26nbsp%3B%22servername%22.%26nbsp%3BFailed%3A%26nbsp%3B1117%26nbsp%3B(The%26nbsp%3Brequest%26nbsp%3Bcould%26nbsp%3Bnot%26nbsp%3Bbe%26nbsp%3Bperformed%26nbsp%3Bbecause%26nbsp%3Bof%26nbsp%3Ban%26nbsp%3BI%2FO%26nbsp%3Bdevice%26nbsp%3Berror).%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20%3CSTRONG%3E%20Working%20on%20this%20issue%20I%20found%3A%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CUL%3E%3CBR%20%2F%3E%3CLI%3EI%20found%20that%20the%20size%20of%20the%20database%20is%20%2B%2F-%20300%20GB.%3C%2FLI%3E%3CBR%20%2F%3E%3CLI%3EThe%20error%20message%20reported%20an%20I%2FO%20device%20error%20but%20not%20that%20the%20Azure%20Storage%20Account%20space%20is%20full.%3C%2FLI%3E%3CBR%20%2F%3E%3C%2FUL%3E%3CBR%20%2F%3E%20%3CSTRONG%3E%20As%20solution%20I%20suggested%3A%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%3CUL%3E%3CBR%20%2F%3E%3CLI%3ETo%20use%20the%20stripping%20backup%20mode%20and%20our%20customer%20was%20able%20to%20proceed%20with%20the%20backup%20due%20to%20the%20limitation%20of%20200%20GB%20of%20Azure%20Storage%20Account%20%3CA%20href%3D%22https%3A%2F%2Femea01.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fblogs.msdn.microsoft.com%252Fsqlserverstorageengine%252F2017%252F10%252F16%252Fnative-database-backup-in-azure-sql-managed-instance%252F%26amp%3Bdata%3D02%257C01%257CJmjurado%2540microsoft.com%257Ce9f8c69feb514975037d08d65514deea%257C72f988bf86f141af91ab2d7cd011db47%257C1%257C0%257C636789945463833117%26amp%3Bsdata%3Dkb86RJlrc6bl7pbUg3uI%252BhnkyEQCt1cpQeCDwATuQz4%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%20https%3A%2F%2Fblogs.msdn.microsoft.com%2Fsqlserverstorageengine%2F2017%2F10%2F16%2Fnative-database-backup-in-azure-sql-managed-instance%2F%3C%2FA%3E%3C%2FLI%3E%3CBR%20%2F%3E%3C%2FUL%3E%3CBR%20%2F%3E%20Enjoy!%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-369153%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20MSDN%20on%20Jan%2013%2C%202019%20Hello%2CI%20found%20several%20service%20requests%20that%20our%20customers%20are%26nbsp%3Btrying%20to%20proceed%20with%20a%20backup%20of%20a%20Azure%20SQL%20Managed%20Instance%20to%20Azure%20Storage%20Account%20and%20they%20are%20facing%20an%20error%2C%20after%26nbsp%3Breaching%26nbsp%3B40%25%3A%20Backup%26nbsp%3Bfailed%26nbsp%3Bfor%26nbsp%3BServer%26nbsp%3B%22servername%22.%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-369153%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EBackup%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eerror%201117%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Emanaged%20instance%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ethe%20request%20could%20not%20be%20performed%20because%20of%20an%20i%20o%20device%20error%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
First published on MSDN on Jan 13, 2019
Hello,

I found several service requests that our customers are trying to proceed with a backup of a Azure SQL Managed Instance to Azure Storage Account and they are facing an error, after reaching 40%: Backup failed for Server "servername". Failed: 1117 (The request could not be performed because of an I/O device error).

Working on this issue I found:

  • I found that the size of the database is +/- 300 GB.

  • The error message reported an I/O device error but not that the Azure Storage Account space is full.


As solution I suggested:

Enjoy!