This chapter provides guidance for backing up your
If you are using CloudBees CI, you also have the option to use the CloudBees Backup Plugin for backup and recovery.
If you are performing a manual backup of CloudBees CI or Jenkins, the recommended manual backup process is to schedule a cron job on a regular cadence to create a tarball of your
The basic steps for backup:
There is no need to stop Jenkins when performing a backup.
Things to consider:
Refer to Explaining $JENKINS_HOME to determine what you want to include in your backup.
Store backup files on a different server for better security and in case of data corruption.
Store backup files on a different network for better security and in case of data corruption.
In CloudBees CI on traditional platforms, you can backup
$JENKINS_HOME manually using the following command. In the following example, you are directly logged in (remotely via SSH or physically on the machine at a command-line terminal):
Navigate to your
$JENKINS_HOMEconfiguration from the command line:
Create a compressed file:
tar -czvf /backups/jenkins_home/production-backup-2021-10-26.tar.gz .
|The CloudBees Backup Plugin steps you through creating an operations center job for both backup and recovery. Even if you prefer to create your backups manually, consider setting it up as an operations center job that backs up everything across all controllers.|
If running in Kubernetes, and your pod is still up and running, you can back it up manually using the following commands. In the following example, the controller is called
kubectl get pods -n cloudbees-ci kubectl exec -n cloudbees-ci -it production-0 -- sh cd /var tar -cf - jenkins_home/ | gzip > /tmp/production-backup-2020-10-06.tar.gz exit kubectl cp -n cloudbees-ci production-0:/tmp/production-backup-2020-10-06.tar.gz ./production-backup-2020-10-06.tar.gz du -m ./production-backup-2020-10-06.tar.gz