{"id":12147,"date":"2012-03-05T19:23:12","date_gmt":"2012-03-05T19:23:12","guid":{"rendered":"https:\/\/aidanfinn.com\/?p=12147"},"modified":"2012-03-05T19:23:12","modified_gmt":"2012-03-05T19:23:12","slug":"windows-server-8-hyper-v-replica","status":"publish","type":"post","link":"https:\/\/aidanfinn.com\/?p=12147","title":{"rendered":"Windows Server 2012 Hyper-V Replica &#8230; In Detail"},"content":{"rendered":"<p><a href=\"http:\/\/www.amazon.com\/Windows-Server-Hyper-V-Installation-Configuration\/dp\/1118486498%3FSubscriptionId%3DAKIAIJ5WNI7ZSH7W4OXA%26tag%3Dafm0c-20%26linkCode%3Dxm2%26camp%3D2025%26creative%3D165953%26creativeASIN%3D1118486498\"><\/a>If you asked me to pick the killer feature of WS2012 Hyper-V, then Replica would be high if not at the top of my list (64 TB VHDX is right up there in the competition).\u00a0 In Ireland, and we\u2019re probably not all that different from everywhere else, the majority of companies are in the small\/medium enterprise (SME) space and the vast majority of my customers work exclusively in this space.\u00a0 I\u2019ve seen how DR is a challenge to enterprises and to the SMEs alike.\u00a0 It is expensive and it is difficult.\u00a0 Those are challenges an enterprise can overcome by spending, but that\u2019s not the case for the SME.<\/p>\n<p>Virtualisation should help.\u00a0 Hardware consolidation reduces the cost, but the cost of replication is still there.\u00a0 SAN\u2019s often need licenses to replicate.\u00a0 SAN\u2019s are normally outside of the reach of the SME and even the corporate regional\/branch office.\u00a0 Software replication which is aimed at this space is not cheap either, and to be honest, some of them are more risky than the threat of disaster.\u00a0 And let\u2019s not forget the bandwidth that these two types of solution can require.<\/p>\n<p><strong><span style=\"text-decoration: underline;\">Isn\u2019t DR Just An Enterprise Thing?<\/span><\/strong><\/p>\n<p>So if virtualisation mobility and the encapsulation of a machine as a bunch of files can help, what can be done to make DR replication a possibility for the SME?<\/p>\n<p>Enter Replica (Hyper-V Replica), a built-in software based asynchronous replication mechanism that has been designed to solve these problems.\u00a0 This is what Microsoft envisioned for Replica:<\/p>\n<ul>\n<li>If you need to replicate dozens or hundreds of VMs then you should be using a SAN and SAN replication.\u00a0 Replica is not for the medium\/enterprise sites.<\/li>\n<li>Smaller branch offices or regional offices that need to replicate to local or central (head office or HQ data centre) DR sites.<\/li>\n<li>SME\u2019s who want to replicate to another office.<\/li>\n<li>Microsoft partners or hosting companies that want to offer a service where SME\u2019s could configure important Windows Server 2012 Hyper-V host VMs to replicate to their data centre \u2013 basically a hosted DR service for SMEs.\u00a0 Requirements of this is that it must have Internet friendly authentication (not Kerberos) and it must be hardware independent, i.e. the production site storage can be nothing like the replica storage.<\/li>\n<li>Most crucially of all: limited bandwidth.\u00a0 Replica is designed to be used on commercially available broadband without impacting normal email or browsing activity \u2013 Microsoft does also want to sell them Office 365, after all <img decoding=\"async\" class=\"wlEmoticon wlEmoticon-smile\" style=\"border-style: none;\" src=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2012\/03\/wlEmoticon-smile2.png\" alt=\"Smile\" \/> How much bandwidth will you need?\u00a0 How long is a piece of string?\u00a0 Your best bet is to measure how much change there is to your customers VMs every 5 minutes and that\u2019ll give you an idea of what bandwidth you\u2019ll need.<\/li>\n<\/ul>\n<p><img loading=\"lazy\" decoding=\"async\" style=\"display: block; float: none; margin-left: auto; margin-right: auto;\" src=\"http:\/\/i.technet.microsoft.com\/dynimg\/IC564317.jpg\" alt=\"Figure 1  Replicate virtual machines\" width=\"500\" height=\"194\" \/><\/p>\n<p>In short, Replica is designed and aimed at the ordinary business that makes up 95% of the market, and it\u2019s designed to be easy to set up and invoke.<\/p>\n<p><strong><span style=\"text-decoration: underline;\">What Hyper-V Replica Is Not Intended To Do<\/span><\/strong><\/p>\n<p>I know some people are thinking of this next scenario, and the Hyper-V product group anticipated this too.\u00a0 Some people will look at Hyper-V Replica and see it as a way to provide an alternative to clustered Hyper-V hosts in a single site.\u00a0 Although Hyper-V Replica could do this, it is not intended for for this purpose.<\/p>\n<p>The replication is designed for low bandwidth, high latency networks that the SME is likely to use in inter-site replication.\u00a0 As you\u2019ll see later, there will be a delay between data being written on host\/cluster A and being replicated to host\/cluster B.<\/p>\n<p>You can use Hyper-V Replica within a site for DR, but that\u2019s all it is: DR.\u00a0 It is not a cluster where you fail stuff back and forth for maintenance windows \u2013 although you probably could shut down VMs for an hour before flipping over \u2013 <strong><em><span style=\"text-decoration: underline;\">maybe<\/span><\/em><\/strong> &#8211; but then it would be quicker to put them in a saved state on the original host, do the work, and reboot without failing over to the replica.<\/p>\n<p><strong><span style=\"text-decoration: underline;\">How It Works<\/span><\/strong><\/p>\n<p>I describe Hyper-V Replica as being a storage log based asynchronous disaster recovery replication mechanism.\u00a0 That\u2019s all you need to know \u2026<\/p>\n<p>But let\u2019s get deeper <img decoding=\"async\" class=\"wlEmoticon wlEmoticon-smile\" style=\"border-style: none;\" src=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2012\/03\/wlEmoticon-smile2.png\" alt=\"Smile\" \/><\/p>\n<p><strong><span style=\"text-decoration: underline;\">How Replication Works<\/span><\/strong><\/p>\n<p>Once Replica is enabled, the source host starts to maintain a HRL (Hyper-V Replica Log file) for the VHDs.\u00a0 Every 1 write by the VM = 1 write to VHD and 1 write to the HRL.\u00a0 Ideally, and this depends on bandwidth availability, this log file is replayed to the replica VHD on the replica host every 5 minutes.\u00a0 This is not configurable.\u00a0 Some people are going to see the VSS snapshot (more later) timings and get confused by this, but the HRL replay should happen every 5 minutes, no matter what.<\/p>\n<p>The HRL replay mechanism is actually quite clever; it replays the log file in reverse order, and this allows it only to store the latest writes.\u00a0 In other words, it is asynchronous (able to deal with long distances and high latency by write in site A and later write in site B) and it replicates just the changes.<\/p>\n<p>Note: I love stuff like this.\u00a0 Simple, but clever, techniques that simplify and improve otherwise complex tasks.\u00a0 I guess that\u2019s why Microsoft allegedly ask job candidates why manhole covers are circular <img decoding=\"async\" class=\"wlEmoticon wlEmoticon-smile\" style=\"border-style: none;\" src=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2012\/03\/wlEmoticon-smile2.png\" alt=\"Smile\" \/><\/p>\n<p>As I said, replication or replay of the HRL will normally take place every 5 minutes.\u00a0 That means if a source site goes offline then you\u2019ll lose anywhere from 1 second to nearly 10 minutes of data.<\/p>\n<p>I did say \u201cnormally take place every 5 minutes\u201d.\u00a0 Sometimes the bandwidth won\u2019t be there.\u00a0 Hyper-V Replica can tolerate this.\u00a0 After 5 minutes, if the replay hasn\u2019t happened then you get an alert.\u00a0 The HRL replay will have another 25 minutes (up to 30 completely including the 5) to complete before going into a failed state where human intervention will be required.\u00a0 This now means that with replication working, a business could lose between 1 second and nearly 1 hour of data.<\/p>\n<p>Most organisations would actually be very happy with this. Novices to DR will proclaim that they want 0 data loss. OK; that is achievable with EUR100,000 SANs and dark fibre networks over short distances. Once the budget face smack has been dealt, Hyper-V Replica becomes <em>very, very<\/em> attractive.<\/p>\n<p>That\u2019s the Recovery Point Objective (RPO \u2013 amount of time\/data lost) dealt with.\u00a0 What about the Recovery Time Objective (RTO \u2013 how long it takes to recover)?\u00a0 Hyper-V Replica does not have a heartbeat.\u00a0 There is not automatic failover.\u00a0 There\u2019s a good reason for this.\u00a0 Replica is designed for commercially available broadband that is used by SMEs.\u00a0 This is often phone network based and these networks have brief outages.\u00a0 The last thing an SME needs is for their VMs to automatically come online in the DR site during one of these 10 minute outages.\u00a0 Enterprises avoid this split brain by using witness sites and an independent triangle of WAN connections.\u00a0 Fantastic, but well out of the reach of the SME.\u00a0 Therefore, Replica will require manual failover of VMs in the DR site, either by the SME\u2019s employees or by a NOC engineer in the hosting company.\u00a0 You could simplify\/orchestrate this using PowerShell or System Center Orchestrator.\u00a0 The RTO will be short but have implementation specific variables: how long does it take to start up your VMs and for their guest operating systems\/applications to start?\u00a0 How long will it take for you to get your VDI\/RDS session hosts (for remote access to applications) up, running and accepting user connections?\u00a0 I\u2019d reckon this should be very quick, and much better with the 4-24 hours that many enterprises aim for.\u00a0 I\u2019m chuckling as I type this; the Hyper-V group is giving SMEs a better DR solution than most of the Fortune 1000\u2019s can realistically achieve with oodles of money to spend on networks and storage replication, regardless of virtualisation products.<\/p>\n<p>A common question I expect: there is no Hyper-V integration component for Replica.\u00a0 This mechanism works at the storage level, where Hyper-V is intercepting and logging storage activity.<\/p>\n<p><strong><span style=\"text-decoration: underline;\">Replica and Hyper-V Clusters<\/span><\/strong><\/p>\n<p>Hyper-V Replica works with clusters.\u00a0 In fact you can do the following replications:<\/p>\n<ul>\n<li>Standalone host to cluster<\/li>\n<li>Cluster to cluster<\/li>\n<li>Cluster to standalone host<\/li>\n<\/ul>\n<p>The tricky thing is the configuration replication and smooth delegation of replication (even with Live Migration and failover) of HA VMs on a cluster.\u00a0 How can this be done?\u00a0 You can enable a HA role called a Hyper-V Replica Broker on a cluster (once only).\u00a0 This is where you can configure replication, authentication, etc, and the Broker replicates this data out to cluster nodes.\u00a0 Replica settings for VMs will travel with them, and the broker ensures smooth replication from that point on.<\/p>\n<p><strong><span style=\"text-decoration: underline;\">Configuring Hyper-V Replica<\/span><\/strong><\/p>\n<p>I don\u2019t have my lab up and running yet, but there are already many step-by-step posts out there.\u00a0 I wanted to focus on the how it works and why to use it.\u00a0 But here are the fundamentals:<\/p>\n<p>On the replica host\/cluster, you need to enable Hyper-V Replica.\u00a0 Here you can control what hosts (or all) can replicate to this host\/cluster.\u00a0 You can do things like have one storage path for all replicas, or creating individual policies based on source FQDN such as storage paths or enabling\/pausing\/disabling replication.<\/p>\n<p>You do not need to enable Hyper-V Replica on the source host.\u00a0 Instead, you configure replication for each required VM.\u00a0 This includes things like:<\/p>\n<ul>\n<li>Authentication: HTTP (Kerberos) within the AD forest, or HTTPS (destination provided SSL certificate) for inter-forest (or hosted) replication.<\/li>\n<li>Select VHDs to replicate<\/li>\n<li>Destination<\/li>\n<li>Compressing data transfer: with a CPU cost for the source host.<\/li>\n<li>Enable VSS once per hour: for apps requiring consistency \u2013 not normally required because of the logging nature of Replica and it does cause additional load on the source host<\/li>\n<li>Configure the number of replicas to retain on the destination host\/cluster: Hyper-V Replica will automatically retain X historical copies of a VM on the destination site.\u00a0 These are actually Hyper-V snapshots on the destination copy of the VM that are automatically created\/merged (remember we have hot-merge of the AVHD in Windows 8) with the obvious cost of storage.\u00a0 There is some question here regarding application support of Hyper-V snapshots and this feature.<\/li>\n<\/ul>\n<p><strong><span style=\"text-decoration: underline;\">Initial Replication Method<\/span><\/strong><\/p>\n<p>I\u2019ve worked in the online backup business before and know how difficult the first copy over the wire is.\u00a0 The SME may have small changes to replicate but might have TBs of data to copy on the first synchronisation.\u00a0 How do you get that data over the wire?<\/p>\n<ul>\n<li>Over-the-wire copy: fine for a LAN, if you have lots of bandwidth to burn, or if you like being screamed at by the boss\/customer.\u00a0 You can schedule this to <em>start<\/em> at a certain time.<\/li>\n<li>Offline media: You can copy the source VMs to some offline media, and import it to the replica site.\u00a0 Please remember to encrypt this media in case it is stolen\/lost (BitLocker-To-Go), and then erase (not format) it afterwards (DBAN).\u00a0 There might be scope for an R2\/Windows 9 release to include this as part of a process wizard.\u00a0 I see this being the primary method that will be used.\u00a0 Be careful: there is no time out for this option.\u00a0 The HRL on the source site will grow and grow until the process is completed (at the destination site by importing the offline copy).\u00a0 You can delete the HRLs without losing data \u2013 it is not like a Hyper-V snapshot (checkpoint) AVHD.<\/li>\n<li>Use a seed VM on the destination site: Be very very careful with this option.\u00a0 I really see it as being a great one for causing calls to MSFT product support.\u00a0 This is intended for when you can restore a copy of the VM in the DR site, and it will be used in a differencing mechanism where the differences will be merged to create the synch.\u00a0 This is not to be used with a template or similar VMs.\u00a0 It is meant to be used with a restored copy of the same VM with the same VM ID.\u00a0 You have been warned.<\/li>\n<\/ul>\n<p>And that\u2019s it.\u00a0 Check out the social media and you\u2019ll see how easy people are saying Hyper-V Replica is to set up and use.\u00a0 All you need to do now is check out the status of Hyper-V Replica in the Hyper-V Management Console, Event Viewer (Hyper-V Replica log data using the Microsoft-Windows-Hyper-V-VMMSAdmin log), and maybe even monitor it when there\u2019s an updated management pack for System Center Operations Manager.<\/p>\n<p><strong><span style=\"text-decoration: underline;\">Failover<\/span><\/strong><\/p>\n<p>I said earlier that failover is manual.\u00a0 There are two scenarios:<\/p>\n<li>Planned: You are either testing the invocation process or the original site is running but unavailable.\u00a0 In this case, the VMs start in the DR site, there is guaranteed zero data loss, and the replication policy is reversed so that changes in the DR site are replicated to the now offline VMs in the primary site.<\/li>\n<li>Unplanned: The primary site is assumed offline.\u00a0 The VMs start in the DR site and replication <em>is not reversed. <\/em>In fact, the policy is broken.\u00a0 To get back to the primary site, you will have to reconfigure replication.<strong><span style=\"text-decoration: underline;\">Can I Dispense With Backup?<\/span><\/strong>No, and I\u2019m not saying that as the employee of a distributor that sells two competing backup products for this market.\u00a0 Replication is just that, replication.\u00a0 Even with the historical copies (Hyper-V snapshots) that can be retained on the destination site, we do not have a backup with <em>any<\/em> replication mechanism.\u00a0 You must still do a backup, as I previously <a href=\"https:\/\/aidanfinn.com\/?p=11419\" target=\"_blank\">blogged<\/a>, and you should have offsite storage of the backup.Many will continue to do off-site storage of tapes or USB disks.\u00a0 If your disaster affects the area, e.g. a flood, then how exactly will that tape or USB disk get to your DR site if you need to restore data?\u00a0 I\u2019d suggest you look at backup replication, such as what you can get from DPM:<img loading=\"lazy\" decoding=\"async\" style=\"display: block; float: none; margin-left: auto; margin-right: auto;\" src=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2011\/07\/image16.png\" alt=\"\" width=\"500\" height=\"219\" \/>\n<p>&nbsp;<\/p>\n<p><strong><span style=\"text-decoration: underline;\">The Big Question: How Much Bandwidth Do I Need?<\/span><\/strong><\/li>\n<p>Ah, if I knew the answer to that question for every implementation then I\u2019d know many answers to many such questions and be a very rich man, travelling the world in First Class.\u00a0 But I am not.<\/p>\n<p>There\u2019s a sizing process that you will have to do.\u00a0 Remember that once the initial synchronisation is done, only changes are replayed across the wire.\u00a0 In fact, it\u2019s only the final resultant changes of the last 5 minutes that are replayed.\u00a0 We can guestimate what this amount will be using approaches such as these:<\/p>\n<ul>\n<li>Set up a proof of concept with a temporary Hyper-V host in the client site and monitor the link between the source and replica: There\u2019s some cost to this but it will be very accurate if monitored over a typical week.<\/li>\n<li>Do some work with incremental backups: Incremental backups, taken over a day, show how much change is done to a VM in a day.<\/li>\n<li>Maybe use some differencing tool: but this could have negative impacts.<\/li>\n<\/ul>\n<p>Some traps to watch out for on the bandwidth side:<\/p>\n<ul>\n<li>Asynchronous broadband (ADSL):\u00a0 The customer claims to have an 8 Mbps line but in reality it is 7 Mbps down and 300kbps up.\u00a0 It\u2019s the uplink that is the bottleneck because you are sending data up the wire.\u00a0 Most SME\u2019s aren\u2019t going to need all that much.\u00a0 My experience with online backup verifies that, especially if compression is turned on (will consume source host CPU).<\/li>\n<li>How much bandwidth is actually available: monitor the customer\u2019s line to tell how much of the bandwidth is being consumed or not by existing services.\u00a0 Just because they have a functional 500 kbps upload, it doesn\u2019t mean that they aren\u2019t already using it.<\/li>\n<\/ul>\n<p><strong><span style=\"text-decoration: underline;\">Very Useful Suggestion<\/span><\/strong><\/p>\n<p>Think about your servers for a moment.\u00a0 What\u2019s the one file that has the most write activity?\u00a0 It is probably the paging file.\u00a0 Do you really want to replicate it from site A to site B, needlessly hammering the wire?<\/p>\n<p>Hyper-V Replica works by intercepting writes to VHDs.\u00a0 It has no idea of what\u2019s inside the files.\u00a0 You can\u2019t just filter out the paging file.\u00a0 So the excellent suggestion from the Hyper-V product group is to place the paging file of each VM onto a different VHD, e.g. a SCSI attached D drive.\u00a0 Do not select this drive for replication.\u00a0 When the VMs are failed over, they\u2019ll still function without the paging file, just not as well.\u00a0 You can always add one after if the disaster is sustained.\u00a0 The benefit is that you won\u2019t needlessly replicate paging file changes from the primary site to the DR.<\/p>\n<p><strong><span style=\"text-decoration: underline;\">Summary<\/span><\/strong><\/p>\n<p>I love this feature because it solves a real problem that the majority of businesses face.\u00a0 It is further proof that Hyper-V is the best value virtualisation solution out there.\u00a0 I really do think it could give many Microsoft Partners a way to offer a new multi-tenant business offering to further reduce the costs of DR.<\/p>\n<p>EDIT:<\/p>\n<p>I have since <a href=\"https:\/\/aidanfinn.com\/?p=12286\" target=\"_blank\">posted <\/a>a demo video of Hyper-V Replica in action, and I have written a <a href=\"http:\/\/www.zdnet.com\/blog\/microsoft\/one-of-windows-server-2012s-secret-weapons-hyper-v-replica\/12707\">guest post<\/a> on Mary Jo Foley&#8217;s blog.<\/p>\n<p>EDIT2:<\/p>\n<p>I have written around 45 pages of text (in Word format) on the subject of Hyper-V Replica for a chapter in the <a onclick=\"javascript:_gaq.push(['_trackEvent','outbound-article','http:\/\/www.amazon.com']);\" href=\"http:\/\/www.amazon.com\/Windows-Server-Hyper-V-Installation-Configuration\/dp\/1118486498%3FSubscriptionId%3DAKIAIJ5WNI7ZSH7W4OXA%26tag%3Dafm0c-20%26linkCode%3Dxm2%26camp%3D2025%26creative%3D165953%26creativeASIN%3D1118486498\" target=\"_blank\">Windows Server 2012 Hyper-V Installation and Configuration Guide<\/a> book. It goes into great depth and has lots of examples. The book should be out Feb\/March of 2013 and you can pre-order it now:<\/p>\n<p><a href=\"http:\/\/www.amazon.com\/Windows-Server-Hyper-V-Installation-Configuration\/dp\/1118486498%3FSubscriptionId%3DAKIAIJ5WNI7ZSH7W4OXA%26tag%3Dafm0c-20%26linkCode%3Dxm2%26camp%3D2025%26creative%3D165953%26creativeASIN%3D1118486498\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter\" src=\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2012\/09\/image_thumb19.png\" alt=\"\" width=\"196\" height=\"244\" \/><\/a><\/p>\n<div id=\"scid:0767317B-992E-4b12-91E0-4F059A8CECA8:f14c0d01-47af-493f-90c8-75a8b5dd5527\" class=\"wlWriterEditableSmartContent\" style=\"margin: 0px; display: inline; float: none; padding: 0px;\">Technorati Tags: <a rel=\"tag\" href=\"http:\/\/technorati.com\/tags\/DR\">DR<\/a>,<a rel=\"tag\" href=\"http:\/\/technorati.com\/tags\/Windows+Server+2012\">Windows Server 2012<\/a>,<a rel=\"tag\" href=\"http:\/\/technorati.com\/tags\/Hyper-V\">Hyper-V<\/a>,<a rel=\"tag\" href=\"http:\/\/technorati.com\/tags\/Virtualisation\">Virtualisation<\/a>,<a rel=\"tag\" href=\"http:\/\/technorati.com\/tags\/System+Center\">System Center<\/a>,<a rel=\"tag\" href=\"http:\/\/technorati.com\/tags\/DPM\">DPM<\/a><\/div>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>If you asked me to pick the killer feature of WS2012 Hyper-V, then Replica would be high if not at the top of my list (64 TB VHDX is right up there in the competition).\u00a0 In Ireland, and we\u2019re probably not all that different from everywhere else, the majority of companies are in the small\/medium &hellip; <a href=\"https:\/\/aidanfinn.com\/?p=12147\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Windows Server 2012 Hyper-V Replica &#8230; In Detail&#8221;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[20],"tags":[175,61,181,193,195,118],"class_list":["post-12147","post","type-post","status-publish","format-standard","hentry","category-hyper-v","tag-dpm","tag-dr","tag-hyper-v","tag-system-center","tag-virtualisation","tag-windows-server-2012"],"aioseo_notices":[],"jetpack_featured_media_url":"","amp_enabled":true,"_links":{"self":[{"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/posts\/12147","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=12147"}],"version-history":[{"count":0,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=\/wp\/v2\/posts\/12147\/revisions"}],"wp:attachment":[{"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=12147"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=12147"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aidanfinn.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=12147"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}