Re: Informix Proves its worth

On 30 Nov, 13:44, dcrunch...@aim.com wrote: > In article <bc14e145-d38e-44f8-bdc5-cd1f7dcb0...@e10g2000prf.googlegroups.com>, > ibmsoftwarequesti...@bellmicro.eu says... > > > > >Hello all, > > >Please read the attached case study demonstrating Informix Dynamic > >Server's great performance. > > >http://www.informixcity.com/downloads/Nomad%20Case%20Study.pdf > > I am not sure whether I understood this: > > ============================= > With Nomad's previous database platform, it was only possible to perform backups > at an instance level - making it very difficult to restore data without taking > the entire system offline. Since Nomad's central database instance supports a > number of different customers, all of whom demand 24x7 availability, this was > not an option. As a result, on the rare occasions when a restore was necessary, > the company's IT staff had to employ a complex workaround. > By contrast, Informix Dynamic Server 10 offers highly localised backup and > restore functionality, enabling the recovery of individual tables without > interrupting the entire instance. As a result, Nomad has an easier and safer way > of handling database issues, reducing business risk. > ============================== > > AFAIK Informix's backup is always at an instance level. The only way to > make a backup localized to a database is to store a database in a dbspace > and do a dbspace level restore. I would suggest that the client is refering/drawing attention to the ability to perform "restores" at table-level. This feature allows the restoration of a table or set of tables, without affecting the avaliablity of the whole database.

<SNIP> >>============================== >> >>AFAIK Informix's backup is always at an instance level. The only way to >>make a backup localized to a database is to store a database in a dbspace >>and do a dbspace level restore. Nope, all dbspaces within an instance have to be at a single point in time; restoring a dbspace on it's own without doing logical recovery leaves you with an inconsistent / unavailable dbspace. Perhaps a feature request (which in effect opens one up to corruption) could be made to provide the ability for : Cold restore a "logical set of dbspaces that make up a database" and force "them" online. > > > I would suggest that the client is refering/drawing attention to the > ability to perform "restores" at table-level. > > This feature allows the restoration of a table or set of tables, > without affecting the avaliablity of the whole database. "Instance" not "Database"

On Nov 30, 6:43 am, "TBP (The Big Potato)" <T...@NotHere.Co.Uk> wrote: > <SNIP> > > >>============================== > > >>AFAIK Informix's backup is always at an instance level. The only way to > >>make a backup localized to a database is to store a database in a dbspace > >>and do a dbspace level restore. > > Nope, all dbspaces within an instance have to be at a single point in time; restoring a dbspace on it's own without doing logical > recovery leaves you with an inconsistent / unavailable dbspace. > > Perhaps a feature request (which in effect opens one up to corruption) could be made to provide the ability for : > > Cold restore a "logical set of dbspaces that make up a database" and force "them" online. > > > > > I would suggest that the client is refering/drawing attention to the > > ability to perform "restores" at table-level. > > > This feature allows the restoration of a table or set of tables, > > without affecting the avaliablity of the whole database. > > "Instance" not "Database" backups are done at the instance or dbspace level. restores can be done at instance, dbspace, table or partial table level. point-in-time restores can be done at the instance, table or partial table level. online restores can be done at the dbspace level and point-in-time restores can be done online at the table and partial table level.

On Nov 30, 7:39 pm, pokeyman <pokeyma...@gmail.com> wrote: > On Nov 30, 6:43 am, "TBP (The Big Potato)" <T...@NotHere.Co.Uk> wrote: > > > > > <SNIP> > > > >>============================== > > > >>AFAIK Informix's backup is always at an instance level. The only way to > > >>make a backup localized to a database is to store a database in a dbspace > > >>and do a dbspace level restore. > > > Nope, all dbspaces within an instance have to be at a single point in time; restoring a dbspace on it's own without doing logical > > recovery leaves you with an inconsistent / unavailable dbspace. > > > Perhaps a feature request (which in effect opens one up to corruption) could be made to provide the ability for : > > > Cold restore a "logical set of dbspaces that make up a database" and force "them" online. > > > > I would suggest that the client is refering/drawing attention to the > > > ability to perform "restores" at table-level. > > > > This feature allows the restoration of a table or set of tables, > > > without affecting the avaliablity of the whole database. > > > "Instance" not "Database" > > backups are done at the instance or dbspace level. > restores can be done at instance, dbspace, table or partial table > level. point-in-time restores can be done at the instance, table or > partial table level. online restores can be done at the dbspace level > and point-in-time restores can be done online at the table and partial > table level. I think that the table restores that are being referred to are those using the new table IDS 10.00+ restore feature built into the archecker utility. This can read any onbar or ontape archive and extract data from a single table and use the resulting data in insert statements. Art S. Kagel