| Hi Dean,
About Ingres : no incremental backup; online backup supposedly in Ingres 6.3.
Very poor backup/restore tool anyway. It actually uses standard operating
system backup tools (BACKUP on VMS, tar on U*ix), but can be reconfigured to
use other tools (like cpio on U*ix).
The weakest part is the restore. The only case when you can restore a database
easily is if (1) the central ingres catalog (the iidbdb database) still nows
about the database to be restored, and (2) if the configuration file of the
database (roughly equivalent to an rdb root) is still there and (3) if you want
to restore from the latest backup and journal.
Anything else, and you are in for a lot of manual operations (creating dummy
databases, renaming files, ...).
I have no info about speed, but considering they use the standard OS backup
tools, I guess they can be derived from (for example) the VMS/BACKUP figures.
/albert
|
| >i was looking at the ULTRIX/SQL documentation. how close is this product to
>INGRES? i was told it should be the same.
It is the same as Ingres 6.2-3 - but "Digitalized", i.e. repackaged to be
installable using 'setld', with slightly improved manuals and man pages. Also,
it is a 'runtime only' versions, i.e. only includes the database manager,
management tools and remote access.
> their documentation alos references
>a utility called ckpdb to checkpoint the database. the documentation was not
>clear what was being backed up. is it the journal file being backed up
>and not the database? if so i then assume you use tar to backup up the database.
CKPDB performs the following actions when you invoke it :
- it uses 'tar' (or any other tool you configured it to use) to back up
all the files that compose the database. A database contains at least one
file for each table and index in the database; the files can be in several
'locations'. You will get one tar file (.ckp) for each location.
By default, the .ckp files go into the directory you designed to receive
backups for that database when you initally created that database. Optionally
you can direct them to tape (keeping in mind that tar does not allow
multi-volume tapes)
- it then starts a new journal file in the directory you designed when you
created the database.
/albert
|