Existing SQL Cluster: Easiest Method to Move to new Datacenter

Although there are a few questions similar to mine, I didn't find anything with these special circumstances, so I'll try a new thread:
We have an existing SQL 2008 Cluster with shared storage in a data center and we're moving this to a new data center. It's quite a bit of data (400GB+), and I'm looking for a way to move it over without extended downtime. Is there a way to
add a third node perhaps to the cluster that's read only but syncs the data? As a systems administrator (this company just lost their DBA, so I'm short filling the role), I may be approaching this the wrong way, but anyway.
Any ideas?
Thanks!

Hi VintageDon,
According to your description, personally，if you choose to use log shipping after adding a third node, you will need to manually transfer things like logins, linked servers, SQL jobs, etc. Even if you can failover the databases and recover
them, however, this still causes SQL Server downtime due to the bit of data. Microsoft added live migration to Hyper-V in Windows Server 2008 R2, and Windows Server 2012. The management feature helps reduce planned downtime and provides a foundation for the
dynamic data center by allowing you to move virtual machines (VMs) between Hyper-V hosts with no downtime at all.
A memory synchronization process occurs where the target VM is updated with the user’s changes to the source VM. After the memory is synchronized, the user is cut over to the VM running on the target Hyper-V host. The VM on the new host can immediately access
its virtual hard disk (VHD) files stored on Cluster Shared Volumes (CSVs). For more information, see:
http://windowsitpro.com/windows-server-2012/windows-server-2012-shared-storage-live-migration
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Similar Messages

Can a SQL Cluster have many Master Secret \ SSO systems?

We are trying to build a BizTalk environment that will offer multiple BizTalk instances off one SQL cluster.
Our SQL cluster consists of 2 servers configured in an ACTIV\ACTIVE configuration and reads data from a SAN.
We have to set up 6 BizTalk instances to create 6 environments for UAT, Support, DR, etc. These BizTalk groups will contain 2 BizTalk servers each. Each instance will have a group of service accounts assigned to it ino order to separate the environments
but will still use the same SQL cluster.
We have named cluster resources for each UAT, Support, etc for the SAN so that the databses are written and read from mounted disks.
My question and confusion surrounds SSO and the clustering of the Master Secret for multiple instances.
I want to cluster the Master Secret on the existing SQL cluster as the documentation states, but I am not sure if this is correct when there are multiple BizTalk instances running off the the same SQL cluster. The nodes of the SQL cluster will have
the SSO service installed and so too will the BizTalk servers in each instance group - UAT, Support, etc. So, would this mean there is only one master secret being used for all BizTalk instances, which I feel is wrong?
Or should the master secret just exist on a bizTalk server without HA?
I want HA but not sure where the SSO and master secret should go and ensure there are no dependencies from the other BizTalk instances should the SSO service need restarting on the SQL cluster.
I have not implemented multiple instances on the same SQL cluster before so this is new and confusing. The microsoft documentation isn't too great either.
Any help and guidance would be greatly appreciated.

post Windows Server 2008 you can have multiple MS DTC instances on one cluster. So unlike previous versions (w2k3) where the recommendation was to add MSDTC to the base cluster group, you can now have one instance of MSDTC cluster resource per resource group.
In short yes if you feel that MSDTC is becoming a bottleneck in your processing. Also it would be preferred that for each of your BizTalk Environments you create at least ONE MSDTC resource per environment.
Regards.

Is it possible to move to Alwayson Availability groups from existing sql server FCI ?

Is it possible to move to Alwayson Availability groups from? existing sql server FCI ?
If yes, how to move and what are the pre-requisites?

Hi Rahul,
Based on your description, we need to verify if you want to move from Failover Cluster Instances(FCI) and database mirroring to SQL Server Alwayson Availability groups. If so, it is possible.
You can review the following articles to get more detailed information about this kind of migration.
How To: Migrate from Failover Cluster Instances and Database Mirroring to SQL Server AlwaysOn
– Part 1
How To: Migrate from Failover Cluster Instances and Database Mirroring to SQL Server AlwaysOn
– Part 2
Thanks,
Lydia Zhang

Adding existing SQL Server 2012 to a New SQL 2012 Cluster

We currently have a SQL 20012 Server setup and running on our domain. We would like to switch this to a clustered environment. Is it possible to setup the new SQL 2012 Cluster and add the existing SQL 2012 server as a node in the cluster
without losing any functionality. All servers will be built with same drive letter.

