![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi, I have a site running P2000 SP2a and am trying to figure out the best way to manage backups. Please see options below. Has anyone had any experience with problems caused by stopping pervasive services with users possibly logged on? Option 1 - Stop the Pervasive services 'should' be OK as long as you aren't running anything major on the database at the time that is updating the records - note the 'should' Any application that was running will not be able to connect to the database when it is down Option 2 - open file backup This just copies the files that are open This can cause backups with files out of sync and may corrupt data Option 3 - Continuous operations This locked up Pervasive on our server and we wound up with a corrupted database From some research it seems to be unreliable before Pervasive 2000 SP3 Pervasive 2000 SP3 & SP4 cause problems with file locking in the application we are running This is doesn't seem to be a problem with Pervasive v8 Option 4 - Upgrade to Pervasive v8 Cost |
#3
| |||
| |||
|
|
Hi again. Option 1 should be fine. The engine should do an orderly shutdown regardless of load. Transactions aborted, files closed, sessions closed cache committed then down. Of course it will be unavailable to the application when stopped. Option 2 is a maybe. A good open file manager should let you get a snapshot of the data files. Unfortunately there is no guarantee the data files are in a consistent state when the snapshot is taken. However the engine is pretty good about recovering from a partial system transaction. Option 3, well. SP2 in your experience just does not work reliably. Actually SP1 was ok. SP2 added AsyncIO and well... SP3 added row level locking. Not behaving properly with the application is possible. SP4 is pretty well behaved with locking. Depends on whether the application likes row level or page level locking. Rebuilding the files with repeating duplicate instead of linked duplicate keys may help. V8 has the same row level locking so I do not know why the application would work any better with it than SP4. Leonard On Tue, 20 Jan 2004 12:21:34 +1300, "John Anisy" j.anisy (AT) cchlawbase (DOT) co.nz> wrote: Hi, I have a site running P2000 SP2a and am trying to figure out the best way to manage backups. Please see options below. Has anyone had any experience with problems caused by stopping pervasive services with users possibly logged on? Option 1 - Stop the Pervasive services 'should' be OK as long as you aren't running anything major on the database at the time that is updating the records - note the 'should' Any application that was running will not be able to connect to the database when it is down Option 2 - open file backup This just copies the files that are open This can cause backups with files out of sync and may corrupt data Option 3 - Continuous operations This locked up Pervasive on our server and we wound up with a corrupted database From some research it seems to be unreliable before Pervasive 2000 SP3 Pervasive 2000 SP3 & SP4 cause problems with file locking in the application we are running This is doesn't seem to be a problem with Pervasive v8 Option 4 - Upgrade to Pervasive v8 Cost |
![]() |
| Thread Tools | |
| Display Modes | |
| |