Microsoft-Windows-StorageReplica-Service

Fields #

Message #

Computer account to security identifier (SID) conversion failed.

ReplicationGroup: %1
ComputerAccount: %2
Error: %3

Guidance: This may cause connectivity issues when a computer tries to connect to its replication group partners. For security purposes, replication endpoints are secured so that only administrator-defined partners can connect. This is done through an Access Control List (ACL) consisting of replication partner computer accounts that is applied on the replication endpoint. Once the SID lookup issue is resolved, restart the Storage Replica service (for standalone replication group deployments) or restart the cluster resource group consisting of replicated disks (for clustered replication deployments).

Fields #

Fields #

Message #

Created a new replication group.

ReplicationGroupName: %1
ComputerName: %2
ReplicationGroupId: %3

Fields #

Fields #

Message #

Removed an existing replication group.

ReplicationGroupName: %1
ComputerName: %2
ReplicationGroupId: %3

Fields #

Fields #

Message #

Created a new replication partnership.

SourceReplicationGroupName: %1
SourceComputerName: %2
DestinationReplicationGroupName: %3
DestinationComputerName: %4

Fields #

Fields #

Message #

Deleted an existing replication partnership.

SourceReplicationGroupName: %1
SourceComputerName: %2
DestinationReplicationGroupName: %3
DestinationComputerName: %4

Fields #

Fields #

Message #

Added a new partition into a replication group.

ReplicationGroupName: %1
ComputerName: %2
PartitionId: %3

Fields #

Fields #

Message #

Removed an existing partition from a replication group.

ReplicationGroupName: %1
ComputerName: %2
PartitionId: %3

Fields #

Fields #

Message #

Made this replication group the source of replication.

ReplicationGroupName: %1
ComputerName: %2
ReplicationGroupId: %3

Guidance: This event is triggered when an administrator performs a role switch, which reverses the replication direction. Changing direction may lead to data loss on the previous source if using asynchronous replication. Always perform a backup before taking any remedial actions.

Fields #

Fields #

Message #

Made this replication group the destination of replication.

ReplicationGroupName: %1
ComputerName: %2
ReplicationGroupId: %3

Guidance: This event is triggered when the replication direction is modified. This can be a result of the initial configuration of a partnership or an administrative action such as a role switch or modification of the partnership to which this replication group belongs. Changes to an existing replication direction may lead to data loss on the previous source if using asynchronous replication. Always perform a backup before taking any remedial actions.

Fields #

Fields #

Message #

Suspended replication of an existing replication group.

ReplicationGroupName: %1
ComputerName: %2
PartitionId: %3

Guidance: This event is triggered when an administrator pauses replication, which temporarily stops data synchronization. You can resume replication using the Sync-SRGroup cmdlet.

Fields #

Fields #

Message #

Resumed replication of an existing replication group.

ReplicationGroupName: %1
ComputerName: %2
PartitionId: %3

Fields #

Fields #

Message #

Removed an invalid partition record.

DiskId: %1
PartitionId: %2
Status: %3

Guidance: The partition should now be available for regular operations.

Fields #

Fields #

Message #

Failed to remove an invalid partition record.

DiskId: %1
PartitionId: %2
Status: %3

Fields #

Fields #

Message #

Successfully removed an orphan Storage Replica cluster resource.

Resource Name: %1
Status: %2

Fields #

Fields #

Message #

Failed to remove an orphan Storage Replica cluster resource.

Resource Name: %1
Status: %2

Fields #

Fields #

Message #

Storage Replica service failed to connect to failover cluster.

ReplicationGroup: %3
ClusterName: %5
Error: %6

Guidance: This will prevent replication. Verify that the cluster name is available. Once the network name is available, restart the secondary replication group.

Fields #

Fields #

Message #

Storage Replica service found a leftover non-cluster replication group configuration.

ReplicationGroup: %1

Guidance: This will prevent replication for that replication group. Make sure to cleanup non-cluster replication groups on the computer before joining cluster.

Fields #

Fields #

Message #

Storage Replica CIM provider API is invoked: %1

Fields #

Fields #

Message #

Succeed granting Storage Replica delegation on computer %1
for user %2
Status: %3

Fields #

Fields #

Message #

Failed granting Storage Replica delegation on computer %1
 for user %2
Status: %3

Fields #

Fields #

Message #

Succeed revoking Storage Replica delegation on computer %1
 from user %2
Status: %3

Fields #

Fields #

Message #

Failed revoking Storage Replica delegation on computer %1
 from user %2
Status: %3

Fields #

Fields #

Message #

Succeed reverting granting Storage Replica delegation on computer %1
 for user %2
Status: %3

Fields #

Fields #

Message #

Failed reverting granting Storage Replica delegation on computer %1
 for user %2
Status: %3

Fields #

Fields #

Message #

Succeed reverting revoking Storage Replica delegation on computer %1
 from user %2
Status: %3

Fields #

Fields #

Message #

Failed reverting revoking Storage Replica delegation on computer %1
 from user %2
Status: %3

Fields #

Fields #

Message #

Unable to update log size to %1 bytes as requested. Instead, the log size will be updated to %2 bytes.

ReplicationGroupName: %3

Fields #

Fields #

Message #

Remote procedure call from Storage Replica Driver to Storage Replica user mode service completed with error.

Error: %1

Fields #

Fields #

Message #

Storage Replica Volume Shadow Copy Service Writer OnIdentify failed. 

Error (HRESULT): %3

Guidance: Storage Replica will not be notified of backup or restore operations. If any files were successfully restored onto a replicated volume, you must remove the replication partnership and recreate it. The seeded option is recommended when recreating replication in this case, in order to save initial synchronization time

Fields #

Fields #

Message #

Storage Replica Volume Shadow Copy Service Writer post-restore process failed. 

Error (HRESULT): %3 

Guidance: If any files were successfully restored onto a replicated volume, you must remove the replication partnership and recreate it. The seeded option is recommended when recreating replication in this case, in order to save initial synchronization time

Fields #

Fields #

Message #

Storage Replica reset the log after a restore of a Volume Shadow Copy Service backup. 

Volume name: %1
PartitionId: %2
Error (HRESULT): %3

Guidance: Storage Replica will perform initial synchronization of this volume.

Fields #

Fields #

Message #

Storage Replica was unable to reset the log after a restore of a Volume Shadow Copy Service backup. 

Volume name: %1
PartitionId: %2
Error (HRESULT): %3

Guidance: You must remove the replication partnership and recreate it. The seeded option is recommended when recreating replication in this case, in order to save initial synchronization time

Fields #

Fields #

Message #

Storage Replica service added a partner ACL to the share. 

Replication group name: %1
Result (HRESULT): %2

Fields #

Fields #

Message #

Storage Replica service did not add a partner ACL to the share. 

Result (HRESULT): %1

Guidance: Failure to ACL the share indicates a problem with SID lookups against an Active Directory domain controller. This can be caused by problems with network communication, firewall, DNS lookup, or other environmental dependencies. After resolving this issue, restart the Storage Replica service.

Fields #