Re: How to use ON-Archive?
Posted in 1998
Topics: Backup & Restore, Storage & Space Management, Error Codes & Troubleshooting, Logging & Checkpoints, Migration, Import/Export & Data Conversion, Platform-Specific Issues
Rudi Brunner <brunner@forwiss.fmi.uni-passau.de> wrote in article
<3528B32A.EE9@forwiss.fmi.uni-passau.de>...
> Hi,
>
> I'm using Informix 7.12 under Solaris 2.5.
>
> What I want to do:
> ------------------
> I want to backup a database daily and automatically on disk (not tape).
>
> What I've already tried:
> ------------------------
> The documentation tells me that there is only the ON-Archive-mechanism
> to do this. (Are there any alternatives?)
>
> First thing I needed was my database in an own dbspace as ON-Archive
> only
> works on dbspaces. (Right?)
>
> So I created an own dbspace on a raw device and copied my database to it
> with dbexport/dbimport. (Should I do it different?)
>
> Then I configured the ON-Archive-mechanism the following way (my
> application is called "cms"):
> > cd $INFORMIXDIR/etc
> > cp config.arc config.arc.cms
> insert the following line to config.arc.cms: > DEVICE cms_vop =
> /home/calendar/cms_data
> (/home/calendar/cms_data exists and is writable to informix-user.)
> > export ARC_CONFIG=config.arc.cms
> > start_oncatlgr
> (Are there any principle mistakes till now?)
>
> Then I edited the ON-Archive reqests:
> > onarchive
"DEFINE/VSET=cms_vset/DEVICE_TYPE=cms_vop/CLASS=SYSTEM/DRIVER=DISK/ACCESSIBI
LITY=80"
> > onarchive
"DEFINE/VOLUME/VSET=cms_vset/VIRTUAL=(/home/calendar/cms_data/volume1)/MAX_S
PACE=100000"
> (/home/calendar/cms_data/volume1 exists and is writable to
> informix-user.)
> > onarchive "DEFINE/DBSPACESET=cms_dbset/DBSPACE=cms_dbspc"
> > onarchive "ARCHIVE/DBSPACESET=cms_dbset/VSET=cms_vset/REPEAT=1"
> > onautovop
> (Did I do here something wrong?)
>
> Then I`ve tried to retrieve the database for testing:
> > onarchive "RETRIEVE/DBSPACESET=cms_dbset/DBSPACE=cms_dbspc"
> > onautovop
>
> And now my problem arises:
> --------------------------
> The retrieved database is inaccessable to any request.
> If I try for example to select the database via isql I get the message:
> 311: Cannot open system catalog (systables).
> 155: ISAM error: Primary and Mirror chunks are bad>
> Ok, I'm not an expert of using databases at all. So maybe there is a
> principle thing
> I've done wrong.
> Anyway, has anybody ever used the ON-Archive-mechanism successfully?
> If yes, please tell me how. And how can I repair these damned chunks
> without reading masses of documentation.
> I've already spend one week of work to this and I'm down with my nerves.
> So please, help!
>
> Ciao
> Rudi
>
> --
> Gib Gates keine Chance.
>
Use Ontape instead of onarchive.
use "ontape -s -L 0 " to do a level 0 Backup of the database.
use "ontape -a " to do logical log backups
*** U can include these cmds in the Cron task to do the backup
automatically.