|
Solution Search:
|
Related Best Practices
How to implement snapshots
It can take up to 12 hours or more to process a full backup job and move the entire backup volume to tape or disk. For many companies, that's just too much time. IT departments can use snapshots to capture entire storage environments, or simply track changes to the state of mission-critical systems. Snapshots can establish recovery points in just a fraction of the time...
More...
How to implement disk-to-disk backups
and location are needed. Below are a series of best practices that can ease implementation of disk-to-disk (D2D) backup.
Preprocess files before moving Processing a backup job takes time and demands significant work from the backup server. Some storage or backup administrators choose to process the entire backup job to the local server first, and then move the backup... More...
How to improve tape backup performance and reliability
drives. Experts note that some organizations can ease shoeshining by processing the backup job to disk first, and then streaming the completed job to the tape system. This approach allows all of the server's processing power to focus on moving backup data rather than creating the backup and moving data at the same time.
Use data reduction technologies to shrink the... More... FAQ's
Server-free backup FAQ
present that data to some other system or device that can copy the data to tape. The typical way that this is done is via a dedicated backup server. So, you have a server that's being backed up. It's using data that's on the storage area network (SAN), which is being controlled and split off and snapped by a backup server...
More...
Data deduplication FAQ
going on. You have recoveries going on. You have data being moved off to tape. It just becomes a much more complex, dynamic environment.
Some of the technologies I personally think are enterprise-ready are Dilligent Technologies and Sepaton. Both companies have had products on the market for some time now... More...
What type of data reduction ratios should you realistically expect using deduplication?
at it in that context, you'll hear advertised ratios of anywhere from 10 to 500X.
But, realistically, I think it's safe to assume a ratio of anywhere between 13 to 17X. You'll probably see lower ratios on target-based deduplication, and you'll see higher ratios on source-based deduplication just because of how... More... |