PDA

View Full Version : one file per database



offmct
April 3rd, 2008, 08:06 PM
I guess this has been asked before but it seems that the discussion did not push through. http://forums.zmanda.com/showthread.php?t=941&highlight=file+database

I would like to raise the question again. Can mysql-zrm do a single file per database backup? I am aware that mysql-zrm can restore a particular database from a single mysqldump file. However, if a very large database gets in the way of the particular database that I would like to restore, mysql-zrm can consume a lot of time before it can finish the restore procedure. (db_humongous comes before db_tiny in the output of mysqldump). If the output of mysqldump was written in one file per database, this would have been fast. This would come in handy if we want to do a restore quickly and save us from the wrath of our bosses.

Thanks a lot.

kkg
April 3rd, 2008, 08:13 PM
I guess this has been asked before but it seems that the discussion did not push through. http://forums.zmanda.com/showthread.php?t=941&highlight=file+database

I would like to raise the question again. Can mysql-zrm do a single file per database backup? I am aware that mysql-zrm can restore a particular database from a single mysqldump file. However, if a very large database gets in the way of the particular database that I would like to restore, mysql-zrm can consume a lot of time before it can finish the restore procedure. (db_humongous comes before db_tiny in the output of mysqldump). If the output of mysqldump was written in one file per database, this would have been fast. This would come in handy if we want to do a restore quickly and save us from the wrath of our bosses.

Thanks a lot.

Another mechanism you could use is to have different backupsets backup different databases.

Suggest you add your comment to the bug
http://forums.zmanda.com/bugzilla/show_bug.cgi?id=25

--kkg

offmct
April 3rd, 2008, 08:44 PM
That's a viable solution but usually, we backup the whole server using "all-databases=1" so that we don't have to worry about creating (or forgetting to create) a new backup set for the newly created database.

Right now, our solution would be to backup the whole server using "all-databases=1" and create a separate backup set for the same server which only includes the selected databases. Not optimal but nonetheless acceptable.

I guess I would file an enhancement at zmanda-bugzilla just a you suggested.

Thanks a lot kkg.