When the disk is created – takes a couple of seconds – hit the save button in the disks blade of the VM. Make sure to select source type as Snapshot and refer to your existing snapshot. In the bottom you’ll see, Add Data disks, click that and then hit “Create new Disk”.įill in the right details to create your disk. Go into your target VM blade (suse in my case), open the disks blade, and hit the edit button. When the snapshot is taking, we’ll create a new disk. To take the snapshot, head over to the disk in Azure, and hit the Create Snapshot button.įollow the instructions in the next pane to create the snapshot.Ĭreating the snapshot takes about a minute or less. If you cannot shut down the source, make sure you’re not writing any files to disk when taking the snapshot to avoid corruption. Recommendation for production use cases here is to shutdown the source VM to avoid any data corruption. We need to execute three steps to copy that disk to our new VM.įirst step is taking the snapshot. Creating the snapshot, creating a disk, mounting the disk to the new VM The SUSE VM is running nothing special, just the OS disk for now. I mounted a 2TB premium disk to my Windows VM, and have 2 files there: a sort of large files (ubuntu ISO) and a text file (saying hello to myself). Let’s walk through it: Test infrastructure I had this proposal in a customer scenario recently, where we needed to move large files from a Windows Machine to a Linux Machine (SLES15). If you need to move large amounts of data from 1 VM in Azure to another VM, a easy way to move that data is rather than copying the individual files, you could take a disk snapshot, and then mount the snapshot to a new VM.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |