When I perform a complete backup of my development content database using Backup-SPSite and restore the site on a separate farm using Restore-SPSite its currently taking around 25 mins to backup and 45 minutes to restore. Although the process works correctly I'm keen to reduce the time taken as the current deployment time window is an hour turnaround.
I tried exporting only the elements that required deployment but between missing dependencies, missing permissions and also the general lack of SharePoint experience within the organisation I'd feel more comfortable knowing a full backup / restore has been performed.
I believe the reason for the slow backup / restore is due to a single list in the site which contains 9000 items. Each with around 5/6 individual item user role permissions. I can't change this design for the moment so I'm forced to find a better deployment approach.
One thing I've started investigating is taking a SQL Server backup of the content database and restoring it on the destination SQL server. Can I simply restore the dev .bak over the live content database? If so, do I need to IISReset to completely clear the previous cache etc? In the past I've relied on the built in stsadm / PowerShell commands and I can't find any in depth articles covering this option.
Any guidance on the best practice for deploying large content SharePoint sites in a timely manner would be greatly appreciated.
Thanks in advance, Brian.