FireBoard
Welcome, Guest
Please Login or Register.    Lost Password?
Re:Extracting data upon failure (1 viewing) (1) Guest
Go to bottom Post Reply Favoured: 0
TOPIC: Re:Extracting data upon failure
#506
Sugarat (User)
Fresh Boarder
Posts: 2
graphgraph
User Offline Click here to see the profile of this user
Extracting data upon failure 2 Months, 2 Weeks ago Karma: 0  
Hi All,

I'm new to OpenKM and have a question. I just started using another DMS but it strangely died out of the blue. I'd like to switch to OpenKM but my concern is how to retrieve files should OpenKM ever go wrong. I'm not that fussed about the file metadata, but should I need to get to the uploaded files in a situation where OpenKM was broken, how could I do so?

It looks like the files are kind of 'sucked' into OpenKM and cannot be found on the servers local filesystem?

Any tips to ease my nervousness about putting loads of info into OpenKM?

Thanks,

Adam
 
Report to moderator   Logged Logged  
  The administrator has disabled public write access.
#507
jllort (Admin)
Admin
Posts: 186
graphgraph
User Online Now Click here to see the profile of this user
Re:Extracting data upon failure 2 Months, 2 Weeks ago Karma: 4  
Don't worry.

Files on OpenKM can be stored on several ways, dbms ( postgre, mysql, oracle ) or file system.

By default The OpenKM configuration save files on file system under Jboss/repository, but are saved on a special structure - refer to jackrabbit if you want more information about it.

One think that always we've got present since starting OpenKM is that end user is owner of files, and if want to move to other system this must be done easilly, we think it's some to evaluate comparting to other dms.

You must not try to recover - find - files from this structure (it's special blobs structure not tipical to facilite fast access and other improvements). On OpenKM there's a way to export all data structure to normal server file system. Connect as system user, go to admin menu options, an select export option.

Take a look at this threath about exporting option.
 
Report to moderator   Logged Logged  
 
Be open my friend
  The administrator has disabled public write access.
#508
Sugarat (User)
Fresh Boarder
Posts: 2
graphgraph
User Offline Click here to see the profile of this user
Re:Extracting data upon failure 2 Months, 2 Weeks ago Karma: 0  
Hi,

I'm not really sure how you can say 'Dont worry' because OpenKM can export all files. Thats not much good if OpenKM is borked and won't start for some reason. I won't have the expertise to start it up again, which is why having the files stored as binary blobs makes me nervous. If OpenKM is dead then I've lost all the files?
 
Report to moderator   Logged Logged  
  The administrator has disabled public write access.
#509
jllort (Admin)
Admin
Posts: 186
graphgraph
User Online Now Click here to see the profile of this user
Re:Extracting data upon failure 2 Months, 2 Weeks ago Karma: 4  
See files names on file system not ensures that if your computer corrupts you recover it. It's not a problem about how files are stored, is a problem if you don't make backups of OpenKM or other file system, database etc...

For example if your dms stores on a DBMS could not be so easy to know a direct correspondence about what you see on front and how is stored information on dbms. If you backup correctly database you don't lost information if your server corrupts that's the same idea.

You must ensure you backup well OpenKM like other system, and we recomend of course on production environment to have a UPS.

I talk about export, because some dms, especially some comertial ones, makes difficult to export files from theirs repositories, why ?

About OpenKM backup, if you install as you download, without modifying repository.xml parameters you must ensure to backup /Jboss/repository directory
 
Report to moderator   Logged Logged  
 
Be open my friend
  The administrator has disabled public write access.
Go to top Post Reply
Powered by FireBoardget the latest posts directly to your desktop