Resolving Scan, Migrate / Store, Restore, and Database Backup Project Issues

Issue	Cause
The StorCycle solution says that a project name “already exists”, but the project name does not display in any project lists.	Even after deleting a project, the StorCycle solution must maintain the history of any associated jobs to a project. Once a project has been used in some manner that name cannot be reused even if deleted.
The BlackPearl storage location does not display as a source for scans or migrate / store projects.	Currently, a BlackPearl system cannot be configured as a source storage location.
Peak hour restrictions do not take effect at the scheduled times.	The time range is in Coordinated Universal Time (UTC), not local time.
Not all of the expected objects in a migrate / store project are migrated / stored.	§ If Use Last Scan is selected: § Only files present in the directory when the prior scan executed are considered for migration. Files added after the last scan are not considered. § The current size and age of the file are considered against the selection criteria when determining files to migrate / store. § The StorCycle solution does not migrates files that have been previously migrated, even if the file has changed on the source storage device. If you want to archive the file again, you must first move it to another path location. § If a project attempts to migrate / store a file to a location in which a file of the same name already exists, the job fails. The existing file is not overwritten. § When a migrate / store job is canceled, the StorCycle solution leaves the job in whatever completion state it was in when the job cancelation command was received. No rollback occurs.
Not all expected objects in a restore project are restored.	§ If a project attempts to restore a file to a location in which a file of the same name already exists, the job fails. The existing file is not overwritten. § When a restore job is canceled, the StorCycle solution leaves the job in whatever completion state it was in when the job cancelation command was received. No rollback occurs.
The StorCycle solution does not migrate / store all of the files meeting either the Object Age or Object Size criteria.	Only those objects meeting the Object Age and the Object Size requirements are included.
The StorCycle solution did not remove / replace all of the files that were migrated / stored.	When a migrate / store project is configured to delete the source file or replace the source file with an HTML file after migrating / storing, after the file is migrated / stored, but before it is deleted or replaced, the StorCycle solution checks the file property date/time and the file size to ensure that the file did not change. If the file changed during this time, then the file is not deleted from the source storage and a note is added to the job logs.
HTML links replacing migrated / stored files include an IP address.	If the network does not support reverse DNS lookups, then the IP address of the storage location is used in the HTML link created during a migrate / store job.
When files are migrated / stored to a BlackPearl storage location configured to use packing and the zip file is downloaded from the BlackPearl system directly using the Eon Browser or a BlackPearl client, double-clicking the zip file does not open a directory with the individual files.	Using 7-zip or another non-OS-native zip application is necessary to extract the files.
A scan, migrate / store, or restore job fails with an error of “working directories are not siblings”.	A job using the same storage location branch is already in progress. Wait for the original job to complete and try the second job again.
A canceled migrate / store job stays in a “canceling” state.	If you cancel a migrate / store job that uses a BlackPearl system as the target, and the final storage target of the BlackPearl data policy is offline or unavailable, the job stays in a “canceling” state until the final storage target is back online so that the data in flight can persist to the final storage target.
Recurring schedules are running an hour earlier or later than expected.	Daylights savings time is not handled by the solution, the server time is in UTC. So a scheduled job runs an hour earlier or later in local time than the original scheduled time depending on the time of year.
Limit Transfers During Peak Hours does not limit some transfers.	Limiting transfer during peak hours only applies when reading from the storage location. If the Storage Location Type is Source, this occurs when the location is scanned or is the source of a migrate / store project. If the Storage Location Type is Target, this occurs when a restore is done of a file previously migrated / stored to the target.
The permissions / ACLs on a directory changed after a restore.	When the StorCycle solution migrates / stores or restores files, it also migrates / stores or restores associated directories. While the StorCycle solution ensures that a file does not already exist on the target and does not overwrite the file, it may overwrite existing directories. When it overwrites the directory: § The Windows version of the StorCycle solution resets the permissions/ACL's based on the permissions/ACL's that are on the directory that it is migrating. § The Linux version of the StorCycle solution does not reset the permissions/ACL's (because Linux does not have an "Auto Inherit" flag like Windows).
Migrations were working, but then stopped working.	Check password expiration on the user running the StorCycle service.
With StorCycle running on a WIndows server, files are inheriting rights from the directory instead of keeping the files rights.	The user running the StorCycle service does not have the take ownership rights required. See Configure the User Account for instructions.
With StorCycle running on a Windows server, System Access Control Lists (SACLs) are not retained when the StorCycle solution migrates / stores Windows system files.	For Windows system files and CIFS files shares, the StorCycle solution migrate / stores and restores file permissions / ACLs, but does not migrate / store Alternative Data Streams or SACLs.
With StorCycle running a Windows server, the StorCycle solution displays the error "The process cannot access the file because it is being used by another process".	Having the target directory for a migrate / store job or the Restore Destination for a restore job open in Windows Explorer can cause this error. Close Windows explorer and try the job again.

File Transfer Failures

The StorCycle solution includes mechanisms to monitor file transfers. For cloud and BlackPearl targets, if there is a problem transferring a file, the StorCycle solution retries the file transfer several times before failing. For NAS targets, the file transfer fails after the first unsuccessful attempt. Whatever the target type – NAS, BlackPearl, or Cloud – if a file transfer fails, the file is marked as failed and the file failure is logged. The StorCycle solution then attempts to transfer the remaining files in the job. However, if a job has more than 10,000 files that fail to transfer, then the entire job ends and is marked as failed. Any files in the job that successfully transferred continue to reside on the target location. StorCycle does not attempt to clean up partially completed transfer jobs.

1-800-833-1132 : 1-303-449-6400