• State Verified Answer
  • Replies 10 replies
  • Subscribers 46 subscribers
  • Views 5606 views
  • Users 0 members are here
Options
Related

Exchange of the GroupShare server

Jan Schlüter

We have a setup consisting of 4 virtual machines: Domain controller, database server, application server and terminal server.

These are VMs that are hosted at Azure. We cannot upgrade the operating system in a traditional way (in-place upgrade), but have to rebuild the VMs and transfer the services and data. We have already replaced the domain controller with a Windows Server 2019 (previously: 2016). This worked as expected without problems.

Now we have to upgrade the application server to Windows Server 2019. The VM with Windows Server 2016 must also be replaced by a new one with Windows Server 2019. GS 2020 CU02 is installed on the application server. The database server is - as mentioned above - separated.

Is it possible that I set up a new Windows Server 2019 VM, stop all services on the existing GroupShare server and shut it down (hoping I will never have to start it again) and then install GS 2020 CU02 on the Windows Server 2019 and simply enter the access data of the old server as database server?

Maybe it is important to mention that the host name of the application server has to change for technical and regulatory reasons. I cannot avoid this. However, the host name of the database server and the name of the database instance would remain identical.

Has anyone already had to do anything similar?
Rate translation
×
Suggest better translation
×
  • 0

    Hi, it should work without issues. I do not see any problem with the setup you have and with the steps you described.

    You have same GS version and even though you would have different version it should work, the GS installer would update containers during installation. On the DB server side is not any information about application server, so there should not be really any problem.

    I had done similar changes few times already and have not encountered problems. Always take DB backup prio to change like this and you are save. I hope it helps. 
  • 0 in reply to Frantisek Spicak

    Thank for your answer! Are there any more data I've to transfer? Maybe on the filesystem or RabbitMQ? Or is really everything stores inside the DBMS?
  • 0 in reply to Jan Schlüter

    I am not aware about any GroupShare related data stored on Application server. 
  • 0 in reply to Frantisek Spicak

    Sounds easy. So I'll wait for other Feedbacks until tomorrow evening and give it a try. And afterwards I'll inform you about the result. Thank you!
  • 0

    I did the same when passing from GS2017 to GS2020 and at the same time switching windows server and such. Everything went smooth.

    - Remember to give back the groupshare license before shutting it down

    - I would suggest on the application server to use the same path for projects (I have E:/ as mine) since I'm not sure if projects file path are set as absolute or relative path.

    When installing GS on the new VM have handy and working the right accesses to the database server and note down the right name for SDLSystem and other databases and such (if you come from an old version they may be different from the default ones).

    Everything should work fine. Good luck!
  • 0

    No success. At the end of the installation I got:

    2020-04-22 16:49:32.382#Sdl.Server.Configuration.InternalTmServiceClient#InternalTmServiceClient - http://[fqdn]:41235/
    2020-04-22 16:49:32.384#Sdl.Server.Configuration.InternalTmServiceClient#LogIn
    2020-04-22 16:49:32.385#Sdl.Server.Configuration.InternalTmServiceClient#LogIn:Posting to http://[fqdn]:41234/ with auth Basic R3JvdXBTaGFyZTpHcjB1cFNoYXJl
    2020-04-22 16:49:32.385#Sdl.Server.Configuration.InternalTmServiceClient#LogIn:Posting content System.Net.Http.FormUrlEncodedContent
    2020-04-22 16:49:32.385#Sdl.Server.Configuration.InternalTmServiceClient#LogIn:Posting attempt 1
    2020-04-22 16:49:34.530#Sdl.Server.Configuration.InternalTmServiceClient#LogIn:Response status code does not indicate success: 401 (Unauthorized). occured pausing and trying again.
    2020-04-22 16:49:44.531#Sdl.Server.Configuration.InternalTmServiceClient#LogIn:Posting attempt 0
    2020-04-22 16:49:44.533#Sdl.Server.Configuration.InternalTmServiceClient#LogIn:One or more errors occurred. occured pausing and trying again.
    2020-04-22 16:49:54.534#Sdl.Server.Configuration.InternalTmServiceClient#LogIn:Posting attempt -1
    2020-04-22 16:49:54.535#Sdl.Server.Configuration.InternalTmServiceClient#LogIn:One or more errors occurred. occured pausing and trying again.
    2020-04-22 16:50:04.537#Sdl.Server.Configuration.InternalTmServiceClient#LogIn:Posting attempt -2
    2020-04-22 16:50:04.538#Sdl.Server.Configuration.InternalTmServiceClient#LogIn:One or more errors occurred. occured pausing and trying again.
    2020-04-22 16:50:14.539#Sdl.Server.Configuration.InternalTmServiceClient#LogIn:Posting attempt -3
    2020-04-22 16:50:14.540#Sdl.Server.Configuration.InternalTmServiceClient#LogIn:One or more errors occurred. occured pausing and trying again.
    2020-04-22 16:50:24.542#Sdl.Server.Configuration.InternalTmServiceClient#LogIn:return token.
    2020-04-22 16:50:24.542#Sdl.Distribution.ServerInstall.Config.PostInstallation#RegisterTMContainer:looking for database server.
    2020-04-22 16:50:24.910#Sdl.Distribution.ServerInstall.Wizard.PostInstallStep#An error occurred during default container registration - One or more errors occurred.
    2020-04-22 16:50:24.969#Sdl.Distribution.ServerInstall.Config.PostInstallation#An error occurred during default container registration - System.AggregateException: One or more errors occurred. ---> System.Net.Http.HttpRequestException: Response status code does not indicate success: 401 (Unauthorized).
       at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()
       at Sdl.Server.Configuration.InternalTmServiceClient.<GetDatabaseServersAsync>d__6.MoveNext()
       --- End of inner exception stack trace ---
       at Sdl.Server.Configuration.InternalTmServiceClient.GetDatabaseServers()
       at Sdl.Distribution.ServerInstall.Config.PostInstallation.RegisterTMContainer(Action`1 Messenger, String RestUrl)
    ---> (Inner Exception #0) System.Net.Http.HttpRequestException: Response status code does not indicate success: 401 (Unauthorized).
       at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()
       at Sdl.Server.Configuration.InternalTmServiceClient.<GetDatabaseServersAsync>d__6.MoveNext()<---

    I have nevertheless completed the post-configuration to test it (https and setspn).

    When I log in now, I get "One or more errors occured". The dashboard does not load at all. But I can change the page and call projects & co. Does anyone have an idea?
  • 0 in reply to Jan Schlüter

    Found the problem. Had to trust the companies certificate chain. Dashboard works now. Will keep on testing...
  • 0 in reply to Jan Schlüter

    I have just checked few installation logs of my instances and this error occurs in all installtion logs. The part about default container is known and i can understand it in my setup. But the firs part of these errors is unclear. It would be good if someone from SDL representatives explain it in detail...
  • 0 in reply to Jan Schlüter

    There were issues with dashboard display if you used different port than 80 or 443. This should be solved with CU2