OS6, rsync+ssh command line changes between reconnects

Latest OS6.
Large backup job running. At one point in the middle, there was a corrupted packet and the job restarted.
Why does the first iteration of the job have --acls, but the second start of the same job has --no-acls --no-perms ?

fvbackup_utils.c:655 (debug) write(/var/log/frontview/backup/status_backup_001,BACKUP_STATUS__IN_PROGRESS,0!!1401823175!!OK)
fvbackup_rsync.c:207 (debug) as_src=1 src.type=remote src.share_proto=rsync+ssh
fvbackup_utils.c:249 (debug) cmd= nice -n 10 rsync -v -8 --timeout=1800 --recursive --links --times --devices --specials --one-file-system --modify-window=1 --owner --group --acls --rsh='ssh -o StrictHostKeyChecking=no -o PasswordAuthentication=no -p 22' root@192.168.66.12:/c/ /data/Backup >/tmp/backup_001_copy.log 2>&1

Jun  4 08:55:00 Share sshd[12042]: Received disconnect from 192.168.66.15: 2: Packet corrupt
Jun  4 08:55:01 Share sshd[29741]: Accepted publickey for root from 192.168.66.15 port 41663 ssh2

fvbackup_rsync.c:207 (debug) as_src=1 src.type=remote src.share_proto=rsync+ssh
fvbackup_utils.c:249 (debug) cmd= nice -n 10 rsync -v -8 --timeout=1800 --recursive --links --times --devices --specials --one-file-system --modify-window=1 --owner --group --no-acls --no-perms --rsh='ssh -o StrictHostKeyChecking=no -o PasswordAuthentication=no -p 22' root@192.168.66.12:/c/ /data/Backup >/tmp/backup_001_copy.log 2>&1