This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(60.8, 84%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKS%3C/text%3E%3C/svg%3E)
I have a recovery storage vault that is storing recovery points in cloud- ZRS. I have tiering enabled and the Azure portal is telling me none of my recovery points are eligble to be moved to archive storage for cost savings. They meet the requirements of over 3 months old with more than 6 months of retention left.
How can I move my storage points to archive?
Hi Kyle,
Archive tiering isn't supported for ZRS. That is why the pricing table shows N/A:
Same is true if you are storing blobs in ZRS storage account.
Please click Accept Answer and upvote if the above was helpful.
Thanks.
-TP
Does Microsoft provide an easy method for transferring from ZRS to LRS or do I need to build. A new recovery services vault and create new policies while turning off the old back up policies?
Does Microsoft provide an easy method for transferring from ZRS to LRS or do I need to build. A new recovery services vault and create new policies while turning off the old back up policies?
Unsure if I would describe it as "easy". For example, for VM you would stop backup and retain data, move VM to new resource group, then set the VM to back up to LRS vault.I just did quick test on single VM to make sure it still worked. Backed up VM to ZRS vault, stopped backup and retained data, moved VM to different resource group, set it to back up to LRS vault. If I go to ZRS vault the restore point is there if I want to trigger restore. Please see article below:
Must preserve previous backed-up data
I tried this process and received errors. I tried to move the entire contents of the RG to a new RG and received an error message of:
{"message":"The resource batch move request has '1' validation errors. Diagnostic information: timestamp '20250326T164920Z', tracking Id '652412a8-8734-4560-8bf3-5b7306aef75b', request correlation Id 'cc497924-7889-4c09-a8ca-8ce656f89ef5'. (Code: ResourceMoveValidationFailed) Resource move is not supported for resource types 'Microsoft.Compute/restorePointCollections'. (Code: ResourceMoveNotSupported, Target: /subscriptions/8bd33e2b-f421-49e7-bcc7-128f0d5e0665/resourceGroups/DevelopmentRG/providers/Microsoft.Compute/restorePointCollections/SAP)","code":"ResourceMoveValidationFailed","name":"ec462376-c337-452d-816f-be27a715a038","status":400}
I removed the specific item from the move that was triggering the error.
What are your thoughts on deleting the old backups and keeping them in soft delete while enabling backups to the new recovery services vault. Obviously I lose the backups after 14 days, but if they aren't required once i build up 2 weeks of new backups would that work?
If not do I need to move the entire VM to the new RG (disks, network card, and etc) or just the VM?
What are your thoughts on deleting the old backups and keeping them in soft delete while enabling backups to the new recovery services vault. Obviously I lose the backups after 14 days, but if they aren't required once i build up 2 weeks of new backups would that work?
I've not tried that so unsure if it would work. Worth a try.
If not do I need to move the entire VM to the new RG (disks, network card, and etc) or just the VM?
Just the VM is enough.
@Kyle Sicard Any update?
Yeah. Moving the VM’s by themselves works but you get warnings that certain scripts wouldn’t work until you point them at the correct resource groups.
I wasn’t interested in creating new problems for myself so I ended up soft deleting the old back up’s and then turning on a recovery plan in the new storage zone that I wanted
Sounds good. Please click Accept Answer and upvote to close up this thread.
Thank you.