Dan,

I'm not sure I fully understand the problem. Let's get things clarified first.

So I understand you are creating backups to your StoreOnce device and after that doing object copies to Azure. Please confirm or correct if needed.

I also understand the objects on Azure are correctly seen for 12 months, only on the local StoreOnce device you do not see them anymore after 6 months (at least not from the DP perspective). Is that correct?

Please let us know what protection you see in your backup specification. Also check the Advanced options to see the Catalog protection. What is it set too?

In addition to checking the protection set in the backup spec, you could also take a look at objects which are still seen and check their protection. If you are saying that you do not see any local objects older than 6 months then I assume that you will see on the existing objects that the protection is set to 6 months indeed.

Yet something else you can double check is what objects you see on your StoreOnce device directly (so not in DP, but by checking through the StoreOnce GUI). Can you see objects older than 6 months or not?

I don't believe this will be a corruption. There must be an explanation for the behavior. Let's try to find it.

Thanks for the swift reply. Yes you are correct backups are created to the storeonce device's local stores and replicated to Azure. I cant be sure that the objects are in Azure as when I look at the Azure object browser they are obviously encrypted, but I do see files over a year old. Ive just done what you suggested and viewed the azure stores through the Storeonce and the files seem to be missing. Ive checked the protection as you suggested and its set to 52 weeks which is correct. The Catalogue protection on the replication job is set to "Same as source" (so 52 weeks). Im now worried that the media has been expired early maybe? although why would I not see a record of the replication job in the "internal database" still as I only see jobs going back 6 months, Thanks again for your help with this.

Can you log a support case for this? It may get a bit complicated to be resolved here as it may require more interactive troubleshooting.

Thanks Koen, I've just raised 02413294.

OK so if I have understood this correctly then you can see the objects through the Azure browser and they seem to be missing on the DP side. If that's indeed the case then you could use omnimm -add_slots <LibraryName> <Object> to create the slot and next you could import that slot. Hopefully there are not too many slots to be created and imported!? Also, hopefully you can easyly generate the list from your Azure browser!? in any case I would at least try 1 to see whether this works fine.

Now even when that works, it still does not explain the behavior. Please work with the support engineer to find out the root cause.

In your previous post, there are a few statements where I'm not 100% sure I understand them correctly. When you say backup are "replicated to Azure", how exactly is that done? Is that an object copy job from DP's perspective? Or is the replication done out of DP in some way?

Also where you write that you "viewed the azure stores through the Storeonce", I'm not sure what you mean. Did you mean you viewed through the Azure browser rather than StoreOnce? Or if it is really through StoreOnce then explain please.

It seems like your internal database is only showing object copies going back 6 month instead of the year that the backup was protected for. You mention using an HPE Storeonce device to replicate completed backup jobs to an Azure container, and that you can see data in the container going back a year. However, this doesn't help with restore efforts. You also mention that the Auditing feature within DataProtector shows the successful backup and replication job. Based on this information, it's possible that the IDB could be corrupt.

Hello Robert, thanks for adding more information to this thread!!!