| Subject | Re: [firebird-support] Confused about delta files [SOLVED] |
|---|---|
| Author | Maury Markowitz |
| Post date | 2014-01-17T19:39:12Z |
On 2014-01-17, at 2:33 PM, Ann Harrison wrote:
However, in my case, the presence of the failed nbackup meant that the delta file it left behind also had to be copied. I'm actually surprised that simply copying both files actually solved the problem, but I suppose it did so because the original FDB had some sort of pointer to the existence of the delta. This is definitely *not* something that the documentation covers.
Actually, from your post it would seem that the whole concept of simply coping the FDB is a bad idea anyway, and the proper solution would be to always use gbak?
>No, sorry, I meant to say that every reference I have ever found has suggested the "correct" way to move a FB database from one machine to another is to simply copy the FDB file while the server is down.
> Gbak is a backup/restore program that produces an architecture agnostic backup file. The backup file contains a logical representation of the format and contents of the database. Nbackup is a fast physical backup that supports incremental backups. Nbackup is not a database transport mechanism. If you found documentation that suggests using Nbackup as a transport, the Firebird Documentation group should know about it, because neither the database file nor the delta is architecture independent.
However, in my case, the presence of the failed nbackup meant that the delta file it left behind also had to be copied. I'm actually surprised that simply copying both files actually solved the problem, but I suppose it did so because the original FDB had some sort of pointer to the existence of the delta. This is definitely *not* something that the documentation covers.
Actually, from your post it would seem that the whole concept of simply coping the FDB is a bad idea anyway, and the proper solution would be to always use gbak?