Tag Info

New answers tagged

2

You can use export-spweb / import-spweb which by default will not carry over user security settings. Command reference: http://technet.microsoft.com/en-us/library/ff607895(v=office.15).aspx


0

I believe the PowerShell cmdlets "export-spweb" and "import-spweb" will bring the views along with them. For example... # To export export-spweb -identity $srcweburl -path "\\server\c$\BackupDir" -itemurl $listname -confirm -force -haltonerror -includeusersecurity -nofilecompression; # To import import-spweb -identity $tgtweburl -path ...


2

Are you Backup on shared folder, if yes then check SQL Server permission there on Shared folder. For me it looks like permission issue. Yes it will do SharePoint part properly but when it will try to do the backup of SQL Database, that time it will use SQL Server Service account may be that account will not have permission to Shared folder. Another thing ...


0

You can save site collection as a template without including content. Then create new site collection based on that template.


1

To get the site id use powershell. Interestingly in my case I can create the powershell object. E.g. $s=Get-SpSite <url> $s.ID Go to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN Then execute STSADM -o deleteconfigurationobject -id <site id> In once case this worked Or you can try deleting $s.Delete ...


1

7105 is the build number. If you run Fiddler and check your current SharePoint farm, you will find in the header of your request "MicrosoftSharePointTeamServices: 14.0.0.6029" In order to restore your backup, you need a farm that is beyond build 7105 (e.g. build 7106 - August 2013 CU which was released after SP2).


1

Check in the Event Viewer if there are SQL permission error. Open Event Viewer (click start and search it) Expand Windows Logs and than click Application (in the left side) Check if there are critical error like this with the following details SQL Database *DATABASE_NAME* on SQL Server instance *SQL_INSTANCE* not found. Additional error information from ...


1

I found an answer, just for site collection created on web application root. Use this command to backup a site collection Backup-SPSite -Identity "http(s)://your-site-collection-url" -Path "C:\backups\your-site-collection-backup.bak" It's important to use an absolute path as -Path parameter. Then create a new web application and then run the following ...


1

couple of things you can do. 1) Backup curent site collection and then restore it with different name & url. 2) you can use export Site Collection and Import site collection. You will lose the metadata etc. 3) you can use the 3rd party tool for this, which give you more power & flexbility and less effort. try ShareGate migration tool. they have 15 ...


0

Have you checked if there is a enough free space in the location you are saving the .bak file as well as the directory where temp files are saved ? It first writes it to the temp dir and than moves it to your location, effectively you need the target .BAK size as free space twice. EDIT: According to this post a bit down the thread, his issue was caused ...



Top 50 recent answers are included