OMNIBACK RETENTION

[Kurt Harless_3]

Greetings,

Noticing that my OMNIBACK retention doesn't seem to be purging old backups,
e.g. I can use the restore feature and drill down to backups older than the
current (which has never been changed) retention period.

Any ideas?

Also, saw a write up that says an export to ascii of a 2 Gb Db can take 10+
hours, if I'm using 250 Mb of a max alloc of 2 Gb Db, any estimates on the
export time? Import?

Thanks

Kurt

[Melanie Goetz]

Essentially, until a tape is reused within Omniback, the session can be
restored. If you init the expired tapes, or delete the session info the details
will be flushed from the catalogs. (Hence the sessions listed in the version
lists as 'possible').

The writeascii for your db should be much briefer than the 10+ hours for the 2
gig db, about 10 % of the time.
The readascii will take longer than the write, as the process needs to recreate
the indexes for the db files as it creates the new db files.

Typically you shouldn't need to perform a write/read ascii for db maintenance.

[Anthony Goonetilleke_1]

I did a read/write ascii with OBII v3 and it tok about an hour for the write
ascii of both the mmdb and the cdb, but it took a whopping 5.5 hours to do the
read and recreate the database on a new installation. Both machines were
identical in terms of specs I think it was just the reacreation of the tables
that takes a while. There are a few things you can do
- delete old sessions from the database
- run a purge of the database
- do a write ascii with the nodetail option, this is much faster but slower
when you go to do a recovery as the tape has to be scanned.