Alfresco name from Linux filename

[swhitman]

Our backup software is griping about a file it is trying to backup. The Linux file system name: …/contentstore/2011/12/1/14/18/aa6e871f-c381-4d42-b9f7-0a088ce03668.bin causes the problem. How do I find out the name, directory and owner that Alfresco uses. I am running Alfresco 3.4.c on a 32-bit CentOS 5.5 system.

I have searched the forum already. I found 2 posts, but I did not understand the answers. One looked like java code was involved. The other said to do a query. But I did not recognize the format of the query and did not know if I was supposed to type into a search box in the Alfresco server web interface, or if it was a url fragment I needed to put in the address bar of the browser.

Any help would be appreciated.

Stu

[lotharmärkle]

This kind of "reverse lookup" (to find the alfresco node(s) that references a given binary file on disk) can only be done by looking at the alfresco database.

If you know the db schema of the 3.4 you could issue some SQL.

If not, and there are not too many documents in alfresco, you could try the query interface of the Node Browser:
Using query language 'selectnodes':

 
//*[starts-with(@cm:content, 'contentUrl=store://2011/12/1/14/18/aa6e')]
[/code]

But please keep in mind, this will not work with larger repositories, because this type of query will load every node from the database.‍‍‍‍‍

[mrogers]

What do you mean by "griping"?   When it comes to backing up the content store then as far as your backup stuff is concerned its just a plain file/folder service.

Your content store should also have permissions set such that only alfresco and the backup have access.

[swhitman]

I tried using the query interface of the node browser, but there must be too many documents because the query did not finish before I left to go home.

The griping had to do with the file size being greater than 2GB, a problem we fixed a while ago, but forgot to update on the Alfresco server. I was just trying to figure out the user so I could let them know of the problem.

I finally executed a unix "file" command on the file. It turned out to be an DVD iso image. The file command printed the DVD label, which gave me a clue as to which user uploaded the file.