Known Issues

The following are known issues as of the release of ShadowControl 3.6.0. If possible, Arcserve will fix these issues for the next ShadowControl release.

• An SPX job policy that uses the All Volumes option might automatically add an external USB drive to a backup job if it is connected when ShadowControl checks the policy job status. This can cause DiffGen incrementals if the USB drive is regularly removed and reconnected to the endpoint.
• ShadowControl cannot properly push install or update the endpoint agent to Windows XP/Server 2003 (including 2003 R2) endpoints, resulting in an endpoint in a bad state. To avoid this, ShadowControl 3.6.0 excludes XP and 2003 endpoints from push install operations. You must manually install and update the endpoint on these endpoints.
• ShadowControl might not properly activate ShadowProtect when attempting to use MSP keys generated from the EU MSP Portal (eu.storagecraft.com/msp). If the activation fails, you can still activate the endpoint manually from the Endpoint Details page.
• Reassigning an endpoint to a new policy might not start a new full backup at its scheduled time. The workaround is to unsubscribe and then re-subscribe the endpoint to the appliance.
• Uploading a malformed CSV file causes Server 500 errors on the ShadowControl Discovery page. Make sure to follow the example CSV file format to avoid this issue.
• Uploading a CSV source file reads the entire file into the appliance memory. A very large file could crash the appliance by consuming all memory.
• After manually updating a ShadowProtect endpoint to SPX, the "Last Success" field in Endpoint Details might not update properly. To resolve this, do the following:
• Stop the endpoint agent service.
• Delete the endpoint database, located at \Program Data\StorageCraft\endpt\endpt.db3.
• Start the endpoint agent service.
• The appliance sometimes fails to properly expire a token on the specified expiration date.
• The appliance sometimes treats Organization-specific tokens as Global tokens.
• Email notifications fail if the Contact email address has Unicode characters in it.