BuyDomino Search MyDomino Portals Change Region Menu

Domino Automation - How to Migrate from SQL 2019 towards SQL 2022 (.bak)

Safety Note

This document applies to:

  • The Domino Printing group
  • The IT department of Domino's customers
  • The end user of the Domino Designer software
  • The end user of the Domino Automation software

Description

This document aims to outline the steps to migrate SQL 2019 towards SQL 2022.

✍️ NOTE
  • Administrative rights are required to perform migration operations.
  • The server will need to be restarted.
    • It's important to plan accordingly, either by choosing an appropriate time for migration or by notifying relevant colleagues about the upcoming server restarts.

Step 1

Perform a Manual Backup (.bak) on Server

✍️ NOTE

 In this scenario, the Automation project name to backup DA_RSERIES
  1. Open SQL Management Studio



  2. Connect to the instance

    Several possibilities to enter in "Server Name" for the connection:
    1. SERVER_NAME\INSTANCE_NAME
    2. SERVER_IP\INSTANCE_NAME

  3. After connecting, the following page appears



  4. Left-click on the "+" located next to "Databases":



    You need to backup both the database and the metrics database, ie: DA_RSERIES & DA_RSERIES_Metrics

  5. Right-click on DA_RSERIES, then "Tasks", then "Back Up…"



  6. Verify backup directory and click “OK”



  7. The following message will confirm whether the backup worked:



  8. You may verify the directory itself:



  9. Right-click on DA_RSERIES_Metrics, then "Tasks", then "Back Up…"



  10. Verify backup directory and click “OK”



    The following message will confirm whether the backup worked:



  11. You may verify the directory itself



  12. You can save the backup on an external or backup hard drive.

Step 2

UNINSTALL SQL SERVER 2019

✍️ NOTE

Care must be taken to delete only the instance used by Domino Automation. Otherwise, it may affect other software solutions and have significant consequences for the client and their server.

 

  1. After backing up the entire Domino Automation database, go to "Control Panel" / "Uninstall a program."

  2. Uninstall "Microsoft SQL Server 2019 (64-bit)":



  3. Click on "Delete":

  4. In the drop-down menu, select the instance used by Domino Automation:

  5. By default, the name used is MSSQLSERVER. It is necessary to confirm with the client's IT service to ensure that the correct instance is being deleted.

  6. Check the following two items and click "Next" to proceed with the uninstallation:

    [x] Database Engine Services
    [x] SQL Server Replication

  7. Click "Remove" and wait for the instance to be uninstalled.



  8. Close the setup at the end of the uninstallation.



  9. Restart the server.

Step 3

DOWNLOAD SQL EXPRESS 2022

  1. Navigate to Microsoft® SQL Server® 2022 Express

  2. Select language, i.e: English and Download



  3. Copy the file “SQL2022-SSEI-Expr.exe” in a certain local directory, i.e: C:\Temp\2022\EN

Step 4

CREATE MANUALLY AN INSTANCE: DASQL

  1. Reference the following guide: How to manually create an SQL Instance named "DASQL"

  2. Create an instance named: DASQL

Step 5

Restore the Database through .bak Methodology on New Server

  1. Open Windows explorer



  2. Connect the backup device that includes the .bak files of the database



  3. Copy the backups



  4. Go to the following directory:

    C:\Program Files\Microsoft SQL Server\MSSQL16.DASQL\MSSQL\BackupC:\Program Files\Microsoft SQL Server\MSSQL16.DASQL\MSSQL\Backup

  5. Then paste the backups



  6. Open SQL management studio



  7. Connect to the instance



  8. Several possibilities to enter in "Server Name" for the connection

    1. SERVER_NAME\INSTANCE_NAME
    2. SERVER_IP\INSTANCE_NAME

  9. After connecting, the following page appears



  10. Left-click on the "+" located next to "Databases"



  11. Right-click on "Databases" then select "Restore Database"



  12. Click on "Device"



  13. Select the three dots "…"



  14. Click on "Add"



  15. Go to the directory:

    C:\Program Files\Microsoft SQL Server\MSSQL16.DASQL\MSSQL\Backup

  16. Choose the first backup file: DA_RSERIES_DATE_TIME.bak



  17. Confirm with "OK".



    Go to the next menu by pressing the button "OK"

  18. On the left-hand side, select “files”:



  19. Toggle [✔️] "Relocate all files to folder"

  20. Click on "OK" to start the restoration of the first database

    The following message appears:



  21. Right-click again on "Databases" and then select "Restore Database"



  22. Choose "Device" again



  23. Then select the three dots "..."



  24. Choose "Add"



  25. Navigate to the following directory:

    C:\Program Files\Microsoft SQL Server\MSSQL16.DASQL\MSSQL\Backup

  26. Select the second backup file: DA_RSERIES_Metrics_DATE_TIME.bak



  27. Confirm with "OK"

  28. Continue by pressing "OK" again



    Proceed to the next menu by using the "OK" button.

  29. On the left-hand side, select Files

  30. Toggle "Relocate all files to folder"

  31. Click on "OK" to start the restoration of the Metrics database

    The following message appears:



  32. Validate with "OK"

  33. On the left menu, the database should appear as follows:

