Using PowerShell to shorten SharePoint backup time

Microsoft SharePoint in the enterprise is increasingly popular, which is in stark contrast to the boredom and dislike of many administrators. One reason for anger is that SharePoint stores all relevant data in multiple different places, which makes it tricky to execute SharePoint-specific backup. It is not impossible to back up each independent part, but it is really troublesome.

Fortunately, the programmer Jesper M. Christensen decided to do something about it. Christensen sat down and wrote a PowerShell script, which makes it possible to back up the entire instance of Windows SharePoint Services or Microsoft Office SharePoint Server, including site, 12 reserve, and IIS metadata. You can use stsadm.exe to back up a database.

In a scheduled task or other script initiated as needed, the script called SP backup can be run manually and obtained free of charge according to Microsoft's public authorization Ms-PL. This script supports IIS 6.0 and IIS 7.0 backup and works on all Windows versions that support SharePoint clients and servers.

SP backup consists of the script itself and an XML configuration file. The script parses the file to obtain information such as the backup destination, which can be a local path or shared by the server. The two files must be placed in the same directory, but it is up to you to decide which directory they belong.

Of course, you will need to edit the XML file to provide the appropriate parameters for your server. Some of the parameters are in the script and are only explained in the script file. For example, the maximum retention period parameter of the backup target allows you to specify how many days the old backup can be retained before it is automatically deleted.

You can also set parameters to allow email sending and Event Description during backup at the end of work. Other parameters allow you to specify the password for decryption of IIS 6.0 metadata, so you can choose to store on other servers or perform a catastrophic backup and perform the same full SharePoint backup as the Management Center path ).

Another report is also logged on to the console, but there is no provision in the script to write the report to the system log. To be honest, it does not seem difficult to write log results by using the mail sending function in the script and writing Event Logs command. In addition, an additional feature required by the user is to back up the GAC folder and virtual directory without the need to complete the process of backing up a file.

Finally, the exposed environment does not have a complete list of options that can be used to perform backup operations for SharePoint itself through stsadm.exe. An option that is completely unavailable
It is a backup thread. Although it is recommended that the running SharePoint Server 2007 should be set to 3 to improve efficiency, the default value is 1. You can add this to the script based on your performance requirements. If your server has multiple cores, is there anyone else ?), This is of great significance.

Finally, even though the script performs a backup, it does not perform storage operations, so you still need to manually and separately execute them for each SharePoint element.