SharePoint
au
Quotidien
avec
EROL
|
|
|
|
B acking Up and Restoring Servers on the Server Farm
You can back up and restore an entire server farm, an entire server, or individual components by using the Microsoft SharePoint Portal Server Data Backup and Restore utility. You can start the utility from the SharePoint Portal Server group on the All Programs menu. The SharePoint Portal Server Data Backup and Restore utility does not back up Internet Information Services (IIS) or the Web servers. To recover data in your server farm or single server deployment, you must first use the operating system backup and restore for Web servers and the single server deployments. You can then use the SharePoint Portal Server Data Backup and Restore utility to restore the remaining data. You must use the operating system backup and restore in the following situations:
If you do not use the operating system backup and restore in these situations, you may encounter the following problems:
Important For SharePoint Portal Server "v2.0" Beta 2, the operating system backup and restore should be needed only in the scenario where all of the Web servers fail. 1) Single Server Deployments You should have regularly scheduled backups of your server so that you can restore data in case of server failure. You should also maintain a list of all document libraries, portals, and pure team sites. Ensure that you have the exact names and URLs for the document libraries. In case of total server failure, you can build a server with the same name or with a new name and restore your SharePoint Portal Server data to it.
1. Install SharePoint Portal Server. 2. Recreate the portals, document libraries, and Windows SharePoint Services Beta 2 sites outside of the portal. 3. Restore everything except for the configuration database. If you are using the single sign-on service in your deployment, ensure that you restore the single sign-on database. Use the Edit button on the Restore tab to specify the server for the restore operation. 4. Open a command prompt and type iisreset. 5. Configure the single sign-on service, if it is part of your deployment. 6. Restore the base system key, if you have configured the single-sign on service. 1. Install SharePoint Portal Server. 2. Recreate the portals, document libraries, and team sites. 3. Restore everything except for the configuration database. If you are using the single sign-on service in your deployment, ensure that you restore the single sign-on database. Use the Edit button on the Restore tab to specify the server for the restore operation. 4. Open a command prompt and type iisreset. 5. Configure the single sign-on service, if it is part of your deployment. 6. Restore the base system key, if you have configured the single-sign on service. 2) Server Farm Deployments You should have regularly scheduled backups of your server farm so that you can restore data in case of server failure. You should also maintain a list of all document libraries, portals, and Windows SharePoint Services Beta 2 outside of the portal. Ensure that you have the exact names and URLs for the document libraries. In case of total server failure, you can build a server with the same name or with a new name and restore your SharePoint Portal Server data to it.
1. Delete all document libraries by using the SharePoint Portal Server Central Administration for Server ServerName page. Since the server has failed, you are not actually deleting the document libraries, but you are deleting the entry for them in the configuration database. Note For SharePoint Portal Server "v2.0" Beta 2, delete any document libraries associated with portals by using the Site Settings page for each portal. Delete any document libraries not associated with portals by using the following URL: http://ServerName:8080/sps/DmWorkspaceDelete.aspx?WorkspaceName=NameOfWorkspace 2. Remove the document management server from the server farm topology by removing it from the component assignments. 3. Remove the document management server from the server farm. 4. Install the document management component of SharePoint Portal Server on the newly-built server. 5. Add the document management server to the server farm. 6. Add the document management server to the server farm topology by adding it to the component assignments. 7. Recreate the document libraries using the same names. 8. Restore the document management components to the server. 1. Delete all document libraries by using the SharePoint Portal Server Central Administration for Server ServerName page. This will not actually delete the document libraries (because the server has failed), but it will delete the entry for them in the configuration database. Note For Microsoft SharePoint Portal Server "v2.0" Beta 2, delete any document libraries associated with portals by using the Site Settings page for each portal. Delete any document libraries not associated with portals by using the following URL: http://ServerName:8080/sps/DmWorkspaceDelete.aspx?WorkspaceName=NameOfWorkspace 2. Remove the document management server from the server farm topology by removing it from the component assignments. 3. Remove the document management server from the server farm. 4. Install the document management component of SharePoint Portal Server on the newly-built server. 5. Add the document management server to the server farm. 6. Add the document management server to the server farm topology by adding it to the component assignments. 7. Recreate the document libraries using the same names. 8. Restore the document management components to the server. 1. Remove the index management server from the server farm topology by removing it from the component assignments. 2. Remove the index management server from the server farm. 3. Install SharePoint Portal Server on the newly-built server. 4. Add the index management server to the server farm. 5. Add the index management server to the server farm topology by adding it to the component assignments. Add it as a content index server and as the job server, if applicable. 6. Restore the index management components to the server. 7. If the server is also a job server, and you are using the single sign-on service in your deployment, configure the single sign-on service, and then restore the base system key. 1. Install SharePoint Portal Server on the newly-built server. 2. Add the index management server to the server farm. 3. Add the index management server to the server farm topology by adding it to the component assignments. Add it as a content index server and as the job server, if applicable. 4. Remove the old index management server from the server farm topology by removing it from the component assignments. 5. Remove the old index management server from the server farm. 6. Restore the index management components to the server. 7. If the server is also a job server, and you are using the single sign-on service in your deployment, configure the single sign-on service, and then restore the base system key. 1. Install SharePoint Portal Server on the newly-built server. 2. Create a configuration database. 3. Restore the configuration database from the backup image. 4. Restore the content databases from the backup image. 5. Restore the single sign-on database from the backup image, if you are using the single sign-on service in your deployment. 6. On each Web server, open a command prompt and type iisreset. You cannot restore data to a server with a new name by using SharePoint Portal Server "v2.0" Beta 2. Data is restored to servers using the same name as the failed servers. 1. Install SharePoint Portal Server on each newly-built server. 2. Install the document management component of SharePoint Portal Server on the newly-built document management server. 3. Configure the farm topology but add only one Web server. 4. Recreate the portals, document libraries, and team sites. o You do not need the exact virtual server names and port numbers for the portals.o You do need to use the exact same names for the document libraries.5. Restore the data. Important Do not restore the configuration database, but restore all other data. Ensure that you restore the single sign-on database, if you are using the single sign-on service in your deployment. Use the Edit button on the Restore tab to specify the server for the restore operation. 6. On the Web server, open a command prompt and type iisreset. 7. Configure the single sign-on service, if it is part of your deployment. 8. Restore the base system key, if you have configured the single-sign on service. 9. Add additional Web servers and extend the sites. 1. If at least one Web server on the server farm is still active, add additional Web servers to the server farm and extend the sites. 2. If all Web servers have failed, you must use the operating system backup. 1. Install SharePoint Portal Server on the newly-built server. You can use a server with the same name as the failed server or with a new name. 2. Add the search server to the server farm. 3. Add the search server to the server farm topology by adding it to the component assignments. 4. Restore the search component to the server. 3)Backing Up Data This is a preliminary document. Additional information about this feature will be provided prior to final commercial release. You can back up all server farm components or individual components.
1. Click Start, point to All Programs, point to SharePoint Portal Server, and then click SharePoint Portal Server Data Backup and Restore. The Microsoft SharePoint Portal Server V2.0 Beta 1 Backup and Restore dialog box opens. 2. Click the Backup tab. 3. In the tree view, expand Available components by clicking the plus sign. 4. Click the components that you want to back up. 5. In the Backup location and name box, do the following: 1. Type or browse to the location where you want to store the backup files. 2. After the folder name, type the file name that will be the prefix for each backup file. 6. In the Backup comment box, type a comment. 7. If you want to encrypt the credentials for the search service, in the Password for encryption box, type a password. 8. Optionally, select the Overwrite existing files check box. 9. Optionally, select the Generate a trace log file in the SharePoint Portal Server Logs directory check box. 10. Click Start Backup. 11. On the successful completion message box, click OK. 4) Restoring Data This is a preliminary document. Additional information about this feature will be provided prior to final commercial release. You can restore all server farm components or individual components.
1. On the task bar, click Start, point to All Programs, point to SharePoint Portal Server, and then click SharePoint Portal Server Data Backup and Restore. The Microsoft SharePoint Portal Server V2.0 Beta 1 Backup and Restore dialog box opens. 2. Click the Restore tab. 3. In the Manifest file box, specify the location of the manifest file. The manifest file is the XML file that is in the directory that you specified for the backup files when you backed up the server. The file name is the prefix you specified for the backup file names. For example, if the file name you specified as the prefix for the backup file names was Adventure, the name of the manifest file would be Adventure.XML. 4. In the tree view, expand Available components by clicking the plus sign. 5. Click the components that you want to restore. 6. If you specified a password to encrypt the credentials for the search service when you performed the backup, in the Password for decryption box, type the password. Important Ensure that the password you supply for decryption is the same password that you supplied for encryption. 7. Optionally, select the Generate a trace log file in the SharePoint Portal Server Logs directory check box. 8. Click Start Restore. Important Restore will overwrite existing data. Ensure that you have verified that each backup image corresponds to the correct component. 9. On the confirmation message box, click OK. 10. On the successful completion message box, click OK. 19/06/2003 |
|
|
