| Subject | Re: [ib-support] Backup and restore of a database |
|---|---|
| Author | Helen Borrie |
| Post date | 2003-03-18T05:21:05Z |
At 03:05 PM 18/03/2003 +1000, you wrote:
with the -force switch if necessary.
the database. That's a good test for whether it's clear to carry on
maintenance. (Gbak backups and sweeps don't need a shut-down db though...)
can't manage to overwrite an open DB file but I can't say whether other OS
variants will allow it. Another problem that can give corruption occurs if
you allow users to log in during a database restore. Once the operating
system has begun to lay down the file to disk, there's nothing to stop this
happening.
can then log in. You will have exclusive access then until you log
out. Warning: if another user tries to log in as sysdba, owner or root,
shutdown won't stop them. I assume you have these basic security things
taken care of.
heLen
> > You shouldn't be renaming database files in their normal location whileYes. You need to get exclusive access by performing a gfix -shut[down]
>the
> > server is running, anyway. Of course you can expect corruption if you try
> > to do any filesystem-level things to the database whilst users are
> > connected, or trying to connect. You can't fix a puncture on a moving
>vehicle!
>
>Is it possible to disconnect a single database without taking down the whole
>server?
with the -force switch if necessary.
>I need to run 2 applications and allow access to one whileNo. In fact, if any connections are active, you won't be able to rename
>maintaining the other.... Also, is renaming a database the same as copying
>the file? That is, can renaming the file corrupt the database as well?
the database. That's a good test for whether it's clear to carry on
maintenance. (Gbak backups and sweeps don't need a shut-down db though...)
>IYes, for sure you can copy it while connected (but don't!) On Win2K, I
>seem to be able to copy a database while connected and copy it back over
>itself....
can't manage to overwrite an open DB file but I can't say whether other OS
variants will allow it. Another problem that can give corruption occurs if
you allow users to log in during a database restore. Once the operating
system has begun to lay down the file to disk, there's nothing to stop this
happening.
>Not recommended that you try this at home.... However, if youEggzackerly...ONLY if no-one is connected - not even sysdba.
>try to rename the file, it says it is in use... Is it safe to rename an
>interbase database? If it works no one was connected...?
> > You shouldn't even try to perform metadata updates whilst you don't haveYes - do a shutdown -force. Once the shutdown is in effect, nobody else
> > exclusive access to the database...
>
>Is it possible to enforce this without shutting down the server?
can then log in. You will have exclusive access then until you log
out. Warning: if another user tries to log in as sysdba, owner or root,
shutdown won't stop them. I assume you have these basic security things
taken care of.
>Also, whatJust try to rename it.
>can I check to ensure my database isn't currently in use?
heLen