Skip to content

Commit 8091bcc

Browse files
author
AbhishekMallick-MS
committed
CSS doc ask - Added script for manual clearing of files
1 parent cefed11 commit 8091bcc

File tree

2 files changed

+4
-3
lines changed

2 files changed

+4
-3
lines changed

articles/backup/backup-azure-restore-files-from-vm.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Recover files and folders from Azure VM backup
33
description: In this article, learn how to recover files and folders from an Azure virtual machine recovery point.
44
ms.topic: how-to
5-
ms.date: 06/30/2023
5+
ms.date: 04/12/2024
66
ms.custom: references_regions
77
ms.service: backup
88
author: AbhishekMallick-MS
@@ -353,7 +353,8 @@ After identifying the files and copying them to a local storage location, remove
353353

354354
Once the disks have been unmounted, you'll receive a message. It may take a few minutes for the connection to refresh so that you can remove the disks.
355355

356-
In Linux, after the connection to the recovery point is severed, the OS doesn't remove the corresponding mount paths automatically. The mount paths exist as "orphan" volumes and are visible, but throw an error when you access/write the files. They can be manually removed. The script, when run, identifies any such volumes existing from any previous recovery points and cleans them up upon consent.
356+
In Linux, after the connection to the recovery point is severed, the OS doesn't remove the corresponding mount paths automatically. The mount paths exist as "orphan" volumes and are visible, but throw an error when you access/write the files. They can be manually removed
357+
by running the script with 'clean' parameter (`python scriptName.py clean`). The script, when run, identifies any such volumes existing from any previous recovery points and cleans them up upon consent.
357358

358359
> [!NOTE]
359360
> Make sure that the connection is closed after the required files are restored. This is important, especially in the scenario where the machine in which the script is executed is also configured for backup. If the connection is still open, the subsequent backup might fail with the error "UserErrorUnableToOpenMount". This happens because the mounted drives/volumes are assumed to be available and when accessed they might fail because the underlying storage, that is, the iSCSI target server may not available. Cleaning up the connection will remove these drives/volumes and so they won't be available during backup.

articles/backup/backup-azure-vm-backup-faq.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -298,7 +298,7 @@ sections:
298298
299299
- question: How do I clear iSCSI session and it's processes after running the Python script for Linux ILR?
300300
answer: |
301-
After you unmount disks from the Azure portal, run the Python script `<python file name>` with `clean` parameter to clear the session and remove the mount paths of the recovery point from the machine.
301+
After you unmount disks from the Azure portal, run the Python script with `clean` parameter (`python scriptName.py clean`) to clear the session and remove the mount paths of the recovery point from the machine.
302302
303303
- name: Manage VM backups
304304
questions:

0 commit comments

Comments
 (0)