July 8, 2018 at 3:40 am
Hi Guys,
So I have a snapshot on a DB taken about 6 days ago. I also have another snapshot taken 24 hours ago.
Both the snapshots and the Source DB are on the SAME SAN volume.
The SAN volume ran out of space. Meanwhile there were plenty of space in the DB Files, so transactions were not affected.
After assigning more space, I've noticed that the snapshots are not usable. They still appear in the list but you cannot expand to view then, also you cannot query them. The error returned is that the table doesn't exist.
Is this now a permanent unfixable problem? I would assume so as I cannot see how it would recover from this? Should I just drop the snapshots now, or is there anyway i can recover them?
Cheers
Alex
July 8, 2018 at 3:58 am
alex.sqldba - Sunday, July 8, 2018 3:39 AMHi Guys,So I have a snapshot on a DB taken about 6 days ago. I also have another snapshot taken 24 hours ago.
Both the snapshots and the Source DB are on the SAME SAN volume.
The SAN volume ran out of space. Meanwhile there were plenty of space in the DB Files, so transactions were not affected.
After assigning more space, I've noticed that the snapshots are not usable. They still appear in the list but you cannot expand to view then, also you cannot query them. The error returned is that the table doesn't exist.
Is this now a permanent unfixable problem? I would assume so as I cannot see how it would recover from this? Should I just drop the snapshots now, or is there anyway i can recover them?
Cheers
Alex
Given that the SAN volume filled up, then almost certainly the snapshots haven't been updated, hence have become unusable. The only thing to do is to drop them.
😎
July 8, 2018 at 7:34 am
That's what I had assumed but wasnt sure if there was a magic DBCC CreateMiraclesFrom('ThinAir') that I could run.
July 8, 2018 at 8:09 am
alex.sqldba - Sunday, July 8, 2018 7:34 AMThat's what I had assumed but wasnt sure if there was a magic DBCC CreateMiraclesFrom('ThinAir') that I could run.
You might give the TIMEWARP parameter a try, unfortunately I cannot remember the additional parameters needed 😀
😎
July 8, 2018 at 8:29 am
Thought that was MySQL only?!
Out of interest, what happens to a snapshot thats taken on a DB thats apart of an AlwaysOn Group, and that group then fails over. Making the Snapshot technically on a read only replica?
July 8, 2018 at 8:38 am
alex.sqldba - Sunday, July 8, 2018 8:29 AMThought that was MySQL only?!Out of interest, what happens to a snapshot thats taken on a DB thats apart of an AlwaysOn Group, and that group then fails over. Making the Snapshot technically on a read only replica?
Rather than me writing an answer, I suggest that you have a look at this article
😎
Boiling it down, the snapshot remains on the node where it was originally created and does not replicate over when the nodes chance roles.
July 8, 2018 at 10:11 am
Perfect, article. Cheers
July 8, 2018 at 10:24 am
alex.sqldba - Sunday, July 8, 2018 10:11 AMPerfect, article. Cheers
You are very welcome.
😎
Please feel free to ping back if you have any further questions and please do post any useful findings 😉
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply