Mark Bucciarelli wrote:

I just had to restore a database dump, and I got nervous watching top. The box, which doesn't have much RAM, started to swap on the restore. At times, the monetdb process was using over 90% of available RAM.

MonetDB uses the memory available.

While I only have 500M RAM, the database only has 10m records. The gzipped dump is 142MB.

gzipped version does not tell anything about the actual database size. MonetDB does not use internally compressed files (aside form dictionary compression)

Other than the backup/restore issue, Monet seems quite happy running with this much data and so little RAM. It looks like it could support much more data---but I'm not so sure the restore will.

If I run

       $ monetdb stop -a

can I safely tar the database files and use that as a backup?

yes if you completely take the dbfarm/<database> you can safely transfer it

Or do I need to stop merovingian too?

Or is this approach not safe?

Thanks,

Mark

---

The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users

On 09-02-2010 11:10:31 -0500, Mark Bucciarelli wrote:

If I run

       $ monetdb stop -a

can I safely tar the database files and use that as a backup?

you better also $ monetdb lock <db1> <db2>

to make sure no users will actually accidentially start up the databases by connecting to it. Best: first lock, then stop.