Sql Server Migration

  • Hi Expert,

    I  am doing migration of sql server 2012 from server A to server B. There is no connectivity between server A to server B. so will be doing backup and restore . we have availability group name called group1,group2group3. so while migrating, can we use the same availability group 'name' as it is  to server B  or it suppose to be different

     

    Regards

    Shree

  • Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

  • Any suggeston

  • Suggestion please

  • It isn't clear what you are asking - what does moving from server A to server B have to do with availability groups?  You also stated there is no connectivity...if there is no connectivity how are you getting the backups from server A to server B?

    Are all servers in the same domain?  If so - and you are creating a 'new' AG in a different location then you cannot use the same names (assuming you are creating 2 servers with multiple availability groups - or multiple servers with a single availability group).

    What is the purpose of this migration?  It would be an ideal time to upgrade to the latest version of SQL Server - instead of remaining on SQL Server 2012.

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

  • Open Microsoft SQL Management Studio on the Source server.

    Log in to your SQL server.

    Expand the server and as well as Databases.

    Right click on the name of your database and go to Tasks > Generate Scripts.

    Click Next.

     

     

    http://www.myaarpmedicare.com

    • This reply was modified 3 years, 8 months ago by  Amighost.
  • Amighost wrote:

    Open Microsoft SQL Management Studio on the Source server. Log in to your SQL server. Expand the server and as well as Databases. Right click on the name of your database and go to Tasks > Generate Scripts. Click Next.

    What?

    How will that help solve the original question?

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • I'm going to agree with Jeffrey here. I think you would need to tear down the existing AG before you can create a new AG, especially using the same name.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply