Monitoring AIR Replication of a large backup image

I would look inside  /disk/log/spad/replication.log    & the output of

/usr/openv/netbackup/bin/admincmd/nbstlutil report -lifecycle <AIRname>

Thank you watsons,

This is the backup image being replicating:

med5220im01:/disk/log/spad # bpimagelist -backupid msiefsp_1402088404 -U
Backed Up         Expires       Files       KB  C  Sched Type   Policy
----------------  ---------- -------- --------  -  ------------ ------------
06/06/2014 23:00  06/20/2014  3334836 1875470356  N  Full Backup  W_SIEFSP

med5220im01:/disk/log/spad # nbstlutil stlilist -backupid msiefsp_1402088404
V7.0.1 I msiefsp_1402088404 DR_SLP_MED5220IM01-REPL_Ret-14days 2
V7.0.1 C *Remote*Master* 2 3

med5220im01:/disk/log/spad # nbstlutil stlilist -backupid msiefsp_1402088404 -U
Image msiefsp_1402088404 for Lifecycle DR_SLP_MED5220IM01-REPL_Ret-14days is IN_PROCESS
  Copy to *Remote*Master* of type DUPLICATE_TO_REMOTE_MASTER is IN_PROCESS

It's about 1.8 tb

here is the output of the report command you suggest:

med5220im01:/disk/log/spad # nbstlutil report -client msiefsp

Backlog of incomplete SLP Copies
        In Process (Storage Lifecycle State: 2):
                Number of copies:       1
                Total expected size     3840509 MB

SLP Name: (state)                                 Number of copies: Size:
DR_SLP_MED5220IM01-REPL_Ret-14days (active)                    1     3840509 MB

Total:                                                         1     3840509 MB

why is there so much data to trasfer? how much data have been replicated?

Your SLP DR_SLP_MED5220IM01-REPL_Ret-14days  may have a total of 3840509 MB data to be replicated to remote master, the image msiefsp_1402088404 (1.8TB) is probably just part of the 3.8 TB. Why is there so much data? Really depend on how you configure the backup to go through AIR. If you don't want that much data, just scale down your backup selection.

In /disk/log/spad/replication.log, you can do a "tail -f" to follow the progress of the replication, see how fast it goes. Some performance tuning is available in 

http://www.symantec.com/docs/TECH204574

Thank you again watson, but I need some hint to understand the replication.log

how I find the exact lines related to my big replication? I don't find the backup image name, and the "Job ID" that I read doesn't match with what I see in bpdbjobs command:

June 12 09:02:42 INFO [1092761920]: ===  Replication Monitor  ===
June 12 09:02:42 INFO [1092761920]: Job ID: 1624, Target: pdde://med5220ps01, Segments Processed: 5355956, Age: 152025 seconds
June 12 09:02:42 INFO [1092761920]: Job ID: 2170, Target: pdde://med5220ps01, Segments Processed: 2096539, Age: 10398.1 seconds
June 12 09:02:42 INFO [1092761920]: There are 2 replication jobs currently running and 0 jobs waiting in the queue

The first job (ID 1624) is running since 42 hours, so it could be my job... so I know that 5355956 segments were processed... but what is the total number of segments?

Thank you!

The segment is for deduplication processing,  I don't think you can work out the actual duplication progress by this. I will try to find out if there is other way..