Hi, Helix84,
On 08/27/2013 04:51 PM, helix84 wrote:
On Tue, Aug 27, 2013 at 6:53 PM, Thomas Ronayne
ronayne.tho...@gmail.com wrote:
doing the same with /var/lib/pgsql -- files are just files after all else is
said and done, eh? Stop PostgreSQL on both servers, do the rsync and restart
the
Hi guys,
I have a serious problem with the machine where I had my DSpace
installation. And I say 'had' because a few days that machine physically
died... I had a lot of DSpace data here, so now I have this question:
Assuming I have access to all the files of DSpace, and also to the
postgresql
Yes, it's possible to save it as long as the database is undamaged.
Your first step should be recovering the database on a new machine. If
it's intact, also copy the assetstore directory to a new installation
of DSpace (same version). When you have it working, you can verify
which bitstreams have
Hi miguel, sure there is...
Just follow any of the procedures of migrating a version to another (of
course... skipping the steps of code upgrading)
Basically:
1. Export the BBDD (normal database procedures..)
2. copy the assetstore
3. copy the log files and the solr/statistics/data files
Thanks for your help!
The main thing is I'm not 100% sure the database is undamaged, as the
system crashed unexpectedly, but I followed your instructions and here's
the result:
1) Exported the PSQL files to the new system, I had to reset the xlog
directory in order to let me run the PSQL
I'll consider the DB is corrupted as a given... :(
Don't give up. If you don't have proper backups (I'm assuming you
don't because otherwise you would have mentioned it) restoring the
database is the critical step.
Try doing pg_dump of your database. That might reveal errors in the
database. If
Fortunately I was able to recover a backup just a day prior to the
crash I restored the assetstore from that backup and also the pgsql
dump and it works perfectly now!
Thank you so much for your help guys, you saved me a lot of work! :-)
Regards.
2013/8/27 helix84 heli...@centrum.sk
On Tue, Aug 27, 2013 at 4:38 PM, Thomas Ronayne
ronayne.tho...@gmail.com wrote:
Any problem with doing that?
No, that's a perfectly good way to backup all the contents that
changes often (there are also other ways but this one is easy and
complete). Also remember to backup configuration, any
Helix84,
Kinda what what I thought -- sure beats unloading data base files. I'm
thinking just rsync /opt/dspace; ought to get everything (logs and all)
and doing the same with /var/lib/pgsql -- files are just files after all
else is said and done, eh? Stop PostgreSQL on both servers, do the
On Tue, Aug 27, 2013 at 6:53 PM, Thomas Ronayne
ronayne.tho...@gmail.com wrote:
doing the same with /var/lib/pgsql -- files are just files after all else is
said and done, eh? Stop PostgreSQL on both servers, do the rsync and restart
the DBMS on both. Maybe stop Tomcat, too, but that might be
10 matches
Mail list logo
