Forum Discussion
How we can be sure that we have sufficient backups for our sharepoint on-premises 2013/2016
Hi John,
I always ensure SQL backups of both the Configuration Databases and Content Databases are made. This is the best / fastest / most reliable way to get back online in a real disaster. You can use transaction log backups to have more recovery points e.g. restore full backup + incremental (transaction log) up to the recovery point. I am talking about SQL Database Backups using a SQL Maintenance plan.
It is also a good idea to have snapshots of the SharePoint Servers themselves - this includes all of the file system bits you will need to recover.
Content Database backups also allow you to recovery sites, libraries, lists and documents using the 'Unattached' restore process via Central Admin.
The Farm Backup is may be useful in a disaster and can be scripted / scheduled.
I blogged about this a while back too. This might be helpful https://onehundredwatt.wordpress.com/2016/10/30/recovering-sharepoint/
Trevor Seward wrote:
Configuration/Administration databases cannot be restored. If a farm wasn't built with PowerShell, then using `Backup-SPFarm -ConfigurationOnly` is appropriate. Other than that, use SQL jobs to backup databases.Trevor Sewardcan you advice what do you mean by configuration/administration databases cannot be restored? are those usual sql databases that can be backed-up from sql management studio and got restored?? and how we can recreate these databases if we faced an issue that require restoring the Configuration/Administration databases ?
I've restored Config and Administration databases to recover a farm when a CU failed successfully on two different farms. Process was to restore the databases and then reapply the CU and run PSConfig.
