SOBR Capacity Tier Offloads Broken Since v10 Update

[mmartin@emcllc.com]

I was advised to post here regarding this issue, in case anyone has suggestions or can help with Support Case escalation.

Since performing the v10 update to our VBR server, our SOBR performance tier offloads to Amazon S3-based capacity tier (via "move" job) have ceased to function; prior to the v10 update, we were using v9.5u4, and the SOBR offloads were succeeding without fail. We have not had a successful SOBR offload since fall of 2020.

In the meantime, our performance tier - and as a result, our backup storage in general - is nearly full. We currently have ~70 TB of GFS backup copies sitting in our performance tier waiting to offload.

So far, registry entries have been changed, SOBR jobs have been disabled to stop exacerbation of the capacity problem, and permissions have been checked.

Interestingly, re-scanning the Scale-out Backup Repository fails, and log entries suggest that access to the ADMIN$ share on the backup server is failing, even though the share remains in place, and both the NTAUTHORITY\SYSTEM account and the active profile both have Administrator rights on the server.

We opened a support case on January 22nd, 2021, and have yet to reach any resolution as of March 15th. Our assigned Tier 2 support engineer is consulting with a Tier 3 engineer, and advises that our case is escalated 'as high as it can go'. If something doesn't get fixed within a week or so, we will either start failing backup jobs, or backup copy jobs, due to our storage being full.

Thanks for any suggestions or assistance that anyone can provide!

[Gostev]

Hello! Please include the support case ID, as requested when you click New Topic. We cannot help with escalation if we don't know the case number Thanks.

[dalbertson]

Hi Mike,

Are you referring to case #04603624

[mmartin@emcllc.com]

Yes, this is Case # 04603624.