After you have created the protection group and created the recovery point, if you want to test item level restore, you need to wait for a day so that DPM can run its catalog generation in its own sweet time. in previous versions it was about 3 hours after the recover point creation, not sure what the exact duration is in 2012 SP1 version. Oh, by the way, if you are using System Center Data Protection Manager 2012 SP1, I highly recommend running Microsoft Update and getting RU3 patch.

Anyway, back to the topic at hand.

Open up DPM Management Shell or PowerShell ISE and run the following script:

Import-Module DataProtectionManager
# the import Module command is only required when using PowerShell or PowerShell ISE

$hostname = hostname
Get-ProtectionGroup $hostname | Get-Datasource | Where-Object {$_.type -like "*sharepoint*"} | Start-CreateCatalog

To monitor the progress of the Job, go to your Monitoring Tab in DPM Console.

B/w backup restore SharePoint 2013 works with both HostHeader Site Collection and HostNamed SiteCollection with System Center Data Protection Manager 2012 SP1 with RU3 patch.

Hope this helps.

Cheers!

Priyo

https://blogs.technet.com/b/ptsblog/archive/2013/09/20/configuring-sharepoint-2013-forms-based-authentication-with-sqlmembershipprovider.aspx 

Cheers!

Priyo

Cheers!

Priyo

Cheers,

Priyo

Compare the different Office versions from 2003 – 2013 : https://www.microsoft.com/business/en-ie/Whats-new/Pages/Article.aspx?cbcid=75# 

Cheers!

Priyo

For sake of sanity… there is a zip file attached to this post with the ps1 file in it.

Clear-Host

# Values mentioned below needs to be edited

 $DatabaseServer = "SQL01"; #SPecify the instance name if SQL is not installed on default instance

$FarmName = "SP2013";

$ConfigDB = $FarmName+"_ConfigDB";

$AdminContentDB = $FarmName+"_CentralAdminContent";

$Passphrase = convertto-securestring "pass@word1" -asplaintext -force;

$Port = "2013";

$Authentication = "NTLM";

$FarmAccount = "waterfall\spfarm"

##########################################################################

############################### DO NOT EDIT ANYTHING BELOW THIS LINE #####

##########################################################################

#Start Loading SharePoint Snap-in

$snapin = (Get-PSSnapin -name Microsoft.SharePoint.PowerShell -EA SilentlyContinue)

IF ($snapin -ne $null){write-host -f Green "SharePoint Snapin is loaded... No Action taken"}

ELSE {

write-host -f Yellow "SharePoint Snapin not found... Loading now"

Add-PSSnapin Microsoft.SharePoint.PowerShell

write-host -f Green "SharePoint Snapin is now loaded"}

# END Loading SharePoint Snapin

# checking to see if SharePoint Binaries are installed

IF((Get-WmiObject -Class Win32_Product | Where {$_.Name -eq "Microsoft SharePoint Server 2013 "}) -ne $null)

{"Found SharePoint Server 2013 Binaries. Will create Farm now"

New-SPConfigurationDatabase -DatabaseName $ConfigDB -DatabaseServer $DatabaseServer -FarmCredentials (Get-Credential $farmAccount) -Passphrase $Passphrase -AdministrationContentDatabaseName $AdminContentDB

Remove-PSSnapin Microsoft.SharePoint.PowerShell

Add-PSSnapin Microsoft.SharePoint.PowerShell

Install-SPHelpCollection -All

"Installed Help Collection"

Initialize-SPResourceSecurity

"Initialized SP Resource Security"

Install-SPService

"Instaled Ssp service"

Install-SPFeature -AllExistingFeatures

"Installed SP Feature"

New-SPCentralAdministration -Port $Port

"Created Central Administration Site"

Install-SPApplicationContent

"Installed Application Content. This was the last step.

Farm Configuration Complete!"

}

ELSE {"SP Binaries not found"}

This posting is provided "AS IS" with no warranties, and confers no rights.

Create SP Farm-Blog.zip

This posting is provided "AS IS" with no warranties, and confers no rights.

Having SharePoint connect to a SQL Alias instead of the NetBIOS name is always a good idea. The main benefit is, if you ever have to switch the SQL Server or connect to a SQL Cluster VIP address, you just change the Alias to point to the SQL Cluster name on the SharePoint Server and restart the SharePoint Timer Service and you are good to go. This can save huge amount of time and headache. Follow the steps below to create a SQL Alias on all your SharePoint Servers:

