October 29, 2010 at 9:05 am
I am running into a bit of a problem that I am not sure where to look to resolve the problem. I have a SQL 2000 server (OS = Windows 2003) that can perform a 65 GB full database backup without a problem. However, I have a 40 GB database on a SQL Server 2005, Windows 2008 OS server that gets a file system limitation error. If I stripe the backup to make 4 smaller files then it backs up the database without issue. This same database was able to create one backup file without error until it got to be about 40 GB. I am wondering if anyone can help point me to the file system limitation issue and where to look to see why I can't have it create one backup file?
I am up for any suggestions.
Thanks
Sherri
October 29, 2010 at 9:27 am
That is strange, NTFS has no limit other than the hard limit of the HDD. Fat32, there is a limit of 4GB and and for FAT16 a limit of 2 GB. If you are using NTFS, then it should never be a problem.
-Roy
October 29, 2010 at 9:39 am
Thanks Roy. I just verified on the server that it is NTFS. The drive has over 500 GB free (it is a SAN Blade attached to this server).
October 29, 2010 at 9:45 am
What's the exact error you're getting?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 29, 2010 at 9:55 am
Gail, here is what the event log says (I blocked out the database name otherwise it is exactly what the message says):
BackupMedium::ReportIoError: write failure on backup device 'E:\SQLBackups\UserDB\<databasename>\<databasename>_backup_201010290100.bak'. Operating system error 665(The requested operation could not be completed due to a file system limitation).
October 29, 2010 at 10:08 am
Native SQL backup or 3rd party tool?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 29, 2010 at 10:28 am
Native SQL Server backup.
October 29, 2010 at 10:32 am
Using compressed file/folder? backup fails then arround 35 Gb
October 29, 2010 at 10:45 am
Like Marco mentioned it could be due to compressed folders. Please go through this discussion
Pradeep Adiga
Blog: sqldbadiaries.com
Twitter: @pradeepadiga
October 29, 2010 at 11:10 am
It is a compressed folder. So I am guessing that I am going to have to either work with the server team and see if we can uncompress that folder or else I am going to have to stripe my backups to keep the file size down below 35 GB? Or is there another option?
Thanks again everyone.
Sherri
October 29, 2010 at 11:27 am
dont compress will be the prefered option (backup will also be faster)
As you dont run sql 2008 you are not able to compress youre backup during backup (hmm that sounds funny)
If you have enough diskspace dont compress
If you have enough diskspace to make a uncompressed backup but not to store it there long enough script a rar command for it, love always to see how backup files and up with only 10 to 25% of the originale space.
But i can understand you dont want a heavy compress tool running on youre server. So consider get enough diskspace either local or on a share
October 29, 2010 at 12:28 pm
Thanks everyone. I will work with my server guys to see if I can get them to uncompress that folder.
Thanks again.
Sherri
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply