Backup Compression

Question

Post reply

Backup Compression

forsqlserver

SSCoach

Points: 18902
More actions
January 4, 2012 at 8:58 pm

#250848

Comments posted to this topic are about the item Backup Compression
Thanks

Viewing 15 posts - 1 through 15 (of 30 total)

You must be logged in to reply to this topic. Login to reply

Ron McCullough SSC Guru Points: 63877 More actions · Answer 1

Nice question

If everything seems to be going well, you have obviously overlooked something.

Ron

Please help us, help you -before posting a question please read[/url]
Before posting a performance problem please read[/url]

Paul White SSC Guru Points: 150468 More actions · Answer 2

That's two wrong in a row for me

Paul White
All articles available on SQL.kiwi
@SQL_Kiwi

Kwex Default port Points: 1407 More actions · Answer 3

First attempt this year, and was lucky

Good question ... thanks.

Kwex.

Thomas Abraham SSChampion Points: 10761 More actions · Answer 4

Thanks for the easy and straightforward question. Sometimes not having to think hard first thing in the morning is great.

And then I started thinking ... but WHY can't they co-exist? Is it a design choice, or is there a physical limitation that prevents this from being implementable?

[font="Verdana"]Please don't go. The drones need you. They look up to you.[/font]
Connect to me on LinkedIn

Britt Cluff SSCertifiable Points: 5083 More actions · Answer 5

Went with my gut and got it right. Thanks for the question.

http://brittcluff.blogspot.com/

M&M SSC-Insane Points: 21700 More actions · Answer 6

M&M

SSC-Insane

Points: 21700

January 5, 2012 at 5:55 am

#1428944

Good question, thanks.

M&M

arun1_m1 SSCommitted Points: 1949 More actions · Answer 7

Hi,

More information about the restriction can be found at the below link;

http://support.microsoft.com/kb/2297053

arun1_m1 SSCommitted Points: 1949 More actions · Answer 8

Thomas Abraham (1/5/2012)
Thanks for the easy and straightforward question. Sometimes not having to think hard first thing in the morning is great.
And then I started thinking ... but WHY can't they co-exist? Is it a design choice, or is there a physical limitation that prevents this from being implementable?

Hi ,

You can find more information at the below link;

http://support.microsoft.com/kb/2297053

Thomas Abraham SSChampion Points: 10761 More actions · Answer 9

arun1_m1 (1/5/2012)
Thomas Abraham (1/5/2012)
Thanks for the easy and straightforward question. Sometimes not having to think hard first thing in the morning is great.
And then I started thinking ... but WHY can't they co-exist? Is it a design choice, or is there a physical limitation that prevents this from being implementable?
Hi ,
You can find more information at the below link;
http://support.microsoft.com/kb/2297053

Thanks for the link. However, I don't think it explains the underlying reason that this must be the case. It explains the results of attempting to add a backup in the different permutations, but it doesn't explain WHY that MUST be the way it works. What is there about mixing a compressed and uncompressed backup in the same media set that is either impossible or undesirable to implement?

[font="Verdana"]Please don't go. The drones need you. They look up to you.[/font]
Connect to me on LinkedIn

jeff.mason SSCrazy Eights Points: 9585 More actions · Answer 10

Exactly. I agree that this limitation really makes no sense. There's no reason why two backups can't go to the same file, one compressed, one not compressed, and that link merely explains how and not why.

SQLRNNR SSC Guru Points: 281334 More actions · Answer 11

Gut said one way, but never tried it the way the third option said. Went with gut and got it right.

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

DBA_Dom SSCrazy Points: 2902 More actions · Answer 12

I happened to have been researching this just a few months ago since we have started to go with compressed backups for the servers that support it. Nice question.

sknox SSChampion Points: 12388 More actions · Answer 13

Thomas Abraham (1/5/2012)
arun1_m1 (1/5/2012)
Thomas Abraham (1/5/2012)
Thanks for the easy and straightforward question. Sometimes not having to think hard first thing in the morning is great.
And then I started thinking ... but WHY can't they co-exist? Is it a design choice, or is there a physical limitation that prevents this from being implementable?
Hi ,
You can find more information at the below link;
http://support.microsoft.com/kb/2297053
Thanks for the link. However, I don't think it explains the underlying reason that this must be the case. ...

But it does answer at least part of your question. As the article states, the compression setting is stored in (and hence read from) the header of the media set. That, at least, was clearly a design choice on Microsoft's part. Why they made that choice is anyone's guess.

My guess is that it was inherited from tape systems, as the compression option for tape was historically implemented in firmware because back in the day general purpose CPUs weren't fast enough or were too busy doing other tasks to compress the data as well.

jeff.mason SSCrazy Eights Points: 9585 More actions · Answer 14

That brings up an interesting question -- how many DBAs have their backups go straight to tape? In my professional career I have never had a backup infrastructure where the SQL Server was backing up straight to tape; we always do backup to disk first and then a subsequent backup to tape. That way the backups are locally available for other purposes. Isn't the idea of setting up a backup process to primarily center around tape options a little bit archaic in itself? I mean, you want to keep the tape options in the system, but I would think that file-based options would be more in line with the typical default structures. And to use a "media set" to drive backup issues assumes that you are using tape, IMO.

Backup Compression

Cookies on SQLServerCentral