{"id":1696,"date":"2013-09-12T00:00:00","date_gmt":"2013-09-12T00:00:00","guid":{"rendered":"https:\/\/test.simple-talk.com\/uncategorized\/a-practical-guide-to-microsoft-hyper-v-replica-part-ii\/"},"modified":"2021-04-27T13:55:26","modified_gmt":"2021-04-27T13:55:26","slug":"a-practical-guide-to-microsoft-hyper-v-replica-part-ii","status":"publish","type":"post","link":"https:\/\/www.red-gate.com\/simple-talk\/devops\/containers-and-virtualization\/a-practical-guide-to-microsoft-hyper-v-replica-part-ii\/","title":{"rendered":"A Practical Guide to Microsoft Hyper-V Replica: Part II"},"content":{"rendered":"
\n

\tIn Part I<\/a> of this article series, I explained the basic concepts of Microsoft Hyper-V Replica and how to configure a virtual machine for Hyper-V Replication. In this article, I’ll explain the Replication options for a Replica Virtual Machine. <\/p>\n

A Hyper-V Replica installation consists of a primary site where all Hyper-V hosts and the respective Virtual Machines are running. Besides the primary site there’s also a replica site. Hyper-V hosts are also located in this replica site but they contain replicas of virtual machines that are running in the primary site. Every five minutes, the primary site sends information regarding these last five minutes to the replica site where this information is replayed into the Hyper-V Replica.<\/p>\n

Replication Actions on a Replica Virtual Machine<\/h2>\n

\tFor any Replica Virtual Machine participating in the Hyper-V Replica, right-click the machine name to bring up the context menu and view the Replication actions available as shown in the figure 1.19 below: <\/p>\n

\t\"1870-2286bbc0-1b57-4a84-974c-672cd3d8ca4\"<\/strong> <\/p>\n

\tFigure 1.19 – Context Menu of the Replica Virtual Machine on Replica Server <\/p>\n

\t“Failover” <\/strong>and “Test Failover” <\/strong>will be discussed further on in this article. <\/p>\n

\t“Pause Replication<\/strong>” pauses the replication for the Virtual Machine. The status of the Virtual Machine replication will be reflected on the “Replication Health” status page. This action can be performed on the Primary or Replica Server. <\/p>\n

\t“View Replication Health<\/strong>” brings up the following screen which shows the overall status of the Replica Virtual Machine. This action can be performed from the Primary or Replica Server. <\/p>\n

\t“Remove Replication<\/strong>” is used to stop the replication for the Replica Virtual Machine. This action can be performed on the Primary or Replica Server. Stopping the replication for the Virtual Machine does not delete the Virtual Machine and its files from the Replica Server! You must manually delete the files if you need to do so. <\/p>\n

\tHyper-V Failover <\/h2>\n

\tFor any Primary and Replica Virtual Machine in a Hyper-V Replica environment, there are three types of failover operations available. Some of the failover tests can be used for the Primary Virtual Machine and some can be used for Replica Virtual Machine. <\/p>\n

    \n
  • \tTest Failover (TFO) <\/li>\n
  • \tPlanned Failover (PFO) <\/li>\n
  • \tUnplanned Failover (UFO) <\/li>\n<\/ul>\n

    Test Failover (TFO)<\/h3>\n

    \tTest Failover, as the name suggests, can be used to run tests against the Replica Virtual Machine. The “Failover Test” action is executed on the Replica Virtual Machine to ensure that it can come online successfully at the Replica Server in case of a Primary Virtual Machine running on Primary Server disaster. You can initiate a “Test Failover<\/strong>” without impacting the Primary Virtual Machine. <\/p>\n

    \n

    NOTE:<\/strong> The “Test Failover” is same as Windows Failover Cluster’s “Simulate<\/strong>” feature. <\/p>\n<\/p><\/div>\n

    \tThis type of failover can be performed by using the “Test Failover<\/strong>” option located on the Right Click context menu on the Replica Virtual Machine as shown in the Figure 1.20 below. <\/p>\n

    \t\"1870-d3168eb2-0916-4a6f-8464-4896377f38c\"<\/p>\n

    \tFigure 1.20 – “Test Failover” action on Right Click Context Menu of Replica Virtual Machine <\/p>\n

    \tOnce you click “Test Failover<\/strong>“, the next snapshot shows the available recovery points for the Replica Virtual Machine. <\/p>\n

    \t\"1870-7e93c9aa-4dc9-4cba-a743-aec771c0a7a\"<\/p>\n

    \tFigure 1.21 – Available Recovery Points for a Replica Virtual Machine <\/p>\n

    \tThere are following types of recovery points available for your selection: <\/p>\n

      \n
    • \tLatest Recovery Point <\/li>\n
    • \tStandard Replicas (multiple) <\/li>\n
    • \tApplication-Consistent Recovery Point (multiple) <\/li>\n<\/ul>\n

      \t “Latest Recovery Point” is the backup of Primary VHD of the Replica Virtual Machine which will be used to test the failover. <\/p>\n

      \t“Application-Consistent Recovery Point” and “Standard Replicas” are created by the Volume Shadow Copy Service (VSS) based on the interval you specified when configuring this Virtual Machine for replication. <\/p>\n

      What does Test Failover Do?<\/h3>\n

      \tUsing one of the recovery points you selected, the “Test Failover<\/strong>” operation creates a “Test Virtual Machine” on the Replica Server. The new Virtual Machine is appended with a tag “-Test” as shown in the figure 1.23 below. <\/p>\n

      \t\"1870-819c83f6-ff06-4371-acd5-85058642e9d\"<\/strong> <\/p>\n

      \tFigure 1.22 – Test Virtual Machine created by “Test Failover” Action on the Replica Server <\/p>\n

      \tIn fact, “Test Failover” operation uses Hyper-V’s “Export and Import” feature internally to create a new Virtual Machine and then rename it. The “Test Failover” operations include: <\/p>\n

        \n
      1. \tExport the Replica Virtual Machine to a temporary location (XML file, VHD files, etc.) <\/li>\n
      2. \tModify the XML file of exported Virtual Machine to use a unique GUID <\/li>\n
      3. \tRegister the newly created Virtual Machine with Hyper-V (VMMS.exe) <\/li>\n
      4. \tRename the Virtual Machine name <\/li>\n
      5. \tImport the Virtual Machine onto the same Hyper-V server <\/li>\n<\/ol>\n
        \n

        NOTE:<\/strong> The Test Virtual Machine remains OFF after it has been imported successfully, by default, an imported Virtual Machine is not started automatically. <\/p>\n<\/p><\/div>\n

        \tAfter turning Test Virtual Machine (RVM1 – Test in this case) ON and once you are satisfied that it functions properly, you can always delete the test Virtual Machine from the Replica Server. Before you delete the test Virtual Machine, use “Stop Test <\/strong>Failover<\/strong>” action from the Right Click Context menu. This action will clean up the duplicate files (VHD and configuration files) for the test Virtual Machine. <\/p>\n

        \n

        NOTE:<\/strong> You must have enough resources available on the Replica Server in order to start the test Replica Virtual Machine and enough storage for “Test Failover” operation to create\/store VHD files. <\/p>\n<\/p><\/div>\n

        \n\n\n\n
        Tip:<\/strong> <\/td>\nOnly one “Test Failover” operation is allowed at one time for a Replica Virtual Machine. However, you can perform multiple “Test Failover” operations for different Replica Virtual Machines at the same time. <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
        \n\n\n\n
        Tip:<\/strong> <\/td>\nSince the “Test Failover” operation is performed at the Replica Site, there is no impact on the Primary Virtual Machine which continues to serve the client requests. <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

        Planned Failover (PFO)<\/h3>\n

        \tA “Planned Failover<\/strong>” action is available to be performed on the Primary Virtual Machine running on the Primary Server. This action can be performed when you know that Primary Server or Primary Site will go down for some maintenance purpose and you want to move the virtualized workloads to the Replica Server or Replica Site with minimum downtime. This type of failover operation is performed from the Right Click context menu on the Replica Virtual Machine as shown in the Figure 1.23 below. <\/p>\n

        \t\"1870-12cc0322-d356-4832-aa14-4d20906f7e7\"<\/p>\n

        \tFigure 1.23 – “Planned Failover” action on Right Click Context Menu of Primary Virtual Machine <\/p>\n

        \tWhen you click on the “Planned Failover<\/strong>” action, it shows the following screen shown in the Figure 1.24 below: <\/p>\n

        \t\"1870-5f41675f-4a69-4c41-bab7-4f972147d21\"<\/p>\n

        \tFigure 1.24 – “Planned Failover” <\/p>\n

        \tThere are a number of prerequisites checks and actions performed when you click the ‘Fail Over<\/strong>” button located on the above Figure 1.24. Prerequisites include checking to make sure the Primary Virtual Machine is turned off and reverse replication is allowed from Replica to Primary Server. <\/p>\n

        \tThe checkbox “Start the Replica Virtual machine after failover<\/strong>” allows you to turn on the Replica Virtual Machine on the Replica Server. <\/p>\n

        \n

        Note:<\/strong> The “Planned Failover” operation requires manual intervention and must be performed by an administrator. This is similar to Live Migration or Shared-Nothing Live Migration Planned Failover. The only difference is that there will be little downtime in case of “Planned Failover” performed in the Hyper-V Replica environment. <\/p>\n<\/p><\/div>\n

        \tA few actions are performed which are listed in Figure 1.24. <\/p>\n

        \tThe “Primary Virtual Machine” must be turned off and the Primary Server (this server) must be configured to accept the replication from the Replica Server before the planned failover operation can start. If none of the conditions are true, an error message will be displayed as shown in Figure 1.25 below. <\/p>\n

        \t\"1870-d6aaa463-f4c5-4d68-bd2c-8e8bccc51cc\"<\/p>\n

        \tFigure 1.25 – “Planned Failover” Error message for Primary Virtual Machine at Primary Server <\/p>\n

        \tThe following requirements must be met before the “Planned Failover” operation can start: <\/p>\n

          \n
        • \tPrimary Server is configured to accept replication <\/li>\n
        • \tThe Primary Virtual Machine is turned off <\/li>\n<\/ul>\n

          \tUsually, in a Hyper-V Replica environment, it is the Replica Server which accepts replication packets from a Primary Server running in production site but not the vice-versa – in some cases it is required by the Hyper-V Replica to reverse replicate the virtualized workload. The “Reverse Replicate” action requires this type of configuration, this will be touched on again later in this article. <\/p>\n

          \tA “Planned Failover” operation initiated for a Primary Virtual Machine is initiated manually by an administrator. Since it is a “planned event”, Hyper-V Primary Server knows what all actions need to be taken for a Primary Virtual Machine. This is what happens as part of the operation: <\/p>\n

            \n
          1. \tAn administrator initiates the “Planned Failover” action from a Right Click context menu of Primary Virtual Machine <\/li>\n
          2. \tHyper-V server process (VMMS.exe) is notified of the action <\/li>\n
          3. \tVMMS.exe talks to Hyper-V VSS Writer to create a snapshot of the Primary Virtual Machine <\/li>\n
          4. \tHyper-V VSS Writer creates a “Standard Replica” backup copy. <\/li>\n
          5. \tThe Replica Server is notified of the event. <\/li>\n
          6. \t“Standard Replica” backup copy is sent to the Replica Server <\/li>\n
          7. \tThe Replica Server applies the backup copy it has received and starts the Replica Virtual Machine <\/li>\n<\/ol>\n

            \tIn case of a Planned Failover, there is no data loss. Since the Primary Server is informed of the action, it takes the necessary actions on the Primary Virtual Machine ensuring no data loss occurs because they are sent to Replica Server. <\/p>\n

            Unplanned Failover (UFO)<\/h3>\n

            \tThe “Unplanned Failover<\/strong>” operation is performed on the Replica Virtual Machine running on the Replica Server and must be used only if you are experiencing issues with: <\/p>\n

              \n
            • \tPrimary Server alone <\/li>\n
            • \tPrimary Site where the Primary Servers resides <\/li>\n
            • \tPrimary Virtual Machine which cannot be brought online <\/li>\n
            • \tNetwork connectivity issues for the Primary Virtual Machine <\/li>\n<\/ul>\n

              \tThe objective of performing the unplanned failover action is to resume the services at the Replica Site as soon as possible. <\/p>\n

              \n

              Note:<\/strong> “Unplanned Failover” operation is unplanned and occurs without your notice. <\/p>\n<\/p><\/div>\n

              \tUnplanned Failover appears as the “Failover<\/strong>” action on the Right Click Context Menu of the Replica Virtual Machine as shown in the below figure 1.26. <\/p>\n

              \t\"1870-9307140b-8908-42eb-bd38-ab73cd1fd7e\"<\/p>\n

              \tFigure 1.26 – “Failover” (unplanned failover) Action on Right Click Context Menu Of Virtual Machine <\/p>\n

              \n\n\n\n
              Tip:<\/strong> <\/td>\n“Failover”, “Cancel Failover” and “Reverse Replication” actions are related to each other which are explained in this section. <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

              \tClicking the “Failover” button brings up the following screen: <\/p>\n

              \t\"1870-b6a1f16d-9514-43d1-81cc-3d8327ea894\"<\/p>\n

              \tFigure 1.27 – Selecting Recovery Points for Virtual Machine <\/p>\n

              \tFailover allows you to select the recovery point if you enabled for the Primary Virtual Machine. <\/p>\n

              \n\n\n\n
              Tip:<\/strong> <\/td>\nAlways select the latest recovery point from the drop down list to restore the Replica Virtual Machine from a latest recovery point. <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

              Planned vs Unplanned Failover Types<\/h3>\n

              \tIn the case of a “Planned Failover”, the Hyper-V Primary Server is notified of the operation\/action so it takes necessary actions for the primary Virtual Machine. On the other hand, “Unplanned Failover”, which is performed at the Replica Server, does not provide any notification to the Replica Server. <\/p>\n

              \tIf the Replica Server is notified of a failure on the Primary VM, then there’s no difference between Hyper-V Replica and Windows Failover Clustering. <\/p>\n

              \tSince the Replica Server is not notified of any issues with the Primary Virtual Machine in an unplanned failover, it maintains a list of recovery points or backup copies you can choose to recover the Virtual Machine to resume its services. <\/p>\n

              \tAn “Unplanned Failover” must be performed only when one of the following conditions is true: <\/p>\n

                \n
              • \tThe Primary Site is experiencing some issues and cannot be contacted. <\/li>\n
              • \tClients cannot connect to the Primary Virtual Machine and you need to restore the services as soon as possible on the Replica Virtual Machine running on Replica Server. <\/li>\n<\/ul>\n
                \n

                Note:<\/strong> The Primary Virtual Machine at Primary Server site must be turned off before you can use the “Unplanned Failover”. <\/p>\n<\/p><\/div>\n

                \n\n\n\n
                Tip:<\/strong> <\/td>\nAny test Replica Virtual Machine, created by the “Test Failover” action, will be deleted when you use “Failover” action on the Replica Virtual Machine. <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n
                \n\n\n\n
                Tip:<\/strong> <\/td>\nThere is no need to turn on the Replica Virtual Machine on Replica Server as the Failover operation will automatically turn it on. <\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

                Cancel Failover and Reverse Replication<\/h3>\n

                \t“Cancel Failover<\/strong>” and ‘Reverse Replication<\/strong>” actions are available on the Replica Virtual Machine on which you initiated the “Failover” action. These two actions are shown in the below Figure 1.28. <\/p>\n

                \t\"1870-0e40092e-b10a-47ad-aacb-41ae17c7dd8\"<\/p>\n

                \tFigure 1.28 – “Cancel Failover” and “Reverse Replication” options for Virtual Machine <\/p>\n

                \t“Cancel Failover<\/strong>” action allows you to cancel the failover and turn off the Replica Virtual Machine. The “Cancel Failover<\/strong>” action is created in a situation where a Replica Virtual Machine restored from a recovery point is not working normally. You can always initiate the “Cancel Failover” action to revert back the changes and then start over with a different recovery backup copy this time. <\/p>\n

                \t“Reverse Replication<\/strong>” is a manual failback option provided with Replica Virtual Machine! You may wonder; Why not have automatic failback<\/em>? Well, Hyper-V Replica is a disaster recovery solution and not a high availability solution. Microsoft may develop further the Hyper-V Replica components in the next few years to provide the failback functionality but it is not implemented in the current version of Hyper-V Replica. <\/p>\n

                \t“Reverse Replication<\/strong>” action just allows you to failback the load from Replica Server to Primary Server. Clicking on the “Reverse Replication<\/strong>” brings the following screen as shown in the figure 1.29 below: <\/p>\n

                \t\"1870-d5e7969a-6c4b-4b4c-8c56-32ecbd897cb\"<\/p>\n

                \tFigure 1.29 – “Reverse Replication” wizard <\/p>\n

                \tAs stated in figure 1.29, this is the same wizard which you used to enable a Virtual Machine for replication earlier in this article. The configuration pages provided in this wizard are similar to those when you enable a Virtual Machine to participate in the Hyper-V Replica. <\/p>\n

                \tThe wizard checks to see if the destination server is able to accept the incoming replication traffic generated from this server and this is where it is required for Primary Server to become a Replica Server. <\/p>\n

                \n

                Note:<\/strong> “Planned Failover” and “Reverse Replication” actions can be performed only if Primary Server is allowed to accept incoming replication requests. <\/p>\n<\/p><\/div>\n

                \tYou might want to remove all the recovery points associated with a Replica Virtual Machine. You would want to do that if recovery points are corrupted or you just don’t need them. To remove all the recovery points, select “Remove Recovery Points<\/strong>” action, as shown on the Right Click menu in Figure 1.29 above. When you click this action, a warning message will be displayed which requires your confirmation before recovery points associated with this Replica Virtual Machine can be removed from the local disk. <\/p>\n

                \t\"1870-97071dfb-3bd3-4d41-8cca-fe1f79b18e4\"<\/p>\n

                Figure 1.30 – “Remove recovery points” confirmation message <\/p>\n

                Recovery Points for a Replica Virtual Machine can be removed only if the Virtual Machine has been failed over using “Failover” action. The “Remove Recovery Points” action does not provide you a list of available recovery points rather it deletes all the recovery points associated with this Virtual Machine at a time. <\/p>\n

                \tAs suggested in the Figure above, “Cancel Failover” option will no longer be available on the Right Click Context Menu if all recovery points are deleted. <\/p>\n

                \n\n\n\n
                Tip:<\/strong> <\/td>\nRemove recovery points for a Virtual Machine if you want to start over or if you think there is no use of all the recovery points of a Virtual Machine.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

                \tTo summarize, the following actions are available on the Right Click Context Menu of Primary and Replica Virtual Machines: <\/p>\n\n\n\n\n\n\n\n\n\n\n\n
                \n

                \t\tRight Click Context Menu Actions<\/strong><\/p>\n<\/td>\n

                		\n

                \t\tAvailable On Replica Virtual Machine<\/strong><\/p>\n<\/td>\n

                		\n

                \t\tAvailable on Primary Virtual Machine<\/strong><\/p>\n<\/td>\n

                		\n

                \t\tDescription<\/strong><\/p>\n<\/td>\n<\/tr>\n

                \n

                Test Failover<\/p>\n<\/td>\n

                		\n

                \t\tYes<\/p>\n<\/td>\n

                		\n

                \t\t \t\tNo<\/p>\n<\/td>\n

                		\n

                \t\t \t\tTest to see if Replica Virtual Machine can come online successfully at \t\tDR site. Creates a test virtual machine at the DR site.<\/p>\n<\/td>\n<\/tr>\n

                \n

                \t\tPlanned Failover<\/p>\n<\/td>\n

                		\n

                \t\tNo<\/p>\n<\/td>\n

                		\n

                \t\tYes<\/p>\n<\/td>\n

                		\n

                \t\tUsed to failover from Primary to Replica Server<\/p>\n<\/td>\n<\/tr>\n

                \n

                \t\tPause\/Resume Replication<\/p>\n<\/td>\n

                		\n

                \t \t\tYes<\/p>\n<\/td>\n

                		\n

                \t\t \t\tYes<\/p>\n<\/td>\n

                		\n

                \t\t \t\tPause or Resume Replication for Virtual Machine<\/p>\n<\/td>\n<\/tr>\n

                \n

                \t\tView Replication Health<\/p>\n<\/td>\n

                		\n

                \t\tYes<\/p>\n<\/td>\n

                		\n

                \t\tYes<\/p>\n<\/td>\n

                		\n

                \t\tShows replication health of the Virtual Machine<\/p>\n<\/td>\n<\/tr>\n

                \n

                \t\tRemove Replication<\/p>\n<\/td>\n

                		\n

                \t \t\tYes<\/p>\n<\/td>\n

                		\n

                \t \t\tYes<\/p>\n<\/td>\n

                		\n

                \t \t\tRemove replication for Virtual Machine<\/p>\n<\/td>\n<\/tr>\n

                \n

                \t\tReverse Replication<\/p>\n<\/td>\n

                		\n

                \t\tYes<<\/p>\n<\/td>\n

                		\n

                \t\tNo<\/p>\n<\/td>\n

                		\n

                \t\tUsed to \t\treverse replicate from Replica to Primary Server<\/p>\n<\/td>\n<\/tr>\n

                \n

                \t\tCancel Failover<\/p>\n<\/td>\n

                		\n

                \t\t \t\tYes<\/p>\n<\/td>\n

                		\n

                \t\t \t\tNo<\/p>\n<\/td>\n

                		\n

                \t\t \t\tUsed to cancel the failover operation<\/p>\n<\/td>\n<\/tr>\n

                \n

                \t\tRemove Replication Points<\/p>\n<\/td>\n

                		\n

                \t\tYes<\/p>\n<\/td>\n

                		\n

                No<\/p>\n<\/td>\n

                		\n

                \t\tThis Action \t\tcan be used to remove all Recovery Points<\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

                \tTable 1.0 – Right Click Context Menu Actions <\/p>\n

                \tConclusion <\/h2>\n

                \tIn the final part of this article series, we learned the actions available on Right Click context menu on Virtual Machines. I also covered the different types of failover available in Hyper-V Replica environment and what they do when recovering a virtual machine. <\/p>\n<\/p><\/div>\n","protected":false},"excerpt":{"rendered":"

                A Hyper-V replica installation provides rapid disaster-recovery by asynchronously replicating a VM running at a primary site to a replica site. Know how to prepare for something to go wrong at the Primary Server\/Site? In this article Nirmal Sharma presents the Replication options for a Replica Virtual Machine with a focus on Hyper-V Failover.
                \n…<\/p>\n","protected":false},"author":143880,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[143513],"tags":[5892,4908,4286,4871,5893,4907],"coauthors":[],"class_list":["post-1696","post","type-post","status-publish","format-standard","hentry","category-containers-and-virtualization","tag-failover","tag-hyper-v","tag-replication","tag-sysadmin","tag-virtual-machine","tag-virtualization"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/1696","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/users\/143880"}],"replies":[{"embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/comments?post=1696"}],"version-history":[{"count":2,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/1696\/revisions"}],"predecessor-version":[{"id":90750,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/posts\/1696\/revisions\/90750"}],"wp:attachment":[{"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/media?parent=1696"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/categories?post=1696"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/tags?post=1696"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.red-gate.com\/simple-talk\/wp-json\/wp\/v2\/coauthors?post=1696"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}