That means the system has been sucesfully migrated and restored.

Step 6

Configure Database Owner on New Server

✍️ NOTE

On Domino Automation, if the following message pops up while opening a project

“Owner of database <project_name> must be ‘TeeDbo’ or another local MSSQL login”

The account “TeeDbo” has to be configured as the DBowner & Enable Broker.

 

  1. Open SQL management studio



  2. Connect to your SQL server’s instance



    1. SERVER_NAME\INSTANCE_NAME
    2. SERVER_IP\INSTANCE_NAME

  3. Right-click, then properties on the <project_name>



  4. Navigate to the “Files” menu



  5. The database owner is blank, select the triple dots […]



  6. Click on “Browse…”



  7. Select “TeeDbo”



  8. Confirm with “OK”

  9. Before validating, click on "Options"



  10. Scroll to the bottom, the "Broker" must be Enabled



  11. Validate through “OK”

    Repeat the same steps for the Metric Database.

  12. Right-click, then select properties on the <project_name_Metrics>



  13. Navigate to the “Files” menu



  14. The database owner is blank, select the triple dots […]



  15. Click on “Browse…”



  16. Select “TeeDbo”



  17. Confirm with “OK”

  18. Before validating, click on "Options"



  19. Scroll to the bottom, the "Broker" must be Enabled

Step 7

Update Server Name in Automation on New Server

  1. Open Domino Automation



  2. The software will load the available projects, select the right project to open then click on "Existing project"



  3. The software loads the project and show the home page



  4. Open the « Network » menu



  5. Click on « Controller services »

  6. If the database comes from another server or machine, you need to enter your machine's DNS name in the "network address"



  7. This information can be found in "Control Panel / System"

  8. Check the "Full computer name" line



  9. After entering the correct machine name, the field is no longer red

  10. Validate with the check mark at the top right



  11. Approve and OK

      >

  12. By navigating through the different menus (for example, "Devices"), it is possible to verify the presence of the configuration of your system:



    The SQL migration was successful.

Attachments

  1. image (1).png
  2. image (10).png
  3. image (100).png
  4. image (101).png
  5. image (102).png
  6. image (103).png
  7. image (104).png
  8. image (105).png
  9. image (106).png
  10. image (107).png
  11. image (108).png
  12. image (109).png
  13. image (11).png
  14. image (110).png
  15. image (111).png
  16. image (112).png
  17. image (113).png
  18. image (114).png
  19. image (115).png
  20. image (116).png
  21. image (117).png
  22. image (118).png
  23. image (119).png
  24. image (12).png
  25. image (120).png
  26. image (121).png
  27. image (122).png
  28. image (123).png
  29. image (124).png
  30. image (125).png
  31. image (126).png
  32. image (127).png
  33. image (128).png
  34. image (129).png
  35. image (13).png
  36. image (130).png
  37. image (131).png
  38. image (132).png
  39. image (133).png
  40. image (134).png
  41. image (135).png
  42. image (136).png
  43. image (137).png
  44. image (138).png
  45. image (139).png
  46. image (14).png
  47. image (140).png
  48. image (141).png
  49. image (142).png
  50. image (143).png
  51. image (144).png
  52. image (145).png
  53. image (146).png
  54. image (147).png
  55. image (148).png
  56. image (149).png
  57. image (15).png
  58. image (150).png
  59. image (151).png
  60. image (152).png
  61. image (153).png
  62. image (154).png
  63. image (155).png
  64. image (156).png
  65. image (157).png
  66. image (158).png
  67. image (159).png
  68. image (16).png
  69. image (160).png
  70. image (161).png
  71. image (162).png
  72. image (163).png
  73. image (164).png
  74. image (165).png
  75. image (166).png
  76. image (167).png
  77. image (168).png
  78. image (169).png
  79. image (17).png
  80. image (170).png
  81. image (171).png
  82. image (179).png
  83. image (18).png
  84. image (181).png
  85. image (185).png
  86. image (188).png
  87. image (19).png
  88. image (20).png
  89. image (21).png
  90. image (22).png
  91. image (23).png
  92. image (24).png
  93. image (25).png
  94. image (26).png
  95. image (28).png
  96. image (29).png
  97. image (32).png
  98. image (33).png
  99. image (34).png
  100. image (36).png
  101. image (45).png
  102. image (46).png
  103. image (5).png
  104. image (52).png
  105. image (53).png
  106. image (54).png
  107. image (55).png
  108. image (57).png
  109. image (58).png
  110. image (60).png
  111. image (62).png
  112. image (65).png
  113. image (66).png
  114. image (68).png
  115. image (7).png
  116. image (70).png
  117. image (71).png
  118. image (73).png
  119. image (74).png
  120. image (76).png
  121. image (77).png
  122. image (78).png
  123. image (79).png
  124. image (80).png
  125. image (81).png
  126. image (82).png
  127. image (84).png
  128. image (85).png
  129. image (86).png
  130. image (87).png
  131. image (88).png
  132. image (9).png
  133. image (90).png
  134. image (91).png
  135. image (93).png
  136. image (95).png
  137. image (96).png
  138. image (97).png
  139. image (98).png
  140. image (99).png