# Locating com.bar.foo:example:123:jar in a 50TB S3 bucket when Nexus3 fails to start
**URL:** https://community.sonatype.com/t/locating-com-bar-foo123-jar-in-a-50tb-s3-bucket-when-nexus3-fails-to-start/2420
**Category:** Sonatype Nexus Repository
**Created:** [September 2, 2019, 1:21pm UTC](https://community.sonatype.com/t/locating-com-bar-foo123-jar-in-a-50tb-s3-bucket-when-nexus3-fails-to-start/2420 "2019-09-02T13:21:54Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@mcarneholm](https://community.sonatype.com/u/mcarneholm)
#### Post date: [September 2, 2019, 1:21pm UTC](https://community.sonatype.com/t/locating-com-bar-foo123-jar-in-a-50tb-s3-bucket-when-nexus3-fails-to-start/2420/1 "2019-09-02T13:21:54Z")
So, this is (so far) a purely hypothetical question - but let’s say that Nexus (3.x) for some reason can’t be started, and that you have a whole team of developers (and their nervous manager) who are urgent to make a production hotfix deploy of `com.bar.foo:example:123:jar`.
With Nexus 2.x you could have fetched the jar file from the `com/bar/foo/example/123` directory, but how would you quickly find this specific jar file in a 50TB S3 bucket that contains the blob store files created by Nexus3?
---
### Author:  [@mprescott](https://community.sonatype.com/u/mprescott)
#### Post date: [September 3, 2019, 6:50pm UTC](https://community.sonatype.com/t/locating-com-bar-foo123-jar-in-a-50tb-s3-bucket-when-nexus3-fails-to-start/2420/2 "2019-09-03T18:50:48Z")
The blob store’s index is held inside NXRM’s embedded Orient database, so if for some reason you can’t start NXRM 3, you could use a [standalone Orient client .jar to connect to the embedded database](https://support.sonatype.com/hc/en-us/articles/115002930827-Accessing-the-OrientDB-Console). (Or a recent backup of it, if your hypothetical NXRM 3 instance is damaged.)
Alternately, you can look in the properties files that are stored alongside the blobs—these hold the repository name and coordinates in case of a restore-from-blobs scenario. Accessing these probably isn’t quick for a 50 TB blob store, however.
I don’t advise ever _updating_ the blobs outside of NXRM 3, however, as that will confuse NXRM when it eventually gets up and running.
---
### Author:  [@mcarneholm](https://community.sonatype.com/u/mcarneholm)
#### Post date: [September 4, 2019, 9:42am UTC](https://community.sonatype.com/t/locating-com-bar-foo123-jar-in-a-50tb-s3-bucket-when-nexus3-fails-to-start/2420/3 "2019-09-04T09:42:20Z")
@mprescott Thanks, that was however what I feared. After reading various reports of corrupted Orient databases, I concluded that the Nexus2 way of storing artifacts is a better solution for mission critical operation: regardless of whether Nexus2 is running or not, you’ll always be able to find com/somecompany/urgentlyneededfile/123 by just navigating to that location in the file system.
The NXRM 3 storage approach might be optimized for GUI searches, but it seems like it introduces a risk in mission critical situations when Nexus for some reason doesn’t start due to a corrupted DB 😐