Skip to content

Commit ac4253b

Browse files
Merge pull request #234706 from msaenzbosupport/patch-14
[Doc-A-THon]Updating the code block
2 parents dc21681 + 8d844fc commit ac4253b

File tree

1 file changed

+17
-10
lines changed

1 file changed

+17
-10
lines changed

articles/backup/backup-azure-vm-file-recovery-troubleshoot.md

Lines changed: 17 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -46,12 +46,15 @@ This section provides steps to troubleshoot common issues you might experience w
4646
1. Ensure you have the [required permissions to download the script](./backup-azure-restore-files-from-vm.md#select-recovery-point-who-can-generate-script).
4747
1. Verify the connection to the Azure target IPs. Run one of the following commands from an elevated command prompt:
4848

49-
`nslookup download.microsoft.com`
50-
49+
```bash
50+
nslookup download.microsoft.com
51+
```
5152
or
5253

53-
`ping download.microsoft.com`
54-
54+
```bash
55+
ping download.microsoft.com
56+
```
57+
5558
### The script downloads successfully, but fails to run
5659

5760
When you run the Python script for Item Level Recovery (ILR) on SUSE Linux Enterprise Server 12 SP4, it fails with the error "iscsi_tcp module can’t be loaded" or "iscsi_tcp_module not found".
@@ -67,11 +70,14 @@ You might see an "Exception caught while connecting to target" error message.
6770
1. Ensure the machine where the script is run meets the [access requirements](./backup-azure-restore-files-from-vm.md#step-4-access-requirements-to-successfully-run-the-script).
6871
1. Verify the connection to the Azure target IPs. Run one of the following commands from an elevated command prompt:
6972

70-
`nslookup download.microsoft.com`
71-
73+
```bash
74+
nslookup download.microsoft.com
75+
```
7276
or
7377

74-
`ping download.microsoft.com`
78+
```bash
79+
ping download.microsoft.com
80+
```
7581
1. Ensure access to iSCSI outbound port 3260.
7682
1. Check for a firewall or NSG blocking traffic to Azure target IPs or recovery service URLs.
7783
1. Make sure your antivirus software isn't blocking the execution of the script.
@@ -115,8 +121,9 @@ To resolve this issue, check if the volume is encrypted with a third-party appli
115121

116122
1. Sign in to the backed-up VM and run this command:
117123

118-
`lsblk -f`
119-
124+
```bash
125+
lsblk -f
126+
```
120127
![Screenshot showing the results of the command to list block devices.](./media/backup-azure-restore-files-from-vm/disk-without-volume-5.png)
121128

122129
1. Verify the file system and encryption. If the volume is encrypted, file recovery isn't supported. Learn more at [Support matrix for Azure VM backup](./backup-support-matrix-iaas.md#support-for-file-level-restore).
@@ -168,4 +175,4 @@ Check if the source server has disk deduplication enabled. If it does, ensure th
168175

169176
## Next steps
170177

171-
- [Recover files and folders from Azure virtual machine backup](backup-azure-restore-files-from-vm.md)
178+
- [Recover files and folders from Azure virtual machine backup](backup-azure-restore-files-from-vm.md)

0 commit comments

Comments
 (0)