Hi Rajiesh, 1. I've tried in both scenarios, restoring a backup from 16.6, as well as from another 16.7 version. 2. It's installed on CentOS 7
I'll investigate now verifying the database restore and check the sizes. We've rolled back to 16.6 and we did manage to restore the same backup there. Has the restore procedure changed between 16.6 and 16.7? Our restore script hasn't changed. Thanks, Chris On 18 August 2016 at 13:49, Rajiesh Narayanan <[email protected]> wrote: > Hi Chris, > > We checked our regression for 16.7 release and the backup functionality is > not broken. However we would like to understand your scenario more in > detail. > > As we understand from your issue a possible reason for losing the > pipelines history is if the database backup is not restored properly. Could > you please help us with few information, > > > 1. Is the back up taken from 16.7 version of Go server or previous > version? If previous version please let us know the version number > 2. Go server is installed on which OS? > 3. Could you please confirm if the database backup restored > successfully? > 4. Is there a significant difference in the size of *'cruise.h2.db'* > file extracted from *'<BACKUP_DIR>/db.zip'* and the one in > *'<SERVER_INSTALLATION_DIR>/db/h2db/'* folder?. If the database > restore was not successful, Go server restart would have created a new > database file and its size would be about ~2.4MB > > > Thanks, > Rajiesh > > > On Thu, Aug 18, 2016 at 3:51 PM, Chris Northwood <[email protected]> > wrote: > >> Hi there, >> >> We've spotted a major regression on updating to Go 16.7, in that it >> appears backups no longer capture the history of a pipeline. When we >> restore a backup, we lose all pipeline history, and all pipelines instantly >> restart, including ones which were previously suspended. >> >> Our deployment pattern for Go follows the "Phoenix server" pattern, in >> that all boots happen from a golden master, and then on boot the most >> recent backup is restored in order to restore configurations, etc, so the >> ability to restore pipeline history is a crucial part of our workflow. >> >> Is this a known issue, or a new one? Or has the backup/restore procedure >> changed (although we still appear to be following the procedure in the >> documentation)? >> >> Regards, >> >> *Chris Northwood* >> >> Senior Technologist, UX >> BBC Research & Development, Dock House, 5th Floor, MediaCityUK, Salford >> M50 2LH >> >> -- >> You received this message because you are subscribed to the Google Groups >> "go-cd" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