1. Perform this on the Application Server that is hosting Central Administration

a. Stop all SharePoint Services

b. Open CLICONFIG.exe from C:\Windows\System32\cliconfg.exe (64 bit version of cliconfig.exe)

c. Enable TCP/IP under general tab

d. Click on Alias Tab

e. Type Current SQL Server Name in the Alias Name field

f. Type Current SQL Server Name in the Server field (see screenshot below. In your case SQL Alias and SQL Server name is the same)

g. Validate SQL Alias

i. Create a new text file on SharePoint Server and name it “TestDBConnection.udl”

ii. Double click to open the file and enter your SQL Server Alias name

iii. Use Windows Integrated Security

iv. You should be able to see all your SharePoint databases when you click on “Select the database on the Server”

h. Start all services for SharePoint Server / Reboot SharePoint Server

i. Perform the steps above on all other SharePoint servers

This posting is provided "AS IS" with no warranties, and confers no rights.

• What is SkyDrive Pro? – its your My Site in SharePoint 2013.
• What is SkyDrive Pro client then? – its a Client for Syncing your My Site content on your client machine. Its a part of Office 2013 Standard or ProPlus install and not available as a separate download. this means you cannot use the Sync client if you have Office 2010 or 2007
• Can I Use SharePoint Workspace 2010 – Yes. it needs a HotFix when installed with Office 2013. Ref: https://support.microsoft.com/kb/2687364 . In fact, if you need to take a list offline, SharePoint WorkSpace 2010 is what you need, SkyDrive Pro client cannot do that.
• Can I use SkyDrive instead? – No. SkyDrive is the consumer offering and cannot be used as a replacement for SkyDrive Pro.
• Why does it say SkyDrive on my internal SharePoint site? – its an abbreviation of SkyDrive Pro :-)
• Is there a peer-to-peer sync capability with SkyDrive Pro? No.
• Can I choose what to sync like commercial SkyDrive? No. Not at the moment.

More references:

• https://sharepoint.microsoft.com/Blogs/GetThePoint/Lists/Posts/Post.aspx?ID=675
• https://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=1015
• https://office.microsoft.com/en-us/sharepoint-server-help/what-is-skydrive-pro-HA102822076.aspx 
• https://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=1033 

Update Sep 2013

SkyDrive Pro stand alone client has been released. You can download it from here.

This posting is provided "AS IS" with no warranties, and confers no rights.

There are 2 examples of this script, both are 100% automated. The only thing the Script expects the User to provide is the name of the New Content Database. I would love to automate it with Read-YourMind cmdlet… but let’s leave it for now J.

Method 1 – Using Move-SPSite cmd-let.

What we are doing here:

1. Getting the Central Admin URL and the New Content DB Name from the User

2. Populating the variables we need to perform the operation like the Current Admin Content DB Name, SQL Server Name and the Database ID

3. Creating a New Content Database and Attaching it to the Central Admin Web Application

4. Calling SP-MoveSite to Move 2 sites from Old Content Database to the New one

5. Lastly, we ask the user if he wants to Detach the Content DB from the web application or completely delete it from SQL

The operation can be screen in the below screenshots:

Current Content DB with 2 Site Collections

New Content DB Attached to the same Web App and Site Collections have been moved to the New Content DB

