We have created a Stash 3.0.1 backup using stash backup client 1.9.0 on Windows. When we tried to restore it on a CentOS machine, the restore failed with
stash-20150519-104526-716.tar could not be restored. Reason: /data/stash-data/system.zip (No such file or directory)
(/data/stash-data/ is my home directory, where I try to restore to)
I enabled DEBUG logging for the backup client, but it did not provide anything additional that seems useful.
2015-05-28 17:40:25,859 DEBUG Adding jar sqljdbc-4.0.2206.jar to the classpath 2015-05-28 17:40:25,869 DEBUG Adding jar postgresql-9.4-1201-jdbc41.jar to the classpath 2015-05-28 17:40:25,870 DEBUG Adding jar hsqldb-2.2.4.jar to the classpath 2015-05-28 17:40:25,870 DEBUG Adding jar ojdbc6-220.127.116.11.0.jar to the classpath 2015-05-28 17:40:25,896 INFO Initializing 2015-05-28 17:40:27,019 INFO Unpacking stash-20150519-104526-716.tar to /data/stash-data 2015-05-28 17:42:38,105 DEBUG Unpacking system backup to /data/stash-data 2015-05-28 17:42:38,133 ERROR stash-20150519-104526-716.tar could not be restored. Reason: /data/stash-data/system.zip (No such file or directory) java.io.FileNotFoundException: /data/stash-data/system.zip (No such file or directory) at java.io.RandomAccessFile.open(Native Method) ~[na:1.7.0_79] at java.io.RandomAccessFile.<init>(RandomAccessFile.java:241) ~[na:1.7.0_79] ... 12 more frames available in the log file
I have checked the backup file, and it indeed does not contain any system.zip, despite being huge (27GB). What is this system.zip file and what could be reason for it gone missing?
We've seen this problem happening on this bug report:
It surprises me though you said the backup is from a 3.0.1 instance.
If you backup an instance that is 2.7.5+ or 2.8.3+ with the latest backup tool, that shouldn't happen.
Can you make sure of that and, in case you can't solve it, raise an issue with us? https://support.atlassian.com.
I know this is an old thread but this is at the top of Google results for this issue. I have just experienced a similar issue.
The system.zip seems to contain the database backup so is rather important.
In our case when we checked the tar file generated by the backup client the system.zip had a file size of 0b.
This was using version 3.3.3 of the client with a 4.8 instance of bitbucket server.
Short of taking a new backup there isn't much that can be done.
Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...
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