Re: Archive Options - 5.0 OnLine

In article <01bbe84b.7c47eba0$d201050a@w95cyoul-5->, Chris Youll <cyoul@dillon.com> writes >Engine 5.07 >Hardware: 1 - 2 CPU's >OS: AT&T SVR4, and SCO > > >We are moving from SE to OnLine and one of the changes is the archive >method. One option presented was to mirror all the raw dbspaces to cooked >dbspaces, and use the existing backup procedures to just backup the >mirrored dbspaces. > >About the only down side that I can think of is performance, and I have >been able to prove this. I am looking for any other reasons not to mirror >dbspaces to cooked dbspace and only backup the cooked dbspace. > >Thanks, > >Chris Youll >cyoul@dillon.com > > If you read a mirrored dbspaces and back it up you will not get a consistent image of it as it is continually being updated. If you then restored that backup you would get a corrupt database. Look into the Informix Backup tool tbtape. It co-ordinates with the other OnLine processes so it can read a consistent copy of the database. i.e. gets before images of page if they are about to be updated. -- David Williams