0

Currently running several databases on an Active/Passive SQL Server 2014 Failover Cluster on Windows Server 2012 R2. Recently there was an event that caused the active server to failover. The failover was just a quick moment.

The problem is when the passive node came online, the data was a month old. It wasn't just one database, it was multiple (all six) databases that must have rolled back ~30 days. This is the first time this has ever happened. We've had plenty of failovers; virtual host update/failure, SQL server update/failure, or even failures on the SQL server itself.

We don't yet know why the SQL machine instance itself failed over yet, and we don't know why all the data was rolled back. We fortunately have full and transaction log backups we are currently restoring to.

However, we'd like to understand why did this happen and how do we prevent this in the future; how can we troubleshoot this issue?

mustaccio
  • 28,207
  • 24
  • 60
  • 76
David Gerst
  • 1

1 Answers1

1

The problem is when the passive node came online, the data was a month old. It wasn't just one database, it was multiple (all six) databases that must have rolled back ~30 days.

Much as others have said in the comments, there is no way SQL Server can go back in time 30 days on its own. Given that this is a FCI and uses "shared" disk, the most likely explanation is an improper mapping of the disks or otherwise incorrect setup at the storage/VM level.

You'll need to work with whomever owns the storage setup to check the mappings (current and historical) and if it's a virtual machine, whomever owns the configurations for that and go through each item.

Sean Gallardy
  • 38,135
  • 3
  • 49
  • 91