crainlee2 (4/29/2011)
Great questions, Craig.We only use Compellent's simple replays (snapshots/backups) for the database backup files produced by SQL Server's regular backup operations.
Interesting. So you're not using the SAN to avoid standard backup procedure. You're snapshotting the .bak files.
We use the Compellent Replay Manager generated replays for all of our databases. The difference is that the simple replays are not "transaction aware". The Replay Manager generated ones are and they ensure a consistent snapshot of a database's data and log files. Replay Manager uses Microsoft's VSS technology to accomplish this.
Either of the 2 types of Compellent replays can be used for point in time restoration to the degree of frequency the SAN administrator has set them up.
So if they snapshot every 15 minutes, that's your point in time you can return to. However, if it's snapshotting the log AND DB constantly, that's got to be a space hog if you want 15 minute point in time ability. Also, you mention consistent snapshot of data and log file. I assume somehow you pair them in compellent as mdf/ldf combinations, but still, if you poke around there's any number of articles out there about how an unclosed/detached/offlined database that you do this with would end up performing and the data errors. What's the workaround here?
SAN snapshot backups of mdfs, particularly because of point in time requirements, have always worried me.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA