StoreOnce and Backup Exec Error

[glarson3]

We purchased the StoreOnce 3620 and we're attempting to use Backup Exec on our servers.

StoreOnce 3620 (28 TB) version: 4.3.0-2132.20

Backup Exec Version: 21.4 Rev. 1200 (64-bit)

HPE StoreOnce Catalyst Plugin Version: 4.3.0 for Veritas Backup Exec

The Catalyst store is configured and can be used in Backup Exec. Our problem is that sometimes the backup works and sometimes it doesn't.

For example:

One server's incremental backup failed on 5/18/2022 but the same server's incremental backup succeeded on 5/22/2022. The error message when it fails is usually S_TF_NO_TAPE_PRESENT or Robotic Library is full.

The StoreOnce 3620 is not a tape backup, and Backup Exec is using the Catalyst store as the destination. We contacted Backup Exec and they responded that they only support CIFS for backup.

We are currently stumped on why the S_TF_NO_TAPE_PRESENT error is occurring and why the backup is failing.

Any suggestions or pointers on this problem would be greatly appreciated.

George.

[support_s]

System recommended content:

1. HPE Storage Management Pack for System Center 5.4 User Guide | HPE StoreOnce Backup warnings and errors

2. StoreOnce Backup System 2700, 2900, 4500, 4700, and 4900 User Guide

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

[neutral]

Hello @glarson3,

The error 'S_TF_NO_TAPE_PRESENT' (code 0x2000040d) is Veritas Backup exec specific error - https://www.veritas.com/support/en_US/article.100029933.

Can you please check if there are any StoreOnce virtual tape libraries involved in any of the Backup exec's backup jobs?
You can check that in StoreOnce data services. If yes, what is the percentage utilization of VTL data service?
Parallelly are you getting any errors in StoreOnce?

[glarson3]

@neutral 

We are only using Catalyst stores, we don't have any VTL or NAS setup.

There are no errors listed in the StoreOnce event log. Is there a way to enable verbose information on the StoreOnce?

[glarson3]

I did work with Backup Exec tech support for three days to resolve this problem. They finally said that they only support CIFS for the StoreOnce and told me to contact HP.

[neutral]

Hello @glarson3.,

Basically, the error 'S_TF_NO_TAPE_PRESENT' is due to a tape backup failure. Either the tape media is not available or no space on the tape is available or even due to a tape backup job queue processing delay for very long (several days).
In this case, No VTL's configured in the StoreOnce. Your StoreOnce 3620 doesn't even support VTL data services. There is no question of tape media availability from StoreOnce.

The question is why the Backup Exec is looking for tape media in the StoreOnce?

You can look at the below areas:

1. In the past, was the Backup Exec connected to some other archival device (where tape library backup was configured)? Were there any residual tape library backup jobs which are not removed gracefully?

2. Are there any services running on Backup Exec that are looking for tape media space and not getting it?

3. Is the RSM service causing the issue (Pt no 3 under Solution, also check Pt 5 and 6 - https://www.veritas.com/support/en_US/article.100029933 ).

4. You may find this article helpful as well - https://www.veritas.com/support/en_US/article.100022844

If the issue has started after upgrading the backup exec to v21.4, please check if all the post requisites are completed as per this article - https://www.veritas.com/content/support/en_US/downloads/detail.REL523933#item0

This is one of the most frequently reported errors in Backup Exec. I think StoreOnce's role here is very minimal.

The error may be due to some bug in Backup Exec as well.

[glarson3]

I have tracked the problem down to Immutability. If I turn Immutability off the backups succeed. If I turn it on the backups fail with the S_TF_NO_TAPE_PRESENT. This, of course, totally defeats the purpose of the StoreOnce as we require immutability as part of our backup plan.

[sbhat09]

Hello @glarson3,

I will check about this. Can you please provide these details?

1. Were your backups ever been successful with immutability on in the past?

2. Since when the issue started? Do you think of any changes or administrative actions in correlation to the issue?

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of the company.

[glarson3]

@sbhat09 

Backups were intermittently successful when Immutability was on. Sometimes they succeed. Usually, they failed. I was unable to detect a rhyme or reason for the success or failure.

They have all been successful since I turned off Immutability on the StoreOnce 3620. This has been an issue since we purchased the StoreOnce server and Veritas Backup Exec

[Jyothiyash]

Hi Glarson3,

Thanks for the details. We will check and update you regarding this.

[glarson3]

Should I open a case with tech support for this issue?

[sbhat09]

Hello @glarson3,

I have put it to the relevant team to take a look. I am expecting an update by tomorrow.

To find the root cause of this issue, it requires a detailed log analysis. Parallelly, it will be good if you can raise support case as well. Because we have some limitation here in forum to collect all required data.

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of the company.

[sbhat09]

Hello @glarson3,

While I was trying to find more about the issue, I got a chance to discuss this with one of the senior experts and found this document.
As per the StoreOnce G4 Support Matrix, Catalyst store Data Immutability (DI) is not available for Veritas Backup Exec (pg no 26) - https://spock.corp.int.hpe.com/spock/utility/document.aspx?docurl=Shared%20Documents/hw/nearline/storeonce_compatibility_g4_matrix.pdf

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of the company.

[glarson3]

That document appears to be an internal HP document. Is there a way to get a copy of it?

[sbhat09 · Accepted solution]

Hello @glarson3,

There is no option to share the share documents here. So, I am pasting the screenshot:

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of the company.

[glarson3]

Thanks for sharing.

What do Server DI and ISV DI mean?

[glarson3]

I tracked it down to Data Immutability.

Thanks for tracking down this document.

[sbhat09]

Hello @glarson3,

Good to know you found it. I had mentioned it "Data Immutability (DI)" in my Monday's post in this chain above.

Regards,
Srinivas Bhat

If you feel this was helpful please click the KUDOS! thumb below!
Note: All of my comments are my own and are not any official representation of the company.