Missing Attachments - JIRA Migration

[Sravya Vuggina]

We are migrating from cloud instance to server and as part of the import attachment process, manually copied files to JIRAHOME/data/attachments folder. Due to some reason not all files were copied and as a result the attachments are missing in the new instance. Below is the log from import process (used Configuration Manager to deploy a snapshot from staging server). 

I am having trouble finding ways to import these missing attachments to new instance. Tried copying the physical files to default location and restarted JIRA hoping it would magically pick them up from the file system but no luck. What are my options here. 

2018-07-29 16:44:15,403 pool-47-thread-1 WARN VUS1OWT 987x1306x1 1275cb4 10.230.178.45 /rest/configuration-manager/1.0/deployment/2 [c.b.j.r.impl.issuedata.IssueDataMergeInterceptor] Failed to import attachment Script Errors 06-19-2017.xlsx for issue with key IAMNACD-4446.
2018-07-29 16:44:15,403 pool-47-thread-1 WARN VUS1OWT 987x1306x1 1275cb4 10.230.178.45 /rest/configuration-manager/1.0/deployment/2 [c.a.j.issue.managers.DefaultAttachmentManager] Got exception while saving attachment in attachment store. Exception: D:\JIRA\data\attachments\IAMNACD\10000\IAMNACD-4446\164471 (The system cannot find the path specified)

[Alexey Matveev]

Hello,

Why not all files were copied? You can try to take a backup from the Cloud instance again and put attachment again to the Jira_home/data/attachments folder.

[Sravya Vuggina]

Are you suggesting to migrate again? We have our server instance up and running now so its preferred to not take whole backup from cloud (no longer used). Can we just migrate the attachments? 

[Alexey Matveev]

I mean try to migrate only attachments

[Sravya Vuggina]

This is what we tried - Copied all the files (complete set) to the attachments folder on server (overwrote partially copied files) and restarted JIRA server. Missing attachments are still not found. Am i missing something here?

[Vickey Palzor Lepcha]

Assuming you placed all attachments in the right location - try re-indexing your environment.

[Sravya Vuggina]

Tried re-indexing just now- No luck there as well. Verified the attachments location in System > Attachments > Attachments Path. 

[Alexey Matveev]

It is strange.  Attachments must be seen, if they are valid attachments

[Vickey Palzor Lepcha]

Is this happening for all the attachments that you've moved from JIRA CLOUD ?  Or do you see some of them in your on-prem JIRA 

[Sravya Vuggina]

This is only for few, out of 7 projects that were moved - 6 projects imported completely. Only one project imported 10% of the attachments. 

@Alexey Matveev : Was thinking the same. During migration not all files were copied to attachments folder so I understand if there were no traces of it in fileattachments table but after copying the files to respective folders and restarting JIRA (and re-indexing) also there are no traces of the newly copied files in database and UI. 

[Sravya Vuggina]

We did the migration yesterday and today people added few attachments to the production server and they seem to be working fine. But no sign of the missing files. 

Took the snapshot of production server and deployed to a testing server with full attachment files (files backed up from cloud instance and the new ones created today) hoping that the deployment will pick up all the attachments. However, only the ones attached today got imported. Please note: all this is done using Configuration Manager plug-in. 

[Alexey Matveev]

I did migration with Configuration Manager as well and it worked just fine with attachments. I am not sure what is wrong in your instance.

[Sravya Vuggina]

It was not an issue with Configuration Manager but we haven't payed attention while manually copying attachments to temp folder in PROD server and ended up not being able to pick while using config manager (because the files don't exist in the pointed location).

We couldn't come up with an optimized solution to upload missing files without having to bring down the prod server so here is what we did - 

Exported all the issues created/modified on Monday(for later reference). Copied ALL attachments from to temp folder (this time ensured all files got copied) and re-deployed the snapshot from staging server. This helped in restoring all the issues and related files - of course to the time of snapshot, and all the issues created/ modified on Monday had to be redone. 

Thanks @Alexey Matveev and @Vickey Palzor Lepcha for taking time to assist.