Is there any fullproof and complete way to setup a sharepoint site from one machine to another machine with everything. Assume both machine have installed sharepoint server.
Create a Backup of your site collection using backup command in power shell or using central Admin. Restore the backup using restore Command Power Shell.
Related
Here is a scenario that I would like to know best way to tackle it.
SharePoint 2013 Farm 5 servers (2 app, 2 web, 1 DB) -- Windows Server 2012
Workflow Manager Server (a standalone box) -- Windows Server 2012
Workflow Manager DB Server (a SQL shared box) -- Windows Server 2008
As part of the infrastructure upgrade - we are decommissioning Windows 2008 servers. I was told to move workflow manager databases out of Windows 2008.
What I found online are the articles pointing to WFM disaster recovery plan where we backup restore workflow DBs onto a different server, re-install workflow manager on a new server, and execute the WFM restore using PowerShell.
Without doing Workflow Manager installation or uninstall/re-stalling, is there a way (even possibility) to migrate just the 6 workflow databases to different DB server, and then update existing workflow manager DB connection strings?
There is no direct way of the updating the WFM databases. You need to setup new WFM servers and use backup and restore command to attach the 4 DBS. Check the details here https://social.technet.microsoft.com/wiki/contents/articles/29158.workflow-manager-disaster-recovery.aspx
So the user seems to have overriden a file on a sharepoint list with no versioning. I don't know what SharePoint version it is, but it's definitely on prem (not online). A back-up was made yesterday, prior to the user overriding the file.
Is it possible to restore the file & restore everything back to normal from user admin/back-up? If yes, how?
As the first step enable versioning to the current library.
If there is a SQL backup create a separate site or web application and over write the database of the newly created web application with the existing backup.
The you can access the site using the newly created webapp , download the file and upload it to the original site.
Do the restoring of the database in a test environment as its not recommended to create so many web applications (More than 6).
References
https://technet.microsoft.com/en-us/library/ee748604.aspx
https://technet.microsoft.com/en-us/library/gg266384.aspx
I have a SharePoint 2010 web application with one site collection. I want to copy that site collection to a new web application on the same server.
I took a backup and restored it to a new database on the sql server. I then created a new web application with a temporary content database that I removed from the web application. I then added the restored copy of the original web app to the new web application.
The problem is the newly attached content database show 0 site collections, but there is in fact 1 single site.
I guess it has something to do with the id's? I have tried adding the content db both with and without assigning a new ID to the database.
Any idea how one can copy a site collection to a new web application on the same server?
--
Christian
Try using import/export. The main difference between import/export and backup/restore is that import/export generates new Guids.
http://technet.microsoft.com/en-us/library/ee428301.aspx
Use Windows PowerShell to export a site, list, or document library in SharePoint Server
You can use Windows PowerShell to export a site, list, or document library manually or as part of a script that can be run at scheduled intervals.
To export a site, list or document library by using Windows PowerShell
Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
On the Start menu, click All Programs.
Click Microsoft SharePoint 2010 Products.
Click SharePoint 2010 Management Shell.
At the Windows PowerShell command prompt, type the following command:
Is there a command to delete the entire web application (database, iis sites etc) using the Sharepoint admin tool?
I know the same can be done in the central admin, but i have a need to automate this process as we want our build servers to rebuild the sharepoint site from scratch each night.
You should be able to do that with the stsadm unextendvs operation.
stsadm -o unextendvs -url http://MySite -deletecontent -deleteiissites
In addition to the unextendvs stsadm command you will need to drop the table in SQL. Using this command to remove the content database will remove the link from the content database to the SharePoint web application, but I don't think it will actually drop the SQL table.
So if you are running this every night be sure to either re-use the same content database or also script the table drop to ensure your SQL environment does not end up with abandoned tables.
I've used the central admin backup facility to backup our Shared Services Provider. The backup location was a drive on a new server.
I then try to restore the SSP via central admin on the new server. It fails with an error relating to the fact that it cant find the .mdf files that it requires. It is looking in the location that they were on the original server.
Does the backup not take care of moving these .mdf files as part of the backup restore process?
Would appreciate anyone's suggestions.
Are you following these instructions on migrating the SSP?