Thankfully, I've never had to do anything with our AI files. The one time I had a DB go really, really south, it was overnight and only a couple of hours after the nightly backup. Since the job scheduler restored to it's previous state anyway, I just let it get the overnight stuff caught up. But I would like to know how to restore/reapply/whatever my AI files in case the need ever comes up.
Here's our current setup:
Progress 10.1b database running on Red Hat Linux.
AI is "managed" by scripts provided by the ERP vendor, but I'll include the important commands below.
Every 5 minutes, a script runs that checks for full extents (_rfutil <db> -C aimage extent list), copies them to an archive folder with a unique sequential number as it's file extension, and then marks that extent as empty (-C aimage extent emtpy <extent number>). We usually wind up with around 150 copied extents each week (ie, <dbname>.1 through <dbname>.150).
Every weeknight an online backup runs. Nothing is done to AI at this time.
Every Saturday, an offline backup is made. At this time, AI is rolled over to the next empty extent (-C aimage new), and then shut down. All of the extents are "archived". After the backup, AI is marked as backed up (-C mark backedup) and restarted. This also resets the counter used by the archive script, so archived files start off with "<dbname>.1" again.
Let's say things go south on Wednesday afternoon. What would I do?
Here's our current setup:
Progress 10.1b database running on Red Hat Linux.
AI is "managed" by scripts provided by the ERP vendor, but I'll include the important commands below.
Every 5 minutes, a script runs that checks for full extents (_rfutil <db> -C aimage extent list), copies them to an archive folder with a unique sequential number as it's file extension, and then marks that extent as empty (-C aimage extent emtpy <extent number>). We usually wind up with around 150 copied extents each week (ie, <dbname>.1 through <dbname>.150).
Every weeknight an online backup runs. Nothing is done to AI at this time.
Every Saturday, an offline backup is made. At this time, AI is rolled over to the next empty extent (-C aimage new), and then shut down. All of the extents are "archived". After the backup, AI is marked as backed up (-C mark backedup) and restarted. This also resets the counter used by the archive script, so archived files start off with "<dbname>.1" again.
Let's say things go south on Wednesday afternoon. What would I do?