Select a method for Sharepoint backup

You may be familiar with the backup and restoration functions of SharePoint. But how many backup methods are there for Sharepoint? Which backup method is more suitable for you? This article will mainly help you sort out and study several common backup methods in depth, so that everyone can understand and understand the use cases.

What levels of backups does SharePoint provide?

• Web-level backup
• Sitecollection-level backup
• Database-level backup

 

Web-level backup

For Web-level backup, the common command line is:

The following is a decompilation to see how this method is implemented. The process is omitted and the core backup class is directly found:

As you can see, Sharepoint serializes the content on the site and stores the content. What is the serialization process? Here we take web as an example:

Here, we can see that SharePoint serializes the content in the site set in step-by-step mode by using APIs. Therefore, backup and restoration are performed through APIS, this example also demonstrates the strength of the SharePoint API itself.

The specific implementation content will not be described in detail. You can understand it yourself. Here we can summarize the features of web-level backup:

• Based on the sharepointapi
• The backup sequence is structured and its Functions
• The restoration is also performed through the SharePoint API. Therefore, if you use this backup data for restoration, the IDs and so on will not be repeated.

 

Sitecollection-level backup

For sitecollection-level backup, the common command line is:

In the same process, we decompile the code and take a look at the implementation of this command line:

As identified in the red line, it seems to be related to contentdatabase. Let's look at the Core Method Manager. serialize.

The keyword marked in the red line clearly tells us that SharePoint serializes each table in contentdatabase and then stores it locally.

So here, we can briefly summarize the features of sitecollection-level backup:

• It is based on sitecollection level and cannot be refined.
• The backup process follows the sequence of tables in the database.
• This method determines that some IDs will be repeated after restoration, but the actual test results show that the sitecollectionid will not be repeated.

 

Database-level backup

This does not need to be repeated. Its features are as follows:

• Database-level-based, not refined
• Data blocks or snapshots are taken during the backup process.
• After this method is restored, the ID, primary key, and other information are exactly the same as those during Backup.

 

How can we choose which backup method we want to use?

The following list can help you select

Content repeatability (compared with backup data ):

	Sitecollectionid	Webid	Entid
Web level	Different	Different	Different
Sitecollection level	Different	Same	Same
Database level	Same	Same	Same

 

This list already lists data repeatability. Therefore, when using this list, consider the following:

• In the same spfarm, there cannot be two spsites with the same ID. Therefore, database-level backup and Backup recovery data are not compatible in the same spfarm.

• The same spcontentdatabase cannot have the same webid. Therefore, sitecollection-level backup and data restoration are incompatible with the same spcontentdatabase.
• There are no two problems with web-level backup

Efficiency Comparison:

	Theoretical speed
Web level	Slowest
Sitecollection level	Moderate
Database level	Fast

 

Efficiency Comparison, I believe you can understand, is to use the snapshot pointapi backup efficiency <backup by table <snapshot backup by SQL.

 

Therefore, we can clearly see the advantages and disadvantages of each backup method and its efficiency through comparison. Because SharePoint not only provides many interfaces for Backup recovery, but even many third-party software also supports Backup recovery for Sharepoint, the basic idea is that these three methods are basically the same, when you know which backup method you are using, you can understand its efficiency and possible problems.

Select a method for Sharepoint backup