InMage isn’t dedupe – it’s better than dedupe

InMage backup uses less disk storage than leading dedupe backup solutions, while retaining data for a longer term and providing better RPO and RTO.

√ Long-term storage requirements are similar or better than dedupe

√ InMage provides near zero RPO and RTO with a disk paradigm

√ Fast recovery – roll back to any point in time and the data and applications are ready to go with near zero impact on production performance

√ Multi-tier Sparse Retention allows you to store less and less journals, the older the data gets

√ Requires no additional headroom that is necessary in dedupe for tracking all the dedupe pointers

√ InMage is a light-weight (~0-3%) low impact continuous process that is not noticeable when running

InMage Solves Traditional Backup

 

Problems Dedupe only Minimizes

Challenges with Dedupe

ELIMINATE BACKUP WINDOWS
(Figure 1)

Backup windows are still a challenge even when using dedupe

Instantaneous and granular recovery to any point in time - make data recoverable as soon as it's created

Backup is a point in time process resulting in loss of data

Eliminate resource overhead by capturing changes in data as they occur
(Figure 2)

High impact on servers, storage and network during full and repeat backups

Recover both data and applications

Recover only data

Fast recovery from disk - get what you need back up and running quickly and reliably
(Figure 3)

Dedupe has to restore older full backups and then apply differentials to get to the current time costing time and money

Flexible to preserve your existing backup software and storage subsystems, also allowing you to buy and/or use different products as needed

Limited to work with particular backup software products, just hope you work with ones that are supported

Restore from any previous point in time as far back as you want with no impact on performance or scalability

The further back in time you want to go the more headroom you will need increasing cost and limiting scalability

Reduce target storage requirements with thin provisioning, sparse retention and compression

Exponential storage growth over time due to full and repeat backups

Scalable to deal with increasingly large data sets because InMage only manipulate changed data

Have to manipulate full backups each time it's processed

Over 5x reduction in overall target storage by customizing retention policies
(Figure 4)

Dedupe does not allow customization of retention points since full backups are needed

 

 

 
Eliminate Backup Windows

Figure 1. InMage Scout eliminates backup windows by continuously backing up changes as they occur in real time with no impact to production environments. Figure 2. A major downside to deduplication is the increase load on network resources that occur from backup windows. InMage eliminates backup windows by capturing data as it's created so there is no impact on network resources.
Figure 3. With push-button application failover InMage Scout can recover your data and applications within minutes to have you backup and running. Figure 4. Application consistent recovery points available with sparse retention minimizes target storage requirements by retaining fewer application points for older data.

 

For more information on how InMage eliminates the need for deduplication and can provide you with an all around better backup and replication software:

InMage Scout Home Page >>
White Paper: InMage: A Compelling Alternative to Deduplicating Virtual Tape Libraries >>