![]() ![]() $snapshoturl = Checkpoint-blob -BlobUrl $bloburl -AccountName $storageaccountname -AccountKey $storageaccesskey Once the VM has stopped, you can use the Cerebrata cmdlet to take the snapshot. Stop-AzureVM -ServiceName $servicename -Name $vmname If you take the snapshot while the VM is running you won’t get the running state, so when you restore and start your VM it’ll come up in a crash-consistent state. Remember, that the snapshot operation is performed on the blob storage object, so you’ll take a snapshot of whatever is persisted to disk. This is a relatively straightforward affair, but it would be a good idea to shut the VM down first. The URL of the blob representing the VD ($bloburl).The Azure location of your VM ($location).The storage container name where the vhd resides ($containerName).The storage access key ($storageaccesskey).The storage account name ($storageaccountname).The service name your VM belongs to ($servicename).The various bits of account information for Azure, as noted in the Azure cmdlets getting started guide here.You’ll need a couple things before this will work: It seems that Microsoft changed something in Azure that means the method presented in that link no longer works (more on that in a minute) and probably means that my method will cease to work at some point in the future too. I’ve updated the steps to work with Azure now (April 2013). Solutionįollowing on from work here which uses the Cerebrata Azure Management cmdlets. ![]() Unfortunately, Azure doesn’t currently support this, although it does support snapshots of a blob, which gives us a possible option. You want to take a snapshot of it, so you can revert back to it at a later date. ![]()
0 Comments
Leave a Reply. |