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
Related
I am using Visual Studio Community 2013, SQL Server 2008 R2 Express Edition for an MVC web application using entity framework code first migrations for my database.
I am trying to get my local application hosted on the Microsoft Azure platform.
I have registered for a trial account which expires in 30 days, and deployed my MVC5 app out which has been successful.
However, this app requires a database which I am struggling to deploy.
What is the easiest way to get my database deployed out to Azure as I do not seem to have the :
"Tasks" -> "Deploy Database to Microsoft Azure SQL Database" option available to me in SSMS.
I have extracted a Data-tier Application of my local database and have it stored on my C drive, however if I connect to my Azure Account in a second window, and right click the server then select Deploy Data-tier Application, it fails on "Creating schema object in database" with the following error:
TITLE: Microsoft SQL Server Management Studio
An exception occurred while executing a Transact-SQL statement or
batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------ ADDITIONAL INFORMATION:
Users cannot be mapped to certificates, asymmetric keys, or Windows
logins in this version of SQL Server. (Microsoft SQL Server, Error:
40528)
I'm assuming its tried to create my local account plus the IIS APPPOOL account I had to set up to host the website on my local network, however I do not see a way of removing them from the .dacpac export.
When I refresh the Databases node, there is still no database, I'm fairly lost now as to how I might get my db deployed to this server?
If you can extract a compatible Data-tier application and then Deploy it to your target server using your current version of Management studio, then this approach should work, see this link for more reading on ensuring your database is compatible.
Failing this, as was in my case. I downloaded Management Studio 2015, which gave me the option to deploy database to Azure by simply right clicking the required database.
Again, this threw up the error regarding my database level IISAPPOOL user, but not my server account user. As a way around this, I took a backup/restore of the database and removed this user then deployed the copy database obviously minus the problem account.
Now all that was left to do was add a transform to my Release web.config with the Azure connection string as provided on the Azure dashboard, and re-deploy the website.
Problem solved.
We have a SQL Server 2012 enterprise VM on azure, we found it is a bit expensive so we decide to go back to standard, since the VM is already provisioned and configured, we thought the easiest way is to uninstall the SQL Server Enterprise, then download and install SQL Server standard from MSDN.
Question, will this reflect the billing change, which is the goal? Nor we have to provision a new standard instance from gallery. Thanks
No, this will not reflect the billing change. You will need to provision a new standard SQL from the gallery and then employ one of the migration techniques enumerated here (https://msdn.microsoft.com/en-us/library/azure/jj156165.aspx#move) to migrate the sql data to the newly provisioned VM.
We have a windows server 2012 hosted by an Italian provider named Aruba.
The roles of the server are:
Active Directory
HMailServer
3- SharePoint 2013
Project Server 2013
Team Foundation Server 2013
We have some doubt on how to migrate this server, of course the solution to crete a new VM in Azure and transfer users and roles is absolutely impossible as we will surely have bug problems during the migration of the role 3 4 5.
We have tried to create a VHD file using DSK2VHD, but after the upload of the disk to Azure, we wasn't able to create the Virtual machine.
What if we create a parallel machine in the Italian cloud and then use VmWare Converter to export the machine and subsequently convert it to Hyper-V and update to Azure ?
What is the best and reliable approach we should use to migrate correctly all?
It is possible that your issue is due to size restriction or that the disk is not fixed size?
Uploading the VHD using CSUpload could help as it will ensure the disk is converted to fixed size before uploading.
I created a BizTalk VM on Azure (Trial version). I can get to the console but I cannot connect it to an existing group. Where is the BizTalk database? Do I need to create that also. Do I need to create a BizTalk Service? I am new to BizTalk and definitely BizTalk on Azure so forgive me.
The BizTalk trial edition image has BizTalk and SQL installed but it does not have a group pre-configured.
To use it you will first need to run the BizTalk Configuration Tool and create a group on the local SQL Server before you can see it in the BizTalk Administration Console.
The configuration tool will create all the necessary databases on the local SQL Server (or any other SQL Server you will point it at) and create the BizTalk Windows Services as needed.
It's worth noting that non-trial editions of BizTalk server do not include a local SQL Server as these are targeting the recommended architecture for a BizTalk farm whereby the SQL Servers are dedicated and separate from any BizTalk servers
This is highlighted in the announcement of the availability of these images
Yes, you need to configure a number of elements. Steps include
> Create the Domain User Accounts and Groups [standard and enterprise]
> Create a SQL Server virtual machine [standard and enterprise]
> Configure using BizTalk Configuration [evaluation, standard and enterprise]
I have recently started working on Sharepoint 2010 and created a 3 tier test setup (server1- WFE and CA, server2- running all service applications, server3- Database server). I used powershell commands as listed in this blog to first create the admin and config databases. After that i used the Farm wizard to provision all the service applications.
After completion all the service app DB names have GUIDs. In IIS 7, all the application pools and the virtual directories under Sharepoint web services have GUIDs. Also all the service apps are running in the same user id (domain\spservice) and i am unable to change the id for some of the services.
I want to recreate my environment and not have any GUIDs, neither in the DB names nor in IIS. I have not been able to find any documentation on how to create all the service application DBs and IIS app pools without GUIDs. The one article i found mentions how to remove the GUIDs after installation. (I am left wondering if all production sharepoint 2010 farms out there really use GUIDs in DB names and in IIS (app pools, virtual directories)!?)
Can someone please direct me to an article that outlines steps to configure a complete sharepoint 2010 environment without GUIDs in DB and IIS?
When i started out on the initial test setup I used the Farm Configuration Wizard which creates almost all the databases with GUIDs and all those GUIDs can seem overwhelming for managing the environment, for documentation etc.
To answer my question in short- the sharepoint databases can be created without GUIDs (using powershell). However in IIS, the creation of application pools and virtual directories in IIS for the service applications will have to be with GUIDs. There is no alternative for that.
I followed the steps in the article here for initial install and then used the script to create service applications from this technet article making the necessary server and database name changes.
With most of my experience as a windows web farm administrator and managing uniform naming conventions the GUID names seemed annoying initially! But since there is very little to manage or troubleshoot from the IIS interface, we do not have to worry about app pool names and vdirs with GUIDs. It is all about ULS logs, event viewer and Central Administration site!