28.07.2013 Views

Unify Your Backup and Recovery Strategy with LiteSpeed® for SQL ...

Unify Your Backup and Recovery Strategy with LiteSpeed® for SQL ...

Unify Your Backup and Recovery Strategy with LiteSpeed® for SQL ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Unify</strong> <strong>Your</strong> <strong>Backup</strong> <strong>and</strong> <strong>Recovery</strong> <strong>Strategy</strong> <strong>with</strong> <strong>LiteSpeed®</strong><br />

<strong>for</strong> <strong>SQL</strong> Server <strong>and</strong> <strong>LiteSpeed®</strong> Engine <strong>for</strong> Oracle<br />

USING LITESPEED: REAL-WORLD EXAMPLES<br />

To wrap up, I offer several scenarios I have addressed <strong>with</strong> LiteSpeed.<br />

Need Both Compression <strong>and</strong> Encryption but<br />

<strong>Backup</strong> Window is Short<br />

This is the most frequent scenario. Most of our “in-scope of compliance”<br />

applications have large databases <strong>and</strong> are very busy, <strong>with</strong> a limited window of<br />

availability <strong>for</strong> backups <strong>and</strong> other maintenance. There<strong>for</strong>e, we need the backup<br />

completed as quickly as possible, while at the same time ensuring it is encrypted<br />

<strong>and</strong> compressed to reduce storage needs.<br />

LiteSpeed is the best choice <strong>for</strong> us in this scenario. LiteSpeed encrypts both our<br />

Oracle <strong>and</strong> <strong>SQL</strong> Server databases to the same encryption level, <strong>with</strong>out the need<br />

<strong>for</strong> extra-cost Oracle options, <strong>and</strong> compresses them to about 10-30% of their<br />

original size—just as fast as the uncompressed, unencrypted native backup utility<br />

(<strong>and</strong> often faster).<br />

Need Compression <strong>and</strong> Have Plenty of Time<br />

We do have some large databases that see relatively light use. This is typical when<br />

an application stores a lot of data but accesses it infrequently, such as lookups on<br />

an historical billing database.<br />

In these cases, our primary goal is to reduce the storage needs of the backup as<br />

much as possible. There<strong>for</strong>e, we want to maximize the compression, even if that<br />

means increased elapsed time <strong>and</strong> processor utilization. LiteSpeed addresses<br />

this situation nicely by allowing us to configure a higher compression level on<br />

both plat<strong>for</strong>ms.<br />

Need Speed More than Anything Else<br />

In some cases, the elapsed time of the backups is causing us the most pain. The<br />

speed of a backup depends on the size of the backup, disk I/O speed, processor<br />

speed, system utilization by other processes, <strong>and</strong> the compression <strong>and</strong> encryption<br />

levels. In most cases, we can achieve the fast backups we need <strong>with</strong> LiteSpeed by<br />

using the minimum compression level <strong>and</strong> no encryption. In fact, sometimes the<br />

backups are dramatically faster.<br />

12

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!