Backup was working for some time. But it started failing after we migrated more repositories to stash. The error we received is:
WARN [threadpool:thread-995154] admin 1320x3126501x1 1utuvpt 172.16.100.94,0:0:0:0:0:0:0:1 "POST /mvc/admin/backups HTTP/1.1" c.a.s.i.m.LatchAndDrainDatabaseStep The DataSource could not be drained; some database connections are still open. Aborting migration...
WARN [threadpool:thread-995154] admin 1320x3126501x1 1utuvpt 172.16.100.94,0:0:0:0:0:0:0:1 "POST /mvc/admin/backups HTTP/1.1" c.a.s.i.m.DefaultMaintenanceTaskMonitor BACKUP maintenance has failed (Cause: BackupException: A backup file could not be created.)
If you are using Stash 3.2.2 you have to update to latest Stash Backup Client 1.3.0
But ... There is a known issue with Stash Backup Client 1.3.0 - which fails due to locked ".lock" file.
2014-08-27 04:40:42,852 ERROR [main] c.a.s.i.b.c.layout.DefaultStashHome E:\GitRepo\shared\.lock could not be read
This can be resolved by excluding those lock files.
For the time being, you can add this line in <tt>backup-config.properties</tt> to exclude <tt>.lock</tt> files as a workaround:
(suggested by Atlassian support desk)
Hi everyone, I am Marek, a Senior Product Manager for Crowd Server and Data Center here at Atlassian. I would like to spark a discussion about challenges you have with managing use...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs