Refresh Azure VM with a new Linux OS












0















I created several VMs in Azure classic cloud service several years ago, and would like to retain them (size setting, DNS names, etc). But it looks impossible to me, as the old portal doesn't even exist any more and there seems no way to reuse the old DNS names, i.e., the cloud service. So here is my question,



What would Azure Linux VMs different from each other, apart from the obvious machine/host name, UUID etc?



If MS Azure doesn't support Refresh Azure VM to a new version officially, would the traditional *nix's tar save & restore do the trick? Or there are better tools nowadays?



PS. I don't like the Ubuntu's apt upgrade route because according to the docs that I read, it is not recommended and not guaranteed either, if I am to bring up my Ubuntu 15.04 to the latest.










share|improve this question























  • Any 15.04 should have been updated a long time ago, before Trump got elected.

    – GabrielaGarcia
    Nov 12 '18 at 9:17











  • Not mine I'm afraid @GabrielaGarcia

    – xpt
    Nov 12 '18 at 14:17
















0















I created several VMs in Azure classic cloud service several years ago, and would like to retain them (size setting, DNS names, etc). But it looks impossible to me, as the old portal doesn't even exist any more and there seems no way to reuse the old DNS names, i.e., the cloud service. So here is my question,



What would Azure Linux VMs different from each other, apart from the obvious machine/host name, UUID etc?



If MS Azure doesn't support Refresh Azure VM to a new version officially, would the traditional *nix's tar save & restore do the trick? Or there are better tools nowadays?



PS. I don't like the Ubuntu's apt upgrade route because according to the docs that I read, it is not recommended and not guaranteed either, if I am to bring up my Ubuntu 15.04 to the latest.










share|improve this question























  • Any 15.04 should have been updated a long time ago, before Trump got elected.

    – GabrielaGarcia
    Nov 12 '18 at 9:17











  • Not mine I'm afraid @GabrielaGarcia

    – xpt
    Nov 12 '18 at 14:17














0












0








0








I created several VMs in Azure classic cloud service several years ago, and would like to retain them (size setting, DNS names, etc). But it looks impossible to me, as the old portal doesn't even exist any more and there seems no way to reuse the old DNS names, i.e., the cloud service. So here is my question,



What would Azure Linux VMs different from each other, apart from the obvious machine/host name, UUID etc?



If MS Azure doesn't support Refresh Azure VM to a new version officially, would the traditional *nix's tar save & restore do the trick? Or there are better tools nowadays?



PS. I don't like the Ubuntu's apt upgrade route because according to the docs that I read, it is not recommended and not guaranteed either, if I am to bring up my Ubuntu 15.04 to the latest.










share|improve this question














I created several VMs in Azure classic cloud service several years ago, and would like to retain them (size setting, DNS names, etc). But it looks impossible to me, as the old portal doesn't even exist any more and there seems no way to reuse the old DNS names, i.e., the cloud service. So here is my question,



What would Azure Linux VMs different from each other, apart from the obvious machine/host name, UUID etc?



If MS Azure doesn't support Refresh Azure VM to a new version officially, would the traditional *nix's tar save & restore do the trick? Or there are better tools nowadays?



PS. I don't like the Ubuntu's apt upgrade route because according to the docs that I read, it is not recommended and not guaranteed either, if I am to bring up my Ubuntu 15.04 to the latest.







linux ubuntu virtual-machine system-restore azure






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 11 '18 at 22:44









xptxpt

3,161115389




3,161115389













  • Any 15.04 should have been updated a long time ago, before Trump got elected.

    – GabrielaGarcia
    Nov 12 '18 at 9:17











  • Not mine I'm afraid @GabrielaGarcia

    – xpt
    Nov 12 '18 at 14:17



















  • Any 15.04 should have been updated a long time ago, before Trump got elected.

    – GabrielaGarcia
    Nov 12 '18 at 9:17











  • Not mine I'm afraid @GabrielaGarcia

    – xpt
    Nov 12 '18 at 14:17

















Any 15.04 should have been updated a long time ago, before Trump got elected.

– GabrielaGarcia
Nov 12 '18 at 9:17





Any 15.04 should have been updated a long time ago, before Trump got elected.

– GabrielaGarcia
Nov 12 '18 at 9:17













Not mine I'm afraid @GabrielaGarcia

– xpt
Nov 12 '18 at 14:17





Not mine I'm afraid @GabrielaGarcia

– xpt
Nov 12 '18 at 14:17










1 Answer
1






active

oldest

votes


















1














First, the Azure VM is just a logic group that consists of serial resources and it also a resource at the same time. The VM differ from others according to the resource ID which Azure set. So does all the Azure resources. In the same tenant, same subscription, the resource ID is unique which differs from others.



Then, you can convert the VM from Classic to ARM through convert the os disk to managed disk and then create a new VM with the managed disk. Follow the steps Migrate the VM.






share|improve this answer
























  • I would like to retain those Azure classic VMs (size setting, DNS names, etc) as is, without converting them to ARM. But thanks for helpging though. upvoting.

    – xpt
    Dec 21 '18 at 14:50











  • So what you really want?

    – Charles Xu - MSFT
    Dec 22 '18 at 8:39











  • Have I not made myself clear enough? What part of my request you don't understand? I don't want to Migrate the VM, I want to keep them as-is as the classic cloud service.

    – xpt
    Dec 24 '18 at 16:02













Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1374577%2frefresh-azure-vm-with-a-new-linux-os%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