We currently have a SQL 20012 Server setup and running on our domain. We would like to switch this to a clustered environment. Is it possible to setup the new SQL 2012 Cluster and add the existing SQL 2012 server as a node in the
cluster without losing any functionality. All servers will be built with same drive letter.
No its not possible to convert standalone installation to cluster.Moreover first you need to configure Windows cluster then backup all SQL server databases logins jobs packages and install fresh instance of SQL Server in cluster aware mode
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

What's the easiest way to move app data and data structures to a server?

Hi guys,
I've been developing my app locally with Apex 4.2 and Oracle 11g XE on Windows 7. It's getting close to the time to move the app to an Oracle Apex server. I imagine Export/Import is the way to move the app. But what about the app tables and data (those tables/data like "customer" and "account" created specifically for the app)? I've been using a data modeling tool, so I can run a DDL script to create the data structures on the server. What is the easiest way to move the app data to the server? Is there a way to move both structures and data in one process?
Thanks,
Kim

There's probably another way to get here, but, in SQL Developer, on the tree navigation, expand the objects down to your table, right click, then click EXPORT.. there you will see all the options. This is a tedious process and it sucks IMO, but yeah, it works. It sucks mostly because 1) it's one table at a time, 2) if your data model is robust and has constraints, and sequences and triggers, then you'll have to disable them all for the insert, and hope that you can re-enable constraints, etc without a glitch (good luck, unless you have only a handful of tables)
I prefer using the oracle command line EXP to export an entire schema, then on the target server I use IMP to import the schema. That way, it's near exact. This makes life messy if you develop more than one application in a single schema, and I've felt that pain -- however -- it's a whole lot easier to drop tables and other objects than it is to create them! (thus, even if the process of EXP/IMP moved more than you wanted to "move".. just blow away what you don't want on the target after the fact..)
You could use oracle's datapump method too.
Alternatively, what can be done, IF you have access to both servers from your SQL developer instance (or if you can tnsping them both already from the command line, you can use SQL*PLUS), is run a script that will identify your apex apps' objects (usually by prefix to object names, like EBA_PROJ_%, etc) and do all the manual work for you. I've created a script that does exactly this so that I can move data from dev to prod servers over a dblink. It's tricky because of the order that must be executed to disable constraints and then re-enable them, and of course, trickier if you don't consistently prefix ALL of your "application objects"... (tables, views, triggers, sequences, functions, procs, indexes, etc)

What is the easiest way to move all my iPhone photos to an external hard drive?

How can I manually backup the enormous collection of photos clogging my iPhone 4?
Syncing with iTunes sounds like I'd be doing just the opposite -- and actualy adding to my iPhone's image girth.
On my laptop, I work primarily with PS Elements, iPhoto, and Aperture.
Thanks
PHT

These are two possible approaches that will normally work to move an existing library to a new computer.
Method 1
Backup the library with this User Tip.
Deauthorize the old computer if you no longer want to access protected content on it.
Restore the backup to your new computer using the same tool used to back it up.
Keep your backup up-to-date in future.
Method 2
Connect the two computers to the same network. Share your <User's Music> folder from the old computer and copy the entire iTunes library folder into the <User's Music> folder on the new one. Again, deauthorize the old computer if no longer required.
Both methods should give the new computer a working clone of the library that was on the old one. As far as iTunes is concerned this is still the "home" library for your devices so you shouldn't have any issues with iTunes wanting to erase and reload.
I'd recommend method 1 since it establishes an ongoing backup for your library.
Note if you have failed to move contacts and calendar items across you should create one dummy entry of each in your new profile and iTunes should merge the existing data from the device.
If your media folder has been split out from the main iTunes folder you may need to do some preparatory work to make it easier to move. See make a split library portable.
Should you be in the unfortunate position where you are no longer able to access your original library or a backup then then see Recover your iTunes library from your iPod or iOS device for advice on how to set up your devices with a new library with the maximum preservation of data.
tt2

SQL cluster 2008 R2 migration to new Hardware in VM

