Forum Discussion

Gnana_Sekaran's avatar
10 years ago

Actual amount of data Replicated through AIR

Is there any way we can find out the actual amount of data that is being transferred through WAN (AIR) from Onestie site to Other site.

I referred the replication.log on the storage server .but calculating each CR-sent is time taking and Opscenter SLP report is showing only the total size of the image not the actual transferred size.

 

For an example : Client A backup is 5 TB &stored into de-dup disk pool and its 90 % de-duplicated .this backup images are replicated to DR site long back ago which took more than a week to complete 5 TB transfer.

 

For the same Client A -recent backup completed with 98 % de-dup ,when i try to replicate the current image its completed in 2 hours ,that means only the changes since last replicated data was transferred over WAN or the entire 5 TB was transferred ?

  • If its solely used for this backup then both sides should be looking the same in terms of space used. If other backups use it as well, then it gets too complicated.

  • The first time it had to replicate everything as there was probably no reference on the other site/appliance. THe next time it could replicate only changes, and therefore took only 2 hours. There is no easy way to figure out how much data was sent (besides look at the CR sent values).

  • Thanks Riaan 

    I just compared the disk pool utilization before/post replication.

    We replicated 200TB of  font end data (with out de-dup) from onsite to DR site and but only close to 20TB was utilized  at target n the disk pool.

    That means is it only about 20TB was transfered over WAN ?

    if so only the changes (Block level changes) verified with desitnation METADATA is getting replicated then how netbackup compares this metadata either will it be at source or destination .(compare the data with last time replication )

  • Not sure what you mean with "We replicated 200TB of  font end data (with out de-dup)"? I understand the FETB is 200, but what is size of the that data in your local pool? Its probably not 200TB, its probably 20TB, which would be the same amount as what would be on the DR pool. If you replicated each and every backup taken to the local pool.

  • Thanks Riaan,I mean the total front end backup volume is 200TB and its stored in 50TB MSDP disk pool.

    Size in the local disk pool is about 48TB & only full backup was replicated.

     

     

     

     

     

     

  • If its solely used for this backup then both sides should be looking the same in terms of space used. If other backups use it as well, then it gets too complicated.