Wiki

Case Status
Log In

Wiki

 
Database Recovery Event
  • RSS Feed

Last modified on 2/22/2019 12:40 PM by User.

Database Recovery Event

Case 169982
Date: January 21st, 2019
Event: Assertion failure due to lack of resources on the server.
Resolution: cleared out temp files, old OASIS files, and restarted server to clear cache to free up temp space on the C: to allow database to start.

Case 171602
Date: February 6, 2019
Event: Assertion failure due to database update
Resolution: Did a rebuild of the database.

Case 171941
Date: February 6, 2019
Event: Assertion failure due to database update
Resolution: Did a rebuild of the database.

Case 171933
Date: February 6, 2019
Event: Assertion failure due to database update
Resolution: Did a rebuild of the database.

Case 171817
Date: February 6, 2019
Event: Assertion failure due to database update
Resolution: 

Case 171725
Date: February 6, 2019
Event: Assertion failure due to database update
Resolution: Did a rebuild of the database.

Case 171699
Date: February 6, 2019
Event: Assertion failure due to database update
Resolution:

Case 171547
Date: February 6, 2019
Event: Assertion failure due to database update
Resolution: 

Case 171570
Date: February 6, 2019
Event: Assertion failure due to database update
Resolution: Did a rebuild of the database.

Case 171586
Date: February 6, 2019
Event: Assertion failure due to database update
Resolution: Did a rebuild of the database.

Case 171595
Date: February 6, 2019
Event: Assertion failure due to database update
Resolution: 

Case 171596
Date: February 6, 2019
Event: Assertion failure due to database update
Resolution: 

Case 171607
Date: February 6, 2019
Event: Assertion failure due to database update
Resolution: Did a rebuild of the database.

Case 171627
Date: February 6, 2019
Event: Assertion failure due to database update
Resolution: Did a rebuild of the database.

Case 171640
Date: February 6, 2019
Event: Assertion failure due to database update
Resolution: Did a rebuild of the database.

Case 171645
Date: February 6, 2019
Event: Assertion failure due to database update
Resolution: Did a rebuild of the database.

Case 171670
Date: February 6, 2019
Event: Assertion failure due to database update
Resolution:  Did a rebuild of the database.

Case 171845
Date: February 6, 2019
Event: Assertion failure due to database update
Resolution: Did a rebuild of the database.

Case 172410
Date: February 6, 2019
Event: Assertion failure due to database update
Resolution: 

Case 172255
Date: February 6, 2019
Event: Assertion failure due to database update
Resolution: 

Case 171573
Date: February 6, 2019
Event: Assertion failure due to database update
Resolution: Did a rebuild of the database.


Case 171553
Date: February 6, 2019
Event: Assertion failure due to database update
Resolution: Used a last known good copy and applied logs to roll it forward to current data, then re-ran the database update which was able to finish successfully.

Case 168520
Date: December 13th, 2018
Event: Ransomware across multiple offices
Resolution: Used the cloud backup copy to create a hosted failover copy while the ransomware attack was mitigated. Re-deployed sync databases from the backup copy.


Case 168675
Date: Jan 4th, 2019
Event: Drive failures on RAID array, server shut down until replacement drives arrived
Resolution: Used the cloud backup copy to created a hosted failover copy on standby while the array was rebuilt, in the event that the rebuild was unsuccessful.
 

Case [Unknown]
Date: 11/19/18
Event: Two drive failures on a RAID 5 array, database unrecoverable
Resolution: Customer had been testing Cloud Sync so an offsite backup was readily available.


Case 159444
Date: September 5th, 2018
Event: Server crashed
Resolution: Restarted server, database auto recovered


Case 157310
Date: Aug 8th
Event: Ransomware
Resolution: Had to use a backup from a month prior, then we rolled the copy forward using logs.

 
Case 155163
Date: July 13th
Event: Server Failed
Resolution: Helped recover and validate the database.


Case 152176
Date: May 29th
Event: Database corruption: assertion failed
Resolution: Had to do a rebuild of the backup database and use logs to roll it forward to current data content.

 
Case 149313
Date: April 13th
Event: Reached max database size of 512 GB due to 4k page size limit, no space to rebuild
Resolution: Had to add an additional hard drive then helped them rebuild the database with a larger page size.

 
Case 146258
Date: Feb 27th
Event: Database corrupted: assertion failed
Resolution: Due to multiple damaged tables, the database had to be rebuilt one table at a time, then the damaged tables were unloaded in parts until the damaged records were identified and worked around. Recovered with minimal data loss.

 
Case 138227
Date: October 25th 2017
Event: 3rd party host had a SAN failure, no backups were available
Resolution: A temporary Oasis Cloud Host instance was started so they could work during the 3rd party vendor's month long recovery attempt. After helping them get the recovered database from the 3rd party vendor, the two databases were merged. 

 
Case 137980
Date: Oct 22nd
Event: Server crashed
Resolution: Used a day old backup to recover from a failure. Used Oasis cloud sync to fill in missing data from the day old backup using the other office.


Case 135163
Date: Aug 29th 2017
Event: The database was hosted on a laptop which was dropped. Both the database and its backup were on the laptop.
Resolution: Recovery of the file was not possible. The customer had to start over with a new database.

 
Case 126627
Date: April 6th 2017
Event: Server out of space, database crashed
Resolution: Had to do a rebuild of the database, got them to start using backups.


Case 105995
Date: March 1st 2016
Event: Ransomware
Resolution: Sent a quote for cloud backup at their request, they paid the ransom.


Case 120717
Date: December 14th 2016
Event: Server crashed
Resolution: The data partition was out of disk space. Once some space was freed up the database was able to recover and start normally.


Case 117819
Date: October 10th 2016
Event: Database corruption
Resolution: Recovered from older backup and rolled forward with AA logs. 


Case 112044
Date: June 22nd 2016
Event: Ransomware
Resolution: Used our cloud backup to switch them to host. They paid the ransom because other machines were locked down as well. 

Case 109902
Date: May 16th 2016
Event: Hardware failure
Resolution: Was able to recover the production DB


Case 107632
Date: March 31st 2016
Event: Main office server crashed
Resolution: Used a copy of one of their cloud sync databases to replace the main office's database.


Case 106521
Date: March 9th 2016
Event: Server was shut down
Resolution: Helped start the service and recovery


Case 104773
Date: Feb 10th 2016
Event: Hard drive failed
Resolution: Some files were recovered, had to use a month old backup of their database to move forward. 

 
Case 102855
Date: Jan 4th 2016
Event: Database corrupted: assertion failed
Resolution: Did a recovery from a recent backup.


Case 102226
Date: December 15th 2015
Event: Carbonite backup program corrupted database
Resolution: We helped them get a non-corrupted backup and used logs to roll it forward to current data.

 
Case 97078
Date: Aug 20th 2015
Event: Database corrupted: assertion failed
Resolution: Local rebuild was not successful. A copy sent to Ingen was rebuilt successfully and sent back. 


Case 95188
Date: July 14th 2015
Event: Database corruption
Resolution: We had to rebuild the database using all of the AA log files.