Error restoring from backup

[twv]

[Solved] Error restoring from backup

I am transferring accounts to a new server. I am using Admin Backup/Transfer and it's working fine except for one account. With it, I get the message "Unable to read backup_db: /home/user/backups/backup/domain/domain.db : Can't open file /home/user/backups/backup/domain/domain.db for reading."

When I untar the backup file and look in it, there is no file "backups/backup/domain/domain.db"

The user has one database, but it's used by a different domain. There is a file for the db at "backups/backup/other_domain/other_domain.db"

This is an account that was originally several different accounts that I combined into one some time ago. Could there be a config somewhere that's confusing the backup system?

 

[scsi]

I would search all the files in the backup. There might be a config file with the database name it in somewhere.

 

[twv]

Thanks for the reply. I took a look at the other_domain.db file and it turns out to be the DNS zone file. The domain in question's DNS is managed elsewhere, so I just have to figure out how to tell DA not to look for the zone file or else to create a dummy one.

 

[twv]

Adding a DNS zone for the domain on the old server before doing the backup/transfer fixed the problem.

 

[nobaloney]

My recollection is that the failure to resore a zone file (yes, they end in .db) shouldn't keep the backup from working. It may be reasonable to keep a DNS zone on directAdmin even if you don't use it (just be sure you don't use your nameserver for local lookups), since DirectAdmin also uses it as a definitive indicator of whether or not a domain is hosted on the server. It can be a dummy zone with no working lines (perhaps one for localhost), but if it were there, it should prevent the warning on restore.

Note there are things uses can do which cause errors during restores and backups; we see them from time to time.

Jeff