Is this a good SharePoint SQL Backup and Maintenance Plan Strategy?

%3CLINGO-SUB%20id%3D%22lingo-sub-2274520%22%20slang%3D%22en-US%22%3EIs%20this%20a%20good%20SharePoint%20SQL%20Backup%20and%20Maintenance%20Plan%20Strategy%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2274520%22%20slang%3D%22en-US%22%3E%3CDIV%20class%3D%22lia-message-subject-wrapper%20lia-component-subject%20lia-component-message-view-widget-subject-with-options%22%3E%3CDIV%20class%3D%22MessageSubject%22%3E%3CSPAN%3EHi%20all%3C%2FSPAN%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20class%3D%22lia-message-body%20lia-component-message-view-widget-body%20lia-component-body-signature-highlight-escalation%20lia-component-message-view-widget-body-signature-highlight-escalation%22%3E%3CDIV%20class%3D%22lia-message-body-content%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELooking%20for%20some%20guidance.%20Setting%20up%20SharePoint%20SQL%20Backups%20for%20the%20first%20time%20and%20maintenance%20plans.%20Is%20this%20a%20good%20strategy%20in%20general%20even%20if%20there%20is%20no%20company%20policy%20yet%20defined%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEnvironment%20has%202%20SQLs%20VMs%20on%20a%20Microsoft%20Failover%20Cluster%20hosted%20split%20over%202%20ESXi%20hosts%20connected%20to%20a%20SAN.%20(Cluster%20Shared%20Volume%20in%20use%20for%20SQL%20Data%2C%20SQl%20Log%20and%20SQL%20Backup%20volume).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CTABLE%20border%3D%221%22%20cellspacing%3D%220%22%20cellpadding%3D%220%22%3E%3CTBODY%3E%3CTR%3E%3CTD%3E%3CP%3EGeneral%20DB%20Maintenance%20Task%3C%2FP%3E%3CUL%3E%3CLI%3E%3CSPAN%3ECheck%20Database%20Integrity%20(All%20databases%20include%20indexes)%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3ERebuild%20indexes%20(All%20databases%2C%20tables%2C%20views%2C%20orig%20amount%20of%20free%20space)%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EUpdate%20Statistics%20Task%20(Full%20scan%20all%20DB%20and%20tables%20and%20views%2C%20existing%20statistics)%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EHistory%20Clean%20Up%20Task%20(Backup%20Job%20and%20Maintenance%20plan.%20Age%20older%20than%204%20weeks)%3C%2FSPAN%3E%3C%2FLI%3E%3CLI%3E%3CSPAN%3EMaintenance%20Cleanup%20of%20Reports%20(Age%20older%20than%204%20weeks)%3C%2FSPAN%3E%3C%2FLI%3E%3C%2FUL%3E%3C%2FTD%3E%3CTD%3E%3CP%3E12%3A01AM%20Sunday%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%3CP%3EFull%20Backup%26nbsp%3B%20-%20(compress%2C%20backup%20set%20expires%20after%2014%20days)%3C%2FP%3E%3C%2FTD%3E%3CTD%3E%3CP%3EWeekly%20-%201AM%20Sunday%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%3CP%3EDifferential%20Backup%26nbsp%3B%20-%20(compress%2C%20backup%20set%20expires%20after%207%20days)%3C%2FP%3E%3C%2FTD%3E%3CTD%3E%3CP%3EDaily%20-%202AM%20excl%20Sunday%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%3CP%3ETransaction%20Backup%26nbsp%3B%20-%26nbsp%3B(compress%2C%20backup%20set%20expires%20after%201%20day)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FTD%3E%3CTD%3E%3CP%3EDaily%20-%20Every%2015%20Minutes%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%3CP%3EFull%20Backup%20cleanup%3C%2FP%3E%3C%2FTD%3E%3CTD%3E%3CP%3EWeekly%20-%202%3A30AM%20Sunday%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%3CP%3EDiff%20Backup%20cleanup%3C%2FP%3E%3C%2FTD%3E%3CTD%3E%3CP%3EWeekly%20-%203AM%20Sunday%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3CTR%3E%3CTD%3E%3CP%3ELog%20backup%20cleanup%3C%2FP%3E%3C%2FTD%3E%3CTD%3E%3CP%3EDaily%20-%204%20AM%3C%2FP%3E%3C%2FTD%3E%3C%2FTR%3E%3C%2FTBODY%3E%3C%2FTABLE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2274520%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EBackup%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESQL%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Contributor

Hi all

 

Looking for some guidance. Setting up SharePoint SQL Backups for the first time and maintenance plans. Is this a good strategy in general even if there is no company policy yet defined?

 

Environment has 2 SQLs VMs on a Microsoft Failover Cluster hosted split over 2 ESXi hosts connected to a SAN. (Cluster Shared Volume in use for SQL Data, SQl Log and SQL Backup volume).

 

General DB Maintenance Task

  • Check Database Integrity (All databases include indexes)
  • Rebuild indexes (All databases, tables, views, orig amount of free space)
  • Update Statistics Task (Full scan all DB and tables and views, existing statistics)
  • History Clean Up Task (Backup Job and Maintenance plan. Age older than 4 weeks)
  • Maintenance Cleanup of Reports (Age older than 4 weeks)

12:01AM Sunday

Full Backup  - (compress, backup set expires after 14 days).

Databases (All)

Weekly - 1AM Sunday

Differential Backup  - (compress, backup set expires after 7 days)

Databases (All except Master and Tempdb)

Daily - 2AM excl Sunday

Transaction Backup  - (compress, backup set expires after 1 day)

Databases (Content, SharePoint_Config and SharePoint_AdminContent)

Daily - Every 15 Minutes

Full Backup cleanup

Weekly - 2:30AM Sunday

Diff Backup cleanup

Weekly - 3AM Sunday

Log backup cleanup

Daily - 4 AM

 

0 Replies