Hi,
We have a task to migrate existing Physical SQL Cluster DB to new Hardware but in VM. (cannot argue with the client)
hence our plan is to install new Cluster in VM with same Windows and SQL version i.e Win 2K8 R2 ENT w/SP and SQL 2K8
R2 STD w/SP and use SQL mirroring option for the DB to migrate on the new Server (keeping the downtime to as low as possible and advantage of bringing the old server online in case of any issues..)
Below points are for a single instance, couple of DB to migrate:
Keep the physical production server running
In-Parallel build New SQL Cluster in VM (keep same version windows/sql)
Keep Same drive letter for Quorum, MSDTC, DATA, LOG & Backup
Keep the same Instance Name, SQL Network Name can be different (will be changed to old network name once the PROD is shutdown)
Check all logins windows and SQL to be same on both the clusters
Copy all the jobs, SSIS packages etc.. .create the location folder as per current server on the VM SQL Cluster
Perform full backup of old cluster company-db databases or use the existing latest backup (full, differential, transaction)
Restore databases in the new cluster with no recovery so additional log file or differential backup can be restored
Create SQL Mirroring for the Database and select the principal server (old cluster) and the mirror server (new VM cluster)
Choose mirroring without witness ( no auto failover as we don’t need the old server later)
Start the mirroring – (hopefully everything synchronized and working)
During the downtime –
Stop the application/ client connection – if possible
Failover the DB through Mirroring option
Once the mirrored server becomes Principal and data is accessible – stop the mirroring
Now the new VM SQL Cluster DB is online
Shutdown the old cluster company-db (Node1 & Node2)
Come back to VM SQL Cluster and change the Network name to the old server network name (so that client connections are not affected)
Check if the DNS entries are updated with correct name and IP address
Delete DNS entries for old company-db on DNS Servers if not deleted, delete the old server SQL network name in computer object
Stop SQL Resources on the new VM SQL Cluster (take it offline all the resources)
Bring online the SQL Resource and make sure the SQL resources are online and new network name is reachable
Wait till you see machine name company-db in active directly (AD) and DNS server will have entry for company-db
Verify connectivity for company-db from outside.
If things are not going as per the plan then shut down the new VM cluster
Revert back the DNS settings
Power up the Old SQL Server
The DB will show “restoring mode” – use command to make it online “RESTORE DATABASE (dbname) WITH RECOVERY”
Check the DB
Start using the OLD server again
Troubleshoot the failed scenario ;)
Need to know if the above steps are okay, and any consideration once the new VM SQL Cluster is online.
Kindly let me know if there anything else to transfer apart from the logins, jobs, folder location etc.. !!
Many Thanks

Hello,
Well if you don’t change the instance name (name = ABC) then its OK.
Try the following resources about transferring SQL Server logins:
http://support.microsoft.com/kb/918992/en-us
http://www.mssqltips.com/sqlservertip/2081/transfer-sql-server-jobs-task-and-transfer-sql-server-logins-task-in-ssis/
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Sharepoint 2010 farm Sql cluster

hello,
i have sharepoint farm with 3 server ( Web front , Sql , search server )
can i make sql cluster to sql with 3 sql server or it be must before begin install sharepoint farm
thanks
Nour

Your question isn't very clear but i think i understand.
You have an existing farm with a single SQL server.
You want to upgrade your single SQL server to a clustered SQL installation.
Doing so is not easy, you can't upgrade a single server SQL install to a clustered install as far as I know. You'd need to re-build the SQL server as a single node cluster and add the new servers to make the full cluster before moving the SharePoint databases
over.
In addition you'd need to use SQL Aliases to point to the new clustered SQL address. If you've already used them then that's great, if not you'd need to use the old, single server, address as the Alias address and point it to the cluster.
In short: You can do it later but it's quite tricky and best done before you install SharePoint.

Question on sql cluster failover behaviour

