Hi Tom,
Thanks for replying.
The Product uses native supported Progress way to backup and restore the databases.
But instead of storing the data to a local disk, all the data is sent directly to the backup system.
An example of how this can improve the backup and especially restore / recovery.
1. Progress backup to local disk takes 1 hour
2. TSM File backup of local disk (progress backup) to the TSM Server takes 1 hour
The above example will take 1h + 1h = 2h to protect the data.
With Data Protector for Progress, the below steps will the describe the same:
1. Backup of Progress directly to TSM takes 1 hour
The complete protection will be shorter.
No risk of loosing data.
What happends in the first example if TSM File backup is protecting a progress backup file, while the progress backup to local disk is running?
- The result would be a corrupt backup in TSM
Here is an example how the restore will be faster compared to the other method:
1. restore full backup from TSM to local disk, takes 1 hour
2. execute progress restore of the full backup, takes 1 hour
3. restore incremental backup from TSM to local disk, takes, 20 minutes
4. resore incremental progress data to the database, takes 20 minutes
5. restore after images from TSM to local disk, takes 10 minutes
6. restore after images from local disk to the progress databases, takes 10 minutes
The total restoration time might be as long as 3 hours
With Data Protector solution, the restore is done directly to the progress database
1. full restore from TSM to progress, takes 1 hour
2. inc restore from TSM to progress, takes 20 minutes
3. after image restore from TSM to progress, takes 10 minutes.
The total restore is now down to amazing: 1 hour and 30 minutes
Another benefits is that you do not need the expensier local disk space, which will lower the TCO for the solution.
And that that you will get benefits with deduplication and compression in TSM, compared to not using the solution.
How much data would be different between each full backup in progress?
For a normal Oracle database for example, the reduction ratio for 30 days retention time, and 2 full backup per week, incremental in between, and archive log backups would be ~80%.
So I would guess that you would see something similare here too.
And with this solution you can also protect the data over low performance bandwidth, because of the "client deduplicaiton" options.
Please let me know if this explains the benefits with the solutions.
Regards Tomas