{"id":498,"date":"2025-05-03T21:51:39","date_gmt":"2025-05-04T01:51:39","guid":{"rendered":"https:\/\/zdtdevops.com\/web\/?p=498"},"modified":"2025-05-04T00:46:15","modified_gmt":"2025-05-04T04:46:15","slug":"zdt-replicate-complete-configuration-guide","status":"publish","type":"post","link":"https:\/\/zdtdevops.com\/web\/zdt-replicate-complete-configuration-guide\/","title":{"rendered":"ZDT Replicate: Complete Configuration Guide"},"content":{"rendered":"

ZDT Replicate: Complete Configuration Guide<\/h1>\r\n\r\n\r\n\r\n

Welcome to our comprehensive guide on configuring ZDT Replicate, a powerful tool that simplifies DRBD (Distributed Replicated Block Device) management for Zero Downtime deployments. Whether you’re setting up high availability within a single datacenter or implementing disaster recovery across multiple sites, this guide will help you understand all available configuration options.<\/p>\r\n\r\n\r\n\r\n


\r\n

\"ZDT<\/figcaption>\r\n<\/figure>\r\n\r\n\r\n\r\n

Configuration File Basics<\/h2>\r\n\r\n\r\n\r\n

ZDT Replicate uses a simple environment file (zdtreplicate.env<\/code>) to store all configuration parameters.<\/p>\r\n

This file must be located in your ZDT DevOps installation config directory:<\/strong><\/p>\r\n\r\n\r\n\r\n\r\n\r\n

The file uses a simple KEY=VALUE format, with parameters organized into logical sections. If the file doesn’t exist, you’ll need to create it in the correct location before running zdtreplicate commands.<\/p>\r\n\r\n\r\n\r\n

Important<\/strong>: Make sure you have appropriate permissions to write to the config directory. In most installations, this requires sudo or administrator privileges.<\/div>\r\n\r\n\r\n\r\n

Node Configuration<\/h2>\r\n\r\n\r\n\r\n

ZDTREP_NODE_TYPE<\/h3>\r\n\r\n\r\n\r\n

This parameter defines the role of the node in your replication topology.<\/p>\r\n\r\n\r\n\r\n

\r\n\r\n\r\n\r\n\r\n\r\n\r\n
Possible values<\/strong><\/td>\r\nprimary<\/code>, secondary<\/code>, mirror<\/code>, external<\/code><\/td>\r\n<\/tr>\r\n
Default<\/strong><\/td>\r\nprimary<\/code><\/td>\r\n<\/tr>\r\n
Description<\/strong><\/td>\r\n\r\n
    \r\n
  • primary<\/code>: Active node that serves data (read\/write access)<\/li>\r\n
  • secondary<\/code>: Standby node in local cluster for quick failover<\/li>\r\n
  • mirror<\/code>: Node that replicates data to external datacenter<\/li>\r\n
  • external<\/code>: Node in separate datacenter receiving replication<\/li>\r\n<\/ul>\r\n<\/td>\r\n<\/tr>\r\n
Example<\/strong><\/td>\r\nZDTREP_NODE_TYPE=primary<\/code><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<\/figure>\r\n\r\n\r\n\r\n

ZDTREP_NODE_ID<\/h3>\r\n\r\n\r\n\r\n

A unique identifier for this node in the DRBD configuration.<\/p>\r\n\r\n\r\n\r\n

\r\n\r\n\r\n\r\n\r\n\r\n
Default<\/strong><\/td>\r\nNone (required)<\/td>\r\n<\/tr>\r\n
Description<\/strong><\/td>\r\nShould be a simple string without spaces<\/td>\r\n<\/tr>\r\n
Example<\/strong><\/td>\r\nZDTREP_NODE_ID=nodeA<\/code><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<\/figure>\r\n\r\n\r\n\r\n

ZDTREP_CLUSTER_ADDR<\/h3>\r\n\r\n\r\n\r\n

IP address or hostname of this node.<\/p>\r\n\r\n\r\n\r\n

\r\n\r\n\r\n\r\n\r\n\r\n
Default<\/strong><\/td>\r\n127.0.0.1<\/code><\/td>\r\n<\/tr>\r\n
Description<\/strong><\/td>\r\nUsed for DRBD network communication<\/td>\r\n<\/tr>\r\n
Example<\/strong><\/td>\r\nZDTREP_CLUSTER_ADDR=192.168.1.1<\/code><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<\/figure>\r\n\r\n\r\n\r\n

ZDTREP_DISK_DEVICE<\/h3>\r\n\r\n\r\n\r\n

Block device to be used for DRBD replication.<\/p>\r\n\r\n\r\n\r\n

\r\n\r\n\r\n\r\n\r\n\r\n
Default<\/strong><\/td>\r\n\/dev\/sdb1<\/code><\/td>\r\n<\/tr>\r\n
Description<\/strong><\/td>\r\nThe device will store replicated data. Warning<\/strong>: All data on this device will be erased during setup.<\/td>\r\n<\/tr>\r\n
Example<\/strong><\/td>\r\nZDTREP_DISK_DEVICE=\/dev\/sdb1<\/code><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<\/figure>\r\n\r\n\r\n\r\n

ZDTREP_DATA_DIR<\/h3>\r\n\r\n\r\n\r\n

Directory where the DRBD device will be mounted.<\/p>\r\n\r\n\r\n\r\n

\r\n\r\n\r\n\r\n\r\n\r\n
Default<\/strong><\/td>\r\n\/var\/lib\/etcd<\/code><\/td>\r\n<\/tr>\r\n
Description<\/strong><\/td>\r\nTypically where your application (e.g., etcd) will store its data<\/td>\r\n<\/tr>\r\n
Example<\/strong><\/td>\r\nZDTREP_DATA_DIR=\/var\/lib\/etcd<\/code><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<\/figure>\r\n\r\n\r\n\r\n

Replication Configuration<\/h2>\r\n\r\n\r\n\r\n

ZDTREP_REPLICATION_PROTOCOL<\/h3>\r\n\r\n\r\n\r\n

DRBD replication protocol determining data consistency vs. performance trade-offs.<\/p>\r\n\r\n\r\n\r\n

\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n
Possible values<\/strong><\/td>\r\nA<\/code>, B<\/code>, C<\/code><\/td>\r\n<\/tr>\r\n
Default<\/strong><\/td>\r\nC<\/code><\/td>\r\n<\/tr>\r\n
Description<\/strong><\/td>\r\n\r\n
    \r\n
  • A<\/code>: Asynchronous replication (fastest, potential data loss)<\/li>\r\n
  • B<\/code>: Semi-synchronous (confirms network receipt, not disk write)<\/li>\r\n
  • C<\/code>: Synchronous (slowest but safest, no data loss)<\/li>\r\n<\/ul>\r\n<\/td>\r\n<\/tr>\r\n
Recommendation<\/strong><\/td>\r\nUse C<\/code> for local nodes, A<\/code> for cross-datacenter replication<\/td>\r\n<\/tr>\r\n
Example<\/strong><\/td>\r\nZDTREP_REPLICATION_PROTOCOL=C<\/code><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<\/figure>\r\n\r\n\r\n\r\n

ZDTREP_REPLICATION_PORT<\/h3>\r\n\r\n\r\n\r\n

Base TCP port for DRBD replication.<\/p>\r\n\r\n\r\n\r\n

\r\n\r\n\r\n\r\n\r\n\r\n
Default<\/strong><\/td>\r\n7788<\/code><\/td>\r\n<\/tr>\r\n
Description<\/strong><\/td>\r\nDRBD will use this port for network communication. Make sure this port is open in your firewall.<\/td>\r\n<\/tr>\r\n
Example<\/strong><\/td>\r\nZDTREP_REPLICATION_PORT=7788<\/code><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<\/figure>\r\n\r\n\r\n\r\n

ZDTREP_BANDWIDTH_LIMIT<\/h3>\r\n\r\n\r\n\r\n

Network bandwidth limit for replication.<\/p>\r\n\r\n\r\n\r\n

\r\n\r\n\r\n\r\n\r\n\r\n\r\n
Default<\/strong><\/td>\r\n0<\/code> (unlimited)<\/td>\r\n<\/tr>\r\n
Format<\/strong><\/td>\r\nNumber followed by K, M, or G (e.g., 10M for 10 megabits\/sec)<\/td>\r\n<\/tr>\r\n
Description<\/strong><\/td>\r\nEspecially useful for cross-datacenter replication to avoid network saturation<\/td>\r\n<\/tr>\r\n
Example<\/strong><\/td>\r\nZDTREP_BANDWIDTH_LIMIT=10M<\/code><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<\/figure>\r\n\r\n\r\n\r\n

Remote Node Addresses<\/h2>\r\n\r\n\r\n\r\n

ZDTREP_PRIMARY_ADDR<\/h3>\r\n\r\n\r\n\r\n

IP address of the primary node.<\/p>\r\n\r\n\r\n\r\n

\r\n\r\n\r\n\r\n\r\n\r\n
Default<\/strong><\/td>\r\nEmpty<\/td>\r\n<\/tr>\r\n
Required for<\/strong><\/td>\r\nSecondary and mirror nodes<\/td>\r\n<\/tr>\r\n
Example<\/strong><\/td>\r\nZDTREP_PRIMARY_ADDR=192.168.1.1<\/code><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<\/figure>\r\n\r\n\r\n\r\n

ZDTREP_SECONDARY_ADDR<\/h3>\r\n\r\n\r\n\r\n

IP address of the secondary node.<\/p>\r\n\r\n\r\n\r\n

\r\n\r\n\r\n\r\n\r\n\r\n
Default<\/strong><\/td>\r\nEmpty<\/td>\r\n<\/tr>\r\n
Required for<\/strong><\/td>\r\nMirror nodes<\/td>\r\n<\/tr>\r\n
Example<\/strong><\/td>\r\nZDTREP_SECONDARY_ADDR=192.168.1.2<\/code><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<\/figure>\r\n\r\n\r\n\r\n

ZDTREP_MIRROR_ADDRS<\/h3>\r\n\r\n\r\n\r\n

Comma-separated list of mirror node addresses.<\/p>\r\n\r\n\r\n\r\n

\r\n\r\n\r\n\r\n\r\n\r\n
Default<\/strong><\/td>\r\nEmpty<\/td>\r\n<\/tr>\r\n
Required for<\/strong><\/td>\r\nExternal nodes<\/td>\r\n<\/tr>\r\n
Example<\/strong><\/td>\r\nZDTREP_MIRROR_ADDRS=10.0.0.1,10.0.0.2,10.0.0.3<\/code><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<\/figure>\r\n\r\n\r\n\r\n

Monitoring Configuration<\/h2>\r\n\r\n\r\n\r\n

ZDTREP_MONITOR_INTERVAL<\/h3>\r\n\r\n\r\n\r\n

Time between status checks in seconds.<\/p>\r\n\r\n\r\n\r\n

\r\n\r\n\r\n\r\n\r\n\r\n
Default<\/strong><\/td>\r\n60<\/code><\/td>\r\n<\/tr>\r\n
Description<\/strong><\/td>\r\nControls how frequently the monitor command checks replication status<\/td>\r\n<\/tr>\r\n
Example<\/strong><\/td>\r\nZDTREP_MONITOR_INTERVAL=60<\/code><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<\/figure>\r\n\r\n\r\n\r\n

ZDTREP_MONITOR_LOG_PATH<\/h3>\r\n\r\n\r\n\r\n

Full path to monitoring log file.<\/p>\r\n\r\n\r\n\r\n

\r\n\r\n\r\n\r\n\r\n\r\n
Default<\/strong><\/td>\r\n\/var\/log\/zdtreplicate.log<\/code><\/td>\r\n<\/tr>\r\n
Description<\/strong><\/td>\r\nThe monitor command will write status information to this file<\/td>\r\n<\/tr>\r\n
Example<\/strong><\/td>\r\nZDTREP_MONITOR_LOG_PATH=\/var\/log\/zdtreplicate.log<\/code><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<\/figure>\r\n\r\n\r\n\r\n

NFS Configuration (Optional)<\/h2>\r\n\r\n\r\n\r\n

ZDTREP_NFS_ENABLED<\/h3>\r\n\r\n\r\n\r\n

Enable NFS exports of the DRBD device.<\/p>\r\n\r\n\r\n\r\n

\r\n\r\n\r\n\r\n\r\n\r\n\r\n
Possible values<\/strong><\/td>\r\ntrue<\/code>, false<\/code><\/td>\r\n<\/tr>\r\n
Default<\/strong><\/td>\r\nfalse<\/code><\/td>\r\n<\/tr>\r\n
Description<\/strong><\/td>\r\nAutomatically configure NFS sharing of the replicated data. Useful for Kubernetes PVC integration.<\/td>\r\n<\/tr>\r\n
Example<\/strong><\/td>\r\nZDTREP_NFS_ENABLED=true<\/code><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<\/figure>\r\n\r\n\r\n\r\n

ZDTREP_NFS_EXPORTS_DIR<\/h3>\r\n\r\n\r\n\r\n

Directory to export via NFS.<\/p>\r\n\r\n\r\n\r\n

\r\n\r\n\r\n\r\n\r\n\r\n
Default<\/strong><\/td>\r\n\/mnt\/etcd-data<\/code><\/td>\r\n<\/tr>\r\n
Description<\/strong><\/td>\r\nTypically the same as ZDTREP_DATA_DIR or a subdirectory<\/td>\r\n<\/tr>\r\n
Example<\/strong><\/td>\r\nZDTREP_NFS_EXPORTS_DIR=\/mnt\/etcd-data<\/code><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<\/figure>\r\n\r\n\r\n\r\n

ZDTREP_NFS_ALLOWED_CLIENTS<\/h3>\r\n\r\n\r\n\r\n

Clients allowed to access the NFS export.<\/p>\r\n\r\n\r\n\r\n

\r\n\r\n\r\n\r\n\r\n\r\n
Default<\/strong><\/td>\r\n*<\/code> (all clients)<\/td>\r\n<\/tr>\r\n
Format<\/strong><\/td>\r\nNFS exports syntax (* for all, IP\/subnet for specific clients)<\/td>\r\n<\/tr>\r\n
Example<\/strong><\/td>\r\nZDTREP_NFS_ALLOWED_CLIENTS=192.168.0.0\/24<\/code><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<\/figure>\r\n\r\n\r\n\r\n

ZDTREP_NFS_OPTIONS<\/h3>\r\n\r\n\r\n\r\n

NFS export options.<\/p>\r\n\r\n\r\n\r\n

\r\n\r\n\r\n\r\n\r\n\r\n
Default<\/strong><\/td>\r\nrw,sync,no_subtree_check<\/code><\/td>\r\n<\/tr>\r\n
Common options<\/strong><\/td>\r\n\r\n
    \r\n
  • rw<\/code>: Allow read\/write access<\/li>\r\n
  • sync<\/code>: Synchronous writes (safer)<\/li>\r\n
  • no_subtree_check<\/code>: Disable subtree checking (better performance)<\/li>\r\n
  • no_root_squash<\/code>: Allow root access (use with caution)<\/li>\r\n<\/ul>\r\n<\/td>\r\n<\/tr>\r\n
Example<\/strong><\/td>\r\nZDTREP_NFS_OPTIONS=rw,sync,no_subtree_check<\/code><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<\/figure>\r\n\r\n\r\n\r\n

Advanced Options<\/h2>\r\n\r\n\r\n\r\n

ZDTREP_METADATA_OPTIONS<\/h3>\r\n\r\n\r\n\r\n

Additional options for DRBD metadata creation.<\/p>\r\n\r\n\r\n\r\n

\r\n\r\n\r\n\r\n\r\n\r\n
Default<\/strong><\/td>\r\nEmpty<\/td>\r\n<\/tr>\r\n
Description<\/strong><\/td>\r\nThese options are passed directly to the ‘drbdadm create-md’ command<\/td>\r\n<\/tr>\r\n
Example<\/strong><\/td>\r\nZDTREP_METADATA_OPTIONS=--max-peers=32<\/code><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<\/figure>\r\n\r\n\r\n\r\n

ZDTREP_RESOURCE_NAME_PREFIX<\/h3>\r\n\r\n\r\n\r\n

Prefix for DRBD resource names.<\/p>\r\n\r\n\r\n\r\n

\r\n\r\n\r\n\r\n\r\n\r\n
Default<\/strong><\/td>\r\netcd-data<\/code><\/td>\r\n<\/tr>\r\n
Description<\/strong><\/td>\r\nThe full resource name will be this prefix followed by the node ID<\/td>\r\n<\/tr>\r\n
Example<\/strong><\/td>\r\nZDTREP_RESOURCE_NAME_PREFIX=etcd-data<\/code><\/td>\r\n<\/tr>\r\n<\/tbody>\r\n<\/table>\r\n<\/figure>\r\n\r\n\r\n\r\n

Creating and Editing the Configuration File<\/h2>\r\n

 <\/p>\r\n

The zdtreplicate.env<\/code> configuration file is available for download from the ZDT DevOps community repository on GitHub:<\/p>\r\n

\ud83d\udc49 Download zdtreplicate.env<\/a><\/p>\r\n

After downloading, place it in your configuration directory:<\/p>\r\n

<your ZDT DevOps Installation path>\/DevOps\/config\/zdtreplicate.env\r\n<\/code><\/pre>\r\n
Then, set the appropriate permissions:<\/p>\r\n
sudo chmod 644 <your ZDT DevOps Installation path>\/DevOps\/config\/zdtreplicate.env\r\n<\/code><\/pre>\r\n
You can still use your preferred text editor (e.g., nano<\/code>, vim<\/code>, code<\/code>) to review or customize the configuration file as needed.<\/p>\r\n\r\n\r\n\r\n
Configuration Examples<\/h2>\r\n\r\n\r\n\r\n
Primary Node in Main Datacenter<\/h3>\r\n\r\n\r\n\r\n
ZDTREP_NODE_TYPE=primary\r\nZDTREP_NODE_ID=nodeA\r\nZDTREP_CLUSTER_ADDR=192.168.1.1\r\nZDTREP_DISK_DEVICE=\/dev\/sdb1\r\nZDTREP_DATA_DIR=\/var\/lib\/etcd\r\nZDTREP_REPLICATION_PROTOCOL=C\r\nZDTREP_REPLICATION_PORT=7788\r\nZDTREP_NFS_ENABLED=true\r\nZDTREP_NFS_EXPORTS_DIR=\/mnt\/etcd-data<\/code><\/pre>\r\n\r\n\r\n\r\n
Secondary Node in Main Datacenter<\/h3>\r\n\r\n\r\n\r\n
ZDTREP_NODE_TYPE=secondary\r\nZDTREP_NODE_ID=nodeB\r\nZDTREP_CLUSTER_ADDR=192.168.1.2\r\nZDTREP_DISK_DEVICE=\/dev\/sdb1\r\nZDTREP_DATA_DIR=\/var\/lib\/etcd\r\nZDTREP_PRIMARY_ADDR=192.168.1.1\r\nZDTREP_REPLICATION_PROTOCOL=C\r\nZDTREP_REPLICATION_PORT=7788<\/code><\/pre>\r\n\r\n\r\n\r\n
Mirror Node in External Datacenter<\/h3>\r\n\r\n\r\n\r\n
ZDTREP_NODE_TYPE=mirror\r\nZDTREP_NODE_ID=dcmirror\r\nZDTREP_CLUSTER_ADDR=10.0.0.1\r\nZDTREP_DISK_DEVICE=\/dev\/sdb1\r\nZDTREP_DATA_DIR=\/var\/lib\/etcd\r\nZDTREP_PRIMARY_ADDR=192.168.1.1\r\nZDTREP_SECONDARY_ADDR=192.168.1.2\r\nZDTREP_REPLICATION_PROTOCOL=A\r\nZDTREP_REPLICATION_PORT=7788\r\nZDTREP_BANDWIDTH_LIMIT=10M<\/code><\/pre>\r\n\r\n\r\n\r\n
Troubleshooting<\/h2>\r\n\r\n\r\n\r\n
If you encounter issues with your configuration:<\/p>\r\n\r\n\r\n\r\n
    \r\n
  1. Verify that the configuration file exists in the correct location (<your ZDT DevOps Installation path>\/DevOps\/config\/zdtreplicate.env<\/code>)<\/li>\r\n
  2. Check that the file has the correct permissions (readable by the ZDT system)<\/li>\r\n
  3. Check the log file specified in ZDTREP_MONITOR_LOG_PATH<\/code><\/li>\r\n
  4. Verify that the disk device specified in ZDTREP_DISK_DEVICE<\/code> exists and is not in use<\/li>\r\n
  5. Ensure network connectivity between nodes on the port specified in ZDTREP_REPLICATION_PORT<\/code><\/li>\r\n
  6. Check firewall rules to allow DRBD traffic between nodes<\/li>\r\n<\/ol>\r\n\r\n\r\n\r\n
    Conclusion<\/h2>\r\n\r\n\r\n\r\n
    The ZDT Replicate configuration system is designed to be flexible yet straightforward, allowing you to set up complex replication topologies with minimal effort. By properly configuring the parameters described in this guide and placing the configuration file in the correct ZDT DevOps config directory, you can create a robust Zero Downtime infrastructure that protects your data against both hardware failures and datacenter outages.<\/p>\r\n\r\n\r\n\r\n\r\n\r\n
    If you have questions or need assistance with your ZDT Replicate configuration, please reach out to our support team.\u00a0<\/p>\r\n
    Error:<\/strong> Contact form not found.<\/p>\r\n\r\n\r\n\r\n
     <\/p>\r\n","protected":false},"excerpt":{"rendered":"
    ZDT Replicate: Complete Configuration Guide Welcome to our comprehensive guide on configuring ZDT Replicate, a powerful tool that simplifies DRBD (Distributed Replicated Block Device) management for Zero Downtime deployments. Whether you’re setting up high availability within a single datacenter or implementing disaster recovery across multiple sites, this guide will help you understand all available configuration […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[60,3,24,59],"tags":[72,75,77,66,76,74,65,62,71,79,69,64,68,67,78,73,70,80,61,63],"class_list":["post-498","post","type-post","status-publish","format-standard","hentry","category-configuration-guides","category-devops","category-security","category-zdt-devops-guides","tag-asynchronous-data-mirroring","tag-block-level-replication","tag-cross-datacenter-replication","tag-data-synchronization","tag-datacenter-failover","tag-devops-configuration-management","tag-disaster-recovery-solutions","tag-drbd-configuration","tag-drbd-synchronous-replication","tag-enterprise-data-protection","tag-etcd-data-replication","tag-high-availability-replication","tag-kubernetes-storage-replication","tag-multi-datacenter-replication","tag-network-bandwidth-management","tag-nfs-configuration-for-kubernetes","tag-zdt-devops-platform","tag-zdt-platform-configuration","tag-zdt-replicate","tag-zero-downtime-devops"],"blocksy_meta":[],"_links":{"self":[{"href":"https:\/\/zdtdevops.com\/web\/wp-json\/wp\/v2\/posts\/498","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/zdtdevops.com\/web\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/zdtdevops.com\/web\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/zdtdevops.com\/web\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/zdtdevops.com\/web\/wp-json\/wp\/v2\/comments?post=498"}],"version-history":[{"count":7,"href":"https:\/\/zdtdevops.com\/web\/wp-json\/wp\/v2\/posts\/498\/revisions"}],"predecessor-version":[{"id":542,"href":"https:\/\/zdtdevops.com\/web\/wp-json\/wp\/v2\/posts\/498\/revisions\/542"}],"wp:attachment":[{"href":"https:\/\/zdtdevops.com\/web\/wp-json\/wp\/v2\/media?parent=498"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/zdtdevops.com\/web\/wp-json\/wp\/v2\/categories?post=498"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/zdtdevops.com\/web\/wp-json\/wp\/v2\/tags?post=498"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}