We are having SP 2013 production farm with storing documents in individual site collections using workflow management.
One of the content databases is growing large with 250GB data storage in SQL server.
This content database mainly consists of two large site collections each showing 75 GB data when I checked through SPSite.usage.storage.
I am planning to separate one site collection to another new content database and I should not have option to create new web application as per application design and also should have same site2 url.
Take complete content database full backup. Take site 2 back up separately using Backup-SPsite command (backup-spsite –identity https://site2 -path \\backupsite2.back ) Remove the site2 permanently using Remove-SPSite –identity https://site2 Create the new content database using New-SPContentDatabase pointing existing web application. Restore the site2 backup using same site2 url and attaching it to the new database created in step4 using Retore-SPSite The command should be Restore-SPSite –identity https://site2 –Path \\backupsite.back –ContentDatabase –NewSite2DB -force
We tested this approach in lower environments with site size around 10 GB and worked fine without issues.
This Restore-SPSite operation is taking long time to restore the site (e.g: 3.5 GB data took 4 hours in test server).
I am afraid whether the SP built in tools (Backup & restore commands) can manage taking large site collections with 100GB size
As per this TechNet link, Microsoft recommends to use Built in tools for backup & restore for size upto 100GB.
Is this 100GB site usage size like (SPSite.usage.Storage) or actual size of site backup up file (backup-spsite) ?