It has come to our attention that Pervasive’s management of large files has the potential to invalidate your backups in the event that there are large files in your database and you use a selective backup process.
Pervasive handles files that are larger than 2 Gb in size, differently than smaller files. These large files are split into multiple segments. The first segment of course has the extension .BTR. Subsequent segments get assigned more obscure extensions. So, if you had a sales detail file that was larger than 2 Gb in size, the first segment would be named SALEDET.BTR and the second would be named SALEDET.^01.
If you are using a selective backup process that only backs up files that have extension .BTR, your backups become invalid when you have large files that exceed 2 Gb in size because the second segment of the file (the one with the .^01 extension) does not get backed up. If parts of your data are not backed up, your backup may be useless.
If you simply backup all the files in your Minotaur directories, this issue will not be a problem for you.
The most likely files to encounter this file size issue are the raw EDI data file (EDIRAW.BTR) and the asset posting tracking file (RAWGLPOS.BTR). These files grow relatively quickly and any user that has these files on their system should monitor them carefully if they are using a selective backup process. Of course, some of our older customers can also anticipate having large sales (SALEJOUR.BTR, SALEDET.BTR), receiving (BILLJOUR.BTR, BILLDET.BTR) and inventory tracking (INVEHIST.BTR) files.
We strongly suggest that you examine all your Minotaur data files to identify whether they might exceed 2 Gb in size. If any files exceed that size, you should review your backup process to ensure that all segments of such large files are being backed up. Please contact Minotaur if you would like to arrange for our assistance with this review.
|
