I take it that you create a clone by means other than backup/restore
and that you create a snapshot using EMC hardware or the like.
SQL Server won't let you restore transaction logs unless you've first
restored the database, or at least a database file group or file. Then
you have to restore all
Not answering as an ADSM guy, but addressing the philosophy involved in
protecting a large database...
150 to 500gb? Once an hour? That seems overwhelming, unless I'm
missing something...
We tend to do a two tiered system. We periodically backup everything,
say once per week, with transaction
This from our MS-SQL person who has implemented TDP on a cluster:
>For that large of a database (150-500 GB) there really is no such thing as
>a quick restore. Having a hot spare SQL Server is probably the best
>solution -- i.e. another SQL Server that replicates the production SQL
>Server data
Basic question:
Can I clone or snapshot an MS SQL 7 database and then take hourly
"incremental" backups and do the following restore:
restore the clone (either from tape or from the clone itself) and apply the
"incremental" restores?
I'm after a rather quick restore of a large database. Perhap
