AnsweredAssumed Answered

Broken links in remote container

Question asked by sprosser on Dec 14, 2016
Latest reply on Dec 16, 2016 by sprosser

I've got a solution using remote containers that's still in development. During the last development cycle, the staff uploaded about a hundred documents, which they tell me appeared properly. I delivered a new build and deployed it on the server, overwriting the file they'd put the data into. Only after the new build was installed did I learn that they'd placed the documents and wanted them migrated.

 

No problem, I thought, I'll just take a backup, turn off remote storage, and then import the table from the backup into my new build and turn remote storage back on. However, all their backup files going back to the day they'd placed the documents show broken links for every document.

 

I spot-checked a few documents, and they are living in the server where we expect them to be, so that's not the problem. Is there a fix for this that doesn't involve making them re-import or me writing a script to re-import everything? And for bonus points, does anybody have any educated guesses on what might have happened to break all the links.

Outcomes