4 Replies Latest reply on Feb 2, 2018 2:34 PM by LJ LongWing

    Cloning of production server by restoring the production database over staging server

    PAWAN KAUSHIK

      Hi All,

      This question is posted in reference of my friend he required some information about his concern:

      He is working on remedy 7.6.04 and he tried to setup a remedy staging environment as like their production environment. Hence he has already installed with the application and arserver/database all. Then 2nd step he took backup of existing production databse and restored the same over the staging database server. Now he changed the configuration file which is pointing the new database which was restored. but when he is trying to login into developer studio then he is getting an warning message:

       

      also while trying to create a new entry in people form the in update permission tab while adding module permission of incident master with fixed or floating license then he is getting below error:

       

       

      Could you please help whether this is related to the AR License or what ? Please suggest how to overcome with this problem.

       

      Thanks in advance!

        • 1. Re: Cloning of production server by restoring the production database over staging server
          Ganesh Gore

          Certainly its related to AR Server and ITSM licenses. Non Licensed server allows only 2000 entries.

          Once you have restored prod db to this replica server, you need to add new ARserver license as hostid of the new server is different. 


          If you dont have permanent license then you can generate trial license for this server from the bmc site (It requires valid support id). 


          Apply AR license key in add remove license form and restart the server.

          1 of 1 people found this helpful
          • 2. Re: Cloning of production server by restoring the production database over staging server
            LJ LongWing

            Pawan,

            Yes, the Remedy license is in the Remedy DB, so when you restored the db from prod over to lower environment, if your prod environment didn't already have the lower environment in it's license table, it's not licensed at this point.  You will need to apply a server license to it to get it functional....additionally, you might want to apply the same license in prod so that next time you go through this effort it'll already be there

            2 of 2 people found this helpful
            • 3. Re: Cloning of production server by restoring the production database over staging server
              PAWAN KAUSHIK

              Hi Ganesh And L J,

               

              I think Host ID of a machine is stay constant untill unless we are not changing the hardware. Previously before restoring the database it was working fine. As per your statement before database restoration server hostid in Add remove license form Was 100xyz and after the restoration of production database if has changed the host id to something 111abcd ?? kindly clear me with below points in my mind:-

               

              1. The hostid which we can see in Add or remove license form would get changed ?

              2. If first questions's answer is yes then would it show the same hostid of the server whose database we had restored ?

              3. If i was having the permanent License key with me before production database restored on staging server and after database restoration the host id got changed then how i could retain my previous license for staging server ? so that it can work on the same license on which it was doing earlier.

              • 4. Re: Cloning of production server by restoring the production database over staging server
                LJ LongWing

                Pawan,

                The Host ID is the Mac address of the Remedy server....no matter the db it's connected to, that stays the same....there are only two situations that I've seen where the host id changes on a box.  Either the OS starts recognizing a different NIC as 'primary' and thus using its mac address, or if you are running your Remedy server in a virtual environment and the mac is not hard coded (as it needs to be to remain licensed), depending on what caused your mac to change you can either re-license against the new mac, or you can change the mac to match the license.

                1 of 1 people found this helpful