Hi Experts,
I have a doubt on SQL Cluster.
In SQL cluster, If we MOVE the group or failover the group to another node what happens to the user connections(say 100 conn's) and ongoing open transactions during failover?
Will all connections gets disconnected and open transactions gets rollbacked or the connections and txns will be moved to other node?
Could anyone shed some insight on this?
Thank you.

All connections get disconnected an ongoing transactions have to be rolled back. Its like restarting the service, just on the other node.
Bodo Michael Danitz - MCT, MCITP - free consultant - performance specialist - www.sql-server.de

SCOM 2012 Reporting Components with a shared SQL cluster

Hi, we are planning to install SCOM 2012 but i am a bit confused around the reporting components.
We have a shared SQL Enterprise cluster with multiple instances which we would like to use for our OperationsMananger and OperationsManagerDW databases. However after trying a test SCOM deployment, installing the SCOM reporting components on a VM requires
a local running copy of SQL reporting services.
Is this true? It seems ludicrous to have to purchase an additional license of SQL just to run the reporting components of SCOM. We have spent a lot of money on our SQL cluster and we would like to use it. We dont want to install the SCOM reporting components
on the shared SQL cluster.
If this is true, can you tell me which license of SQL we require? Just to run SQL reporting services on a VM should just require a standard SQL license, right?
Also if we have to purchase a SQL license for this standalone VM, would you recommend having the OperationsManagerDW database on the shared SQL cluster or on the VM where the standalone instance of SQL reporting services resides.
Surely this is something that other people have an issue with? I would have thought most people would want to use a shared SQL cluster. Any help is much appreciated.

Just to add that SQL Reporting Services isn't cluster aware so the best you could do is to install stand-alone onto a node of the cluster.
To reinforce what Scott is saying, see this screenshot of the install of SCOM reporting:
http://www.systemcentersolutions.co.uk/images/easyblog_images/42/scom/CTP2/Install/SQRS9.png
Technically you can install SCOM reporting on a shared SQL Server Reporting Services instance but as Scott (and the screenshot) state - it will overwrite any existing security settings on existing reports.
Scott is also correct that SQL Server Standard Edition is included as part of the licensing cost of System Center 2012 as long as the SQL instance only runs components of System Center.
cheers
Graham
Regards Graham New System Center 2012 Blog! -
http://www.systemcentersolutions.co.uk
View OpsMgr tips and tricks at
http://systemcentersolutions.wordpress.com/
I have one SQL 2012 Server with a few instances. 1 for Scom, 1 for SCCM and 1 for Service Manager. The instance shows up as blank for reporting services on the SCOM. Do I have to install SQL on the SCOM box also? Why Can't
it see the instance on my 2012 SQL box? It is in a different instance than SCCM.

Adding Availability Group to Existing SQL Server 2012 Enterprise installation

Looking at an existing SQL Server 2012 Enteprise vm. We'd like to add availability group functionality. It seems that we should be able to create a second VM and install SQL on it in an identical configuration. Then create a windows cluster with
the two nodes. From there we should be able to configure avaialbility groups.
I've set up avaialbility groups before but have not retrofitted one before. It seems possible though since the instances are standalone. Anyone see a problem with doing this?
thanks
Peter

Hello,
What you have is pretty much it. Since AGs require clustering but do not require a clustered install (stand alone install is used) there shouldn't be any changes with the actual install. You will have to enable the HADR option in the configuration manager
once the clustering is setup.
Sean Gallardy | Blog |
Twitter

Sql cluster with Always on

Hi
I have 2 sites Ho & DR
I have 2 sql servers in each site
I need to make on each site sql cluster and between the 2 sites we need to make always on
please need the steps for this scenario
MCP MCSA MCSE MCT MCTS CCNA

Hi Yasser,
According to your description, you want to setup a disaster recovery solution combining SQL Server Failover Cluster in Primary Datacenter and Availability Group on a SQL Server Failover Cluster in Secondary Datacenter. Assume that, in the Primary DataCenter,
SQL_PV is the FCI instance and CLP_1 and CLP_2 are the two nodes. In the Secondary DataCenter, SQL_SV is the FCI instance and CLS_1 and CLS_2 are the two nodes as the screenshot below shows.
To achieve the goal, you could follow the steps below:
1.Add two nodes CLS_1 and CLS_2 from secondary datacenter into the existing
Windows Server Failover Cluster(WSFC). Please note that all nodes for an availability group must exist on a single WSFC within the same Active Directory domain, even between datacenters.
2.Configure Shared Storage for both CLS_1 and CLS_2 nodes.
3.Install FCI instance of SQL 2012 Enterprise edition using "New SQL Server Failover Cluster Installation" and join the other secondary node using Add node to a SQL Server failover Cluster.
4.Enable Always on Availability Group on newly installed FCI.
5.Define the possible owner for each SQL Server FCI as the following:
a. Go to "SQL Server" services on the Cluster instance under SQL_PV group and go to SQL Properties. Under Advanced Policies, choose only CLP_1 and CLP_2 as possible owner for SQL_PV.
b. Go to "SQL Server" services on the Cluster instance under SQL_SV group and go to SQL Properties. Under Advanced Policies, choose only CLS_1 and CLS_2 as possible owner for SQL_SV.
For more information about the process, please refer to Scenario 2 in the article:
http://www.mssqltips.com/sqlservertip/3150/adding-sql-server-alwayson-availability-groups-to-existing-failover-clusters/
Regards,
Michelle Li
If you have any feedback on our support, please click
here.

SQL Cluster requiremnt for Lync 2013

Hi
We are are planning to deploy Lync 2013 enterprise. Planning to use SQL cluster. Would like to clarify whether we must create a sepearte sql instance for Lync 2013 or can we use an existing shared instance to create a seperate database for Lync.
We prefer 2nd approach. Is there any issues or demerits using existing shared SQL instances?
Thanks and regards,
Aboo Arif

Hi AbooArif.
This kind of question is very common. Basically here is the Microsoft Documentation about it.
Database software support in Lync Server 2013
https://technet.microsoft.com/en-us/library/gg398990.aspx
This point is the important: "If you collocate Lync Server databases with other databases, we highly recommend assessing all factors that might affect availability and performance, as well as ensuring that, if one node fails, the remaining node can
handle the load. To verify failover capabilities, we recommend testing all failover scenarios."
We can say the following: It's recommended to use a separate SQL server for Lync, however collating Lync database with other SQL databases will work, but has an high probability of present some performance problems. Many customers prefer to use this option
considering the cost of SQL licenses.
It is important to consider all the hardware requeriments for the Lync Server BackEnd role:
https://technet.microsoft.com/en-us/library/gg398835.aspx because the normal issue when customers share the SQL server with other instances is due to performance issues. Also note
that if you have multiple front end pools, these cannot share a SQL server.
PLEASE REMEMBER, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answered"

Moving Physical SQL Cluster into Virtual SQL Cluster based on Hyper-V Failover

Hello All............I have a SQL Cluster based on Physical Hardware that has Three-3 instances as well. I have setup a Hyper-V Failover Cluster (2012 R2) and have built Virtual/Guest SQL Cluster (2012 R2) upon it. Now, I intend to move
the instances/databases from Physical SQL Cluster to Virtual SQL Cluster.
1. Is this supported? If so, I would appreciate any guidance on it?
2. Is P2V of SQL Cluster supported in Hyper-V Failover Cluster based on Windows Server 2012 R2?

Hi Sir,
Please refer to the following blog regarding moving SCCVM SQL database to another SQL server:
http://blogs.technet.com/b/configurationmgr/archive/2013/04/02/how-to-move-the-configmgr-2012-site-database-to-a-new-sql-server.aspx
It is quoted from the similar thread :
https://social.technet.microsoft.com/Forums/en-US/a1558842-cdf5-4e5f-8f10-d660e96eae1b/migration-sql-for-sccm-2012?forum=configmanagermigration
But it seems that is a migration of system center production , I would suggest you to post the question to system center forum ：
https://social.technet.microsoft.com/Forums/en-US/home?forum=configmanagermigration%2Coperationsmanagergeneral&filter=alltypes&sort=lastpostdesc
Best Regards,
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Added new parm to an existing SQL stored procedure CR 11 doesn't like it

Hi
I have added a new parameter to an existing SQL stored procedure (SQL 2000). This stored procedure is currently being called from a Crystal XI report. It prompts for a date which works great. (The report was created with this parameter). I added a new parameter to the stored procedure. When I do a preview in Crystal, it prompts for the new parameter, but is NULL when I look at the SQL query and it brings back no data. If I try to verify the database, it tells me that I am missing parameter @ProcessType (varchar(5))--(name of new parameter). I have physically added this parameter to the crystal report with the select expert and still no luck. I have already tried renaming the procedure but am unable to update datasource location because of this parameter. The report is very detailed and I do NOT want to create a new report.

Unfortunately, I have tried and retried to do this. Nothing changes. I usually would get a message like database has changed, proceeding to fix report. I don't get this. It merely tells me database is up to date and only returns the 1 parameter, yet when I go to the datasouce and try to update it, it tells me that I have not supplied the new parameter.
I have tried everything, from closing Crystal reports and then going so far as to reboot my machine, just in case their was some kind of caching going on.
I have even asked other people I work with to look at it to make sure I am not doing something dumb...

Existing SQL Cluster: Easiest Method to Move to new Datacenter

Similar Messages

Maybe you are looking for