Azure-docs: Step14 - Recover a file

[tapialuism]

The temp drive letter is has two files.. "data loss readme......" and "IMC.hiv" where do I locate the file to paste to wwwroot?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 959d21ed-cd7b-dece-d206-8a207f780dad
• Version Independent ID: e440a3e5-f953-ac2f-334c-4d771ed2d009
• Content: Tutorial - Back up Windows virtual machines in the Azure portal
• Content Source: articles/virtual-machines/windows/tutorial-backup-vms.md
• Service: virtual-machines-windows
• GitHub Login: @cynthn
• Microsoft Alias: cynthn

[Karishma-Tiwari-MSFT]

Thanks for the feedback! We are currently investigating and will update you shortly.

[Karishma-Tiwari-MSFT]

@cynthn Can you please share your insights on this one? Thanks.

[cynthn]

@tapialuism I think you might be looking at the wrong drive letter. It sounds like you are looking at the temporary drive for the VM (possibly D:) and not the mount point for the backup (which would be a different drive letter, further down the alphabet).

[Karishma-Tiwari-MSFT]

@tapialuism Did you get a chance to take a look shared above? Please let us know if that helped. Thanks.

[tapialuism]

I will dive in today to take a look. I do recall the that the only drive
letter was D. I’ll check again if the results are the same I’ll repeat the
procedure beginning from installing IIS.
I will keep you informed.

On Fri, Oct 5, 2018 at 9:31 AM Karishma Tiwari - MSFT <
[email protected]> wrote:

@tapialuism https://github.com/tapialuism Did you get a chance to take
a look shared above? Please let us know if that helped. Thanks.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/16033#issuecomment-427424499,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ApBWaFx0lwsWW2ukMYgkgMKDGM5ECKYzks5uh4lWgaJpZM4XEj6I
.

[tapialuism]

I tried again I ran the script and received the error below and the script never finishes.
"Exception calling "GetDirectoryName" with "1" argument(s): "Illegal characters in path."
At line:52 char:1

• $CurrentDir = [System.IO.Path]::GetDirectoryName($myInvocation.MyComm ...
• ~~~~~~~~~~~~~~~~~
  
  
  
  • CategoryInfo : NotSpecified: (:) [], MethodInvocationException
  
  
  • FullyQualifiedErrorId : ArgumentException"
  
  

The error is referring to this line;
$CurrentDir = [System.IO.Path]::GetDirectoryName($myInvocation.MyCommand.Definition)

[Karishma-Tiwari-MSFT]

@tapialuism Can you please confirm that you selected the old recovery point which contains the iisstart.png file and not the recovery point from which you deleted the iisstart.png file.

[Karishma-Tiwari-MSFT]

@tapialuism I followed the tutorial and I was also not able to find a drive letter (Step 14). I am working with the product team to understand whether this is a bug or by design. In any case, we will make sure that the document is updated to reflect the expected outcome.

The workaround solution that you can use is :

1. Click on Search and Type 'Create and Format hard disk partitions' or 'Disk Management'.
2. From the disk management screen, identify the additional disks related to the recovery point. Right-click on it and click on 'Change driver letter and paths'. Select a drive letter, for example G: drive.

1. Got to G: drive and you will find iisstart.png file there.
2. You can now copy this file from G: and paste it to \inetpubwwwroot

Please retry with the above steps and share the results with me. Thanks.
You can use this doc to configure IIS on the VM.

[cynthn]

@Karishma-Tiwari-MSFT it sounds like what you are saying is the .exe that is downloaded isn't creating a mount point for the backup anymore? I was going to test it myself, since I ran through it multiple times when I wrote the doc. It may be that they changed the behavior of the .exe or it might be broken (which is what I think you suspect).

[Karishma-Tiwari-MSFT]

@cynthn That's correct. I am about to share the details/observations about it, with you, in an email.

[cynthn]

@Karishma-Tiwari-MSFT FYI - when I ran the .exe, I got the following (password removed) which has "0 recovery volumes attached":

Microsoft Azure VM Backup - File Recovery

---

Please enter the 15 character password, shown on the portal, to securely connect to the recovery point: xxxxxxxxxx

Connecting to recovery point using ISCSI service....
WARNING: Waiting for service 'Microsoft iSCSI Initiator Service (MSiSCSI)' to start...

Connection succeeded!

Please wait while we attach volumes of the recovery point.

0 recovery volumes attached

*** Open Explorer to browse for files ***

After recovery, to remove the disks and close the connection to the recovery point, please click 'Unmount Disks' in step 3 of the portal.

Press 'Q/q' key to exit ...

[Karishma-Tiwari-MSFT]

@cynthn Yes, this is exactly what I am seeing. I shared the details in the email. Thanks for testing it out. :)

[Karishma-Tiwari-MSFT]

@tapialuism We will close this issue now. We are working internally on the issue with the Product team and will share any updates here. Until then, please follow the workaround as shared above.
Feel free to reopen, if you have additional questions. Thanks.

It is fixed now.

[tapialuism]

Thanks.

[samuelkajindran]

Hi Team, Do we have any update on this bug? We seeing the same issue "0 recovery volumes attached" and unable to assign a drive letter because there isn't any new recovery "Disk" discovered in Disk Management in the first place.

[SAIMMINHAS]

No one is bothering to reply...!

[cynthn]

reopen @SAIMMINHAS, the Issue is currently closed, so folks might not be getting notified. I thought this was fixed. Have you tried this recently?

[SAIMMINHAS]

Hi guys,

I've double checked again and it's sorted. 1 question though, when i run the File recovery script on the VM, it creates 2 mapped drives. One is 'C:\' drive while the other is a temporary storage drive. Due to some reason, it does not creates another mapped drive which is also available in a vm by default. Any idea why this happens?

It's just that if i had to recover a file from that 2nd drive, then it should also be mapped through the script.

[SAIMMINHAS]

It's the above visible 'D:\' drive that does not appears after the Script. Not sure why.

[SAIMMINHAS]

?????

[Karishma-Tiwari-MSFT]

@SAIMMINHAS Sorry for the delay on this. We would need a support engineer to do live troubleshoot with you on this. Can you please send an email to [email protected] with your subscription Id and link to this thread. Please include in the subject 'Attn: Karishma'.
I will enable support request for you and provide further instructions on it.

[SAIMMINHAS]

Hi Karishma,

I've now done as asked.

Many thanks.

[Karishma-Tiwari-MSFT]

Thanks @SAIMMINHAS
I replied over your email.
I will close this issue, once you have it resolved, we can share the resolution here.