Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««12

Backing up a DB with log shipping turned on Expand / Collapse
Author
Message
Posted Monday, July 21, 2014 12:12 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Today @ 4:56 PM
Points: 31,168, Visits: 15,612
GilaMonster (7/16/2014)
Steve Jones - SSC Editor (7/16/2014)
Yes. I believe you can use copy only, which avoids this


Full backups do not break the log chain. Copy only on full backups is solely to avoid resetting the differential base.


Ahh, sorry, was thinking you mentioned extra log backups, which are problematic.

Fulls don't matter, as Gail mentioned







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1594744
Posted Monday, July 21, 2014 2:23 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 7:13 PM
Points: 6,466, Visits: 13,919
Steve Jones - SSC Editor (7/21/2014)
GilaMonster (7/16/2014)
Steve Jones - SSC Editor (7/16/2014)
Yes. I believe you can use copy only, which avoids this


Full backups do not break the log chain. Copy only on full backups is solely to avoid resetting the differential base.


Ahh, sorry, was thinking you mentioned extra log backups, which are problematic.

Fulls don't matter, as Gail mentioned

They don't affect log backups but they do affect differential backups


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1594829
Posted Monday, July 21, 2014 10:51 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 9:36 PM
Points: 35,347, Visits: 31,885
Perry Whittle (7/21/2014)
Steve Jones - SSC Editor (7/21/2014)
GilaMonster (7/16/2014)
Steve Jones - SSC Editor (7/16/2014)
Yes. I believe you can use copy only, which avoids this


Full backups do not break the log chain. Copy only on full backups is solely to avoid resetting the differential base.


Ahh, sorry, was thinking you mentioned extra log backups, which are problematic.

Fulls don't matter, as Gail mentioned

They don't affect log backups but they do affect differential backups


Technically, I agree but if you do a full backup to a different drive or folder than where the backups are normally stored at (or even the same folder) and someone deletes it, I believe (haven't tried it in a very long time and don't remember for sure) that can screw up the GUI for doing a restore because MSDB still thinks the file exists.


--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1594928
Posted Wednesday, July 23, 2014 11:48 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Today @ 4:49 PM
Points: 105, Visits: 379
ONLY Full backup and Differential Backup, No T log backup!!!!!!!
Post #1595635
Posted Wednesday, July 23, 2014 4:12 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 7:13 PM
Points: 6,466, Visits: 13,919
Jeff Moden (7/21/2014)
Perry Whittle (7/21/2014)
Steve Jones - SSC Editor (7/21/2014)
GilaMonster (7/16/2014)
Steve Jones - SSC Editor (7/16/2014)
Yes. I believe you can use copy only, which avoids this


Full backups do not break the log chain. Copy only on full backups is solely to avoid resetting the differential base.


Ahh, sorry, was thinking you mentioned extra log backups, which are problematic.

Fulls don't matter, as Gail mentioned

They don't affect log backups but they do affect differential backups


Technically, I agree but if you do a full backup to a different drive or folder than where the backups are normally stored at (or even the same folder) and someone deletes it, I believe (haven't tried it in a very long time and don't remember for sure) that can screw up the GUI for doing a restore because MSDB still thinks the file exists.

If you take a log backup to different drive or delete it the same is true, so I don't see your point.


-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs"
Post #1595745
Posted Thursday, July 24, 2014 10:44 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 9:36 PM
Points: 35,347, Visits: 31,885
Perry Whittle (7/23/2014)
Jeff Moden (7/21/2014)
Perry Whittle (7/21/2014)
Steve Jones - SSC Editor (7/21/2014)
GilaMonster (7/16/2014)
Steve Jones - SSC Editor (7/16/2014)
Yes. I believe you can use copy only, which avoids this


Full backups do not break the log chain. Copy only on full backups is solely to avoid resetting the differential base.


Ahh, sorry, was thinking you mentioned extra log backups, which are problematic.

Fulls don't matter, as Gail mentioned

They don't affect log backups but they do affect differential backups


Technically, I agree but if you do a full backup to a different drive or folder than where the backups are normally stored at (or even the same folder) and someone deletes it, I believe (haven't tried it in a very long time and don't remember for sure) that can screw up the GUI for doing a restore because MSDB still thinks the file exists.

If you take a log backup to different drive or delete it the same is true, so I don't see your point.


Ah. Apologies. Missing information. I'm talking about folks that may take an ad hoc backup for purposes of doing a restore to a different machine (as some do to make "Dev Copies") and then deleting them (as they should) when they're done. They forget that MSDB is going to remember that the backup was made and deleting the file can mess up what the GUI sees for doing a restore. It doesn't "kill" anything but it can make it a bit confusing.

I haven't actually tried it for several revs of SQL Server. It may be that the GUI now simply ignores missing full backups if the log file chain is intact and, of course, having a missing full backup doesn't change the log file chain.


--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1595961
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse