Thanks for the info.
I think we will then use BUTIL and save the money for the backup agent.
> Backup Agent suffers horribly from the absence of a "white list", or a way
> to force a given set of files open. This creates the exact issue that you
> have witnessed, and causes problems with backups.
> The solution is to implement your own WhiteList solution. Create a batch
> file that runs immediately after your PVBACKUP -ON command that causes all
> of the "critical" Btrieve files to be opened. You can use a tool like our
> HoldOpen (www.goldstarsoftware.com/tools.asp) if you want to create a
> specific list of files, or if you want to use wildcards, then a tool like
> ListStat (same address) can be issued with a command like "LISTSTAT *.BTR"
> and all Btrieve files in the directory will be opened and placed into
> backup mode.
> Only then, AFTER the LISTSTAT command finishes, should you start the
> backup process.
> Goldstar Software Inc.
> Pervasive-based Products, Training & Services
> Bill Bach
> BillB...@goldstarsoftware.com
> http://www.goldstarsoftware.com
> *** Pervasive Training - July in Chicago ***
> michael last wrote:
>> We just noticed a problem with Backup Agent:
>> Our application is using Pervasive Data Provider for .NET and database
>> files are just opened if needed, meaning the database files are NOT
>> constantly open. If we now start the Backup Agent, no files are set to
>> continuous operation which is ok. Now assuming the backup software starts
>> backup for a large database file opening the file in read/write mode -
>> now our application opens this file and Backup Agent tries to set it into
>> continuous operation - this will fail because the file is already opened
>> by the backup software.
>> The only way we can see to solve that problem is using butil command with
>> a list file, but this is also a problem because sometimes new database
>> files are created by our application.
>> Any other suggestions?
>> Thanks for any help.
>> Michael Last
|
