At least two sites now have had difficulties following a major problem where system restores have been required. In both cases, the restoration from incremental backups was not successful and they had to go back some days to the last full backup of both arev & data files and then all OK again but with subsequent major data catch-ups to do. Are there any recommendations regarding the type of backups that AREV should have? (and sorry no, I dont know what software they use for B/up) It would seem to me that a full back up every night is warranted but convincing large govt IT departments requires some more information - can anyone point me to information recommendations - I couldn't find anything in the knowledge base.

Thanks

Each Btree- and Cross-Referenced indexed Linear Hash table is stored as 6 os files. And, if there are Relational indexes you can make a case that more os files are involved. Those relationships between all the os files must be maintained in the backup for restoration to have a chance of success.

Thus, it has always been prudent to make Full backups of folders containing Linear Hash tables.

Dave

Thanks for that - that would explain the problem with incremental backups.

We do differential backups nightly and full backups weekly - I had to refresh my memory as to the difference; differential is backups of all changed files since the last *full* backup where incremental is all changed files since the last backup, which may be the previous incremental backup. I'm wondering if this is an issue with differential backups as well.

David Craig

ABC-Clio

Further to this - one of the sites has sent a post backup report showing that backup of Revlock files failed but did not report any other failures in the Arev directories. I'm wondering if this is of any significance?

The Revlock files are part of the record locking scheme. Don't worry about them.

View this thread on the forum...