Azure Linux VM restart issue (older version of VM instead of last one)

Question

Hello all,

Today I've decided to restart my linux VM on azure

Operating system
Linux (debian 9.5)
Size
Standard A2m v2 (2 vcpus, 16 GiB memory)

When the restart was done. I connected to my VM only to find that it went back to the past(or an older version of it?)
All the data are from 2020. Instead of this year 2022

Does anyone know how can I get back my last VM?

Thanks in advance,
Sincerely,

Answer 1

Thank you Pituach for your answer.

I found the real issue.
When I restarted my linux VM. my disks were mounted differently and i was going into an old path. so I had to revert them with fstab...

Don't know how it happened since it wasn't the first time that I've rebooted my VM.

Answer 2

Hi,

Does anyone know how can I get back my last VM?

I am not sure if you have a newer backup version at this time, but you can check it. Try to follow the documentation on how to restore to a point in time

https://learn.microsoft.com/azure/backup/backup-azure-arm-restore-vms?WT.mc_id=DP-MVP-5001699

The short version is:

(1) Navigate to Backup center in the Azure portal

(2) click Restore from the Overview tab

(3) Select backup instance and click on Select backup instance

(4) In the windows on the right that opened for you, select the relevant VM

Hopefully you will see newer restore point.

Check the time of the most new back if this fit your need

If this did not solve your issue, then someone will need to make some manually check on the specific subscription which we cannot obviously - open a new support ticket from your Azure subscription

Answer 3

Hello @Al , thank you for sharing the resolution steps that helped you fix the issue. Re-summarizing the steps below.
As you mentioned, after restarting your Linux VM, you found that your VM went into an older version and all the data was from 2020, instead of 2022. You said that the VMs disks were mounted differently and you were accessing an incorrect disk (that stored the older data) from the mountpoint (path) - that you thought was the correct one.
After changing the entries in the fstab file (/etc/fstab) and placing the correct mountpoint (path) against the disk's UUID, you were able to access the recent files for 2022, and your issue got resolved.
(Fstab is used to create persistent mountpoints across reboots).
Thanks for using Microsoft QnA and helping us to continuously improve our community.