Skip to content

Commit fa7bc47

Browse files
author
David Curwin
committed
fix capitalization
1 parent ca8038e commit fa7bc47

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/backup/backup-azure-mars-troubleshoot.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -78,10 +78,10 @@ We recommend that you check the following before you start troubleshooting Micro
7878
![Backup job completed with warnings](./media/backup-azure-mars-troubleshoot/backup-completed-with-warning.png)
7979

8080
- Conditions that can cause the backups to skip files include:
81-
- unsupported file attributes (for example: in a OneDrive folder, Compressed stream, reparse points). For the complete list, refer to the [support matrix](https://docs.microsoft.com/azure/backup/backup-support-matrix-mars-agent#supported-file-types-for-backup).
82-
- a file system issue
83-
- another process interfering (for example: antivirus software holding handles on files can prevent the MARS agent from accessing the files)
84-
- files locked by an application
81+
- Unsupported file attributes (for example: in a OneDrive folder, Compressed stream, reparse points). For the complete list, refer to the [support matrix](https://docs.microsoft.com/azure/backup/backup-support-matrix-mars-agent#supported-file-types-for-backup).
82+
- A file system issue
83+
- Another process interfering (for example: antivirus software holding handles on files can prevent the MARS agent from accessing the files)
84+
- Files locked by an application
8585

8686
- The backup service will mark these files as failed in the log file, with the following naming convention: *LastBackupFailedFilesxxxx.txt* under the *C:\Program Files\Microsoft Azure Recovery Service Agent\temp* folder.
8787
- To resolve the issue, review the log file to understand the nature of the issue:

0 commit comments

Comments
 (0)