Full backup: OSCLT_ERR_SERVER_OFFLINE. Err: -1404 | #04665764

[buk3ta]

Hi,

I am currently facing backup to tape issues with "Full backup: OSCLT_ERR_SERVER_OFFLINE. Err: -1404" error message. My current setup is using VBR10a with HPE StoreOnce as the backup repository.

Already logged a case to Veeam support (04665764) and they advised me to upgrade my StoreOnce to the latest firmware version. Currently in a planning phase of upgrading but are there any possible issues that make this issue to happen?

Kindly share your experience guys!

Thx

[Natalia Lupacheva]

Hi Jufri,

As you can see from here and here, the reasons of this message can be different, so I would say it worth it to continue with Support.
Support engineers are able to analyse your logs and find the reason of the problem.

Thanks!

[foggy]

Hi Jufri, what StoreOnce firmware version are you running? Provided it is one of the supported ones (3.15.1 is the minimum requirement), there are no tape-out issues we're aware of that could be solved exclusively by the upgrade, so I'd continue looking deeper with the help of support. Just to confirm, you're not doing Catalyst Copy to a secondary repository, are you?

[buk3ta]

Hi Foggy,

I am currently running on 3.18.X firmware for my StoreOnce. Yes I do have Catalyst Copy job running. Is it the possible cause of the issue? Because the same symptoms occured to my other StoreOnce as well which is a newer version.

[foggy]

Support for Catalyst Copy jobs as the source for Backup to Tape jobs was added in v11, so I'd expect issues on v10a.

[buk3ta]

Oh, in my current setup I am using Catalyst Copy feature to replicate backup files from HQ StoreOnce to DR StoreOnce which both are backup to disk setup.

On my issue, I am created another backup job and monitor whether the issue is still persist because data corruption can be one of the reason right?

[foggy]

So you're copying backups from the HQ StoreOnce to tape then, not from the Catalyst Copy target repository?

[buk3ta]

Hi Foggy,

Yes it is. I have resolved the issue by creating a new source backup job (the one that encountered the error message) by cloning it and set the secondary destination to the tape job.

Now my backup to tape job is success without any error.