My customer just testing Storage accelerator in his environment and has some questions.
Scenario 11.36 : Client installed with file agent. SA in place and does its work for weeks. Now the connection to the S3 library failed for some reason.
We observed that backups still running but without SA (fall back) over a MA.
We also observed that backups do not come automatically back to SA if network connection to S3 lib is repaired.
We found some keys in registry which may steer the behavior, but we do not completely understand how the software decided to use the Storage accelerator feature or not.
If we have no connection to cloudlib the two keys are created.
The StorageacceleratorAutodisabledUntil key seems to renew all 24 hours
The StorageacceleratorConsecutiveFailureCount seems to be increased after timestamp StorageacceleratorAutodisabledUntil was reached if “S3 network connection” is down.
Max value is 8 . After this count value SA does not try again to use a direct connection to the S3 library independent if we have a valid connection or not.
Recycle the services does not change the values of the keys.
Removing the keys cause that SA checks the connection to S3 lib again and if possible data go directly to S3 lib without going through MA
Can anybody exactly explain how this SHOULD work?
