Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.6K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 298 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Damaged .mdf and no up to date Backup
Lilithyan
Member Posts: 32
Hello,
One of our customers has currently a rather large problem with his SQL Navision Database and it's frustrating to no end.
The problem:
Last week Tuesday (20.07.) the employees of our customer noticed that they were unable to access a certain table and its contents. The administrator was at that time on holiday so we immediately got the call for help. Turns out that the hard drive was damaged sometime on the weekend (17./18.07) before and now the .mdf file of the database was faulty, denying access to some of the tables.
When the administrator was back from his holiday, had exchanged the hard drives and established the full backup from the Friday before that fateful weekend (16.07.), one of my colleagues and I drove to the firm to help insert the needed log files into the backup, going from Monday after the incident to now (19.07. – 29.07.).
The really big problem made itself known, when we tried to insert the first log file, because SQL Server Management Studio insisted, that the log file wasn’t the oldest file needed for the full backup from Friday, 16.07.
Upon checking, it was discovered that another full backup had been made during the weekend on Saturday (17.07.) and another on Sunday (18.07.) which was damaged due to the then damaged hard drive and .mdf file. The thing is, on weekends the full backups aren’t saved separately on an external data source and the damaged one from Sunday overwrote the working one from Saturday! And we don’t have any log files going farther back than the Monday after the damaged full backup!
The Question:
Which is the best way to get a fully working database again? Is it possible to trick the existing log files into being written into the full backup from Friday, so the changes and new data saved within aren’t lost?
Hope someone has an idea what to do, and many thanks in advance!
Ciao,
Lilithyan
One of our customers has currently a rather large problem with his SQL Navision Database and it's frustrating to no end.
The problem:
Last week Tuesday (20.07.) the employees of our customer noticed that they were unable to access a certain table and its contents. The administrator was at that time on holiday so we immediately got the call for help. Turns out that the hard drive was damaged sometime on the weekend (17./18.07) before and now the .mdf file of the database was faulty, denying access to some of the tables.
When the administrator was back from his holiday, had exchanged the hard drives and established the full backup from the Friday before that fateful weekend (16.07.), one of my colleagues and I drove to the firm to help insert the needed log files into the backup, going from Monday after the incident to now (19.07. – 29.07.).
The really big problem made itself known, when we tried to insert the first log file, because SQL Server Management Studio insisted, that the log file wasn’t the oldest file needed for the full backup from Friday, 16.07.
Upon checking, it was discovered that another full backup had been made during the weekend on Saturday (17.07.) and another on Sunday (18.07.) which was damaged due to the then damaged hard drive and .mdf file. The thing is, on weekends the full backups aren’t saved separately on an external data source and the damaged one from Sunday overwrote the working one from Saturday! And we don’t have any log files going farther back than the Monday after the damaged full backup!
The Question:
Which is the best way to get a fully working database again? Is it possible to trick the existing log files into being written into the full backup from Friday, so the changes and new data saved within aren’t lost?
Hope someone has an idea what to do, and many thanks in advance!
Ciao,
Lilithyan
0
Comments
You then restore all those backups in the order they were taken.
You cannot 'trick' the restore if logs are missing as the data you want is missing too.
TVision Technology Ltd