$Header: /CVSROOT/public/scylla-charybdis/md5backup/MIGRATION,v 1.1 2005/07/17 00:52:20 tino Exp $ This always assumes the default working path /backup/md5backup/ Note that bin/migrate.sh probably does everything for you. AS THIS IS DEVELOPMENT CODE YOU CAN ONLY MIGRATE FROM ONE MINOR TO THE NEXT HIGHER MINOR (migration was introduced in 0.4.0). AS ALWAYS, THIS EXPECT BUGS! ########################## # Migrate 0.3.x to 0.4.x # ########################## Important: Never put the database on an NFS volume! 0) The only thing you must do, is to create /backup/md5backup/sql/ In case /backup/md5backup/dbm/ is a softlink, the softlink of sql/ can point to the same directory. Nothing else must be done at your side. Some things must be noted: 1) When md5backup runs the first time, it will do a full backup, as it must create a fresh database. If you don't want this, please run bin/migrate.sh 2) The database /backup/md5backup/dbm/ can be deleted as it's no more used in 0.4.x. If you want to be able to revert to 0.3.x then probably keep it, it does no harm. 3) The file store structure has not changed, such that 0.3.x and 0.4.0 are compatible. 4) If you want to do a full backup, remove the new database in sql/, not the one in dbm/ 5) The documentation probably is not correct everywhere. If you read dbm/ then please auto-correct it to sql/ where appropriate. ########################## # Migrate 0.4.x to 0.5.x # ########################## This section will be added as soon as 0.5.0 is reached, which might be more early than expected. 0.5.0 will render the file store structure incompatible to 0.3.x. $Log: MIGRATION,v $ Revision 1.1 2005/07/17 00:52:20 tino added