{"meta":{"title":"Backup in clustering mode","intro":"Enable backup from a node in cluster.","product":"Enterprise administrators","breadcrumbs":[{"href":"/en/enterprise-server@3.22/admin","title":"Enterprise administrators"},{"href":"/en/enterprise-server@3.22/admin/backing-up-and-restoring-your-instance","title":"Back up and restore"},{"href":"/en/enterprise-server@3.22/admin/backing-up-and-restoring-your-instance/backup-in-clustering-mode","title":"Backup in clustering"}],"documentType":"article"},"body":"# Backup in clustering mode\n\nEnable backup from a node in cluster.\n\n## Configuring backups from a cluster node\n\nFor clustering, you can designate a node as your backup server. To minimize latency, GitHub recommends picking a data node (for example, a `mysql-server` node or a `git-server` node) instead of a frontend node.\n\n> \\[!IMPORTANT]\n> Only one node can be specified as a `backup-server` node.\n\n1. To configure your backup server, run the following commands to set up a backup disk on one of the cluster nodes of your choice. See [Configuring the backup service](/en/enterprise-server@3.22/admin/backing-up-and-restoring-your-instance/configuring-the-backup-service).\n\n```shell\nghe-storage-init-backup /dev/YOUR_DEVICE_NAME\n\nghe-config-apply\n```\n\n1. After `ghe-config-apply` is executed, the `backup-server` role will be set on this cluster node. You can now run `ghe-backup` directly on this node, or use the management console to schedule backups."}