Hi,
First thing you need to do is stop what you’re doing and contact support.
The customer supplied key you mention is the encryption passphrase, do you still have this?
Secondly, deploying these lifecycle policies is completely unsupported so there’s a very real question of data integrity. Hence I recommend you work with support.
Veeam has a backup copy job function that works with “archive tier” object repositories such as AWS Glacier to optimise the files for long term retention, batching them for better cost efficiency for the expected long retention & low usage you’d expect from an archive tier. This is the method you should’ve used, so I’d recommend you explore this as a method of archiving data moving forwards.
I’m going to make some assumptions of what you’ve tried so far. I’m guessing you’ve restored the data to a new storage location and when you’ve tried to add the repository to Veeam it has asked you for the encryption passphrase?
Due to the way VB365 splits and stores data, lifecycle policies won’t necessarily have every object within the deep glacier so you would need all the data from every tier which is why it is critical you work with support to assess what has been done and any best effort guidance to bring the data into a recoverable state. There’s more I would add but I don’t want to speculate and steer you down a wrong path.
Thanks,
Michael
First thing you need to do is stop what you’re doing and contact support.
The customer supplied key you mention is the encryption passphrase, do you still have this?
Secondly, deploying these lifecycle policies is completely unsupported so there’s a very real question of data integrity. Hence I recommend you work with support.
Veeam has a backup copy job function that works with “archive tier” object repositories such as AWS Glacier to optimise the files for long term retention, batching them for better cost efficiency for the expected long retention & low usage you’d expect from an archive tier. This is the method you should’ve used, so I’d recommend you explore this as a method of archiving data moving forwards.
I’m going to make some assumptions of what you’ve tried so far. I’m guessing you’ve restored the data to a new storage location and when you’ve tried to add the repository to Veeam it has asked you for the encryption passphrase?
Due to the way VB365 splits and stores data, lifecycle policies won’t necessarily have every object within the deep glacier so you would need all the data from every tier which is why it is critical you work with support to assess what has been done and any best effort guidance to bring the data into a recoverable state. There’s more I would add but I don’t want to speculate and steer you down a wrong path.
Thanks,
Michael
Statistics: Posted by micoolpaul — Apr 23, 2026 10:03 pm






