Backup causes Journal File to fail

[Kenneth Spence-2]

I was wondering if anyone else has seen this.  It is my understanding  
that when a backup runs a new journal file is created after backup is  
completed.  On several occasions over the last 6 months I have had a  
DB  that can't be used when I open the DB the next time because of a  
bad journal file.  I discovered this last time that the DB had run a  
backup and it created a new journal file.  The only thing in the  
journal file is "GOL4ATAD".  If I have the DB create a  
new file it also has the same thing in it.  My thinking at this point  
is the journal file is not getting created correctly after a backup on  
some occasions.

This doesn't happen on every backup.  Seems to happen about once a  
month.  On this last occasion it so happens that I had a kernel panic  
somewhere near the same time of day and I have been having those about  
once a month.  Not sure if they were at the same time as I was away  
form my computer at the time.  Not sure if this is causing a kernel  
panic or a kernel panic is causing this problem or there is no  
relation.  I don't remember if there was a relation in the past  
regarding this.

Any ideas?

Ken


**********************************************************************
Get the speed and power of 4D v11 SQL
before upgrade prices increase - http://www.4d.com


4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4D.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4D_Tech-Unsubscribe@...
**********************************************************************

[psmith-3]

Ken,

A customer just experienced this a few days ago, for the first time  
since going live about 6 months ago. I just assumed they did something  
wrong, but perhaps it's the same problem as you experienced.


Paul Smith

TSE International

> I was wondering if anyone else has seen this.  It is my  
> understanding that when a backup runs a new journal file is created  
> after backup is completed.  On several occasions over the last 6  
> months I have had a DB that can't be used when I open the DB the  
> next time because of a bad journal file.  I discovered this last  
> time that the DB had run a backup and it created a new journal  
> file.  The only thing in the journal file is "GOL4ATAD".  If I have  
> the DB create a new file it also has the same thing in it.  My  
> thinking at this point is the journal file is not getting created  
> correctly after a backup on some occasions.
>
> This doesn't happen on every backup.  Seems to happen about once a  
> month.  On this last occasion it so happens that I had a kernel  
> panic somewhere near the same time of day and I have been having  
> those about once a month.  Not sure if they were at the same time as  
> I was away form my computer at the time.  Not sure if this is  
> causing a kernel panic or a kernel panic is causing this problem or  
> there is no relation.  I don't remember if there was a relation in  
> the past regarding this.
>
> Any ideas?
>
> Ken

**********************************************************************
Get the speed and power of 4D v11 SQL
before upgrade prices increase - http://www.4d.com
   

4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4D.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4D_Tech-Unsubscribe@...
**********************************************************************

[Peter Schumacher-2]

Ken,

yes, I have this seen happen, but was never able to re-produce it and  
hold some hard drive issus for responsible. "Good" (bad) to know!

Am 07.11.2009 um 08:45 schrieb Kenneth Spence:

> I was wondering if anyone else has seen this.  It is my  
> understanding that when a backup runs a new journal file is created  
> after backup is completed.  On several occasions over the last 6  
> months I have had a DB  that can't be used when I open the DB the  
> next time because of a bad journal file.  I discovered this last  
> time that the DB had run a backup and it created a new journal  
> file.  The only thing in the journal file is "GOL4ATAD".  If I have  
> the DB create a new file it also has the same thing in it.  My  
> thinking at this point is the journal file is not getting created  
> correctly after a backup on some occasions.
>
> This doesn't happen on every backup.  Seems to happen about once a  
> month.  On this last occasion it so happens that I had a kernel  
> panic somewhere near the same time of day and I have been having  
> those about once a month.  Not sure if they were at the same time as  
> I was away form my computer at the time.  Not sure if this is  
> causing a kernel panic or a kernel panic is causing this problem or  
> there is no relation.  I don't remember if there was a relation in  
> the past regarding this.
>
> Any ideas?
>
> Ken
>

Greetings,
[4D-Consulting.com]eK, Wiesbaden (Germany)
Peter Schumacher
--------------------------------------------------------
Web: http://www.4D-Consulting.com/
FreeCall:  0800-434 636 7
Tel.:      [phone] - Fax: [phone]
4D-Consulting.com eK - Scharnhorststr. 36 - 65195 Wiesbaden
Member of the German Developer Network  http://www.die4dwerkstatt.de









**********************************************************************
Get the speed and power of 4D v11 SQL
before upgrade prices increase - http://www.4d.com
   

4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4D.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4D_Tech-Unsubscribe@...
**********************************************************************

[Kenneth Spence-2]

Did they have a kernel panic or just a journal file not working after  
a backup?

Ken
On Nov 7, 2009, at 9:01 AM, psmith wrote:

> Ken,
>
> A customer just experienced this a few days ago, for the first time  
> since going live about 6 months ago. I just assumed they did  
> something wrong, but perhaps it's the same problem as you experienced.
>
>
> Paul Smith
>
> TSE International
>
>
>> I was wondering if anyone else has seen this.  It is my  
>> understanding that when a backup runs a new journal file is created  
>> after backup is completed.  On several occasions over the last 6  
>> months I have had a DB that can't be used when I open the DB the  
>> next time because of a bad journal file.  I discovered this last  
>> time that the DB had run a backup and it created a new journal  
>> file.  The only thing in the journal file is "GOL4ATAD".  If I have  
>> the DB create a new file it also has the same thing in it.  My  
>> thinking at this point is the journal file is not getting created  
>> correctly after a backup on some occasions.
>>
>> This doesn't happen on every backup.  Seems to happen about once a  
>> month.  On this last occasion it so happens that I had a kernel  
>> panic somewhere near the same time of day and I have been having  
>> those about once a month.  Not sure if they were at the same time  
>> as I was away form my computer at the time.  Not sure if this is  
>> causing a kernel panic or a kernel panic is causing this problem or  
>> there is no relation.  I don't remember if there was a relation in  
>> the past regarding this.
>>
>> Any ideas?
>>
>> Ken
>
> **********************************************************************
> Get the speed and power of 4D v11 SQL
> before upgrade prices increase - http://www.4d.com
>
> 4D Internet Users Group (4D iNUG)
> FAQ:  http://lists.4d.com/faqnug.html
> Archive:  http://lists.4D.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:4D_Tech-Unsubscribe@...
> **********************************************************************

**********************************************************************
Get the speed and power of 4D v11 SQL
before upgrade prices increase - http://www.4d.com
   

4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4D.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4D_Tech-Unsubscribe@...
**********************************************************************

[psmith-3]

Ken,

Sorry, I don't recall the specifics but I believe the xServe system  
was still responding.

Paul Smith

TSE International


> Did they have a kernel panic or just a journal file not working  
> after a backup?
>
> Ken

**********************************************************************
Get the speed and power of 4D v11 SQL
before upgrade prices increase - http://www.4d.com
   

4D Internet Users Group (4D iNUG)
FAQ:  http://lists.4d.com/faqnug.html
Archive:  http://lists.4D.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4D_Tech-Unsubscribe@...
**********************************************************************