Chapter 17 Data Protection, Recoverability, and Availability

MS Sharepoint 2010 Admin’s Companion eBook (P. 829)

You cannot import data using Central Admin; you need to use STSADM or Windows PowerShell.

All Sharepoint Content is accessed through a web service hosted by internet information services (IIS).

Using Sharepoint 2010 Disaster Recovery Tools —
Most common method for restoring corrupted contents: versioning – disabled by default.

Two-staged recycle bin —
When user deletes a document, emptied out his (first level) recycle bin, the file goes to the second level recycle bin for 30 days.
Recycle bin – also security trimmed.

Administrator can access the first level recycle bin with a global view; also the 2nd level.
First level:

To configure recycle Bin at a web applicatin level:
Central Admin Amanagement Web Application General Settings —

Change recycle settings

Powershell —
Get-Help sp-somecommand

STSADM – (P.844)
Unattached content database – you can recover from an unattached content database

Limitation of backup from Central admin:
(1) schedule not allowed
(2) more thanone web app or site collection backup not allowed.
(3) not backup to tape directly.

Powershell for backup/restore

Backup-SPFarm, Restore-SPFarm: perform backup & restore on: entire farm, service application, web application, content database (all global objects)
– Directory: UNC path
– ConfigurationOnly: backup site customization only
– ShowTree: identity each single item
– Item: name of farm component, content database, service application or web application.
– Percentage:
– Force
(only for backup)
– BackupMethod [Full/Differential] – for backup only
– BackupThread (default 1, from 1-10)
(only for restore)
– RestoreMethod <New | Overwrite>
– RestoreThread
– BackupID: GUID of the backup that is to be restore

To get backup History:
Get-SPBackupHistory –Director <backup folder> -ShowBackup [-verbose]

Use Backup-SPConfigurationDatabase
to back up your farm configuration
– Directory: UNC path
– DatabaseCredentail
– DatabaseName
– DatabaseServer

Using Backup-SPSite and Restore-SPSite

-Identity: URL of the site collection
-Path: location and the file name of the backup file
-Force
-NoSiteLock: site collection is not set to read-only during a site collection backup
-UseSQLSnapshot: Use the content database snapshot when performing the backup.
-GradualDelete: Helps improve performance
-DatabaseServer
-DatabaseServer

To restore a web site:
Restore-SPSite –Identity <site collection URL> -Path <backup File>

Export-SPWeb:
-Identity
-Path
-Force
-IncludeUSerSecurity
-HaltonWarning
-HaltOnFatalError
-NoLogFile
-IncludeVersions
-NoFleCompression (if used in export, must use in import)

Using Import-SPWeb
-UpdateVersions [Append | Overwrite | Ignore]

Using Central Administration to restore your powershell backup —
Central Admin à Backup and Restore à Restore from a backup


(1) Select the path where the backup file can be found
(2) Select components to restore
(3) Select Options

SQL database mirroring —
In Sharepoint 2010, you can specify a failover database for each content database. (principal server, mirror server)

Two types of mirrored sessions: Async and sync.

Asyc: High performance mode: principal server doesn’t wait for the mirror server; high performance; if principal fails, mirror is just a warm stand by.
Sync: High safety mode: All transactions in principal server are guaranteed to be written to mirror server. Name of the principal/mirror must be the same for sync database mirroring to work. Must use Full Recovery mode on the database.

**** To implement auto failover, the session must have a 3rd SQL instance (a witness),
which monitors principal server for connectivity. If it discovers that the principal is unavailable for 15 seconds, and there is still connectivity between witness and mirror, then the mirror server performs the auto failover.

SQL server transaction log shipping —
Automatically send Transaction log backups from one to one or many database servers. How to:
(1) Primary server back up the trans-log.
(2) SQL Server agent on the 2nd server initiates a copy of the primary server transaction log.
(3) Agent on the 2nd server applies the copied transaction log to the associated secondary server database.

SQL Snapshots – provide a read-only copy of your data that allows you to roll back to the data point when the snapshots was made.

01/26/2011, 09:52PM

Advertisements
Post a comment or leave a trackback: Trackback URL.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: