Usually our backups have consistend of doing a mysqldump and backing up specific directories under .BuildServer but reading over the backup instructions in your docs it does state to stop the TeamCity server which we do not do. Up reading further I see the api supports executing a backup command which we could run and not backup the aftifacts. When this is running will TeamCity be accessible? Does it still run the builds?
It's my understanding that while the backup is running, no new builds are scheduled. Any existing builds on the agents will continue to run.
The backup usually doesn't take too long, about 5-10 minutes on my system which is pretty large. I have a cron job that fires a perl REST script to start
the backup and then monitor it for status.
Our system is quite big and the backup without artifacts took 5h28m. The bulk of the time was build logs. I did some experimentation though during the backup process and found out that during the build log backup phase I was able to run builds so maybe builds are only held up when backing up the database. I guess we'll have to decide whether or not the build logs are important to us in the event of a disaster. Can someone from jetbrains comment on this? We have about 1k build configurations and our build history cleanup is 90 days.