IBM Informix Dynamic Server Version 9.30.FC6

Backup method onbar using ISM Netvault.

I have a very large amount of data, many dbspaces some live some for test / training. My onbar back-up takes an age so I want to just backup the primary dbspaces required to run our application.

If I never (ever say) backup a dbspaces and use onbar to restore the backed up dbspaces the non restored dbspaces status go to offline and the chunks are labelled as inconsistent.

Question.

Is there a way to force these dbspaces on-line ?

Hi,
Yes, look onspaces help.

Gustavo.

$ onspaces -s dm2sysdbs -p /dev/informix/ldm2sys01 -o 0 -O
The chunk specified does not exist.

$ ls -l /dev/informix/ldm2sys01
lrwxrwxrwx 1 root system 14 Dec 08 2004 /dev/informix/ldm2sys01 -> /dev/rdm2sys01

What am I doing wrong !!!!!

Hi,

Look if exists /dev/rdm2sys01.

ls -l /dev/rdm2sys01

$ ls -l /dev/rdm2sys01
crw-rw---- 1 informix informix 48, 53 Dec 08 2004 /dev/rdm2sys01
$ onspaces -s dm2sysdbs -p /dev/rdm2sys01 -o 0 -O
The chunk specified does not exist.

Hi,

Please test the permissions of all path.
If you run onspace as informix ?

Gustavo.

I'm doing these commands logged in as Informix. I have been told that only IBM (INFORMIX) can resolve this issue. Is this true.

My chunks are not mirrored.

You cannot force an inconsistent chunk to go online. Only the IBM technical support can do this with their support tools. Even if they manage to make it online, chances are the server will placed if in inconsistent mode.

The only way to make sure all chunks are consistent is to perform a full restore or drive south as fast as possible.

Problem is my friend my IDS instance is full of dbspaces that are NOT critcal and increase the backup time by 3 hours. I am now convinced I need to create a new instance where I can move my non critical dbspace and therfor reduce the critical backup to 2 hours.

Cheers

Kelvin

That's the way we are working.

3 different instances : production, developpment, training

Another instance = another onconfig.

So devlop and in training we don't need to backup the logging, we send it to /dev/null. And we don't have to bckup every day.