Release Notes

Known Issues 7
Issue ID Functional
Area
Description Workaround/Resolution
MDT-220994 Data Protection The replication session may not be
deleted once a Protection Policy is
unassigned from the storage resource.
To delete the replication session, do the
following:
1. If Protection Policy is not assigned to
the storage resource, reassign the the
same Protection Policy that was
previously assigned to the storage
resource.
2. Unassign the Protection Policy from
the storage resource.
MDT-133408 Data Protection
When a volume group is created with
member volumes and is protected by a
protection policy that includes a
replication rule, the volume group
members may be delayed in being
replicated to the remote system until
the next RPO cycle. The default
replication rule RPO value in
PowerStore Manager is 1 hour, but it
can range from 5 minutes to 24 hours.
If the remote system connection is
healthy, the member volumes should
automatically be replicated to the
destination during the next RPO cycle.
To update the member volumes on the
destination before the next RPO cycle,
navigate to Protection-> Replication,
select the volume group session and
perform a "Synchronize" operation.
MDT-146780 Data Protection
When deleting a snapshot rule, the
snapshot rule may not appear to be
deleted, and the following error
appears: "The system encountered
unexpected backend errors. Please
contact support. (0xE0101001000C)".
Do not continue using the rule for
protection.
Delete the snapshot rule again. The same
error appears, but the rule will be
deleted.
MDT-117061 Hardware When beginning cluster creation, the
hardware status is incorrectly indicated
as not configured for clustering.
Wait a few minutes and try again.
MDT-190232 Hardware
The svc_node shutdown command may
reboot the node instead of powering it
off.
Run the svc_node shutdown command
again when the node has finished
rebooting.
MDT-137439 Import If an import from a Unity or VNX2
system to PowerStore is cancelled by
the user or fails for some reason, it is
possible that subsequent attempts to
import the volume will also fail.
Remove the Unity or VNX2 as a remote
system and then add it again. This action
will clear the issue and allow the import
to proceed.
MDT-174416 Import
Hosts groups are not supported for
agentless import.
None