DP 10.8 Unable to restore Virtual Environment disk image over 6 months old despite being protected for 12 months

As above, we are using DP 10.8 so the GRE is not available as we use Vcenter 7. When I attempt to look back at the past year in the internal Database I only see object copies going back 6 months rather than the year that the backup was protected for. We use an HPE storeonce device to replicate the completed backup job from its local catalyst store to an Azure container. I can see data in the azure containers going back a year when I view the container using the object browser, but this doesn't help from a restore POV. Does this sound like the IDB could be corrupt? Another thing worth mentioning is that when I use the "Auditing" feature within DataProtector I can see the successful backup and replication job in question.

  • 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.


    Koen Verbelen
    Micro Focus Customer Care Specialist
    If this answered your question, please mark it as "Suggest as Answer" or "Verify as Answer".
    If you found this post useful, please give it a "Like".

  • 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.


    Koen Verbelen
    Micro Focus Customer Care Specialist
    If this answered your question, please mark it as "Suggest as Answer" or "Verify as Answer".
    If you found this post useful, please give it a "Like".

  • 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.


    Koen Verbelen
    Micro Focus Customer Care Specialist
    If this answered your question, please mark it as "Suggest as Answer" or "Verify as Answer".
    If you found this post useful, please give it a "Like".