• State Suggested Answer
  • Locked Locked
  • Replies 8 replies
  • Answers 2 answers
  • Subscribers 13 subscribers
  • Views 14990 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SQL backup failures to network share

MihirP1129
over 6 years ago

Hello,

We recently stood up a new backup enviornment using HP StoreOnce (Deduplication applicance) 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-8F

C7-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.).

Is there anything I could do on the LiteSpeed configuration side in hopes to resolve this issue?

Any help in resolving this would be greatly appreciated!

Parents
  • 0 over 6 years ago
    In addition to the steps Alexander mentioned. I would also check that your Litespeed backup script uses the below parameter.

    ,@init = 1


    If you are trying to append a Litespeed backup to a native backup ( as may happen when you run a native backup test and then a Litespeed backup test using the same backup file name with @init = 0 in the Litespeed script ) then you would get the same error you are seeing.


    EXAMPLE ERROR:

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

    If this does not help then, as Alexander mentioned, please open a support case, so we can review a Litespeed log.

    Hope that helps,
    -Ben-
Reply
  • 0 over 6 years ago
    In addition to the steps Alexander mentioned. I would also check that your Litespeed backup script uses the below parameter.

    ,@init = 1


    If you are trying to append a Litespeed backup to a native backup ( as may happen when you run a native backup test and then a Litespeed backup test using the same backup file name with @init = 0 in the Litespeed script ) then you would get the same error you are seeing.


    EXAMPLE ERROR:

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

    If this does not help then, as Alexander mentioned, please open a support case, so we can review a Litespeed log.

    Hope that helps,
    -Ben-
Children
No Data