Contents
SharePoint Server does not support the following type of operations while SharePoint Server is online. Virtual machine online backups – If full virtual machine backups are required, shut down the SharePoint and SQL Servers in the farm prior to taking virtual machine backups.
Go to Control Panel -> System and Security -> Windows Firewall. Select Advanced Settings option. Click ‘Inbound Rules’ and select ‘New Rule’ option. This will open up the inbound rule configuration wizard. Select the radio button ‘Port’ and click Next. Select the TCP radio button and specify the port 1433 in specific local ports text box.
Virtual machine snapshots – If a snapshot of SharePoint is required, shut down all SharePoint Servers and SQL Servers in the farm prior to taking a virtual machine snapshot. If a restore is required, restore all servers in the farm. Delete the snapshot as soon as possible as it may incur a performance penalty.
Why is MY SQL Server not connecting to my database?
When connecting to SQL Server, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server). This error is returned by the instance of the Database Engine that hosts the report server database.
What to do with a SharePoint Server 2016 backup?
(2) Farm-level and database-level backups can be used with SharePoint Server 2016 unattached database recovery to restore site collections, sites, lists, and configurations. (3) Content stored in remote BLOB stores cannot be restored by using System Center Data Protection Manager.
As you’ll notice, both tables are similar but specific backup components are shown for each SharePoint Server edition. (1) Farm-level and database-level backup and restore can be used for site collection recovery if a single site collection is stored in a database.
For a graphical overview of the databases that support SharePoint Server 2016, see Quick reference guide: SharePoint Server 2016 databases. Use incremental backups for large databases because you can make them quickly and maintain performance of the environment.