SQL backups failing to HPE StoreOnce CIFS share

Hello EE community,

We recently stood up a new backup enviornment using HP StoreOnce as the backup target. The issue we're currently running into is when we perform a SQL backup using LiteSpeed (not compressed) to the CIFS share (\\hpeso\SQLBackups) on HP StoreOnce we get the following error:

- test backing up a 14GB database
 
Msg 61700, Level 16, State 1, Line 46
Backup of database "TestDatabase" failed.
Error saving data to file. Thread: 0
BACKUP DATABASE is terminating abnormally.
A nonrecoverable I/O error occurred on file "VDI_730BE351-F308-4C41-8FC7-B6434FD61EF6_0:" 995(The I/O operation has been aborted because of either a thread exit or an application request.).
Write on "VDI_730BE351-F308-4C41-8FC7-B6434FD61EF6_0" failed: 4(The system cannot open the file.)

And when it's compressed by LiteSpeed we get a different error writing to the same backup target:

BackupIoRequest::ReportIoError: write failure on backup device 'VDI_9F406D37-986D-4A49-AA3C-844801FE9B6C_7'. Operating system error 4(The system cannot open the file.).

Any help in resolving this would be greatly appreciated!
Michael McGovernVP of Information TechnologyAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Vitor MontalvãoMSSQL Senior EngineerCommented:
It says that the system can't open the file. Verify if the SQL Server service account has permissions to access the file.
0
Michael McGovernVP of Information TechnologyAuthor Commented:
Thanks for the respond Vitor.

The SQL service service account does access to the network share. We tested it by backing up smaller databases (1-4GB in size) without any issues. This seems to be happening on larger dbs (>10GB in size).
0
Michael McGovernVP of Information TechnologyAuthor Commented:
for troubleshooting purposes, I changed the permission on the share to allow everyone with full control  (to rule out access issues) then ran the backup job again but it failed.

CPU Seconds: 11.22
Environment: Intel(R) Xeon(R) CPU           E5620  @ 2.40GHz
CPUs: 4 logical, 4 cores, 4 physical packages.

Msg 60404, Level 16, State 1, Line 0
Backup of database "VC" failed.
Error saving data to file. Thread: 0

BACKUP DATABASE is terminating abnormally.
A nonrecoverable I/O error occurred on file "VDI_DF332AF0-703A-41E5-B04E-4C736EC52E4D_0:" 995(The I/O operation has been aborted because of either a thread exit or an application request.).
Write on "VDI_DF332AF0-703A-41E5-B04E-4C736EC52E4D_0" failed: 4(The system cannot open the file.)

Not a valid LiteSpeed™ for SQL Server® format file (Type is: 1).
Select a valid LiteSpeed™ for SQL Server® file for this restore operation.

However, if I do a SQL native backup by going to the database --> tasks --> backup and specify the location \\hpeso\SQLBackups\testdb-full.bak, it works just fine!
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Vitor MontalvãoMSSQL Senior EngineerCommented:
Oh, this is LiteSpeed. Sorry, I didn't realize that before.
Since SQL Server 2008 that I don't use LiteSpeed as the only interest I had on it was the compression but this feature is available since SQL Server 2008.
Which version of SQL Server are you using?
0
Michael McGovernVP of Information TechnologyAuthor Commented:
After countless testing, the issue was related to encryption at rest being enabled on the storage target. Not sure, why LiteSpeed would bomb the backup job because of this (maybe, because I had @verify = 1?? and it can't verify the restore process of the encrypted data). But, once we disabled the encryption at the storage, the backup succeeded. I have a case open with support to find out why is this the case as we would like to have encryption at the storage level. Funny thing is the sql native backup jobs are successful on the encrypted share, but litespeed backup jobs are not.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Vitor MontalvãoMSSQL Senior EngineerCommented:
You should get rid of litespeed in any SQL Server 2008 instance or superior version. It just doesn't justifies the use of that product as the native SQL Server provides everything that litespeed does. And it will help you save money from the litespeed licenses.
0
Michael McGovernVP of Information TechnologyAuthor Commented:
self-resolved
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Query Syntax

From novice to tech pro — start learning today.