Our team has a DB that is over 3mil KBs. When opening the DB in the console, it remains in 'verifying' mode. I'm thinking the DB is just too large so it won't open. Am I right? Has anyone experienced this? What's the troubleshoot?
What would be a typical troubleshoot if the DB is corrupt?
1. Restore from uncorrupted backup.
2. Use recover on the corrupt file.
3. Get the data out of the recovered file.
4. Put the data in the restored file.
5. Destroy the recovered file.
6. Perform a root cause analysis.
7. Develop a risk mitigation plan.
8. Implement the appropriate mitigation's.
if you do not have an uncorrupted backup then the only guaranteed recovery is to completely rebuild the damaged file from scratch. By that i mean do not move/copy anything from the damaged file to the new file.
I doubt your issue is with size. It sounds like your db may be corrupt. What led up to this situation?
Our IT dept experienced a sudden outage, which shut all systems down (servers, hardware, etc). When they corrected their issue, our servers were rebooted and applications are running fine. Except, with FM, I can't get that ONE DB to reopen. It stays in 'verifying' mode.
You can try to open the db from a fm client first it via server.
If that does not work you will need to recover and rebuild it.
The official thought to recovery is that you should rebuild the application as there may be other repaired damage. In practice no one ever does but it's your call.
If if opened before the crash the size should not be the issue.
Do you have a backup from before the outage?
Was there any/much data entered between the last backup and the outage?
Restoring from backups might be your best option, especially if you can easily reenter any lost data.
Our backup was 4hrs old so that's only 4hrs of data that may be lost. It's still checking for consistencies so if that fails to open the DB, this may be the route. Thanks.
Thank you all! I will attempt all options and see what the outcomes are.
Sounds like you need to change your backup strategy (and check and test it regularly...)
The long "verifying" is typical on big files. Nothing you can do there. Except perhaps change the design so that old data is archived out to another file that only gets updated at night. If you do that then a crash during the day means that you can simply replace the big file with a backup without any data being lost.
Yah. It seems like an archiving strategy may be needed for the huge file. It's only one of 60 DBs we backup regularly.
Further review shows the DB did corrupt. I pulled the last clean backup and re-established a clean version. Thanks for all of the tips shared. Now I know even large files won't hang unusually long and it's something more sinister... corrupt file.
Retrieving data ...