We have migrated Confluence spaces from one instance to another but the attachments did not migrate (they were in the database, I have since pulled out the attachments from the database). Is there a tool of any sort to help me easily find the attachments for the spaces?
I have these sites bookmarked:
However we have thousands of attachments. Is there an easier way to find the attachment storage mapping, such as a program or calculator where I can just put in the necessary information (space id, content id) and it will give me the appropriate folder name/id?
Apologies for the delay; I was on holiday. Before I confirm, can you let me know the Confluence versions of the original site and the destination site?
When you say that the attachments did not migrate, and that they were pulled out of the database, are you saying that you recovered the attachments from the database after migrating them, or that you had removed them from the database prior to migrating? What process exactly did you use to migrate the space from one to another? Was it a full space backup or select pages?
The attachments were in the database during the migration (the migration included changing to a new database). This was realized after the migration was complete. I then went back into the original instance and pulled the attachments out of the database within Confluence's UI. The process used to migrate the spaces was a full space export.
Thank you for clarifying that. Could you share with me the version of the original and source instances of Confluence? With the article I sent you earlier, it won't fix your issue.
Confluence versions 5.4 and earlier gave administrators the ability to store attachments in the database. However, in later versions, there's a task that is supposed to migrate those attachments into the filesystem. If you are migrating from 5.4 or earlier, then you can only migrate to the same Confluence version.
The problem is that when you import a space, the pageIDs change, so there's no way to add your attachments afterward.
Your solution is to first fix the attachments in your source instance, so that they are stored in the local filesystem. See Attachment Storage Configuration for more details.
Let me know if you have any trouble.
Since the migration was already performed and live in production we cannot perform either of the above suggestions. Thank you for your assistance, it seems we will just have to map out the attachment locations from the old instance to the new instance and manually migrate them.
- Create your own custom emoji 🔥 - "Shake for Feedback" on mobile 📱 - An endless supply of GIFs via GIPHY 🤩 Is there anything quite as nice as a pleasant surprise? Comment below with what...
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