I am facing some typical error while taking the
Portal Backup from the front end servers. It was working fine for many
days 2 days back it started throwing error.
This is medium Server Farm Setup, with data getting stored on SAN .
My data size is approx 20 GB
Below are the error message captured in event viewer while taking the
Portal backup using spsbackup.exe.

Error captured in SharePoint Front end server

SQL Server backup failed. Error: There is not enough disk space on
server SPDB to complete the database sps_site operation. Increase the
space available and try again. , Server: SPDB, Database: sps_site,
Backup location: \\spfen1\temp1234\sps-SPDB-sps_site.SPB

Errors captured in SharePoint Back end server

18210 :
BackupMedium::ReportIoError: write failure on backup device
'\\spfen1\temp1234\sps-SPDB-sps_site.SPB'. Operating system error
64(The specified network name is no longer available.).

3041 :
BACKUP failed to complete the command BACKUP DATABASE [sps_site] TO
DISK = N'\\spfen1\temp1234\sps-SPDB-sps_site.SPB' WITH INIT ,
NOUNLOAD , NOSKIP , STATS = 5, NOFORMAT

18210 :
BackupDiskFile::RequestDurableMedia: failure on backup device
'\\spfen1\temp1234\sps-SPDB-sps_site.SPB'. Operating system error
64(The specified network name is no longer available.).


We have tested our disk controllers and disks, every thing is seems to
be fine.

Moreover we are not able to copy huge files on some of the drives on
the setup.
The errors while copping are like "cannot copy files, Path Too
Deep"

Any help will be highly appreciated.

Make sure SQLagent has required privileges on all the drives, ensure no other
programs are accessing these backup files. Better to use UNC names than the
share names within the operating system.
--
-----------------
Satya SKJ
Visit http://www.sql-server-performance.com for tips and articles on
Performance topic.


"Shailender" wrote:

Thanks for the reply,
I am using the UNC name and my drive where I am backing up has the
relevant permissions.

One more error is comming which I missed earlier.

18210 :
BackupMedium::ReportIoError: write failure on backup device
'\\ntraish\backup\test-SPDB-sps_site.SPB'. Operating system error
121(The semaphore timeout period has expired.).

Any help will be appriciated.

Check the server you are backing up to - if it has too much
activity or resource issues on it's end, you can get this
error.

-Sue

On 30 Mar 2006 20:35:26 -0800, "Shailender"
<shailenderrai (AT) gmail (DOT) com> wrote:

Thanks for the reply,
I am backing up to one of the front end server. As there are two front
end servers on NLB, none of the server are very busy at any point of
time.
Both the servers are sharing the load.

I have seen this error occur during MSSQL backups to a Network Drive when a
popular file compression program was compressing files on the Network Drive
Server. In my case, the Network Drive Server was a low-end SCSI based
device. I ended up using Task Scheduler to schedule all backups to the
Network Drive Server so they would not overlap and schedule file compression
during non-backup times. Whenever database size grows, thus causing a longer
backup time, I have seen this error condition reappear. The workaround was
to readjust the execution schedules in Task Scheduler.
--



"Shailender" wrote: