December 18, 2024 at 11:19 am
I''m running a stripped backup (2 files) to a Network share. It's a 32gig machine in which 10gig free and has 4 cpu's .. Cpu % around 50%.
I'm using compression and it's creating those 2 files 340gig each runs for about 10 minutes then fails. I have plenty of space on the network share. I have tried using 6 files and still get same failure.
I am getting this message:
BackupIoRequest::ReportIoError: write failure on backup device
Operating system error 8(Not enough memory resources are available to process this command.).
THanks.
December 18, 2024 at 11:42 am
December 18, 2024 at 12:50 pm
Just my 2ct: did you try to checkpoint all databases before running the backup ?
btw: We mostly produce local backup files and only copy those afterward to a safe zone to avoid all network related issues ( which we have had years ago )
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
December 18, 2024 at 2:51 pm
I started backup right after a server down\up ...
The backup for the past month was working fine... just started this issue a few days ago.
I'm going to try a local backup and see if that works.
It created 2 files 343gig a piece so far it's running.
December 18, 2024 at 4:13 pm
Just my 2ct: did you try to checkpoint all databases before running the backup ?
btw: We mostly produce local backup files and only copy those afterward to a safe zone to avoid all network related issues ( which we have had years ago )
Ditto. Networking steps on backups far too easily. Taking it out of the loop for the initial backup can make a huge difference.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 19, 2024 at 8:17 am
I started backup right after a server down\up ...
The backup for the past month was working fine... just started this issue a few days ago.
I'm going to try a local backup and see if that works.
It created 2 files 343gig a piece so far it's running.
Double check your target folder so no one enabled compression on it !
In the early days, the sql server intance even crashed if the remote target drive or folder had conpression enabled.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
December 23, 2024 at 8:28 am
I agree that network issues can be a problem when doing a backup to a remote location, but if the network works correctly then having the backup stored remotely has advantages.
At my old place we had built an on-prem cloud using 100% MS software. (This became possible with Win2019) and 100% ssd/nvme. All SQL servers ran as Hyper-V guests and all databases and all backups were all held on storage pools in the local site. The backup pool was always accessed via a network share. After doing a backup, Hyper-V replication then copied the backups to a remote site. Because the networking at the local site was virtual, I do not recall any backup failure due to network issues.
However, if your topology involves physical networking then ensuring the network is not a point of failure becomes harder work. You say the network issues are new - I suggest you talk to your manager and get the issue raised with your network people. You have a bit of leverage in that the network issues are killing your business RTO and RPO objectives for business continuity.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
December 23, 2024 at 10:17 am
Thanks for replies..
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy