{"id":2230,"date":"2026-07-19T00:01:50","date_gmt":"2026-07-19T00:01:50","guid":{"rendered":"https:\/\/www.letscloud.io\/blog\/how-to-automate-server-backups\/"},"modified":"2026-07-19T00:01:50","modified_gmt":"2026-07-19T00:01:50","slug":"how-to-automate-server-backups","status":"publish","type":"post","link":"https:\/\/www.letscloud.io\/blog\/how-to-automate-server-backups\/","title":{"rendered":"How to Automate Server Backups Without Gaps"},"content":{"rendered":"

A backup that exists only because someone remembered to run it is not a backup strategy. Production servers change constantly: databases receive writes, application files are deployed, credentials rotate, and configuration drift appears when least expected. Knowing how to automate server backups<\/strong> turns recovery from an urgent manual task into a predictable operational process.<\/p>\n

For a startup, agency, or DevOps team, the goal is not simply to create copies of a server. The goal is to recover the right data, from the right point in time, within a recovery window the business can accept. That requires schedules, retention rules, off-server storage, alerts, and regular restore tests working together.<\/p>\n

Start With Recovery Requirements, Not Backup Software<\/h2>\n

Before configuring a cron job or enabling a provider snapshot feature, define what failure you are planning for. A deleted database table, a bad deployment, ransomware, an unavailable region, and accidental server deletion do not require the same recovery process.<\/p>\n

Two values make the discussion practical. Your recovery point objective, or RPO, is the maximum acceptable amount of data loss. If an application can lose no more than 15 minutes of transactions, daily backups are not enough. Your recovery time objective, or RTO, is how long the service can remain unavailable while you restore it. A full server image may be convenient, but restoring hundreds of gigabytes may not meet a one-hour RTO.<\/p>\n

For many web applications, a useful baseline is daily server-level backups, frequent database backups or transaction-log archival, and a pre-deployment backup for higher-risk releases. Agencies managing WordPress sites may need daily database and media backups, while a SaaS product with customer writes may need database recovery points every few minutes.<\/p>\n

Write down the systems that must be protected: application code, databases, uploaded files, environment configuration, TLS certificates, infrastructure configuration, and audit logs where required. Do not assume a server image includes every managed service or external data store your application depends on.<\/p>\n

Use Layers for Automated Server Backups<\/h2>\n

The most reliable approach combines different backup layers instead of treating one snapshot as complete protection. Each layer addresses a different recovery need.<\/p>\n

Server snapshots capture the disk state of a cloud server at a point in time. They are useful before upgrades, operating system changes, or major deployments. They can also speed up rebuilding a failed instance. Snapshot consistency depends on the workload, however. A snapshot taken while a database is actively writing may not be application-consistent unless the database is prepared first.<\/p>\n

File backups protect directories that change independently of the operating system. This commonly includes user uploads, application assets, configuration directories, and generated reports. Tools such as restic, Borg, or rsync-based workflows can send encrypted, incremental backups to a separate storage destination.<\/p>\n

Database backups deserve their own job. For PostgreSQL or MySQL, create logical dumps for straightforward recovery, or use physical backups and binary logs or write-ahead logs when tighter RPOs are needed. A logical dump is often easier to inspect and restore to a new environment. Physical backups can be faster at scale, but they require more careful version and storage planning.<\/p>\n

Finally, store infrastructure definitions outside the server. Keep deployment scripts, firewall rules, DNS records, and infrastructure-as-code configuration<\/a> in version control or another controlled system. Backups restore data; automation definitions help you recreate the environment around that data.<\/p>\n

Build the Backup Workflow Around a Separate Destination<\/h2>\n

A backup stored only on the same server is vulnerable to the same disk failure, deletion event, compromise, or account-level mistake that affects production. Send copies to an independent storage location and use credentials that are not shared with the application runtime.<\/p>\n

A practical pattern follows the 3-2-1 principle: maintain three copies of important data, on two types of storage, with one copy outside the primary environment. The exact implementation depends on your scale and compliance requirements. A small application may use encrypted object storage plus provider snapshots. A regulated workload may require cross-region copies, immutable retention, and documented access controls.<\/p>\n

Encryption should apply in transit and at rest. Treat backup encryption keys as production secrets. If a team loses the only key, the backup is effectively unavailable. Store recovery credentials in a controlled password manager or secrets platform, document who can access them, and avoid placing long-lived storage keys directly in application repositories.<\/p>\n

Retention is equally important. Keeping every backup forever increases storage costs and makes management harder. Keeping too few copies leaves no recovery point after an unnoticed corruption event. A common rotation is frequent backups for recent days, daily backups for several weeks, and monthly backups for longer-term requirements. Adjust this based on legal, financial, customer, and operational needs.<\/p>\n

How to Automate Server Backups With Jobs and APIs<\/h2>\n

Automation should run without an engineer logging in to a production machine. On Linux, a systemd timer is often a better choice than a basic cron job because it provides service logs<\/a>, dependency controls, failure handling, and missed-run behavior. Cron is still suitable for simple tasks, but it needs clear logging and alerting around it.<\/p>\n

A backup job should follow a deliberate sequence:<\/p>\n

    \n
  1. Validate that required storage credentials and target paths are available.<\/li>\n
  2. Create an application-consistent database backup or trigger log archival.<\/li>\n
  3. Back up required files and configuration, excluding caches and rebuildable artifacts.<\/li>\n
  4. Encrypt and transfer data to the remote destination.<\/li>\n
  5. Verify the transfer, record the backup identifier, and clean up expired copies.<\/li>\n
  6. Send a success or failure result to monitoring.<\/li>\n<\/ol>\n

    For cloud server snapshots, use your infrastructure provider’s API to schedule snapshot creation, label images consistently, and remove images outside the retention policy. API-driven workflows are especially useful when servers are created dynamically for customer environments, test labs, or short-lived production capacity. LetsCloud’s REST API<\/a> can fit this model by allowing teams to integrate infrastructure actions into their existing deployment and operations workflows.<\/p>\n

    Use descriptive names that make recovery faster. Include the environment, server role, application, timestamp, and backup type. For example, `prod-api-us-east-2026-07-18-db` is more useful during an incident than `backup-final-new`.<\/p>\n

    Avoid running heavy full backups during the same period as reporting jobs, indexing, or peak customer traffic. Incremental backups reduce transfer volume, but they can make restoration dependent on a chain of prior backup data. Test the restore path before assuming the storage savings are worth the added complexity.<\/p>\n

    Monitor the Result, Not Just the Job<\/h2>\n

    A scheduled job that starts is not proof that a usable backup finished. Monitor backup age, duration, size, exit status, and destination availability. A sudden backup size drop may indicate that an expected directory was excluded. A job that takes five times longer than normal may signal network, disk, or storage trouble before it fails completely.<\/p>\n

    Create an alert when no successful backup appears within the expected window. The alert should go to a channel someone actively watches, with enough context to identify the affected server and backup type. For critical workloads, alert on failed database log archival separately from failed daily backups.<\/p>\n

    Keep backup logs outside the server where possible. If an instance is deleted or encrypted by an attacker, local logs may disappear with it. Centralized logs also make it easier to identify recurring failures caused by expired credentials, changed permissions, or capacity limits.<\/p>\n

    Restore Tests Are the Real Check<\/h2>\n

    The only meaningful backup test is a restore test. Schedule one at least quarterly for lower-risk systems and more often for critical services. Restore into an isolated environment so you do not overwrite production, then validate the application, database integrity, permissions, configuration, and expected customer data.<\/p>\n

    Time the process. If the restore takes six hours but your RTO is two, the backup system is functioning technically while failing operationally. Use the test to improve runbooks, reduce unnecessary data, pre-provision recovery infrastructure, or choose a faster restore method.<\/p>\n

    A strong test also checks the human side of recovery. Can another engineer locate the correct backup, access the encryption key, follow the runbook, and bring up the service without relying on undocumented knowledge from the person who built the system?<\/p>\n

    Common Automation Mistakes to Avoid<\/h2>\n

    The most common failure is treating snapshots as a complete backup plan. Snapshots are valuable, but they may not meet database consistency, cross-account, cross-region, or long-term retention requirements. Another frequent mistake is backing up everything, including caches, dependencies, and temporary files, which increases cost and slows recovery without improving it.<\/p>\n

    Teams also forget to protect the backup control plane. Restrict deletion permissions, require multi-factor authentication for administrative accounts, and separate backup credentials from normal application credentials. Where supported and appropriate, use immutable or write-protected retention to reduce the damage from ransomware or accidental deletion.<\/p>\n

    Do not let automation hide ownership. Assign a team or role responsible for reviewing backup health, retention changes, and restore-test results. Automation removes repetitive work; it does not remove accountability.<\/p>\n

    The best backup workflow is usually quiet: scheduled jobs finish, retention stays under control, and recovery documentation remains current. Build it before the next failed deployment or deleted volume gives you a reason to wish it had been there.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Learn how to automate server backups with schedules, encryption, retention rules, monitoring, and restore tests that protect production workloads daily.<\/p>\n","protected":false},"author":1,"featured_media":2231,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-2230","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-community","entry"],"yoast_head":"\nHow to Automate Server Backups Without Gaps - LetsCloud Blog<\/title>\n<meta name=\"description\" content=\"Learn how to automate server backups with schedules, encryption, retention rules, monitoring, and restore tests that protect production workloads daily.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.letscloud.io\/blog\/how-to-automate-server-backups\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to Automate Server Backups Without Gaps - LetsCloud Blog\" \/>\n<meta property=\"og:description\" content=\"Learn how to automate server backups with schedules, encryption, retention rules, monitoring, and restore tests that protect production workloads daily.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.letscloud.io\/blog\/how-to-automate-server-backups\/\" \/>\n<meta property=\"og:site_name\" content=\"LetsCloud Blog\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/LetsCloudOfficial\" \/>\n<meta property=\"article:published_time\" content=\"2026-07-19T00:01:50+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.letscloud.io\/blog\/wp-content\/uploads\/2019\/06\/og-image.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"627\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"LetsCloud Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@letscloudInc\" \/>\n<meta name=\"twitter:site\" content=\"@letscloudInc\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"LetsCloud Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.letscloud.io\\\/blog\\\/how-to-automate-server-backups\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.letscloud.io\\\/blog\\\/how-to-automate-server-backups\\\/\"},\"author\":{\"name\":\"LetsCloud Team\",\"@id\":\"https:\\\/\\\/www.letscloud.io\\\/blog\\\/#\\\/schema\\\/person\\\/db5dc1b68cac3498c8aeb0b56f1dbdf6\"},\"headline\":\"How to Automate Server Backups Without Gaps\",\"datePublished\":\"2026-07-19T00:01:50+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.letscloud.io\\\/blog\\\/how-to-automate-server-backups\\\/\"},\"wordCount\":1506,\"commentCount\":0,\"image\":{\"@id\":\"https:\\\/\\\/www.letscloud.io\\\/blog\\\/how-to-automate-server-backups\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.letscloud.io\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/how-to-automate-server-backups-without-gaps-featured.webp\",\"articleSection\":[\"Community\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.letscloud.io\\\/blog\\\/how-to-automate-server-backups\\\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.letscloud.io\\\/blog\\\/how-to-automate-server-backups\\\/\",\"url\":\"https:\\\/\\\/www.letscloud.io\\\/blog\\\/how-to-automate-server-backups\\\/\",\"name\":\"How to Automate Server Backups Without Gaps - LetsCloud Blog\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.letscloud.io\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.letscloud.io\\\/blog\\\/how-to-automate-server-backups\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.letscloud.io\\\/blog\\\/how-to-automate-server-backups\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.letscloud.io\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/how-to-automate-server-backups-without-gaps-featured.webp\",\"datePublished\":\"2026-07-19T00:01:50+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.letscloud.io\\\/blog\\\/#\\\/schema\\\/person\\\/db5dc1b68cac3498c8aeb0b56f1dbdf6\"},\"description\":\"Learn how to automate server backups with schedules, encryption, retention rules, monitoring, and restore tests that protect production workloads daily.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.letscloud.io\\\/blog\\\/how-to-automate-server-backups\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.letscloud.io\\\/blog\\\/how-to-automate-server-backups\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/www.letscloud.io\\\/blog\\\/how-to-automate-server-backups\\\/#primaryimage\",\"url\":\"https:\\\/\\\/www.letscloud.io\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/how-to-automate-server-backups-without-gaps-featured.webp\",\"contentUrl\":\"https:\\\/\\\/www.letscloud.io\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/how-to-automate-server-backups-without-gaps-featured.webp\",\"width\":1536,\"height\":1024,\"caption\":\"How to Automate Server Backups Without Gaps\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.letscloud.io\\\/blog\\\/how-to-automate-server-backups\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.letscloud.io\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Automate Server Backups Without Gaps\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.letscloud.io\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.letscloud.io\\\/blog\\\/\",\"name\":\"LetsCloud Blog\",\"description\":\"Everything you need. Nothing you don\u2019t.\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.letscloud.io\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.letscloud.io\\\/blog\\\/#\\\/schema\\\/person\\\/db5dc1b68cac3498c8aeb0b56f1dbdf6\",\"name\":\"LetsCloud Team\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/ccae1dbb34f990736eba7967e6dfaf22ad95b4790915f19a175e53d146ad0a71?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/ccae1dbb34f990736eba7967e6dfaf22ad95b4790915f19a175e53d146ad0a71?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/ccae1dbb34f990736eba7967e6dfaf22ad95b4790915f19a175e53d146ad0a71?s=96&d=mm&r=g\",\"caption\":\"LetsCloud Team\"},\"url\":\"https:\\\/\\\/www.letscloud.io\\\/blog\\\/author\\\/letscloud\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"How to Automate Server Backups Without Gaps - LetsCloud Blog","description":"Learn how to automate server backups with schedules, encryption, retention rules, monitoring, and restore tests that protect production workloads daily.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.letscloud.io\/blog\/how-to-automate-server-backups\/","og_locale":"en_US","og_type":"article","og_title":"How to Automate Server Backups Without Gaps - LetsCloud Blog","og_description":"Learn how to automate server backups with schedules, encryption, retention rules, monitoring, and restore tests that protect production workloads daily.","og_url":"https:\/\/www.letscloud.io\/blog\/how-to-automate-server-backups\/","og_site_name":"LetsCloud Blog","article_publisher":"https:\/\/www.facebook.com\/LetsCloudOfficial","article_published_time":"2026-07-19T00:01:50+00:00","og_image":[{"width":1200,"height":627,"url":"https:\/\/www.letscloud.io\/blog\/wp-content\/uploads\/2019\/06\/og-image.png","type":"image\/png"}],"author":"LetsCloud Team","twitter_card":"summary_large_image","twitter_creator":"@letscloudInc","twitter_site":"@letscloudInc","twitter_misc":{"Written by":"LetsCloud Team","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.letscloud.io\/blog\/how-to-automate-server-backups\/#article","isPartOf":{"@id":"https:\/\/www.letscloud.io\/blog\/how-to-automate-server-backups\/"},"author":{"name":"LetsCloud Team","@id":"https:\/\/www.letscloud.io\/blog\/#\/schema\/person\/db5dc1b68cac3498c8aeb0b56f1dbdf6"},"headline":"How to Automate Server Backups Without Gaps","datePublished":"2026-07-19T00:01:50+00:00","mainEntityOfPage":{"@id":"https:\/\/www.letscloud.io\/blog\/how-to-automate-server-backups\/"},"wordCount":1506,"commentCount":0,"image":{"@id":"https:\/\/www.letscloud.io\/blog\/how-to-automate-server-backups\/#primaryimage"},"thumbnailUrl":"https:\/\/www.letscloud.io\/blog\/wp-content\/uploads\/2026\/07\/how-to-automate-server-backups-without-gaps-featured.webp","articleSection":["Community"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.letscloud.io\/blog\/how-to-automate-server-backups\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.letscloud.io\/blog\/how-to-automate-server-backups\/","url":"https:\/\/www.letscloud.io\/blog\/how-to-automate-server-backups\/","name":"How to Automate Server Backups Without Gaps - LetsCloud Blog","isPartOf":{"@id":"https:\/\/www.letscloud.io\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.letscloud.io\/blog\/how-to-automate-server-backups\/#primaryimage"},"image":{"@id":"https:\/\/www.letscloud.io\/blog\/how-to-automate-server-backups\/#primaryimage"},"thumbnailUrl":"https:\/\/www.letscloud.io\/blog\/wp-content\/uploads\/2026\/07\/how-to-automate-server-backups-without-gaps-featured.webp","datePublished":"2026-07-19T00:01:50+00:00","author":{"@id":"https:\/\/www.letscloud.io\/blog\/#\/schema\/person\/db5dc1b68cac3498c8aeb0b56f1dbdf6"},"description":"Learn how to automate server backups with schedules, encryption, retention rules, monitoring, and restore tests that protect production workloads daily.","breadcrumb":{"@id":"https:\/\/www.letscloud.io\/blog\/how-to-automate-server-backups\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.letscloud.io\/blog\/how-to-automate-server-backups\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.letscloud.io\/blog\/how-to-automate-server-backups\/#primaryimage","url":"https:\/\/www.letscloud.io\/blog\/wp-content\/uploads\/2026\/07\/how-to-automate-server-backups-without-gaps-featured.webp","contentUrl":"https:\/\/www.letscloud.io\/blog\/wp-content\/uploads\/2026\/07\/how-to-automate-server-backups-without-gaps-featured.webp","width":1536,"height":1024,"caption":"How to Automate Server Backups Without Gaps"},{"@type":"BreadcrumbList","@id":"https:\/\/www.letscloud.io\/blog\/how-to-automate-server-backups\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.letscloud.io\/blog\/"},{"@type":"ListItem","position":2,"name":"How to Automate Server Backups Without Gaps"}]},{"@type":"WebSite","@id":"https:\/\/www.letscloud.io\/blog\/#website","url":"https:\/\/www.letscloud.io\/blog\/","name":"LetsCloud Blog","description":"Everything you need. Nothing you don\u2019t.","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.letscloud.io\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.letscloud.io\/blog\/#\/schema\/person\/db5dc1b68cac3498c8aeb0b56f1dbdf6","name":"LetsCloud Team","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/ccae1dbb34f990736eba7967e6dfaf22ad95b4790915f19a175e53d146ad0a71?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/ccae1dbb34f990736eba7967e6dfaf22ad95b4790915f19a175e53d146ad0a71?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/ccae1dbb34f990736eba7967e6dfaf22ad95b4790915f19a175e53d146ad0a71?s=96&d=mm&r=g","caption":"LetsCloud Team"},"url":"https:\/\/www.letscloud.io\/blog\/author\/letscloud\/"}]}},"_links":{"self":[{"href":"https:\/\/www.letscloud.io\/blog\/wp-json\/wp\/v2\/posts\/2230","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.letscloud.io\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.letscloud.io\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.letscloud.io\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.letscloud.io\/blog\/wp-json\/wp\/v2\/comments?post=2230"}],"version-history":[{"count":0,"href":"https:\/\/www.letscloud.io\/blog\/wp-json\/wp\/v2\/posts\/2230\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.letscloud.io\/blog\/wp-json\/wp\/v2\/media\/2231"}],"wp:attachment":[{"href":"https:\/\/www.letscloud.io\/blog\/wp-json\/wp\/v2\/media?parent=2230"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.letscloud.io\/blog\/wp-json\/wp\/v2\/categories?post=2230"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.letscloud.io\/blog\/wp-json\/wp\/v2\/tags?post=2230"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}