There are now-missing files that existed when rsync built the list of files to copy, but by the time rsync got to the files they were in fact missing. This is normal behavior as explained in the following paragraph. 

The vanished files are due to a couple of factors:
1. The appliance may have a large amount of data to back up and may take one or more days to copy the entire data set
2. The other factor is the index directories are dynamic and are frequently updating or changing. This is more likely to occur on appliances collecting file-based data.. 

When rsync starts the copy process it builds a list of files to process. Then when rsync actually copies the files the engine_archive process may purge them before they can be copied or the temporary index files may already be processed or changed and therefore rsync thinks they are missing. Both of these conditions are normal behavior. The former situation is more likely to happen when there are many terabytes of data to backup over a slow connection because that scenario will increase the chances the backup will take sufficiently long time to complete that engine_archive may purge some of the data that rsync plans to back up.

Unfortunately the missing files cause LogLogic LMI to state that the backup failed when it did not. This event has been reclassified as an INFO level log in a future LMI version.