June 2015
Intermediate to advanced
1800 pages
70h 6m
English
In general, you shouldn’t have too many database snapshots defined on a database because of the copy-on-write overhead each snapshot requires. However, this all depends on the volatility of the source database and a server’s capacity. If there is low volatility and the server is not using much CPU, memory, and disk capacity, your database could more readily support many separate database snapshots at once. If the volatility is high and CPU, memory, and perhaps disk capacity are saturated, you should try and minimize the number of database snapshots generated.
Read now
Unlock full access