Forum Discussion

zoetaite's avatar
zoetaite
Level 4
14 years ago

Backup Schedules fail : 0xe00084f4

Hello,

   Over the last few nights both our schedules for our SQL servers began to fail. The funny thing is there are no other issues with the other servers.

Final error: 0xe00084f4 - An unknown error has occurred. Final error category: System Errors For additional information regarding this error refer to link V-79-57344-34036

All data is backed up by a B2D folder which resides on a Netgear 2100 iSCSI NAS. The NAS resides in a different location and is attached by a 20Mbps VBR PVLAN. There is plenty of free disk. I have also tried creating a new backup job, created a new device pool - same result. I also updated the firmware on the NAS device.

I re-directed the job to another server which resides in the same location as our stand alone Backup EXEC media server. End result it worked. Tried once again and the funny thing is it backed up the data (compared the Byte count), so it appears to be working, but once again it looks like it hangs then it alerts that the job has failed. I have been monitoring the connection and there are no errors being flagged in the logs + like I said other schedules are still working which backup to the same NAS device.

Looking through the event logs here is some of the information:

1. An error occurred while processing a B2D command.
Drive: InitWrite() CreateFile failed (\\sbushapp01.server.local\SQL\B2D000385.bkf).  Error=64

2. Storage device "SBUSHAPP01 SQL" reported an error on a request to write data to media.

Error reported:
The specified network name is no longer available.

Any help would be appreciated!

Thanx

ZT

2010
Backup and Recovery
Backup Exec
  • sksujeet's avatar
    sksujeet
    Level 6
    14 years ago

    The specified network name is no longer available.

    It seems it is loosing the connectivity with the B2D folder. Can you please delete the B2D folder from the devices tab in the BE. Don't worry it will not loose the data as we are just removing the link but not the actual B2D folder. Once removed restart the BE services and try to add the same B2D folder again.

    Also make sure all the Be services are started under the domain account except remote agent which should be under local system account.

  • zoetaite's avatar
    zoetaite
    Level 4
    14 years ago

    Just tried deleting the B2D folder & re-adding, but still didn't work.

    I also tried creating a new schedule, new B2D folder, and a new media set - still failed.

    I looked on the physical SQL server. Re-started the SQL agent. Looked in the Windows 2003 R2 logs and noticed the following:

    An error occurred while attempting to log in to the following server: "SQLServer".
    SQL error number: "0011".
    SQL error message: "[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.".

    An error occurred while attempting to log in to the following server: "SQLServer".
    SQL error number: "4818".
    SQL error message: "Login failed for user 'DOMAIN\sa-backup'.".

    For this SQL box the way it currently backs up is SQL performs a local backup and saves the files as .BAK. I then go after that folder. Been doing this since June 2010 with no issues until the last 4 days. Nothing has changed on the servers (i.e. MS patches).

    ZT

  • pkh's avatar
    pkh
    Moderator
    14 years ago

    I don't understand.  You are using the BE SQL agent to backup your database and then you are using the SQL backup utility to back to .bak files.  Why are you doing double backups?

  • zoetaite's avatar
    zoetaite
    Level 4
    14 years ago

    We have 2 separate SQL servers.

    Server1 -  We use the SQL agent to go after the SQL data "Microsoft SQL server" (.mdf)

    Server 2 - We have the SQL agent installed (before my time), but on this server SQL backs up the data to a local drive (.bak). Then we backup that folder. Maybe we should look at removing the SQL agent and just install a normal agent.

    The result though over the last 4 nights is that both schedules are failing. I ran a disk parity last night on my NetGEAR 2100 and everything passed. This morning I created a new B2D on a server in our datacenter and the schedule passed, and the data was successfully backed up.

    Points to the NAS, but there are no errors being flagged and it has the latest firmware installed. I also have another server (File/Print node) that also gets backed up to the same NAS, but there haven't been an issues.

    ZT

  • Ken_Putnam's avatar
    Ken_Putnam
    Level 6
    14 years ago

    RAWS has always been rather fragile over WAN/PVN links, even (though 20Mbps should be sufficient bandwidth)  and such backups are generally not recommended
     

     

    {edited for spelling}

  • zoetaite's avatar
    zoetaite
    Level 4
    14 years ago

    Would it be worth opening a case up with Symantec. Been working like a charm for 6 months then boom. I know they probably won't do much seeing that everything is pointing to the NAS. I will give NetGEAR a call as well to see if they can offer any suggestions.

    Thanx for all the help!

     

    ZT

  • pkh's avatar
    pkh
    Moderator
    14 years ago

    To isolate the problem, I would suggest that you change the backup to a local disk for both servers.  If the jobs run successfully, then it is the NAS or the WAN link that is the problem.  As Ken said, it is not advisable to backup over a WAN link.  They are just too unreliable.

    As an aside, for the second SQL server, you should not remove the SQL Agent.  Instead, you should use it to backup your SQL databases.  Forget about backing up to .bak and then backing those up.  It is too much trouble.

  • sksujeet's avatar
    sksujeet
    Level 6
    14 years ago

    I am quite confused what you are trying to do? Just to make thing clear I would like to confirm if all the backup that goes to NAS is getting failed or it is only SQL backup.

    Have you updated the firmware of your NAS recently?

    If all the backups that goes to NAS is getting failed them make sure you have the access to that NAS and correct credentials are setup on the NAS.