Files getting damaged and closed

[NewFM85User]

HI,

When my Filemaker backup is running some of the FM files error out as getting damaged and closed.

The backup is aborted.

when I see the files status in the Server admin ,They are still open and running.

its very rare that anydatabse closes, may be once in a while.

Any body is aware of the similar situation ? any suggestions and comments, solutions are welcome.

Thanks

[Ender]

When my Filemaker backup is running some of the FM files error out as getting damaged and closed.

I don't think I've ever seen FM Server show errors during a backup. Where are you seeing these errors?

The "backup" you're talking about is FM Server's Scheduled backup, not some other backup utility, right? Does the event.log file show anything?

[NewFM85User]

you are right, FM did not give any error , but I am seeing them in the Filemaker 8 log viewer from the main windows console.

[Ender]

If it's in the event.log, then what is the actual error?

[Sir Boaregard]

HI,

When my Filemaker backup is running some of the FM files error out as getting damaged and closed.

The backup is aborted.

when I see the files status in the Server admin ,They are still open and running.

its very rare that anydatabse closes, may be once in a while.

Any body is aware of the similar situation ? any suggestions and comments, solutions are welcome.

Thanks

my suggestion would be to close all of your databases, copy them to a client machine with FileMaker Pro, Perform a Save A Copy As (Compacted) and then perform a Recover on the compacted copy.

Then move your recovered / compacted files back to the server and open them for sharing again.

[Vaughan]

It sounds like the live files are being backed-up by another program other than FM Server.

Bad news.

Use FM Server to backup the live files, then get the program to backup these off-line copies.

[Sir Boaregard]

It sounds like the live files are being backed-up by another program other than FM Server.

Bad news.

Use FM Server to backup the live files, then get the program to backup these off-line copies.

Very best backup practice. Also, you should always backup to the default folder and not a network drive...the more complications you add to your backup, the better chance it will become corrupted.

K.I.S.S. (Keep It Simple, Stupid)

[fmlawl]

I believe the reason for the database not being closed when you check them in the admin console is because they Pause rather than stay Open when saving the backup through FileMaker Server.

If this is not a 3rd party backup program and you are using FileMaker Server, i would suggest these steps:

1) Take a copy of one of the databases it says is encountering the error and host only that file.

2) Create a scheduled backup for that database and then run the schedule.

3) If the error is produced, look into the Event.log and post the error it gives or contact tech support.

This will allow us here to try and help give you more information on the error, if not it might just be best to contact tech support ;)

[Steven H. Blackwell]

Do not Recover the file in this instance. Try using the copy saved as compacted as is. Recovered files shouldnot be continued to be used.

Steven

[Sir Boaregard]

Do not Recover the file in this instance. Try using the copy saved as compacted as is. Recovered files shouldnot be continued to be used.

Steven

Any reasoning behind that?

[Raybaudi]

For example, try to look at a custom function inside a recovered file...

Never continue to use a recovered file: import all the data into a secure backup

[Ender]

See if knowledge base article# 5421 helps.

[Steven H. Blackwell]

Any reasoning behind that?

This has long been considered best practice. Additionally, it was explicitly ennunciated by the Lead Server engineer at the 2006 developer conference's Under the Hood session.

Recovery's purpose is to get the file in sufficiently good shape to extract the data. it will sacrifice any other part of the file to accomplish this mission.

Steven

[fmlawl]

Along with what Steve has said, the following knowledge base answers can help you recover a file correctly. This will also explain how to properly use a recovered file to rebuild and get your business up and running.

What to do when your file is corrupt! Answer 5421

How To Organize The Recovery Process When Recovering Related Databases! Answer 1580

Hope these help! btw, they say FMP7 and 8, but apply to FMP9 as well :

[Steven H. Blackwell]

These articles may not reflect best thinking either inside FMI or among experienced developers about the rcovery process.

The engineers are supposed to address this issue once again at the upcoming Developer Conference.

Steven