I'm using a PowerShell script to make copies of my Azure VMs, using the reference below.
http://blogs.technet.com/b/heyscriptingguy/archive/2014/01/24/create-backups-of-virtual-machines-in-windows-azure-by-using-powershell.aspx
It was working fine the last time, until recently, with this error showing up at this line of code below. Why would a lease stop this copy operation, and is there is any PowerShell command to safely close this lease?
Start-AzureStorageBlobCopy -SrcContainer $vmOSContainerName -SrcBlob $vmOSBlobName -DestContainer $backupContainerName -Force
Start-AzureStorageBlobCopy : The remote server returned an error: (412) There is currently a lease on the blob and no lease ID was specified
in the request.. HTTP Status Code: 412 - HTTP Error Message: There is currently a lease on the blob and no lease ID was specified in the request.
At C:\Users\MarkJeremiah\Desktop\Mediacorp\PowerShell scripts\PowerShell scripts\Copy Azure blobs\Backup VM.ps1:24 char:1
+ Start-AzureStorageBlobCopy -SrcContainer $vmOSContainerName -SrcBlob $vmOSBlobNa ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : CloseError: (:) [Start-AzureStorageBlobCopy], StorageException
+ FullyQualifiedErrorId : StorageException,Microsoft.WindowsAzure.Commands.Storage.Blob.Cmdlet.StartAzureStorageBlobCopy