I fully understand that, but someone was asking about the transaction(s)
that could happen during the gbak and they fact that they'ld be no way to
recover those. I pointed out that the same problem exist on a larger scale
if the hard drive blows up an hour before the backup and the last backup was
a day old.
Anyway, here's a way to "kick all the users off and produce a backup with
nothing else happening"

We kick the users off for another reason.

Best regards,
Fred Wilson
SE, Bell & Howell
fred.wilson@...


-----Original Message-----
From: Scott Taylor [mailto:scott@...]
Sent: Tuesday, July 23, 2002 1:21 PM
To: ib-support@yahoogroups.com
Subject: RE: [ib-support] force disconnect users


At 01:06 PM 23/07/2002, you wrote:

<snip, way to much work just for a backup>

>Everyone's happy now. Backup's done (and checked in our case, but that's up
>to you to do if you wish). No one was logged on during the gbak procedure.

The whole idea behind using gbak is that you don't need to shut the
database down to back it up. It's like it takes a snapshot of the current
gdb and stores that into a .gbk file, which can be restored on another
machine in a different environment even. I use it during the day, when the
DB is at it's busiest, to create a test DB away from the server. The users
don't even know it went on, and I have a perfectly good snapshot of the
database.



To unsubscribe from this group, send an email to:
ib-support-unsubscribe@egroups.com



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/