July 21, 2008 at 6:55 am
I have been running backups (Full and TLOG) over the network to one Server.
I use SQL Maint plans and the UNC path for the Backup destination.
recently I have switched to another destination server on the same network. This new backup Server supposedly has more horsepower and it does h ave lots more storage.
Problem I'm having is my backups are failing with this error:
Executed as user: SUPREME\SQLKofC. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
and this in the backuplog:
* spid69 BackupDiskFile::RequestDurableMedia: failure on backup device '\\kocsqllab02\SQL BACKUPS\KOCALT01\Altiris_db_200807210743.BAK'. Operating system error 64(The specified network name is no longer available.).
* backup BACKUP failed to complete the command BACKUP DATABASE [Altiris] TO DISK = N'\\kocsqllab02\SQL BACKUPS\KOCALT01\Altiris_db_200807210743.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
* backup Database backed up: Database: Altiris_Incidents, creation date(time): 2006/02/22(16:32:41), pages dumped: 4518, first LSN: 10369:224:1, last LSN: 10369:226:1, number of dump devices: 1, device information: (FILE=1, TYPE=DISK: {'\\kocsqllab02\SQL BACKUPS\KOCALT01\Altiris_Incidents_db_200807210822.BAK'}).
--
Can anyone help me troubleshoot this? to me it looks like a Network problem .. maybe the switch that the new dest server is attached to or the NIC or something..
ANyone seen this before???
July 21, 2008 at 7:49 am
There are a lot of posts regarding backing up to a network share on this site. Not recommended but plenty of people do it anyway. Do you have proper permissions to the new share? The account running the SQL agent must have read/write permissions, at a minimum.
-- You can't be late until you show up.
July 21, 2008 at 7:56 am
Yes.. permissions are fine.. I can backup most databases to this server.. it's the DBs over a GB that timeout with a Network error.. and it's only to this one server.. they run fine to other servers..
backups to tape are not an option here.. tape drives are old and very slow and very busy..
I thought backups with maint plans over network were my best option. now I'm stuck.. I can do backups to each local server where there is a SQL Instance.. but that doesn't help me if the server dies..
July 21, 2008 at 8:32 am
A 1Gb database is not large by any means. How about enough free space available on the server to handle the size of the backup? Is it butting heads with another job? Have you done a CHECKDB on the database to ensure there isn't any corruption? What's in the job history?
I guess I'm a little confused because the third message states "database backed up". Are you running a MP with both full and log backups in the same job? What service pack are you running, if any?
Check out these:
http://forums.databasejournal.com/archive/index.php/t-12388.html
http://www.dbforums.com/t812439.html
http://sql-server-performance.com/Community/forums/t/4946.aspx
http://www.sqlservercentral.com/Forums/Topic532254-24-1.aspx
edit - added last link. May be of some value.
-- You can't be late until you show up.
July 21, 2008 at 8:33 am
Hi,
because of timeoutproblems with the network and/or firewall (the network admins didnt see any problems on the network 😉 )we do a local dump and then copy the dump with system cmd comands to the backupserver.
so we have a fast backup/restore and in case of a server crash a second copy on a backup server. not a highlevel solution but it works fine..
regards
felix
July 22, 2008 at 5:44 am
Ended up being a probably with the antiquated SAN that was attached as a volume on the Server.
Backing up to the same Server now - but a locally attached drive and everything is working fine!
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply