{"id":2403,"date":"2026-02-07T21:34:38","date_gmt":"2026-02-07T21:34:38","guid":{"rendered":"https:\/\/ssblog.eu.enginyr.ing\/?p=2403"},"modified":"2026-02-07T21:47:38","modified_gmt":"2026-02-07T21:47:38","slug":"migrare-de-la-shared-hosting-la-vps-ghidul-zero-downtime-pas-cu-pas","status":"publish","type":"post","link":"https:\/\/www.serverspan.ro\/blog\/migrare-de-la-shared-hosting-la-vps-ghidul-zero-downtime-pas-cu-pas\/","title":{"rendered":"Migrare de la shared hosting la VPS: Ghidul &#8220;Zero Downtime&#8221; (pas cu pas)"},"content":{"rendered":"\n<h2 class=\"wp-block-heading\">&#8220;Frica de schimbare&#8221; te cost\u0103 bani<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cen industria de hosting, noi numim fenomenul \u0103sta &#8220;Vendor Lock-in pe baz\u0103 de fric\u0103&#8221;. Vedem proprietari de afaceri bloca\u021bi \u00een <a href=\"https:\/\/www.serverspan.ro\/blog\/cum-sa-alegi-un-plan-vps-pentru-un-site-web-o-lista-simpla-de-verificare-pentru-dimensionare\/\">planuri de shared hosting de 5\u20ac\/lun\u0103<\/a> care &#8220;crap\u0103&#8221; de fiecare dat\u0103 c\u00e2nd trimit un newsletter. Ei \u0219tiu c\u0103 au nevoie de un <strong>Server VPS<\/strong>. \u0218tiu c\u0103 <a href=\"https:\/\/www.serverspan.ro\/blog\/realitatea-tichetelor-de-tip-serverul-meu-merge-greu\/\">site-ul se mi\u0219c\u0103 \u00een reluare<\/a>. Dar sunt \u00eengrozi\u021bi de ideea c\u0103 mutarea pe un server nou \u00eenseamn\u0103 48 de ore de erori &#8220;Site Not Found&#8221;.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Am f\u0103cut peste 1.500 de migr\u0103ri \u00een total. Dac\u0103 treaba e f\u0103cut\u0103 ca la carte, vizitatorii t\u0103i-  \u0219i Google &#8211; nici nu vor \u0219ti c\u0103 s-a \u00eent\u00e2mplat ceva, p\u00e2n\u0103 nu vor observa c\u0103 site-ul se \u00eencarc\u0103 instant. Mutarea dintr-un mediu shared limitat c\u0103tre un <strong>VPS de \u00eenalt\u0103 performan\u021b\u0103<\/strong> nu e magie; e o secven\u021b\u0103 de pa\u0219i logici. Acest ghid prezint\u0103 procedura exact\u0103 rsync\/baz\u0103 de date pe care o folosim la ServerSpan pentru a garanta zero downtime.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Faza 1: Strategia &#8220;TTL&#8221; dinaintea migr\u0103rii<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Teoria:<\/strong><br>Cea mai mare cauz\u0103 a downtime-ului nu este transferul fi\u0219ierelor, ci <a href=\"https:\/\/www.serverspan.ro\/blog\/propagarea-dns-demistificata-cum-sa-verifici-ce-vede-lumea-pas-cu-pas\/\">propagarea DNS<\/a>. Dac\u0103 Time To Live (TTL) al domeniului t\u0103u este setat la 14400 secunde (4 ore) \u0219i schimbi serverele, jum\u0103tate din planet\u0103 va vedea serverul vechi, iar cealalt\u0103 jum\u0103tate pe cel nou. Asta duce la probleme de date tip &#8220;split-brain&#8221; (date desincronizate), unde comenzile clien\u021bilor se pierd pe serverul vechi. Po\u021bi citi mai multe despre <a href=\"https:\/\/www.serverspan.ro\/blog\/ce-este-o-inregistrare-dns-un-ghid-pentru-incepatori-despre-agenda-telefonica-a-internetului\/\">cum func\u021bioneaz\u0103 \u00eenregistr\u0103rile DNS aici<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Implementarea:<\/strong><br>Cu 48 de ore <em>\u00eenainte<\/em> de a planifica migrarea, intr\u0103 \u00een contul de la registrar (sau Cloudflare) \u0219i scade TTL-ul \u00eenregistr\u0103rilor A la 300 de secunde (5 minute).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Cazul limit\u0103 (Edge Case):<\/strong><br>Unii registrari ieftini au TTL hardcodat la o or\u0103. Dac\u0103 e\u0219ti \u00een barca asta, n-ai de ales dec\u00e2t s\u0103 a\u0219tep\u021bi. De aceea recomand\u0103m s\u0103 mu\u021bi DNS-ul de la furnizorul de hosting imediat. Folose\u0219te un serviciu DNS dedicat.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-css-opacity\"\/>\n\n\n\n<div class=\"wp-block-group has-light-gray-background-color has-background\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n<h3 class=\"wp-block-heading\">[SCENARIU REAL] Dezastrul comenzilor pierdute<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Problem\u0103 Client:<\/strong> &#8220;Am migrat magazinul WooCommerce ieri, dar 5 comenzi de asear\u0103 lipsesc din dashboard.&#8221;<br><strong>Diagnostic:<\/strong> Clientul a actualizat DNS-ul, dar a uitat s\u0103 scad\u0103 TTL-ul. Utilizatorii care aveau DNS-ul \u00een cache au intrat pe vechiul shared host, au plasat comenzi, iar acele date au r\u0103mas pe baza de date veche\u2014care urma s\u0103 fie \u0219tears\u0103. Noul <strong>Cloud VPS<\/strong> nu le-a v\u0103zut niciodat\u0103.<br><strong>Rezolu\u021bie:<\/strong> A trebuit s\u0103 extragem manual r\u00e2ndurile SQL din serverul vechi \u0219i s\u0103 le inject\u0103m \u00een cel nou. Un co\u0219mar pe care un TTL de 300 de secunde l-ar fi prevenit.<\/p>\n<\/div><\/div>\n\n\n\n<hr class=\"wp-block-separator has-css-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Faza 2: Sincronizarea mediului (Environment matching)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Teoria:<\/strong><br>Shared hosting-ul e adesea \u00een urm\u0103 cu tehnologia. S-ar putea s\u0103 rulezi PHP 7.4 pe vechiul host, \u00een timp ce noul t\u0103u <strong>VPS Linux<\/strong> vine cu PHP 8.2 standard. Mutarea unui site <a href=\"https:\/\/www.serverspan.ro\/blog\/ghidul-suprem-pentru-wordpress-vps-tot-ce-trebuie-sa-stii-in-2026\/\">WordPress<\/a> vechi pe un stack modern va genera erori critice instantaneu.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Implementarea:<\/strong><br>Verific\u0103 mai \u00eent\u00e2i versiunea curent\u0103. Creeaz\u0103 un fi\u0219ier `info.php` pe hostul shared:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&lt;?php phpinfo(); ?&gt;<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Asigur\u0103-te c\u0103 aceast\u0103 <strong><a href=\"https:\/\/www.serverspan.ro\/linux-administration\">configurare VPS<\/a><\/strong> se potrive\u0219te ini\u021bial cu aceast\u0103 versiune. Po\u021bi face upgrade <em>dup\u0103<\/em> ce migrarea e stabil\u0103. La ServerSpan, imaginile noastre de <strong>Managed VPS<\/strong> \u00ee\u021bi permit s\u0103 schimbi versiunile PHP per domeniu ca s\u0103 evi\u021bi exact \u0219ocul \u0103sta.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Faza 3: Mutarea fi\u0219ierelor (Nu mai folosi FTP)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Teoria:<\/strong><br>FTP-ul e dep\u0103\u0219it \u0219i ineficient. Deschide o conexiune nou\u0103 pentru fiecare fi\u0219ier \u00een parte. Dac\u0103 ai un site Magento sau WordPress cu 50.000 de fi\u0219iere mici, prin FTP \u00eemb\u0103tr\u00e2ne\u0219ti l\u00e2ng\u0103 calculator. Ai nevoie de `rsync`. Deoarece majoritatea host-urilor shared \u00ee\u021bi ofer\u0103 acces SSH (sau m\u0103car un terminal web), ar trebui s\u0103 &#8220;tragi&#8221; fi\u0219ierele <em>dinspre<\/em> noul VPS.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Implementarea:<\/strong><br>Logheaz\u0103-te pe noul <strong>Server VPS<\/strong> prin SSH. Ruleaz\u0103 comanda de mai jos pentru a copia fi\u0219ierele de pe vechiul host. Asta p\u0103streaz\u0103 permisiunile, data modific\u0103rii \u0219i symlink-urile.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code># Sintaxa: rsync &#91;flags] &#91;user]@&#91;remote_host]:&#91;source_path] &#91;destination_path]\n\nrsync -avzP --exclude 'wp-content\/cache' user@old-shared-host.com:~\/public_html\/ \/var\/www\/html\/<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Cazul limit\u0103 (Edge Case):<\/strong><br><strong>Stocare VPS<\/strong> vs. <a href=\"https:\/\/www.serverspan.ro\/blog\/de-ce-latimea-de-banda-nelimitata-este-o-minciuna-intelegerea-inodes-a-limitelor-i-o-si-de-ce-site-urile-cu-trafic-mare-mor-pe-hostingul-partajat\/\">limite Inode<\/a>. Host-urile shared m\u0103soar\u0103 adesea utilizarea \u00een &#8220;inode-uri&#8221; (num\u0103r de fi\u0219iere). C\u00e2nd faci `rsync` la milioane de fi\u0219iere cache minuscule, s-ar putea s\u0103 atingi limita de inode-uri pe noua parti\u021bie dac\u0103 nu e formatat\u0103 corect. Exclude \u00eentotdeauna folderul `\/cache`. Oricum vrei ca noul server s\u0103 genereze un cache curat.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Faza 4: Migrarea bazei de date<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Teoria:<\/strong><br>Fi\u0219ierele sunt statice; bazele de date sunt dinamice. \u0102sta e momentul adev\u0103rului. Ca s\u0103 nu ai date corupte, pune vechiul site \u00een &#8220;Maintenance Mode&#8221; pentru cele 5 minute c\u00e2t dureaz\u0103 opera\u021biunea. Dac\u0103 nu faci asta, un client ar putea s\u0103-\u0219i fac\u0103 cont fix \u00een timp ce tu expor\u021bi baza, iar contul lui va fi pierdut.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Implementarea:<\/strong><br>Pe vechiul host, export\u0103 baza de date:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>mysqldump -u username -p database_name &gt; dump.sql<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Transfer-o pe noul <strong>VPS NVMe<\/strong> (folose\u0219te `scp` sau `rsync`) \u0219i import-o:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>mysql -u root -p new_database_name &lt; dump.sql<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Cazul limit\u0103 (Edge Case):<\/strong><br>Encodarea caracterelor (Eroarea &#8220;????&#8221;). Vedem des furnizori de <strong>VPS ieftin<\/strong> care au implicit encodarea `latin1`. Dac\u0103 baza ta de date veche e `utf8mb4` (care suport\u0103 diacritice \u0219i emoji) \u0219i o impor\u021bi \u00eentr-un server setat pe `latin1`, tot textul se va transforma \u00een semne de \u00eentrebare. Verific\u0103 mereu ca `\/etc\/mysql\/my.cnf` pe noul server s\u0103 aib\u0103 `character-set-server = utf8mb4` \u00eenainte de import.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-css-opacity\"\/>\n\n\n\n<div class=\"wp-block-group has-light-gray-background-color has-background\"><div class=\"wp-block-group__inner-container is-layout-flow wp-block-group-is-layout-flow\">\n<h3 class=\"wp-block-heading\">[SCENARIU REAL] Timeout la import<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Problem\u0103 Client:<\/strong> &#8220;\u00cencerc s\u0103 import un SQL de 2GB prin phpMyAdmin dar d\u0103 timeout.&#8221;<br><strong>Diagnostic:<\/strong> phpMyAdmin e un script PHP limitat de `max_execution_time` \u0219i `upload_max_filesize`. Nu e f\u0103cut pentru <strong>migrare VPS<\/strong> cu baze de date mari.<br><strong>Rezolu\u021bie:<\/strong> Ne-am logat prin SSH \u0219i am folosit comanda nativ\u0103 `mysql` de mai sus. A importat fi\u0219ierul de 2GB \u00een 45 de secunde datorit\u0103 stoc\u0103rii NVMe.<\/p>\n<\/div><\/div>\n\n\n\n<hr class=\"wp-block-separator has-css-opacity\"\/>\n\n\n\n<h2 class=\"wp-block-heading\">Faza 5: Trucul cu fi\u0219ierul &#8220;hosts&#8221; (Testarea)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Teoria:<\/strong><br>Trebuie s\u0103 vezi dac\u0103 site-ul merge pe noul server <em>\u00eenainte<\/em> s\u0103 schimbi DNS-ul pentru tot internetul. Po\u021bi p\u0103c\u0103li calculatorul t\u0103u s\u0103 cread\u0103 c\u0103 domeniul s-a mutat deja.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Implementarea:<\/strong><br>Editeaz\u0103 fi\u0219ierul `hosts` pe laptopul t\u0103u.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Windows:<\/strong> `C:\\Windows\\System32\\drivers\\etc\\hosts`<\/li>\n\n\n\n<li><strong>Mac\/Linux:<\/strong> `\/etc\/hosts`<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Adaug\u0103 o linie la final:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>192.0.2.123  domeniultau.ro www.domeniultau.ro<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">\u00cenlocuie\u0219te `192.0.2.123` cu noul t\u0103u <strong>IP VPS<\/strong>. Acum, deschide browserul. Tu navighezi pe site-ul de pe noul server, \u00een timp ce restul lumii e \u00eenc\u0103 pe cel vechi. Testeaz\u0103 co\u0219ul de cump\u0103r\u0103turi, formularele de contact \u0219i login-ul de admin.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Faza 6: Comutarea \u0219i SSL-ul<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Teoria:<\/strong><br>Dup\u0103 ce te-ai convins c\u0103 totul e OK, intr\u0103 la furnizorul DNS \u0219i actualizeaz\u0103 \u00eenregistrarea A (A Record) c\u0103tre noul IP. Deoarece ai sc\u0103zut TTL-ul \u00een Faza 1, schimbarea se va propaga global \u00een c\u00e2teva minute. Pentru detalii despre <a href=\"https:\/\/www.serverspan.ro\/blog\/cum-sa-transferi-un-domeniu-fara-downtime-mutare-registrar-cutover-dns-si-siguranta-email-ului\/\">transferul complet al domeniului<\/a>, consult\u0103 <a href=\"https:\/\/www.serverspan.ro\/blog\/cum-sa-transferi-un-domeniu-fara-downtime-mutare-registrar-cutover-dns-si-siguranta-email-ului\/\">ghidul nostru despre transferul f\u0103r\u0103 downtime<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Implementarea:<\/strong><br>Ruleaz\u0103 imediat Certbot (Let&#8217;s Encrypt) pe noul server. <a href=\"https:\/\/www.serverspan.ro\/blog\/continut-mixt-dupa-activarea-ssl-gasirea-si-remedierea-elementelor-nesecurizate\/\">Certificatele SSL nu se migreaz\u0103 bine<\/a>; e mai curat s\u0103 generezi unul nou.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>certbot --nginx -d domeniultau.ro -d www.domeniultau.ro<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Cazul limit\u0103 (Edge Case):<\/strong><br>Dac\u0103 folose\u0219ti Cloudflare Proxy (Norul Portocaliu), nu trebuie s\u0103 a\u0219tep\u021bi propagarea. Doar schimb\u0103 IP-ul \u00een dashboard-ul Cloudflare. Totu\u0219i, asigur\u0103-te c\u0103 firewall-ul de pe noul plan de<strong> VPS Hosting<\/strong> (UFW\/iptables) permite conexiuni de la IP-urile Cloudflare, altfel site-ul va fi offline cu eroarea 522.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Faza 7: Cur\u0103\u021benia post-migrare<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Teoria:<\/strong><br>E\u0219ti pe un <strong>VPS dedicat<\/strong> puternic acum. Nu l\u0103sa set\u0103rile implicite. Fi\u0219ierele de configurare din shared hosting (`wp-config.php`, `.htaccess`) sunt pline de limit\u0103ri pentru a nu consuma resurse.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Implementarea:<\/strong><br>M\u0103re\u0219te limitele PHP imediat. Ai pl\u0103tit pentru RAM; folose\u0219te-l.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>memory_limit = 256M\nupload_max_filesize = 64M\nmax_execution_time = 300<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">De asemenea, \u0219terge orice plugin-uri de backup care salveaz\u0103 arhive pe discul local. Acum ar trebui s\u0103 folose\u0219ti solu\u021bii de <strong>backup VPS<\/strong> la nivel de server sau stocare offsite.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">G\u00e2nduri de final din partea echipei tehnice<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Prima migrare e cea mai grea. Anxietatea e real\u0103, dar recompensa e pe m\u0103sur\u0103. Un site care se mut\u0103 de la shared hosting la un pachet de <a href=\"https:\/\/www.serverspan.ro\/blog\/managed-vs-unmanaged-pentru-gazduire-magazin-online-cum-sa-faci-alegerea-corecta\/\">G\u0103zduire VPS<\/a> ServerSpan vede de obicei o reducere a TTFB (timpul p\u00e2n\u0103 la primul byte) de 600ms sau mai mult. Asta e aur curat pentru SEO.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Dac\u0103 cititul despre flag-uri `rsync` \u0219i seturi de caractere MySQL \u00ee\u021bi d\u0103 transpira\u021bii, aminte\u0219te-\u021bi c\u0103 noi asta facem toat\u0103 ziua. ServerSpan ofer\u0103 asisten\u021b\u0103 gratuit\u0103 la migrare cu planurile noastre managed. Noi ne ocup\u0103m de `dump.sql`, de TTL \u0219i de stres, ca tu doar s\u0103 te loghezi \u0219i s\u0103 vezi un site care zboar\u0103.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>&#8220;Frica de schimbare&#8221; te cost\u0103 bani \u00cen industria de hosting, noi numim fenomenul \u0103sta &#8220;Vendor Lock-in pe baz\u0103 de fric\u0103&#8221;. Vedem proprietari de afaceri bloca\u021bi \u00een planuri de shared hosting de 5\u20ac\/lun\u0103 care &#8220;crap\u0103&#8221; de fiecare dat\u0103 c\u00e2nd trimit un newsletter. Ei \u0219tiu c\u0103 au nevoie de un Server VPS. \u0218tiu c\u0103 site-ul se mi\u0219c\u0103 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2398,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[773,13949,9010,13954,732,5885,1154,13957,13958,13946,5980,6149,10147,13951,591,13953,13959,3703,590,738,13955,6011,13939,13948,13952,13966,13947,4550,3884,13950,13960,13962,13961,13964,13963,5985,13956,10654,13965,2216],"class_list":["post-2403","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-tutorials","tag-backup-vps","tag-cel-mai-bun-vps-hosting","tag-cloud-vps","tag-comenzi-linux-vps","tag-configurare-vps","tag-depanare-vps","tag-gazduire-cloud","tag-latenta-vps","tag-latime-de-banda-vps","tag-managed-cloud-vps","tag-managed-vps","tag-migrare-vps","tag-monitorizare-vps","tag-panou-de-control-vps","tag-performanta-vps","tag-preturi-vps","tag-recenzii-vps","tag-secure-vps-hosting","tag-securitate-vps","tag-server-privat-virtual","tag-server-vps","tag-stocare-vps","tag-vps-cpu","tag-vps-de-inalta-performanta-3","tag-vps-dedicat","tag-vps-gratuit","tag-vps-ieftin","tag-vps-linux","tag-vps-management","tag-vps-nvme","tag-vps-pentru-business","tag-vps-pentru-developeri","tag-vps-pentru-gaming","tag-vps-pentru-trading","tag-vps-pentru-website","tag-vps-ram","tag-vps-self-hosted","tag-vps-vs-cloud","tag-vps-vs-dedicat","tag-vps-windows"],"_links":{"self":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2403","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2403"}],"version-history":[{"count":10,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2403\/revisions"}],"predecessor-version":[{"id":2420,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2403\/revisions\/2420"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=\/wp\/v2\/media\/2398"}],"wp:attachment":[{"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2403"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2403"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.serverspan.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2403"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}