New answers tagged

0

there are couple of ways to move the production data into Dev. But before start you have to make sure. Source Farm and Dev Farm both should be on same Version(patch level). if you use the backup-spsite and restore-SPsite then it should be same level. But if you use the Content Database method then if destination level is higher it will work but if ...


0

The content database is one of the steps that will make your dev environment identical to production. but as it's named it only match content not configuration like application services. Regarding restoring your backup content database, you can also check How to Restore / Migrate a SharePoint Web Application to another farm from SQL Database Backup


0

You can do it with couple of ways. Export the SQL table data into Excel, then import that excel file into SharePoint list. You can use 3rd party tools i.e List Bulk Import You can think about the BCS using the external list.


0

if you have the Backup of the Content Database of the web applications, by this you can restore the Content of your portal. But if you have Custom solutions, Authentication and other custom changes to IIS or Web.config files...You have to Manually restore them. In case of DR, You have to rebuild the farm, build the webapp, configure the Authentication, ...


0

The backup operation via central administration normally takes long time based on your farm size and tour backup selections so be patient. Also,you can perform backup using PowerShell as mentioned here. for Farm Backup-SPFarm -Directory <BackupFolder> -BackupMethod {Full | Differential} -Item <WebApplicationName> [-Verbose] For Site ...


1

The issue was when we let the scrip create the DB alias, our environment didn't like it. We created the alias manually first using SQL Server Configuration Manager. Under SQL Native Client 11.0 (32bit) --> Alias and SQL Native Client 11.0 Con --> Alias (you need to do both sections), right click, new alias type your alias name "SharePointDB" and fill out ...


0

Check whether any job is using the farm account and trying to connect to the database from SharePoint server. First, try to stop 'SharePoint timer service' for some time and check whether you are still getting the error logs. If it is stopped, there must be some job which is trying to connect to the database. You can get default list of services for ...



Top 50 recent answers are included