This is the Script. For convenience, you can also download the zip file attached to this post. The zip file contains 2 scripts RenameAdminContentDB_Method1.PS1 (Move-SPSite Method) and RenameAdminContentDB_Method1.PS1 (Backup – restore methos described later in the post.)

 1: Clear-Host

 2: ############################################################################################################################ DO NOT EDIT ANYTHING BELOW THIS LINE ###########################

 3: #############################################################################################

 4: # Start Loading SharePoint Snap-in

 5: $snapin = (Get-PSSnapin -name Microsoft.SharePoint.PowerShell -EA SilentlyContinue)

 6: IF ($snapin -ne $null){write-host -f Green "SharePoint Snapin is loaded... No Action taken"}

 7: ELSE  {write-host -f Yellow "SharePoint Snapin not found... Loading now"

 8: Add-PSSnapin Microsoft.SharePoint.PowerShell

 9: write-host -f Green "SharePoint Snapin is now loaded"}

 10: # END Loading SharePoint Snapin

 11: #Detect CA Site URL 

 12: $CA = (Get-SPWebApplication -IncludeCentralAdministration | where {$_.DisplayName -eq "SharePoint Central Administration v4"}).Url

 13: #Get New Content DB Name from User

 14: $NewContentDB = Read-Host "Enter the New Content Database Name for your Central Admin Site"

 15: IF ($NewContentDB -eq ''){Write-Host -f Red "Blank value for Content DB. Cannot proceed. Exiting..."

 16: break}

 17: # grab SQL Server Name

 18: $SQLServer = (Get-SPContentDatabase -WebApplication $CA -EA Stop).Server

 19: $OldDB = (Get-SPContentDatabase -WebApplication $CA -EA Stop).DB

 20: $OldDBID = (Get-SPContentDatabase -WebApplication $CA -EA Stop).ID

 21: #Create new SP_contentDB

 22: Write-Host -f Green "Creating Content DB..."

 23: New-SPContentDatabase -Name $NewContentDB -WebApplication $CA -DatabaseServer $SQLServer -ErrorAction STOP

 24: Write-Host -f Green "New Content DB Created and Attached to your Central Admin Site"

 25: #Grab ID of the New Content DB

 26: $NewContentDBID = (Get-SPContentDatabase -WebApplication $CA | ?{$_.Name -eq $NewContentDB}).id

 27: #Get and Move SP-Site

 28: Get-SPSite -ContentDatabase $OldDBID | Move-SPSite -DestinationDatabase $NewContentDBID -Confirm:$False -EA Stop

 29: Write-Host -f Green "Site Move complete."

 30: Write-Host -f Green "Resetting IIS now..."

 31: IISRESET

 32: $RemoveOption = Read-Host "

 33: Choose Remove Database Option:

 34: 1 - Remove (DELETES the Database from SQL)

 35: 2 - Dismount (Detach the DB from Web Application)"

 36: IF ($RemoveOption -eq '1') {Remove-SPContentDatabase -Identity $OldDBID -EA Stop

 37: Write-Host -F Green "Database deleted from SQL Server."}

 38: ElseIF ($RemoveOption -eq '2') {Dismount-SPContentDatabase -Identity $OldDBID -Confirm:$False -EA Stop

 39: Write-Host -F Yellow "Database detached from SharePoint Web Application. Please delete the Database manually from SQL Server."}

 40: Else {Write-Host -f Yellow "Invalid Option chosen. No action was taken."}

 41: Write-Host -F Green "All Opearation Completed Successfully."

 42: ################### END SCRIPT ###########################

Method 2 – Using SQL Backup and Restore.

This method is primary for demonstration purposes. It shows how you can call SQL Commands and SMO (SQL Server Management Objects) directly from PowerShell along with SharePoint. I will use the same method in future posts on automating tasks for Database mirroring. Though this script can be used for any content database, I have tested this with the Central Admin Content Database only. Also, the script below you will see that when we restore the database, we are getting the LogicalName of the SQL MDF and LDF File from the backup set (your original SharePoint_AdminContent_GUID). Though it’s possible to fire a Alter Database Statement to change the names, running Alter Database statement on SharePoint Databases are not supported and you should refrain from doing that.

This script also has the following prerequisite:

To use this script you need SQL Server Client Components to be installed on the Server and you need the required permissions for backup / restore on SQL. It’s also possible to run the SQL Section of the script on the SQL Box, or put it on the SQL Box as a ps1 file and call it form the script below with –session parameter if you do not have SQL Server Client Components installed on the server.

This script is fully automated and performs the following steps:

