Hi
I have read an IBM white paper regarding electronic vaulting.
https://www.ibm.com/developerworks/c...torage%20pools
Suggested Scenario is this:
1. write the data to a de-dupe enabled pool
2. Copy the data to a remote dedupe enabled copy pool (i assume using backup stg)
3. Copy the data to a local pool (non-dedupe) (i assume using backup stg)
4. Not sure how this works, but i thought it not possible to run an incremental backup stgpool twice, for the
same pool. Once an incr backup stg is complete, it will find no data to process if i run it again.
The detail in the doc mentions setting up device classes, pools and backup the stgpool to the de-dupe copy pool,
but no mention of the local copy pool.
Anyone shed some light on this please?
Any comments/thoughts welcome
I have read an IBM white paper regarding electronic vaulting.
https://www.ibm.com/developerworks/c...torage%20pools
Suggested Scenario is this:
1. write the data to a de-dupe enabled pool
2. Copy the data to a remote dedupe enabled copy pool (i assume using backup stg)
3. Copy the data to a local pool (non-dedupe) (i assume using backup stg)
4. Not sure how this works, but i thought it not possible to run an incremental backup stgpool twice, for the
same pool. Once an incr backup stg is complete, it will find no data to process if i run it again.
The detail in the doc mentions setting up device classes, pools and backup the stgpool to the de-dupe copy pool,
but no mention of the local copy pool.
Anyone shed some light on this please?
Any comments/thoughts welcome