backup big db fail

It's probably talking about memory on the server that SQL Server is running
on. Why would you possibly have the need for Enterprise Edition and 4
processors with 190GB of data but only have 2GB of memory. My laptop has
more than that. Are you using any of the 3rd part backup & compression
tools or is this a native SQL backup? If not I would highly recommend
buying one of them and adding more memory.
Andrew J. Kelly SQL MVP
"906507N" <906507N@.10090.I20034> wrote in message
news:Xns998147FE8B8D0140507NA02619@.207.46.248.16.. .
>I everybody,
> I have a big (well, this is relative) db, when I do a full db backup, the
> .bak is arount 190G
> I run under windows std server 2000, 2G mem, 4 cpu,sql server 2000
> enterprise ed.
> I backup the database to a dedicated server via UNC name with a dedicated
> network card. I have not enought space on local disk
> I do a backup every day but perhaps 1 backup per week works.
> I get the following error message :
> Error 1450 is : Insufficient system resources exist to complete the
> requested service.
> what "ressource" is not enough ? this is not the disk space since the
> target server (windows 2003 R2) has 3T free space.
> hope some one has some advise.
> thanks in advance
> BackupMedium::ReportIoError :
> chec write sur l'unit de sauvegarde \\storage\backup\Backup_22\SD_db_
> 200707291858.BAK .
> Erreur du systme d'exploitation 1450
> (Ressources systme insuffisantes pour terminer le service demand.).
> La sauvegarde n'a pas russir achever la commande
> BACKUP DATABASE [SIMD] TO DISK = N'\\storage\backup\Backup_22\SD_db_
> 200707291858.BAK'
> WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
> Internal I/O request 0x05702918:
> Op: Write, pBuffer: 0x05710000, Size: 983040,
> Position: 137109051904, RetryCount: 10, UMS: Internal: 0x0,
> InternalHigh: 0xF0000, Offset: 0xEC561A00, OffsetHigh: 0x1F, m_buf:
> 0x05710000,
> m_len: 983040, m_actualBytes: 0, m_errcode: 1450,
> BackupFile: \\storage\backup\Backup_22\SD_db_200707291858.BAK
On Aug 2, 6:55 pm, "Andrew J. Kelly" <sqlmvpnooos...@.shadhawk.com>
wrote:
> It's probably talking about memory on the server that SQL Server is running
> on. Why would you possibly have the need for Enterprise Edition and 4
> processors with 190GB of data but only have 2GB of memory. My laptop has
> more than that. Are you using any of the 3rd part backup & compression
> tools or is this a native SQL backup? If not I would highly recommend
> buying one of them and adding more memory.
> --
> Andrew J. Kelly SQL MVP
> "906507N" <9065...@.10090.I20034> wrote in message
> news:Xns998147FE8B8D0140507NA02619@.207.46.248.16.. .
>
>
>
>
>
> - Show quoted text -
That is a rather low amount of memory for a box with those
specifications and needs. I'm not sure if this problem is memory
related, but I've also read a lot of various posts in regards to
posting large files to a network location. Again, most of these will
give other errors than the ones you reported, but might be another
avenue to venture through.
|||Try it out first with a local storage - probably a USB drive that can
accommodate 190GB and dump your backup there and see what happens
"acorcoran" <acorcoran@.gmail.com> wrote in message
news:1186105163.744059.159720@.i38g2000prf.googlegr oups.com...
On Aug 2, 6:55 pm, "Andrew J. Kelly" <sqlmvpnooos...@.shadhawk.com>
wrote:
> It's probably talking about memory on the server that SQL Server is
> running
> on. Why would you possibly have the need for Enterprise Edition and 4
> processors with 190GB of data but only have 2GB of memory. My laptop has
> more than that. Are you using any of the 3rd part backup & compression
> tools or is this a native SQL backup? If not I would highly recommend
> buying one of them and adding more memory.
> --
> Andrew J. Kelly SQL MVP
> "906507N" <9065...@.10090.I20034> wrote in message
> news:Xns998147FE8B8D0140507NA02619@.207.46.248.16.. .
>
>
>
>
>
> - Show quoted text -
That is a rather low amount of memory for a box with those
specifications and needs. I'm not sure if this problem is memory
related, but I've also read a lot of various posts in regards to
posting large files to a network location. Again, most of these will
give other errors than the ones you reported, but might be another
avenue to venture through.