Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

entities.xml exportDescriptor.properties are missing from automated backups causing failed restores

Edited

OS: CentOS 7

Confluence: 6.6.1

When I attempt to restore confluence through the frontend UI and select a staged backup file, the restore fails with the error:

com.atlassian.confluence.importexport.actions.RestoreLocalFileAction.action.name

The zip file did not contain an entry 'exportDescriptor.properties'.

Then lists the thousands of attachments. 

 

I am not doing anything with Mac unzip/zip. 

The zip backup file is 8.3 GB compressed. Browsing the contents with vim, in addition to actually unzipping the file in linux - the files exportDescriptor.properties and entities.xml are both missing. I can see the files present in an old zipped backup from months ago. 

1. Is this a setting to reenable, that may have somehow got disabled? (to have the files be in the backup.zip 

2. Can I get these files from somewhere? Where? I assume then I can rezip in linux with the new files and should be good to restore again?

1 answer

0 votes
Shannon Atlassian Team Apr 08, 2019

Jason,

Welcome to Community! Thank you for reaching out.

To clarify, you're restoring Confluence and not Jira, correct? You mentioned Jira so I want to be sure.

Could you tell me more about how you obtained the backup file? Where did it come from, and how was it generated? You don't see the exportDescriptor.properties file at all? It's automatically included when the backup is generated from Confluence.

Regards,

Shannon

Correct. Apologies - it was a long day of troubleshooting. 

 

The backup file itself is a result of the daily scheduled backup through cron - configured in confluence's admin interface.

Backup Administration:

backup-admin-config.png

Scheduled Cron:

backup-scheduled-job.png

 

History:

backup-history.png

 

 

Correct, the exportDescriptor.properties file is completely missing from the zipped backup, and I'm as confused as you are. 

Shannon Atlassian Team Apr 09, 2019

Thanks, Jason.

We'll get to the bottom of this!

  1. This can also be caused by insufficient disk space, were you able to confirm your disk space on your server?
  2. Second, can you try manually creating a backup but without the attachments? I want to see if it includes the exportDescriptor.properties file when it doesn't backup the attachments.
  3. You want to make sure the backups are actually completing, so we want to troubleshoot them. Troubleshooting Failed XML Site Backups. Make sure to set DEBUGGING on, per step # 4 in the article.

Let me know how that goes.

Regards,

Shannon

Thank you for your help Shannon. I was able to figure out the problem. The Confluence instance we have is large, and the scheduled backup would not be completed before the scheduled cleanup would begin. Thus while the temp directory was being used as a staging place for the backup bits, the scheduled housekeeping started deleting files from the temp directory. So when the backup process finished, it was missing files from the zipped file. 

Like # people like this
Shannon Atlassian Team Apr 12, 2019

Jason,

Thank you for providing that update! Happy to hear you were able to resolve it.

Take care, and have a pleasant weekend.

Regards,

Shannon

Hi Jason,

I just want to thank you very much, as your hint was able to turn a long, frustrating  week of troubleshooting into success. Cheers to you!

 

Best regards,

Andreas

Like Shannon likes this

Jason,

thanks a ton for sharing your solution. We had the exact same issue during a periodic restore test and this forum thread came up in a Google search.

I don't want to imagine how many Confluence installations out there are unsuspectingly running without a working backup just because at one point, the backup started to take more than 2 hours every night and gets constantly sabotaged by the cleanup cron job since then. This is the stuff of nightmares.

@Shannon 
Has this ever been addressed by Atlassian in recent releases? E.g. by making the backup job more robust and by issuing notifications in case of an incomplete XML backup?
Or by restricting the scheduled cleanup task to files older than - say - 6 hours?

Best regards,
Florian

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Confluence Cloud

🏠 Say hello to the new Confluence Home!

Hi Atlassian Community, My name is DJ Chung, and I’m a Product Manager on the Confluence Cloud team. Today, I’m excited to share a new and improved version of Home. The new Home helps you ...

43,153 views 30 134
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you