04-02-2021 07:25 AM - edited 04-02-2021 07:30 AM
04-02-2021 08:02 AM
Are you replicating from a NetBackup appliance to another NetBackup appliance?
04-02-2021 08:23 AM
04-02-2021 09:39 PM
04-02-2021 10:16 PM
04-02-2021 11:02 PM
04-03-2021 01:20 AM
Hi pats,
Source:
.Settings> FibreTransport Deduplication Show
[Info] Fibre Transport Deduplication is disabled.
Target:
.Settings> FibreTransport Deduplication Show
[Info] Fibre Transport Deduplication is enabled.
I've run the command at other appliances and the result are all like this. Is this normal for the receiving end only to be enabled?
04-03-2021 04:33 AM
04-04-2021 01:38 AM
04-04-2021 02:38 AM
04-04-2021 06:28 PM
Hi, what lines should be observed from the logs?
As i have mentioned before, we can see traffic/transaction going on from fcip router management tool at the ports related. From activity monitor, we can also se this line at detailed status
Apr 5, 2021 12:25:48 AM - Info sourceA (pid=164219) StorageServer=PureDisk:sourceA; Report=PDDO Stats for (sourceA): scanned: 16425315 KB, CR sent: 70672 KB, CR sent over FC: 59586 KB, dedup: 99.6%, cache disabled, where dedup space saving:98.0%, compression space saving:1.5%
Apr 5, 2021 12:25:48 AM - Replicated backup id client_1617386992 successfully
Apr 5, 2021 12:25:48 AM - Info bpdm (pid=164219) EXITING with status 0
According to veritas support, this is the the CR sent over FC is the indicator that the data is going through FC.
04-05-2021 05:07 PM
Hi @fira_gojira
IIRC, it is only the data that is transferred over FC. The catalog metadat is still sent via the network. As per the log entry - you are sending 70M via the network which should be the metadata to allow the import to occur, and 60MB via FC which would be the backup image data (optimized duplication from the 16.4G source).
Now this shouldn't really affect your network bandwidth as typically the backup metadata is small compared to the data (the only time this may be different is for a file server with a large number of small files - but that would be an exception I would have thought).
Does the network capping affect the overall transfer rate?
David
04-05-2021 07:55 PM - edited 04-05-2021 07:57 PM
Hi David,
Thanks for the explanation. That actually makes sense. To answer your question, the kbps rate in the detailed status looks much smaller but the replication is actually not so slow. The slowest part is for the Current kb Written to increase from 0kb. We have one 3tb image replication job that stayed at 0kb for 155 hours, and when the Current kb Written start going up, the job finish in less than 2 hours. The kb/s in detailed status only shown 6478. This happened after the network capping takes effect.