• Loads SharePoint and SQL Snap-in
• Detects the Central Admin Site URL
• Populates the required variables like SQL Server Name, Database Name
• Loads SQL Assemblies to get SQL Server Defaults for Backup Location and MDF / LDF File Locations
• Constructs a new Backup File name with TimeStamp
• Creates the Backup Statement and stores it in a String
• Invokes SQLCmd to execute the backup statement – this first runs a full backup and then a Transaction Log backup so that we don’t lose the Tail of the Log (required for all databases with FULL Recovery Model)
• Enters Restore Operation block
• Grabs the LogicalName of the MDF and LDF File from the BackupSet through SQLSMO.Restore object
• Gets the Name of the New Content DB from the User
• Generates the Restore Statement
• Invokes SQLCmd to execute the Restore statement – First the Full backup with NORECOVERY option and then the Transaction Log File
• Comes back to SharePoint Loop – First step is to dismount the Old Content DB
• Mounts the new Content DB to the Web App
• Runs IISRESET
• Provides a remove option to the user – if user selects that option, the database is permanently deleted.

 1: Clear-Host

 2: ############################################################################################################################ DO NOT EDIT ANYTHING BELOW THIS LINE ###########################

 3: #############################################################################################

 4: # Start Loading SharePoint Snap-in

 5: $snapin = (Get-PSSnapin -name Microsoft.SharePoint.PowerShell -EA SilentlyContinue)

 6: IF ($snapin -ne $null){write-host -f Green "SharePoint Snapin is loaded... No Action taken"}

 7: ELSE  {write-host -f Yellow "SharePoint Snapin not found... Loading now"

 8: Add-PSSnapin Microsoft.SharePoint.PowerShell

 9: write-host -f Green "SharePoint Snapin is now loaded"}

 10: # END Loading SharePoint Snapin

 11: # Start Loading SQL Snap-in

 12: ## Check to see if SQL Server Provider for Windows PowerShell is installed 

 13: # Add the SQL Server Provider. Ref: https://technet.microsoft.com/en-us/library/cc281962.aspx 

 14: $ErrorActionPreference = "Stop"

 15: $sqlpsreg="HKLM:\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.SqlServer.Management.PowerShell.sqlps"

 16: if (Get-ChildItem $sqlpsreg -ErrorAction "SilentlyContinue")

 17: {    throw "SQL Server Provider for Windows PowerShell is not installed. Please install Client Components first."}

 18: Else{    $item = Get-ItemProperty $sqlpsreg

 19:     $sqlpsPath = [System.IO.Path]::GetDirectoryName($item.Path)}

 20: $snapin = (Get-PSSnapin -name SqlServerCmdletSnapin100  -EA SilentlyContinue)

 21: IF ($snapin -ne $null){write-host -f Green "SQL Snapin is loaded... No Action taken"}

 22: ELSE  {write-host -f Yellow "SQL Snapin not found... Loading now"

 23: Add-PSSnapin SqlServerCmdletSnapin100

 24: write-host -f Green "SQL Snapin is now loaded"}

 25: # END Loading SQL Snap-in

 26: ######################### START SharePoint Loop ##################################

 27: # Detect CA Site

 28: $CA = (Get-SPWebApplication -IncludeCentralAdministration | where {$_.DisplayName -eq "SharePoint Central Administration v4"}).Url

 29: # Get Content DB Name

 30: $CACurrentdb  = (Get-SPContentDatabase -WebApplication $CA).Name

 31: $SQLServer = (Get-SPContentDatabase -WebApplication $CA).Server

 32: Write-Host -f Green "Central Admin Content DB Name: " $CACurrentdb

 33: Write-Host -f Green "Detected SQL Server: " $SQLServer

 34: Write-Host -f Green " Entering SQL Loop Now..."

 35: ######################### END SharePoint Loop ##################################

 36: ######################### START SQL Loop ##################################

 37: [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SqlServer.SMO")  | out-null

 38: [System.Reflection.Assembly]::LoadWithPartialName("Microsoft.SqlServer.SMOExtended")  | out-null

 39: [Reflection.Assembly]::LoadWithPartialName("Microsoft.SqlServer.ConnectionInfo") | Out-Null

 40: [Reflection.Assembly]::LoadWithPartialName("Microsoft.SqlServer.SmoEnum") | Out-Null

 41: #get server defaults for Backup, MDF and LDF Locations

 42: $smosql=New-Object ('Microsoft.SqlServer.Management.Smo.Server') $sqlserver

 43: $ServerDefaultBackupLocation = $smosql.Settings.BackupDirectory 

 44: Write-Host -f green "Captured Default Backup Directory: " $ServerDefaultBackupLocation

 45: $GetMDFFileLocation = $smosql.MasterDBPath

 46: $GetLDFFileLocation = $smosql.MasterDBLogPath

 47: $timestamp = Get-Date -format yyyyMMddHHmmss

 48: # Construct a new Backup File name to avoid any conflics

 49: $bkSetName = $ServerDefaultBackupLocation +"\CA_Backup_DB_"+$timestamp +  ".bak"

 50: # Creating Backup Statement for Database and Transaction Log Backup

 51: [String] $bkupstmt ="BACKUP DATABASE [" + $CACurrentdb + "]

 52: TO  DISK = N'" + $bkSetName + "' WITH NOFORMAT, NOINIT, NAME = N'SharePoint_AdminContent_BackUp', SKIP, NOREWIND, NOUNLOAD, STATS = 10

 53: GO

 54: BACKUP LOG [" + $CACurrentdb + "] 

 55: TO  DISK = N'" + $bkSetName + "' WITH NOFORMAT, NOINIT, NAME = N'SharePoint_AdminContent_BackUp', SKIP, NOREWIND, NOUNLOAD, STATS = 10

 56: GO"

 57: # Firing the SQL Query

 58: Invoke-Sqlcmd -Query $bkupstmt -ServerInstance $sqlserver

 59: Write-Host -F Green "Backup Completed Successfully"

 60: # Start Restore Operation

 61: #Grab Logical File Names from Backup Set

 62: $res = new-object Microsoft.SqlServer.Management.Smo.Restore

 63: $res.Devices.AddDevice($bkSetName, [Microsoft.SqlServer.Management.Smo.DeviceType]::File)

 64: $LogicalDataFileName = $res.ReadFileList($smosql).Rows[0]["LogicalName"]

 65: $LogicalLogFileName = $res.ReadFileList($smosql).Rows[1]["LogicalName"]

 66: #Get New Content DB Name from User

 67: $NewContentDBName = Read-Host "Enter the name of the New Content Database "

 68: # Start Restore Operation... Create the Query

 69: [String] $restoreStmt = "

 70: RESTORE DATABASE [" + $NewContentDBName + "] FROM DISK = N'"+ $bkSetName+"' WITH FILE = 1, MOVE N'" + $LogicalDataFileName + "' 

 71: TO N'"+ $GetMDFFileLocation +"\"+ $NewContentDBName + ".mdf', MOVE N'"+ $LogicalLogFileName + "' 

 72: TO N'" + $GetLDFFileLocation +"\" + $NewContentDBName + "_log.LDF', NORECOVERY, NOUNLOAD, STATS = 10

 73: GO

 74: RESTORE LOG ["+ $NewContentDBName +"] FROM DISK = N'"+ $bkSetName +"' WITH FILE = 2, NOUNLOAD, STATS = 10

 75: GO"

 76: # Fire the SQL Query

 77: Invoke-Sqlcmd -Query $restoreStmt -ServerInstance $SQLServer

 78: Write-Host -f Green "Retore Completed Successfully... "

 79: # END SQL Loop

 80: # Back to SP Loop to attach the new content DB to Central Admin Site

 81: # First - Dismounting DB

 82: Dismount-SPContentDatabase -Identity (Get-SPContentDatabase -WebApplication $CA) -Confirm:$false

 83: Mount-SPContentDatabase $NewContentDBName -DatabaseServer $SQLServer -WebApplication $CA

 84: Write-Host -f green "New Content Database Attached to Central Admin Site.

 85: "

 86: # reset IIS

 87: Write-Host -f green "Running IISRESET now..."

 88: iisreset

 89: $RemoveOption = Read-Host "

 90: Choose Remove Database Option:

 91: 1 - Remove (DELETES the Database from SQL)

 92: 2 - Exit (Do Nothing)"

 93: IF ($RemoveOption -eq '1') { 

 94: [String] $DropDB = "

 95: ALTER DATABASE ["+ $CACurrentdb + "]

 96: SET SINGLE_USER WITH ROLLBACK IMMEDIATE;

 97: DROP DataBase [" + $CACurrentdb+ "]"

 98: Invoke-Sqlcmd -Query $DropDB -ServerInstance $SQLServer

 99: Write-Host -F green "Database Removed from SQL"}

 100: Else {Write-Host -f Yellow "Exiting Remove Operation... Database was not Dropped from SQL Server."}

 101: Write-Host -F Green "All Opearation Completed Successfully."

 102: #################### END SCRIPT ####################

Cheers

Priyo

Scripts.zip