What exactly is in the backup? Why would a database backup (sql server for example) not be sufficient. (I'm arguing with server admin about this). I need ammo. And probably a flak vest. Maybe a helmet.
I know the backup has config data but does the config change that often? Is it updated everytime you modify a build? What specifically would change in the backup that would make it important to run the backup frequently.
A database backup will only be sufficient if you also back up the home directory separately. For large instances, a checkpointed, journaled database (with standard db backup procedures) together with an FS-backup is the recommended backup strategy.
It's fastest, incremental and does not involve a Bamboo outage.
Can you go into this in more detail? Are there official Bamboo docs around setting up this approach?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Przemyslaw Bruski would it be possible to clarify on the questions @Matt Shelton brought up please?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
A database backup should be sufficient for daily backups. But you should back up Bamboo for configuration information - including the details of your database (!). The config information does not change that much - mainly when you change something through the Administration page. Plans and their details are stored in the database.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well artifacts for 1.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.