4/18/2023 0 Comments Symboliclinker not workingBut we decided that the symbolic-links approach would be faster and wouldn’t require an additional data-disk, and with it, additional costs. Of course there are other methods overcoming this challenge, such as switching the drive letters with a data-disk and moving the PageFile to the other drive letter. The symbolic-links creation would be accomplished with either the mklink command, or with the New-Item cmdlet in PowerShell 5.x. Choosing a solutionĪfter thorough testing of course, we decided to create two symbolic links from the D: drive to the real directories in the OS disk (where the directories were already present as part of the image). ![]() The directories paths were hard-coded in the application and were a couple of gigabytes in size, so copying them to the temporary drive each time the VMs were deployed would be time and resource consuming. In this specific scenario, the customer had a 3rd party legacy application that reads and writes from two directories in the D: drive. The data on the temporary drive is not migrated, but the OS disk is obviously preserved from the vhd in your storage account or managed-disk. So if your VM is re-deployed (due to host updates, host failures, resizing, etc.), the VM is recreated on a new host and the VM will be assigned a new temporary drive on the new host. It is temporary because the storage is assigned from the local storage on the physical host. In an Azure Windows VM you automatically get a temporary disk drive mapped to D: (on Linux it’s mapped to /dev/sdb1).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |