dbTalk Databases Forums  

Server crashed during backup - how do we deal with leftover *.^^^ files?

comp.databases.btrieve comp.databases.btrieve


Discuss Server crashed during backup - how do we deal with leftover *.^^^ files? in the comp.databases.btrieve forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Greg D
 
Posts: n/a

Default Server crashed during backup - how do we deal with leftover *.^^^ files? - 05-09-2007 , 03:42 PM






Hi,

Our Pervasive.SQL v8.7 server locked up last night, and was not responding
this morning. I had to hit the power button to get it to reboot. It appears
it was in the middle of a backup when it stopped responding. I have a backup
scheduled to run each night where it puts the database files in continuous
mode, then backs up everything except the .^^^ files, and when it's done, it
takes the database out of continuous operations. I use the "sqlutil -startbu
<DSN Name>" command to get all of the files within our database. Well, when
it rebooted, the Pervasive services restarted OK, but I'm concerned about
the state of the database. I'm still seeing a lot of .^^^ files, within our
database folder. The .MKD files with corresponding .^^^ files all have the
time stamp of when they went into continuous operations last night. The .MKD
files without a corresponding .^^^ file have a time stamp of when the server
restarted this afternoon.

I tried looking at the database properties in the Pervasive Control Center,
and it gave me a DSN error, but I have a DSN created for that database.

I also tried running a "butil -endbu filename.MKD" command, on one of them,
but it gave this error.
C:\PVSW\Bin>butil -endbu "E:\Database\UDTCONTFLD.MKD"

Btrieve Maintenance Utility 8.70.014.000
Copyright (C) Pervasive Software Inc. 2005
All Rights Reserved.


BUTIL-14: The file that caused the error is E:\DATABASE\UDTCONTFLD.MKD.
BUTIL-100: MicroKernel error = 88. The application encountered an
incompatible m
ode error.

BUTIL-9: The command did not complete due to an unrecoverable error.

How do I go about cleaning this up so that we don't loose any data and get
the tables out of continuous operation mode?

Thanks,
- Greg



Reply With Quote
  #2  
Old   
Bill Bach
 
Posts: n/a

Default Re: Server crashed during backup - how do we deal with leftover *.^^^ files? - 05-10-2007 , 08:03 AM






See pages 5 and 6 of this white paper:

http://www.goldstarsoftware.com/pape...o%20Have%20a%2
0Valid%20Backup.pdf


Greg D wrote:

Quote:
Hi,

Our Pervasive.SQL v8.7 server locked up last night, and was not
responding this morning. I had to hit the power button to get it to
reboot. It appears it was in the middle of a backup when it stopped
responding. I have a backup scheduled to run each night where it puts
the database files in continuous mode, then backs up everything
except the .^^^ files, and when it's done, it takes the database out
of continuous operations. I use the "sqlutil -startbu <DSN Name>"
command to get all of the files within our database. Well, when it
rebooted, the Pervasive services restarted OK, but I'm concerned
about the state of the database. I'm still seeing a lot of .^^^
files, within our database folder. The .MKD files with corresponding
.^^^ files all have the time stamp of when they went into continuous
operations last night. The .MKD files without a corresponding .^^^
file have a time stamp of when the server restarted this afternoon.

I tried looking at the database properties in the Pervasive Control
Center, and it gave me a DSN error, but I have a DSN created for that
database.

I also tried running a "butil -endbu filename.MKD" command, on one of
them, but it gave this error.
C:\PVSW\Bin>butil -endbu "E:\Database\UDTCONTFLD.MKD"

Btrieve Maintenance Utility 8.70.014.000
Copyright (C) Pervasive Software Inc. 2005
All Rights Reserved.


BUTIL-14: The file that caused the error is
E:\DATABASE\UDTCONTFLD.MKD. BUTIL-100: MicroKernel error = 88. The
application encountered an incompatible m
ode error.

BUTIL-9: The command did not complete due to an unrecoverable error.

How do I go about cleaning this up so that we don't loose any data
and get the tables out of continuous operation mode?

Thanks,
- Greg


Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.