1














First, the Azure VM is just a logic group that consists of serial resources and it also a resource at the same time. The VM differ from others according to the resource ID which Azure set. So does all the Azure resources. In the same tenant, same subscription, the resource ID is unique which differs from others.



Then, you can convert the VM from Classic to ARM through convert the os disk to managed disk and then create a new VM with the managed disk. Follow the steps Migrate the VM.






share|improve this answer
























  • I would like to retain those Azure classic VMs (size setting, DNS names, etc) as is, without converting them to ARM. But thanks for helpging though. upvoting.

    – xpt
    Dec 21 '18 at 14:50











  • So what you really want?

    – Charles Xu - MSFT
    Dec 22 '18 at 8:39











  • Have I not made myself clear enough? What part of my request you don't understand? I don't want to Migrate the VM, I want to keep them as-is as the classic cloud service.

    – xpt
    Dec 24 '18 at 16:02


















1














First, the Azure VM is just a logic group that consists of serial resources and it also a resource at the same time. The VM differ from others according to the resource ID which Azure set. So does all the Azure resources. In the same tenant, same subscription, the resource ID is unique which differs from others.



Then, you can convert the VM from Classic to ARM through convert the os disk to managed disk and then create a new VM with the managed disk. Follow the steps Migrate the VM.






share|improve this answer
























  • I would like to retain those Azure classic VMs (size setting, DNS names, etc) as is, without converting them to ARM. But thanks for helpging though. upvoting.

    – xpt
    Dec 21 '18 at 14:50











  • So what you really want?

    – Charles Xu - MSFT
    Dec 22 '18 at 8:39











  • Have I not made myself clear enough? What part of my request you don't understand? I don't want to Migrate the VM, I want to keep them as-is as the classic cloud service.

    – xpt
    Dec 24 '18 at 16:02
















1












1








1







First, the Azure VM is just a logic group that consists of serial resources and it also a resource at the same time. The VM differ from others according to the resource ID which Azure set. So does all the Azure resources. In the same tenant, same subscription, the resource ID is unique which differs from others.



Then, you can convert the VM from Classic to ARM through convert the os disk to managed disk and then create a new VM with the managed disk. Follow the steps Migrate the VM.






share|improve this answer













First, the Azure VM is just a logic group that consists of serial resources and it also a resource at the same time. The VM differ from others according to the resource ID which Azure set. So does all the Azure resources. In the same tenant, same subscription, the resource ID is unique which differs from others.



Then, you can convert the VM from Classic to ARM through convert the os disk to managed disk and then create a new VM with the managed disk. Follow the steps Migrate the VM.







share|improve this answer












share|improve this answer



share|improve this answer










answered Dec 21 '18 at 9:17









Charles Xu - MSFTCharles Xu - MSFT

2584




2584













  • I would like to retain those Azure classic VMs (size setting, DNS names, etc) as is, without converting them to ARM. But thanks for helpging though. upvoting.

    – xpt
    Dec 21 '18 at 14:50











  • So what you really want?

    – Charles Xu - MSFT
    Dec 22 '18 at 8:39











  • Have I not made myself clear enough? What part of my request you don't understand? I don't want to Migrate the VM, I want to keep them as-is as the classic cloud service.

    – xpt
    Dec 24 '18 at 16:02





















  • I would like to retain those Azure classic VMs (size setting, DNS names, etc) as is, without converting them to ARM. But thanks for helpging though. upvoting.

    – xpt
    Dec 21 '18 at 14:50











  • So what you really want?

    – Charles Xu - MSFT
    Dec 22 '18 at 8:39











  • Have I not made myself clear enough? What part of my request you don't understand? I don't want to Migrate the VM, I want to keep them as-is as the classic cloud service.

    – xpt
    Dec 24 '18 at 16:02



















I would like to retain those Azure classic VMs (size setting, DNS names, etc) as is, without converting them to ARM. But thanks for helpging though. upvoting.

– xpt
Dec 21 '18 at 14:50





I would like to retain those Azure classic VMs (size setting, DNS names, etc) as is, without converting them to ARM. But thanks for helpging though. upvoting.

– xpt
Dec 21 '18 at 14:50













So what you really want?

– Charles Xu - MSFT
Dec 22 '18 at 8:39





So what you really want?

– Charles Xu - MSFT
Dec 22 '18 at 8:39













Have I not made myself clear enough? What part of my request you don't understand? I don't want to Migrate the VM, I want to keep them as-is as the classic cloud service.

– xpt
Dec 24 '18 at 16:02







Have I not made myself clear enough? What part of my request you don't understand? I don't want to Migrate the VM, I want to keep them as-is as the classic cloud service.

– xpt
Dec 24 '18 at 16:02




















draft saved

draft discarded




















































Thanks for contributing an answer to Super User!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1374577%2frefresh-azure-vm-with-a-new-linux-os%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Terni

A new problem with tex4ht and tikz

Sun Ra