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

Strange issue with one of the four Sharepoint databases that we Log ship to our DR site. Expand / Collapse
Author
Message
Posted Tuesday, March 19, 2013 4:13 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, August 18, 2014 7:46 AM
Points: 18, Visits: 201
On the server that hosts our Sharepoint databases we are log shipping 4 of them to a sql server instance at our DR site. The issue we are seeing is that for one of the 4 databases the first transaction log generated by the Log Shipping scheduled task after the full backup has been taken is the same size as the database itself (2.4Gb). Following this all subsquent files genrated are much smaller (200 Mb).

I have checked for open / long running transactions but none are reported.

Out of the 4 Sharepoint databases the one with the issue is the only one that has any Sharepoint Workflows configured. However they are configured to run in response to actions rather than at a certain time of day.

Both Servers are SQL Server 2008 SP3 Standard 64 bit.

Has anyone got any thoughts on what might be causing this behavoiur.



Post #1432549
Posted Tuesday, March 19, 2013 5:06 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, November 28, 2013 10:20 PM
Points: 45, Visits: 309
Have you checked this multiple times, are the results same all the time?
There would be transactions/ changes that were in progress when you took the backup and needs to be backed up.
What happens when you take another FULL backup and a Tlog backup following that?

To dig further, you may want to use "RESTORE HEADER ONLY" for the backup taken and review the DatabaseBackupLSN and CHECKPOINTLSN. This might give you a hint for why the LOG Backup is big.

Can also get the similar details from: "msdb..backupset"

Reviewing the above for both backup sets can provide more clarity.
Post #1432571
Posted Wednesday, March 20, 2013 12:48 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, August 18, 2014 7:46 AM
Points: 18, Visits: 201
After investigating further it seems to not be related to when a full backup is taken. It seems to be something to do with either the index optimisation scripts we run, or the fact that the Sharepoint workflows seem to insert a lot of rows into the EventCache table between midnight and 2am.


Post #1433019
Posted Wednesday, March 20, 2013 2:52 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, November 28, 2013 10:20 PM
Points: 45, Visits: 309
Thanks for the update!
Post #1433066
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse