Loading...
Loading...
In a rare instance, HPE MSA 2042, 2040, and 1040 SAN Storage arrays running a Linear Scheduled Replication Task may report a 362 Error-level report:The volume was not found on this system.Review of the Event logs shows a Scheduled Task running and reporting the following:362 ERROR Scheduler: Unable to replicate the volume. - The volume was not found on this system. (task: Task Name, task type: ReplicateVolume)This error occurs due to the Initial Replication snapshot taking longer than the Replication Task maximum timeout value. This error can occur due to I/O load, snap size, and array storage controller resources being limited at the time of the snap. This error will leave the local Replication Snap from this Scheduled Task on the source array. The replication will not take place, and the destination array will not show this replication.
Only linear replication on the following products is affected:HPE MSA 2042 SAN StorageHPE MSA 2040 SAN StorageHPE MSA 1040 SAN Storage
HPE MSA 2042, 2040, and 1040 SAN Storage should be upgraded to firmware GL225P001.HPE has included improvements to GL225P001 to decrease risk of this issue occurring; however, in the rare situation that the issue occurs again on GL225P001 firmware, HPE recommends that the Replication Snap left on the source array is deleted (via the SMU/CLI), and the next Replication Task that is scheduled is run. The next scheduled Replication Task will run successfully and Replicate to the remote target array. No further actions are required.RECEIVE PROACTIVE UPDATES: Receive support alerts (such asCustomer Advisories), as well as updates on drivers, software, firmware, andcustomer replaceable components, proactively in your e-mail through HPESubscriber's Choice. Sign up for Subscriber's Choice at the following URL:Proactive Updates Subscription Form
Operating Systems Affected:Not Applicable
Click on a version to see all relevant bugs
Hewlett Packard Enterprise Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.