Backup data saved with the Fixed Host name when it is triggered by Floating Host

1. The networker is 18.2 version. 

2.  The backup Host is the Telecom typical server  .

        Active Host  + StandbyHost.  

        There is an floating IP to access the server when it is active. 

3.  The Networker server configure the hostname as 

10.76.90.104 zxiaMCASR555
10.76.90.170 zxiaMCASR555-0-0-1
10.76.90.199 zxiaMCASR555-0-0-9

 4.  When we configured zxiaMCASR555  as the client resource,   It will access to the 10.76.90.104. 

   However,  the backup indicate the zxiaMCASR555-0-0-9(active)  will send the backup data to the storage server.

   Don't know how to configure to make Networker Client to use the (floating Host) not the (fixed Host) to communicate with  Networker Server ?  

   The direct save feature is enable (default)

see the logs 

[1] Action Log -- ( I guess it triggered by networker server to networker client)   it is expected.

suppressed 4780 bytes of output.
12/17/2019 10:41:29 AM Starting the '/repsysdata' job on host 'zxiaMCASR555'.
12/17/2019 10:41:29 AM Unable to find any full backups of the save set 'zxiaMCASR555:/repsysdata' in the media database. Recommending that a full backup be performed.
12/17/2019 10:41:29 AM zxiaMCASR555:/repsysdata started
12/17/2019 10:41:29 AM save -LL -s host-10-76-90-213 -g McasProtection/PLATrepsysdata/backup/PLATrepsysdata1 -a "*policy action jobid=32909" -a "*policy name=McasProtection" -a "*policy workflow name=PLATrepsysdata" -a "*policy action name=backup" -y "Fri Jan 17 23:59:59 GMT+0800 2020" -w "Fri Jan 17 23:59:59 GMT+0800 2020" -f - -m zxiaMCASR555 -b MCAS -o REQUESTED_LEVEL:level=incr; -l full -q -W 78 -N /repsysdata /repsysdata
12/17/2019 10:41:35 AM The save job for the save set '/repsysdata' on the host 'zxiaMCASR555' has been completed.
12/17/2019 10:41:35 AM zxiaMCASR555:/repsysdata succeeded.
12/17/2019 10:41:35 AM PLATrepsysdata1:zxiaMCASR555:/repsysdata See the file '/nsr/logs/policy/McasProtection/PLATrepsysdata/backup_032909_logs/32911.log' for command output.
12/17/2019 10:41:40 AM Action backup traditional 'backup' with job id 32909 is exiting with status 'succeeded', exit code 0

[2] Save log .. It is triggered by Networker client ,  (  we expected the zxiamcasr555 as the host) --  It is useful fro the backup.

  81407:save: Step (1 of 7) for PID-22955: Save has been started on the client 'zxiamcasr555-0-0-9'.
174412:save: Step (2 of 7) for PID-22955: Running the backup on the client 'zxiamcasr555-0-0-9' for the save set '/BACKUP/platdb.tgz'.
180569:save: Identified a save for the backup with PID-22955 on the client 'zxiamcasr555-0-0-9'. Updating the total number of steps from 7 to 6.
174920:save: Step (3 of 6) for PID-22955: Contacting the NetWorker server through the nsrd process to obtain a handle to the target media device through the nsrmmd process for the save set '/BACKUP/platdb.tgz'.
174908:save:Saving the backup data in the pool 'MCAS'.
175019:save:Received the media management binding information on the host 'host-10-76-90-213'.
174910:save:Connected to the nsrmmd process on the host 'host-10-76-90-213'.
174922:save: Step (4 of 6) for PID-22955: Successfully connected to the target media device through the nsrmmd process on the host 'host-10-76-90-213' for the save set '/BACKUP/platdb.tgz'.
174422:save: Step (5 of 6) for PID-22955: Reading the save sets and writing to the target device.
174416:save: Step (6 of 6) for PID-22955: Backup has succeeded. Save is exiting. See the savegrp log to track the closure steps of the backup.
zxiaMCASR555: /BACKUP/platdb.tgz level=full, 22 MB 00:00:00 4 files
completed savetime=1576550456
94694:save: The backup of save set '/BACKUP