January 9, 2020 at 11:05 pm
I'm not sure what you mean by pull. Do you mean copy the backup file? SQL backups from from the instance and are written to files. If you are looking for a copy after the backup is complete, that's an interesting question. I'll have to ask the team since I don't remember the architecture here.
January 9, 2020 at 11:57 pm
Good luck with that. Not sure third party tools make this better, but you're welcome to eval SQL Backup from Redgate if it might help
Yeah, I've trialed it a couple times here on my homelab (MAN I wish I could have JUST ONE test server that wasn't locked down 6 ways to Sunday at work!) and I like the interface and such.
Plus, I know it'd be easier if I had to give someone the basics to cover for me!
Maybe, someday, I'll get a REAL backup person to help out...
January 10, 2020 at 8:41 am
Well, I'm finally getting one of my wishes at work and I'm simultaneously happy and worried...
I'm getting complete control over my database backups. We're cloudifying (well, they're calling it a cloud, it's really the same basic setup we've got now except the people managing the underlying hardware are in a different state) our servers (web, SQL, and others,) and the only backups the cloud provides is file-level.
So, initially, I'm going to go with the Ola scripts for the backups rather than trying to roll my own or a maintenance plan or the headaches of purchasing software. Long-term, I'd like to go with a commercial solution just to make it easier for the times I'm on vacation or after I leave, but that's a down-the-road.
Wish me luck (or skill, skill might be better)!
I've inherited Ola everywhere I go and it's great for backups but not really designed too well for restores, but I'm so happy I have Redgate SQLBackup Pro... backups are so fast and the compression (even at level 1) is super cool.
also object level recovery from a .sqb file without needing to restore is cool (by the way - I don't work for Redgate - I just bug their call centre every time I don't read the release notes on an upgragde)
MVDBA
January 10, 2020 at 8:43 am
Steve Jones - SSC Editor wrote:Good luck with that. Not sure third party tools make this better, but you're welcome to eval SQL Backup from Redgate if it might help
Yeah, I've trialed it a couple times here on my homelab (MAN I wish I could have JUST ONE test server that wasn't locked down 6 ways to Sunday at work!) and I like the interface and such.
Plus, I know it'd be easier if I had to give someone the basics to cover for me!
Maybe, someday, I'll get a REAL backup person to help out...
I heard Jeff was looking for work 🙂
MVDBA
January 10, 2020 at 1:52 pm
Steve Jones - SSC Editor wrote:Good luck with that. Not sure third party tools make this better, but you're welcome to eval SQL Backup from Redgate if it might help
Is Redgate backup able to "pull" from database servers to backup servers? I evaluated it once a while back, but it was before all the malware madness, and now I'm reading more often that pulling backups from database servers is better than pushing backups to backup servers.
Ooooo... interesting and very timely subject for me, Patrick. Do you have any favorite links on the subject of pulling rather than pushing?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 10, 2020 at 1:57 pm
also object level recovery from a .sqb file without needing to restore is cool (by the way - I don't work for Redgate - I just bug their call centre every time I don't read the release notes on an upgragde)
Now there's something I didn't know about. RedGate had stopped carrying a previous product that did such a thing and I got lazy and stopped looking to see if there was some other way within RedGate to do object level recoveries. Is that something they have documented on their site?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 10, 2020 at 2:01 pm
Do you have any favorite links on the subject of pulling rather than pushing?
Hmmmm ...
January 10, 2020 at 2:03 pm
jasona.work wrote:also object level recovery from a .sqb file without needing to restore is cool (by the way - I don't work for Redgate - I just bug their call centre every time I don't read the release notes on an upgragde)
Now there's something I didn't know about. RedGate had stopped carrying a previous product that did such a thing and I got lazy and stopped looking to see if there was some other way within RedGate to do object level recoveries. Is that something they have documented on their site?
we've been doing it using sql comparesq version 14 - source is a backup, target is a database.... it's not always fast though, same with sql data compare
MVDBA
January 10, 2020 at 2:12 pm
Honestly, I thought we had pulled this from the product, but I was wrong. Here you go, object level recovery in Redgate SQL Backup.
"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
January 10, 2020 at 2:15 pm
jasona.work wrote:Steve Jones - SSC Editor wrote:Good luck with that. Not sure third party tools make this better, but you're welcome to eval SQL Backup from Redgate if it might help
Yeah, I've trialed it a couple times here on my homelab (MAN I wish I could have JUST ONE test server that wasn't locked down 6 ways to Sunday at work!) and I like the interface and such.
Plus, I know it'd be easier if I had to give someone the basics to cover for me!
Maybe, someday, I'll get a REAL backup person to help out...
I heard Jeff was looking for work 🙂
BWAAAA-HAAAA!!!! Just to be sure... NOT! Like I tell the recruiters that email me, I'm currently working my dream job. I'm doing interesting work with good people for good money and a commute so short that I could ride a unicycle to work without getting chaff marks. Besides, I'm so busy that if I get any busier, I'd need to be twins. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
January 10, 2020 at 2:18 pm
Honestly, I thought we had pulled this from the product, but I was wrong. Here you go, object level recovery in Redgate SQL Backup.
That was my understanding, as well. Thanks for the link, Grant. I'll have a look.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 10, 2020 at 2:18 pm
Honestly, I thought we had pulled this from the product, but I was wrong. Here you go, object level recovery in Redgate SQL Backup.
ha - I hadn't even spotted that way of doing it
MVDBA
January 10, 2020 at 2:19 pm
Honestly, I thought we had pulled this from the product, but I was wrong. Here you go, object level recovery in Redgate SQL Backup.
ha , I hadn't even spotted that way of doing it
MVDBA
January 10, 2020 at 2:21 pm
Do you have any favorite links on the subject of pulling rather than pushing?
Hmmmm ...
Nah thought I had one but no luck retrieving it.
I get better luck when just dropping sql server from the search, ie., googling with the phrase: backup pull vs push.
The bottom line for me is that if your server that needs backup has privileges to "push" the backup to the remote backup server, then in the event the server needing backup gets owned, the writeable remote backup location is also at risk, whereas if the backup server "pulls" from a read only share on the backup client (like the database server containing the .bak you want saved), its less succeptible to security breeches on the database server, and since it can pull from a read only share, the client (database) server is also protected somewhat from the backup server getting taken down.
January 10, 2020 at 2:23 pm
Phil Parkin wrote:Do you have any favorite links on the subject of pulling rather than pushing?
Hmmmm ...
Nah thought I had one but no luck retrieving it.
I get better luck when just dropping sql server from the search, ie., googling with the phrase: backup pull vs push.
The bottom line for me is that if your server that needs backup has privileges to "push" the backup to the remote backup server, then in the event the server needing backup gets owned, the writeable remote backup location is also at risk, whereas if the backup server "pulls" from a read only share on the backup client (like the database server containing the .bak you want saved), its less succeptible to security breeches on the database server, and since it can pull from a read only share, the client (database) server is also protected somewhat from the backup server getting taken down.
We can "pull" the backup from a read only share, yes. Why would you not be able to do that?
"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
Viewing 15 posts - 64,321 through 64,335 (of 66,815 total)
You must be logged in to reply to this topic. Login to reply