Microsoft-Windows-StorageReplica

627 events across 5 channels

Event ID	Title	Channel
1000		Operational
1000	Transitioned to block copying from log record copying.	Admin
1200	Preparing destination for synchronization with source.	Operational
1201	Source completed preparing for replication.	Operational
1202		Operational
1202	Started block copying for a partition.	Debug
1203	Destination started to compare records from the source log with local log.	Operational
1204	Destination started to copy records from the source log.	Operational
1205	Destination started to copy data blocks from the source.	Operational
1206		Operational
1206	Recovery manager resumed for replica.	Debug
1207		Operational
1207	Recovery manager suspended for replica.	Debug
1208		Operational
1208	Block copy completed.	Admin
1209		Operational
1209	Block copy completed.	Admin
1210		Operational
1210	Bitmap recovery finished, but not all bitmap files have the same end LSN.	Debug
1211		Operational
1211	Bitmap recovery failed to save recovery bitmap back to primary.	Debug
1212		Operational
1212	Destination received reply with failure from source for its read disk request.	Debug
1213		Operational
1213	Destination received STATUS_RETRY in read disk blocks reply.	Debug
1214		Operational
1214	Bitmap recovery completed because there is no partition found for the replica.	Debug
1215	Block copy completed for replica.	Operational
1216		Operational
1216	Bitmap recovery failed for replica.	Debug
1217		Operational
1217	Recovery rollback completed successfully for replica.	Debug
1218		Operational
1218	Recovery rollback failed for replica.	Debug
1219		Operational
1219	Recovery failed to start log reader for replica.	Debug
1220		Operational
1220	Recovery successfully started log reader for replica.	Debug
1221		Operational
1221	Recovery log reader has reached the end of the sources log.	Debug
1222		Operational
1222	Recovery log reader terminated due to error in other recovery activity.	Debug
1223		Operational
1223	Recovery log reader terminated due to error in reply from source.	Debug
1224		Operational
1224	Recovery log processor started for replica.	Debug
1225		Operational
1225	Recovery log processor terminated for replica.	Debug
1226		Operational
1226	Recovery log processor encountered error when processing log record.	Debug
1227		Operational
1227	Source returned STATUS_RETRY to a read disk block request because the cluster …	Debug
1228		Operational
1228	Matching checkpoint log record found in source log.	Debug
1229		Operational
1229	No matching checkpoint log record found in source log.	Debug
1230		Operational
1230	Destination received failure reply from source when exchanging checkpoint …	Debug
1231		Operational
1231	Recovery rollback started for replica.	Debug
1232		Operational
1232	Checkpoint log record not found in destination log.	Debug
1233	Unable to prepare for replication.	Operational
1234	Destination unable to exchange checkpoint information with source.	Operational
1235	Destination successfully completed checkpoint exchange with source.	Operational
1236		Operational
1236	Recovery on a destination received a reply from a source containing zero log …	Debug
1237		Operational
1237	Block copy is in progress.	Admin
1238		Operational
1238	Unable to report progress.	Admin
1239		Operational
1239	The asynchronous destination can no longer meet the configured Recovery Point …	Admin
1240		Operational
1240	The asynchronous destination now meets the configured Recovery Point Objective …	Admin
1241		Operational
1241	The Recovery Point Objective (RPO) of the asynchronous destination is …	Admin
1242		Operational
1242	Initial sync block copy completed.	Admin
1243		Operational
1243	Initial sync block copy completed.	Admin
1244		Operational
1244	Storage Replica filter driver failed to update the sync state of the …	Admin
2000		Operational
2000	Unable to flush logged application write to data volume.	Admin
2200		Operational
2200	Start replication for replica.	Admin
2201		Operational
2201	Start replication for replica.	Admin
2202		Operational
2202	Stop replication for replica.	Admin
2203		Operational
2203	Stop replication for replica.	Admin
2204		Operational
2204	Partition belongs to a different replication group.	Admin
2205	Detected invalid replication mode in the configuration exchange request, the …	Operational
2206	Configuration exchange request contains invalid partner, the connection will be …	Operational
2207	Detected mismatching log disk logical sector size in the configuration exchange …	Operational
2208	Detected mismatching log size (in bytes) in the configuration exchange request, …	Operational
2209	Detected mismatching replica set count in the configuration exchange request, …	Operational
2210	Detected mismatching data partition size (in bytes) in the configuration …	Operational
2211	Detected mismatching data disk physical sector size in the configuration …	Operational
2212	Failed to lookup partition during configuration exchange, the connection will be …	Operational
2213	Detected duplicate replica set entries in the configuration exchange response, …	Operational
2214	Detected mismatching data partition size (in bytes) in the configuration …	Operational
2215	Detected mismatching log disk logical sector size in the configuration exchange …	Operational
2216	Detected mismatching log size (in bytes) in the configuration exchange response, …	Operational
2217	Detected mismatching replica set count in the configuration exchange response.	Operational
2218	Detected mismatching data disk physical sector size in the configuration …	Operational
2219	Detected duplicate replica set entries in the configuration exchange request, …	Operational
2220		Operational
2220	Replica is attempting to join consistency group.	Admin
2221		Operational
2221	Write ordering is not possible at this time for this replica.	Admin
2222		Operational
2222	Replica successfully joined consistency group.	Admin
2223		Operational
2223	Attempting to join replica to consistency group failed.	Admin
2224		Operational
2224	Successfully removed the replica from the consistency group.	Admin
2225		Operational
2225	Replica is successfully removed from the consistency group.	Admin
2226		Operational
2226	Failed to remove replica from the consistency group.	Admin
2227		Operational
2227	Successfully removed orphan log container.	Admin
2228		Operational
2228	Failed to remove orphan log container.	Admin
2229		Operational
2229	Successfully removed orphan log file for replication group.	Admin
2230		Operational
2230	Failed to remove orphan log file for replication group.	Admin
2231		Operational
2231	Replication group is online.	Admin
2232		Operational
2232	Failed to flush replication log for a partition.	Admin
3000		Operational
3000	Unable to create a log on the log volume.	Admin
3001		Operational
3001	Log truncation failed.	Admin
3002		Operational
3002	Log is corrupt.	Admin
3003		Operational
3003	Log metadata is corrupt.	Admin
3004		Operational
3004	Unable to read record from the log.	Admin
3005		Operational
3005	Unable to write a record to the log.	Admin
3006		Operational
3006	Unable to close the log file.	Admin
3007		Operational
3007	Unable to delete log file.	Admin
3008	Unable to close log read context.	Operational
3009	Unable to create marshalling area for log file.	Operational
3010		Operational
3010	Unable to create the log file.	Admin
3011		Operational
3011	Unable to read the log file metadata.	Admin
3012		Operational
3012	Failed to initialize the replication log path.	Admin
4000		Operational
4000	Failed to create network share for replication group.	Admin
4001		Operational
4001	Failed to delete network share for replication group.	Admin
4002		Operational
4002	Failed to modify network share for replication group.	Admin
4003		Operational
4003	Connection request rejected from a partner.	Admin
4004		Operational
4004	Failed to establish a connection to a remote computer.	Admin
4005		Operational
4005	Storage Replica detected a configuration mismatch in a replication group.	Admin
5001		Operational
5001	Entered preparation state.	Admin
5002		Operational
5002	Source entered ready state.	Admin
5003		Operational
5003	Source moved to failure state.	Admin
5004		Operational
5004	Source entered wait-for-quorum state.	Admin
5005		Operational
5005	Destination entered stand-by state.	Admin
5006		Operational
5006	Destination entered joining state.	Admin
5007		Operational
5007	Destination entered asynchronous replication state.	Admin
5008		Operational
5008	Destination moved to failure state.	Admin
5009		Operational
5009	Destination attempted to enter synchronous replication state.	Admin
5010		Operational
5010	Asynchronous destination entered wait state.	Admin
5011		Operational
5011	Attempted to take Replication Group offline.	Admin
5012		Operational
5012	Destination entered offline state.	Admin
5013		Operational
5013	Source replication group lost quorum.	Admin
5014		Operational
5014	Connection lost to the share hosting the partner replica.	Admin
5015		Operational
5015	Successfully established a connection to a partner replica.	Admin
5016		Operational
5016	Replica is offline.	Admin
5018		Operational
5018	State machine processing an event for replica.	Debug
5019		Operational
5019	State machine state has changed.	Debug
5020		Operational
5020	Destination entered synchronous replication state.	Admin
5021		Operational
5021	Replication state has changed.	Debug
6001		Operational
6001	Write IRP received	Performance
6002		Operational
6002	IoContext initialized	Performance
6003		Operational
6003	Write log workitem queued	Performance
6004		Operational
6004	Write log record completed	Performance
6005		Operational
6005	Send commit message	Performance
6006		Operational
6006	Commit message send completion	Performance
6007		Operational
6007	Commit response received	Performance
6008		Operational
6008	Commit completion	Performance
6009		Operational
6009	Application write IRP completed	Performance
6010		Operational
6010	Flush request issued	Performance
6011		Operational
6011	Write IRP issued to disk	Performance
6012		Operational
6012	Flush IRP completed	Performance
6013		Operational
6013	Flush completion	Performance
6014		Operational
6014	WVR message send	Performance
6015		Operational
6015	WVR message received	Performance
6016		Operational
6016	Commit log record request received	Performance
6017		Operational
6017	Commit log record reply sent	Performance
6018		Operational
6018	Flush data request received	Performance
6019		Operational
6019	Flush data reply sent	Performance
6020		Operational
6020	Message indicated	Performance
6021		Operational
6021	Write log workitem processing starts	Performance
6024		Operational
6024	Upcall Pre	Performance
6025		Operational
6025	Upcall Post	Performance
6026		Operational
6026	CLFS write log being	Performance
6027		Operational
6027	CLFS write log end	Performance
6028		Operational
6028	IoContext Created	Performance
6029		Operational
6029	IRP assigned to IoContext	Performance
6030		Operational
6030	IRP inserted into pending queue	Performance
6031		Operational
6031	Read IRP overlap detection started	Performance
6032		Operational
6032	Read IRP overlap detection completed	Performance
6033		Operational
6033	Read IRP forwarded to next driver	Performance
6034		Operational
6034	Read IRP completed	Performance
6035		Operational
6035	IoContext completed	Performance
7001	Created a raw partition manager.	Operational
7002	An error has occured when starting the raw ledger and stablizing the ledger …	Operational
7003	An error has occured when starting the raw ledger and building the in-memory …	Operational
7004	An error has occured when adding a raw log ledger.	Operational
7005	An error has occured when allocating the log file metadata handle.	Operational
7006	Same fileId exist when adding a raw log record ledger.	Operational
7007	An error has occured when adding a raw log record ledger.	Operational
7008	An error has occured when allocating the log file handle.	Operational
7009	An error has occured when adding a raw bitmap ledger.	Operational
7010	An error has occured when adding a raw bitmap record ledger.	Operational
7011	Log does not have any log records but the first log record offset is not zero.	Operational
7012	The next log record offset is not zero.	Operational
7013	Bitmap does not have any bitmap records but the first bitmap record offset is …	Operational
7014	The next bitmap record offset is not zero.	Operational
7015	Destroyed a raw partition manager.	Operational
7016	An error has occured when destroying a raw partition manager.	Operational
7017	No logs exist but bitmap file exists while destroying the raw ledger.	Operational
7018	Try to delete a log ledger while the log count is already 0.	Operational
7019	Try to delete a bitmap ledger while the partition count is already 0.	Operational
7020	Try to delete a raw bitmap ledger by property while the ledger is invalid.	Operational
7021	Try to delete a raw bitmap ledger by property while the ledger header is …	Operational
7022	Try to delete a raw bitmap ledger by handle while the ledger is invalid.	Operational
7023	Try to delete a raw bitmap ledger by handle while the ledger header is invalid.	Operational
7024	Try to delete a log metadata by handle while the ledger is invalid.	Operational
7025	Try to delete a log metadata by handle while the ledger is invalid.	Operational
7026	Try to delete a log file by handle while the raw handle is invalid.	Operational
7027	Try to delete a log file by handle while the ledger handle is invalid.	Operational
7028	Try to destroy a log file by handle while the raw handle is invalid.	Operational
7029	Try to destroy a log file by handle while the ledger handle is invalid.	Operational
7030	Clean up orphaned raw log ledgers for all replication groups or specific …	Operational
7031	Clean up orphaned raw log ledger and its related log files.	Operational
7032	Clean up orphaned raw bitmap ledger and its related bitmap files.	Operational
7033	Reconcile the raw ledger entries.	Operational
7034	The ledger entry is in transition state while buiding the in-memory ledger.	Operational
7035	Log record ledger validation failed due to invalid entry type, status or …	Operational
7036	Log ledger validation failed due to invalid entry type, status or checksum.	Operational
7037	Bitmap record ledger validation failed due to invalid entry type, status or …	Operational
7038	Bitmap ledger validation failed due to invalid entry type, status or checksum.	Operational
7039	Ledger entry cannot be in deleted state but with invalid entry type.	Operational
7040	Ledger entry type is invalid and is in use.	Operational
7041	Max ledger size must be zero for log or bitmap ledger entries.	Operational
7042	Log partition is full and cannot accomodate this file.	Operational
7043	A Ledger entry status cannot be any intermediate status right now.	Operational
7044	Could not find a slot to fit in this file.	Operational
8001	Raw Log Initialized.	Operational
8002	Raw Log Initialization Failed.	Operational
8003	Writting an empty log record completed with status.	Operational
8004	Writting an empty log record completed with status.	Operational
8005	Raw Log reconcile completed with status.	Operational
8006	Raw Log reconcile completed with status.	Operational
8007	Raw Log truncate completed with status.	Operational
8008	Raw Log truncate completed with status.	Operational
8009	Reading the last checkpoint completed with status.	Operational
8010	Reading the previous checkpoint completed with status.	Operational
8011	Writing a log record to raw log completed with status.	Operational
8012	Flushing control area failed with status.	Operational
8013	Unable to dispatch write packet at this time.	Operational
9000		Operational
9000	Failed to create metadata files for managing block copy operations.	Admin
9001		Operational
9001	Failed to update metadata files for managing block copy operations.	Admin
9002		Operational
9002	Detected corruption in the metadata files for managing block copy operations.	Admin
9003		Operational
9003	Unable to delete the metadata files used for managing block copy operations.	Admin
9004		Operational
9004	Resetting the recovery bitmap.	Admin
9005		Operational
9005	Failed to query disk provision map when initializing metadata files for managing …	Admin
9006		Operational
9006	The disk is thinly-provisioned.	Admin
9007		Operational
9007	The disk is not thinly-provisioned.	Admin
10001		Operational
10001	Filter driver failed to start.	Admin
10002		Operational
10002	Filter driver started successfully.	Admin
10003	Memory now available.	Operational
10004	There is not enough available memory.	Operational
10005		Operational
10005	The filter Resource Manager subsystem has started but the registry based …	Admin
10007		Operational
10007	The filter Resource Manager subsystem has started but their was a serious error …	Admin
10011		Operational
10011	Filter driver received partition surprise removal request.	Debug
10020		Operational
10020	AddDevice driver routine called.	Debug
10021		Operational
10021	AddDevice driver routine called.	Admin
10022		Operational
10022	AddDevice driver routine called but has determined that device is not a …	Debug
10031		Operational
10031	AddDevice call to IocreateDevice() failed to create a Storage Replica device for …	Debug
10041		Operational
10041	AddDevice call to IoAttachDeviceToDeviceStack() failed to attach to the …	Admin
10050		Operational
10050	Perform DevIoControl.	Debug
10060		Operational
10060	Perform DevIoControl.	Debug
10061		Operational
10061	Perform DevIoControl.	Debug
10070		Operational
10070	DispatchPnp for minor function started.	Debug
10080		Operational
10080	DispatchPnp for minor function completed.	Debug
10090		Operational
10090	StartDevice entered.	Debug
10100		Operational
10100	StartDevice completed.	Debug
10101		Operational
10101	StartDevice completed.	Admin
10110		Operational
10110	StartDevice failed to forward the IRP to the underlying device.	Debug
10111		Operational
10111	PnP device arrival failed to complete processing the device.	Admin
10120		Operational
10120	RemoveDevice entered.	Debug
10121	RemoveDevice completed.	Operational
10130		Operational
10130	SurpriseRemoveDevice entered.	Debug
10131	SurpriseRemoveDevice completed.	Operational
10132		Operational
10132	SurpriseRemoveDevice completed.	Admin
10160		Operational
10160	IOCTL_DISK_GET_DISK_ATTRIBUTES entry.	Debug
10170		Operational
10170	IOCTL_DISK_GET_DISK_ATTRIBUTES exit.	Debug
10171		Operational
10171	IOCTL_DISK_GET_DISK_ATTRIBUTES exit.	Admin
10180		Operational
10180	IOCTL_DISK_GET_DISK_ATTRIBUTES completed.	Debug
10181		Operational
10181	IOCTL_DISK_GET_DISK_ATTRIBUTES completed.	Admin
10190		Operational
10190	IOCTL_DISK_SET_DISK_ATTRIBUTES entry.	Debug
10200		Operational
10200	IOCTL_DISK_SET_DISK_ATTRIBUTES exit.	Debug
10201		Operational
10201	IOCTL_DISK_SET_DISK_ATTRIBUTES exit.	Admin
10202		Operational
10202	IOCTL_DISK_SET_DISK_ATTRIBUTES completion callback.	Debug
10203		Operational
10203	IOCTL_DISK_SET_DISK_ATTRIBUTES completion callback.	Admin
10210		Operational
10210	IOCTL_DISK_SET_DISK_ATTRIBUTES state change.	Debug
10220		Operational
10220	IrpAllocateForAsynchronousIoctlRequest completed.	Debug
10221		Operational
10221	IrpAllocateForAsynchronousIoctlRequest completed.	Debug
10240		Operational
10240	A duplicated partition was detected when processing a newly arrived disk.	Admin
10244		Operational
10244	IOCTL_DISK_SET_DRIVE_LAYOUT completion callback.	Admin
10250		Operational
10250	IOCTL_DISK_SET_DRIVE_LAYOUT entry.	Debug
10251		Operational
10251	IOCTL_DISK_SET_DRIVE_LAYOUT exit.	Debug
10252		Operational
10252	IOCTL_DISK_SET_DRIVE_LAYOUT exit.	Admin
10253		Operational
10253	IOCTL_DISK_SET_DRIVE_LAYOUT completion callback.	Debug
10254		Operational
10254	IOCTL_DISK_SET_DRIVE_LAYOUT completion callback.	Admin
10255	IOCTL_DISK_SET_DRIVE_LAYOUT was called for a disk involved in replication (which …	Operational
10260		Operational
10260	IOCTL_DISK_SET_DRIVE_LAYOUT_EX entry.	Debug
10261		Operational
10261	IOCTL_DISK_SET_DRIVE_LAYOUT_EX exit.	Debug
10262		Operational
10262	IOCTL_DISK_SET_DRIVE_LAYOUT_EX exit.	Admin
10263		Operational
10263	IOCTL_DISK_SET_DRIVE_LAYOUT completion callback.	Debug
10265		Operational
10265	IOCTL_DISK_SET_DRIVE_LAYOUT_EX was called for a disk involved in replication and …	Admin
10266		Operational
10266	IOCTL_DISK_SET_DRIVE_LAYOUT_EX was called for a disk involved in replication …	Debug
10267		Operational
10267	IOCTL_DISK_SET_DRIVE_LAYOUT_EX was called for a disk involved in replication …	Debug
10268		Operational
10268	IOCTL_DISK_SET_DRIVE_LAYOUT_EX was called for a disk involved in replication …	Admin
10269		Operational
10269	IOCTL_DISK_SET_DRIVE_LAYOUT_EX was called for a disk involved in replication …	Admin
10270		Operational
10270	IOCTL_DISK_SET_DRIVE_LAYOUT_EX was called for a disk involved in replication …	Admin
10271		Operational
10271	IOCTL_DISK_SET_DRIVE_LAYOUT_EX was called for a disk involved in replication …	Admin
10290		Operational
10290	IOCTL_DISK_GROW_PARTITION entry.	Debug
10291		Operational
10291	IOCTL_DISK_GROW_PARTITION exit.	Debug
10292		Operational
10292	IOCTL_DISK_GROW_PARTITION exit.	Admin
10293		Operational
10293	IOCTL_DISK_GROW_PARTITION partition validation completed.	Debug
10294		Operational
10294	IOCTL_DISK_GROW_PARTITION was called for a disk which may be involved in …	Admin
10295	Partition resize called on a partition in Storage Replica configuration.	Operational
10296	Partition resize called on a partition in Storage Replica configuration …	Operational
10297	Partition resize called on a partition in Storage Replica configuration …	Operational
10298		Operational
10298	Partition size mismatch with the corresponding data partition on source …	Admin
10299		Operational
10299	Partition size mismatch with the corresponding data partition on source …	Admin
10300		Operational
10300	Source data partition resize succeeded.	Admin
10301		Operational
10301	Source data partition resize failed.	Admin
10302		Operational
10302	Shrinking data partition under replication is not supported.	Admin
10303		Operational
10303	Partition size mismatch during configuration exchange.	Admin
10304		Operational
10304	Partition resize called on a source data partition in Storage Replica …	Admin
10305		Operational
10305	Attempt to shrink destination data partition.	Admin
10306		Operational
10306	Attempted to resize a partition that is protected by Storage Replica.	Admin
10307		Operational
10307	Attempted to resize a partition that is protected by Storage Replica.	System
10310		Operational
10310	A non-GPT partition was detected when processing a newly arrived disk formatted …	Admin
10311		Operational
10311	A GPT partition was detected when processing a newly arrived disk which is …	Debug
10312		Operational
10312	A GPT partition was detected when processing a newly arrived disk that is not …	Debug
10320		Operational
10320	Partition state current value.	Debug
10321	Partition state current value.	Operational
10330	A GPT partition was detected and prepared for replication operations.	Operational
10331		Operational
10331	A GPT partition was detected but preparation for replication operations failed.	Admin
10340		Operational
10340	IOCTL_DISK_DELETE_DRIVE_LAYOUT entry.	Debug
10341		Operational
10341	IOCTL_DISK_DELETE_DRIVE_LAYOUT exit.	Debug
10342		Operational
10342	IOCTL_DISK_DELETE_DRIVE_LAYOUT exit.	Admin
10343		Operational
10343	IOCTL_DISK_DELETE_DRIVE_LAYOUT was called for a disk involved in replication and …	Debug
10350		Operational
10350	IOCTL_DISK_CREATE_DISK entry.	Debug
10351		Operational
10351	IOCTL_DISK_CREATE_DISK exit.	Debug
10352		Operational
10352	IOCTL_DISK_CREATE_DISK exit.	Admin
10353		Operational
10353	IOCTL_DISK_CREATE_DISK was called for a disk involved in replication and one or …	Debug
10360		Operational
10360	IOCTL_WVR_PARTITION_DB_CREATE entry.	Debug
10361		Operational
10361	IOCTL_WVR_PARTITION_DB_CREATE exit.	Debug
10362		Operational
10362	IOCTL_WVR_PARTITION_DB_CREATE exit.	Admin
10370		Operational
10370	IOCTL_WVR_PARTITION_DB_DESTROY entry.	Debug
10371		Operational
10371	IOCTL_WVR_PARTITION_DB_DESTROY exit.	Debug
10372		Operational
10372	IOCTL_WVR_PARTITION_DB_DESTROY exit.	Admin
10373		Operational
10373	IOCTL_WVR_PARTITION_DB_DESTROY called with the NoSafetyInterlocks option …	Admin
10380		Operational
10380	Storage Replica filter driver discovered a serious error with an on-disk …	Admin
10381		Operational
10381	Storage Replica filter driver discovered a serious problem with the existing …	Admin
10382		Operational
10382	Storage Replica filter driver discovered an incompletely initialized Storage …	Debug
10383		Operational
10383	Filter driver discovered an improper disk layout where a GPT initialized disk …	Debug
10384	Filter driver was unable to bring a partition online.	Operational
10385	Filter driver was unable to take a partition offline.	Operational
10386	Filter driver was unable to remove a partition from replication.	Operational
10387		Operational
10387	Storage Replica filter driver discovered a serious error with a mismatch between …	Admin
10388		Operational
10388	Storage Replica filter driver could not find a Storage Replica partition …	Debug
10389	The replica partnership is synchronized but the attempt to update the on-disk …	Operational
10390	The replica partnership is no longer synchronized but the attempt to update the …	Operational
10400		Operational
10400	IOCTL_DISK_GET_CLUSTER_INFO entry.	Debug
10401		Operational
10401	IOCTL_DISK_GET_CLUSTER_INFO exit.	Debug
10402		Operational
10402	IOCTL_DISK_GET_CLUSTER_INFO exit.	Debug
10403		Operational
10403	IOCTL_DISK_GET_CLUSTER_INFO request completed.	Debug
10410		Operational
10410	IOCTL_DISK_SET_CLUSTER_INFO entry.	Debug
10411		Operational
10411	IOCTL_DISK_SET_CLUSTER_INFO exit.	Debug
10412		Operational
10412	IOCTL_DISK_SET_CLUSTER_INFO exit.	Debug
10413		Operational
10413	IOCTL_DISK_SET_CLUSTER_INFO request completed.	Debug
10420		Operational
10420	Filter driver configured the partition to be available for replication …	Debug
10421		Operational
10421	Filter driver attempted to configure the partition to be available for …	Admin
10422		Operational
10422	Filter driver was unable to locate the specified partition.	Admin
10430	Filter driver has configured the partition as no longer eligible for replication …	Operational
10431		Operational
10431	Filter driver attempted to configure the partition to be available for regular …	Admin
10432		Operational
10432	Filter driver was unable to locate the specified partition.	Admin
10440	A partition state change occured which caused the partition GPT attributes to be …	Operational
10441		Operational
10441	A partition state change occured where an attempt to update the partition GPT …	Admin
10442	A partition state change occured which caused the partition GPT attributes to be …	Operational
10443		Operational
10443	A partition state change occured where an attempt to update the partition GPT …	Admin
10444		Operational
10444	Locking the volume for partition surfacing has failed.	Debug
10445		Operational
10445	Locking the volume for partition submerging has failed.	Debug
10446	A partition state change occured which caused volume dismount on the replicated …	Operational
10447		Operational
10447	A partition state change occured where an attempt to dismount the volume on the …	Admin
10448	Storage Replica has failed an application IO.	Operational
11001		Operational
11001	Submitting an I/O context for flush failed.	Debug
11002		Operational
11002	Submitting an I/O context for flush succeeded.	Debug
11003		Operational
11003	Flush for an I/O context completed.	Debug
11004		Operational
11004	An I/O context overlaps with an in-flight I/O, it will be flushed when the …	Debug
11005		Operational
11005	Flush for an I/O context is resumed as the conflicting in-flight I/O has …	Debug
11006		Operational
11006	A flush dequeue thread is started, replica information: ReplicationGroupName: %2 …	Debug
11007		Operational
11007	A flush dequeue thread is stopped as the flush submit queue is empty, replica …	Debug
11020		Operational
11020	RegisterDevice driver routine called.	Debug
11021		Operational
11021	RegisterDevice failed to pre-allocate the disk update context required for …	Admin
11030		Operational
11030	RegisterDevice driver routine completed.	Debug
11040		Operational
11040	RegisterDevice driver routine identified target device.	Debug
11100		Operational
11100	Driver device operation request failure.	Admin
12000		Operational
12000	Filter driver failed to contact Storage Replica user mode service to update the …	Admin
12100		Operational
12100	Partition size mismatch with the corresponding data partition on source …	Admin
12200		Operational
12200	Storage Replica Windows Server Standard Edition requirement violated.	Admin

Event ID 1000 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 1000 — Transitioned to block copying from log record copying.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Transitioned to block copying from log record copying.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 1200 — Preparing destination for synchronization with source.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Preparing destination for synchronization with source.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 1201 — Source completed preparing for replication.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Source completed preparing for replication.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 1202 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—

Event ID 1202 — Started block copying for a partition.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Started block copying for a partition.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
PartitionId: %6

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—

Event ID 1203 — Destination started to compare records from the source log with local log.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Destination started to compare records from the source log with local log.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6
Compare start LSN: 

LogGeneration: %7
LogFileId: %8
CLSFLsn: %9

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`LogGeneration`	—
`LogFileId`	—
`CLFSLsn`	—

Event ID 1204 — Destination started to copy records from the source log.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Destination started to copy records from the source log.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6
Copy start LSN: 

LogGeneration: %7
LogFileId: %8
CLSFLsn: %9

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`LogGeneration`	—
`LogFileId`	—
`CLFSLsn`	—

Event ID 1205 — Destination started to copy data blocks from the source.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Destination started to copy data blocks from the source.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 1206 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 1206 — Recovery manager resumed for replica.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Recovery manager resumed for replica.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 1207 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1207 — Recovery manager suspended for replica.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Recovery manager suspended for replica.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6
Status: %7

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1208 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`LogGeneration`	—
`LogFileId`	—
`CLFSLsn`	—
`BytesRecovered`	—
`ElapsedTimeInSeconds`	—
`Status`	—

Event ID 1208 — Block copy completed.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Block copy completed.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
PartitionId: %6
ReplicaId: %7
Bytes Copied: %11
Elapsed Time (Seconds): %12
Status: %13

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`LogGeneration`	—
`LogFileId`	—
`CLFSLsn`	—
`BytesRecovered`	—
`ElapsedTimeInSeconds`	—
`Status`	—

Event ID 1209 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`LogGeneration`	—
`LogFileId`	—
`CLFSLsn`	—
`BytesRecovered`	—
`ElapsedTimeInSeconds`	—
`Status`	—

Event ID 1209 — Block copy completed.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Block copy completed.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
PartitionId: %6
ReplicaId: %7
Bytes Copied: %11
Elapsed Time (Seconds): %12
Status: %13

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`LogGeneration`	—
`LogFileId`	—
`CLFSLsn`	—
`BytesRecovered`	—
`ElapsedTimeInSeconds`	—
`Status`	—

Event ID 1210 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 1210 — Bitmap recovery finished, but not all bitmap files have the same end LSN.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Bitmap recovery finished, but not all bitmap files have the same end LSN. Bitmap recovery is restarting for all partitions of the replica.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 1211 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1211 — Bitmap recovery failed to save recovery bitmap back to primary.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Bitmap recovery failed to save recovery bitmap back to primary.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
PartitionId: %6
ReplicaId: %7
Status: %8

Guidance: The above information is for the destination replica. This is a recoverable error.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1212 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1212 — Destination received reply with failure from source for its read disk request.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Destination received reply with failure from source for its read disk request.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
PartitionId: %6
ReplicaId: %7
Status in reply: %8

Guidance: The above information is for the destination replica.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1213 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—

Event ID 1213 — Destination received STATUS_RETRY in read disk blocks reply.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Destination received STATUS_RETRY in read disk blocks reply.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
PartitionId: %6
ReplicaId: %7

Guidance: The above information is for the destination replica.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—

Event ID 1214 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 1214 — Bitmap recovery completed because there is no partition found for the replica.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Bitmap recovery completed because there is no partition found for the replica.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 1215 — Block copy completed for replica.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Block copy completed for replica.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %7
End LSN in bitmap: 
LogGeneration: %8
LogFileId: %9
CLSFLsn: %10
Number of Bytes Recovered: %11
Elapsed Time (seconds): %12

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`LogGeneration`	—
`LogFileId`	—
`CLFSLsn`	—
`BytesRecovered`	—
`ElapsedTimeInSeconds`	—
`Status`	—

Event ID 1216 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1216 — Bitmap recovery failed for replica.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Bitmap recovery failed for replica.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6
Status: %7

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1217 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 1217 — Recovery rollback completed successfully for replica.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Recovery rollback completed successfully for replica.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 1218 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1218 — Recovery rollback failed for replica.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Recovery rollback failed for replica.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6
Status: %7

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1219 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1219 — Recovery failed to start log reader for replica.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Recovery failed to start log reader for replica.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6
Status: %7

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1220 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 1220 — Recovery successfully started log reader for replica.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Recovery successfully started log reader for replica.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 1221 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 1221 — Recovery log reader has reached the end of the sources log.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Recovery log reader has reached the end of the sources log.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6

Guidance: The above information is for the destination replica.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 1222 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1222 — Recovery log reader terminated due to error in other recovery activity.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Recovery log reader terminated due to error in other recovery activity.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6
Status: %7

Guidance: The above information is for the destination replica.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1223 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1223 — Recovery log reader terminated due to error in reply from source.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Recovery log reader terminated due to error in reply from source.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6
Status: %7

Guidance: The above information is for the destination replica.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1224 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 1224 — Recovery log processor started for replica.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Recovery log processor started for replica.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 1225 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1225 — Recovery log processor terminated for replica.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Recovery log processor terminated for replica.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6
Exit status: %7

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1226 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1226 — Recovery log processor encountered error when processing log record.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Recovery log processor encountered error when processing log record.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6
Error status: %7

Guidance: The above information is for the destination replica.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1227 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—

Event ID 1227 — Source returned STATUS_RETRY to a read disk block request because the cluster disk was not online.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Source returned STATUS_RETRY to a read disk block request because the cluster disk was not online.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
PartitionId: %6
ReplicaId: %7

Guidance: The above information is for the source replica.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—

Event ID 1228 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`LogGeneration`	—
`LogFileId`	—
`CLFSLsn`	—

Event ID 1228 — Matching checkpoint log record found in source log.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Matching checkpoint log record found in source log.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6
Recovery start LSN: 

LogGeneration: %7
LogFileId: %8
CLSFLsn: %9

Guidance: The above information is for the destination replica.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`LogGeneration`	—
`LogFileId`	—
`CLFSLsn`	—

Event ID 1229 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 1229 — No matching checkpoint log record found in source log.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

No matching checkpoint log record found in source log. The destination will perform bitmap recovery.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6

Guidance: The above information is for the destination replica.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 1230 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1230 — Destination received failure reply from source when exchanging checkpoint information.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Destination received failure reply from source when exchanging checkpoint information.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6
Status: %7

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1231 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`LogGeneration`	—
`LogFileId`	—
`CLFSLsn`	—

Event ID 1231 — Recovery rollback started for replica.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Recovery rollback started for replica.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6
Rollback start LSN: 

LogGeneration: %7
LogFileId: %8
CLSFLsn: %9

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`LogGeneration`	—
`LogFileId`	—
`CLFSLsn`	—

Event ID 1232 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 1232 — Checkpoint log record not found in destination log.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Checkpoint log record not found in destination log. Destination will perform bitmap recovery for replica.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 1233 — Unable to prepare for replication.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Unable to prepare for replication.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6
Status: %7

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1234 — Destination unable to exchange checkpoint information with source.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Destination unable to exchange checkpoint information with source.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6
Status: %7

Guidance: The above information is for the destination replica.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1235 — Destination successfully completed checkpoint exchange with source.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Destination successfully completed checkpoint exchange with source.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6

Guidance: The above information is for the destination replica.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 1236 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1236 — Recovery on a destination received a reply from a source containing zero log records, and end of log flag was not set in the reply.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Recovery on a destination received a reply from a source containing zero log records, and end of log flag was not set in the reply. Destination will retry the request. Destination replica:

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6
Status: %7

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1237 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`PartitionId`	—
`RecoveredBytes`	—
`RemainingBytes`	—
`PrimaryLsn`	—
`SecondaryLsn`	—
`StateMachineState`	—
`ReplicationState`	—
`Status`	—

Event ID 1237 — Block copy is in progress.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Block copy is in progress.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaSetId: %6
PartitionId: %7
CopiedBytes: %8
RemainingBytes: %9
PrimaryLsn: %10
SecondaryLsn: %11
Status: %12

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`PartitionId`	—
`RecoveredBytes`	—
`RemainingBytes`	—
`PrimaryLsn`	—
`SecondaryLsn`	—
`StateMachineState`	—
`ReplicationState`	—
`Status`	—

Event ID 1238 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1238 — Unable to report progress.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Unable to report progress.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaSetId: %6
Status: %7

Guidance: Storage Replica is not able to create a timer which reports progress periodically for initial synchronization or recovery. The problem may be resolved in next recovery. This is not a fatal error.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 1239 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`SourceReplicationGroupNameLength`	—
`SourceReplicationGroupName`	—
`SourceReplicationGroupId`	—
`SourceReplicaNameLength`	—
`SourceReplicaName`	—
`SourcePartitionId`	—
`ReplicaSetId`	—
`TargetReplicationGroupNameLength`	—
`TargetReplicationGroupName`	—
`TargetReplicationGroupId`	—
`TargetRpo`	—
`CurrentRpo`	—

Event ID 1239 — The asynchronous destination can no longer meet the configured Recovery Point Objective (RPO).

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

The asynchronous destination can no longer meet the configured Recovery Point Objective (RPO).

LocalReplicationGroupName: %2
LocalReplicationGroupId: %3
LocalReplicaName: %5
LocalPartitionId: %6
ReplicaSetId: %7
RemoteReplicationGroupName: %9
RemoteReplicationGroupId: %10
TargetRPO: %11
CurrentRPO: %12

Guidance: The RPO determines the maximum difference in seconds between the source and destination volumes replicated data blocks. When exceeding this time, this event is raised to alert administrators. When the difference is reduced to under the RPO, event 1240 is written.

Fields

Name	Description
`SourceReplicationGroupNameLength`	—
`SourceReplicationGroupName`	—
`SourceReplicationGroupId`	—
`SourceReplicaNameLength`	—
`SourceReplicaName`	—
`SourcePartitionId`	—
`ReplicaSetId`	—
`TargetReplicationGroupNameLength`	—
`TargetReplicationGroupName`	—
`TargetReplicationGroupId`	—
`TargetRpo`	—
`CurrentRpo`	—

Event ID 1240 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`SourceReplicationGroupNameLength`	—
`SourceReplicationGroupName`	—
`SourceReplicationGroupId`	—
`SourceReplicaNameLength`	—
`SourceReplicaName`	—
`SourcePartitionId`	—
`ReplicaSetId`	—
`TargetReplicationGroupNameLength`	—
`TargetReplicationGroupName`	—
`TargetReplicationGroupId`	—
`TargetRpo`	—
`CurrentRpo`	—

Event ID 1240 — The asynchronous destination now meets the configured Recovery Point Objective (RPO).

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

The asynchronous destination now meets the configured Recovery Point Objective (RPO).

LocalReplicationGroupName: %2
LocalReplicationGroupId: %3
LocalReplicaName: %5
LocalPartitionId: %6
ReplicaSetId: %7
RemoteReplicationGroupName: %9
RemoteReplicationGroupId: %10
TargetRPO: %11
CurrentRPO: %12

Fields

Name	Description
`SourceReplicationGroupNameLength`	—
`SourceReplicationGroupName`	—
`SourceReplicationGroupId`	—
`SourceReplicaNameLength`	—
`SourceReplicaName`	—
`SourcePartitionId`	—
`ReplicaSetId`	—
`TargetReplicationGroupNameLength`	—
`TargetReplicationGroupName`	—
`TargetReplicationGroupId`	—
`TargetRpo`	—
`CurrentRpo`	—

Event ID 1241 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`SourceReplicationGroupNameLength`	—
`SourceReplicationGroupName`	—
`SourceReplicationGroupId`	—
`SourceReplicaNameLength`	—
`SourceReplicaName`	—
`SourcePartitionId`	—
`ReplicaSetId`	—
`TargetReplicationGroupNameLength`	—
`TargetReplicationGroupName`	—
`TargetReplicationGroupId`	—
`TargetRpo`	—
`CurrentRpo`	—

Event ID 1241 — The Recovery Point Objective (RPO) of the asynchronous destination is unavailable.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

The Recovery Point Objective (RPO) of the asynchronous destination is unavailable.

LocalReplicationGroupName: %2
LocalReplicationGroupId: %3
LocalReplicaName: %5
LocalPartitionId: %6
ReplicaSetId: %7
RemoteReplicationGroupName: %9
RemoteReplicationGroupId: %10
TargetRPO: %11

Guidance: This is typically due to one of the following reasons: 
The asynchronous destination is currently disconnected. The RPO may become available after the connection is restored.

The asynchronous destination is unable to keep pace with the source such that the most recent destination log record is no longer present in the source log. The destination will start block copying. The RPO should become available after block copying completes.

Fields

Name	Description
`SourceReplicationGroupNameLength`	—
`SourceReplicationGroupName`	—
`SourceReplicationGroupId`	—
`SourceReplicaNameLength`	—
`SourceReplicaName`	—
`SourcePartitionId`	—
`ReplicaSetId`	—
`TargetReplicationGroupNameLength`	—
`TargetReplicationGroupName`	—
`TargetReplicationGroupId`	—
`TargetRpo`	—
`CurrentRpo`	—

Event ID 1242 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`LogGeneration`	—
`LogFileId`	—
`CLFSLsn`	—
`BytesRecovered`	—
`ElapsedTimeInSeconds`	—
`Status`	—

Event ID 1242 — Initial sync block copy completed.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Initial sync block copy completed.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
PartitionId: %6
ReplicaId: %7
Bytes Copied: %11
Elapsed Time (Seconds): %12
Status: %13

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`LogGeneration`	—
`LogFileId`	—
`CLFSLsn`	—
`BytesRecovered`	—
`ElapsedTimeInSeconds`	—
`Status`	—

Event ID 1243 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`LogGeneration`	—
`LogFileId`	—
`CLFSLsn`	—
`BytesRecovered`	—
`ElapsedTimeInSeconds`	—
`Status`	—

Event ID 1243 — Initial sync block copy completed.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Initial sync block copy completed.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
PartitionId: %6
ReplicaId: %7
Bytes Copied: %11
Elapsed Time (Seconds): %12
Status: %13

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`LogGeneration`	—
`LogFileId`	—
`CLFSLsn`	—
`BytesRecovered`	—
`ElapsedTimeInSeconds`	—
`Status`	—

Event ID 1244 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`SourceReplicationGroupNameLength`	—
`SourceReplicationGroupName`	—
`SourceReplicationGroupId`	—
`TargetReplicationGroupNameLength`	—
`TargetReplicationGroupName`	—
`TargetReplicationGroupId`	—
`Status`	—

Event ID 1244 — Storage Replica filter driver failed to update the sync state of the asynchronous destination.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Storage Replica filter driver failed to update the sync state of the asynchronous destination.

LocalReplicationGroupName: %2
LocalReplicationGroupId: %3
RemoteReplicationGroupName: %5
RemoteReplicationGroupId: %6
Status: %7

Fields

Name	Description
`SourceReplicationGroupNameLength`	—
`SourceReplicationGroupName`	—
`SourceReplicationGroupId`	—
`TargetReplicationGroupNameLength`	—
`TargetReplicationGroupName`	—
`TargetReplicationGroupId`	—
`Status`	—

Event ID 2000 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 2000 — Unable to flush logged application write to data volume.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Unable to flush logged application write to data volume.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
PartitionId: %6
Status: %8

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 2200 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`PartitionId`	—
`Status`	—
`LogTimeInMs`	—
`StateMachineTimeInMs`	—
`StartTimeInMs`	—

Event ID 2200 — Start replication for replica.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Start replication for replica.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaSetId: %6
PartitionId: %7
Status: %8
LogTimeInMs: %9
StateMachineTimeInMs: %10
StartTimeInMs: %11

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`PartitionId`	—
`Status`	—
`LogTimeInMs`	—
`StateMachineTimeInMs`	—
`StartTimeInMs`	—

Event ID 2201 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`PartitionId`	—
`Status`	—
`LogTimeInMs`	—
`StateMachineTimeInMs`	—
`StartTimeInMs`	—

Event ID 2201 — Start replication for replica.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Start replication for replica.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaSetId: %6
PartitionId: %7
Status: %8
LogTimeInMs: %9
StateMachineTimeInMs: %10
StartTimeInMs: %11

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`PartitionId`	—
`Status`	—
`LogTimeInMs`	—
`StateMachineTimeInMs`	—
`StartTimeInMs`	—

Event ID 2202 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 2202 — Stop replication for replica.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Stop replication for replica.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
PartitionId: %6
ReplicaSetId: %7
Status: %8

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 2203 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 2203 — Stop replication for replica.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Stop replication for replica.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
PartitionId: %6
ReplicaSetId: %7
Status: %8

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 2204 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`PartitionDBReplicationGroupId`	—
`Status`	—

Event ID 2204 — Partition belongs to a different replication group.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Partition belongs to a different replication group. 

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
PartitionId: %6
ReplicaSetId: %7
ConflictingReplicationGroupId: %8
Status: %9

Guidance: Storage Replica received a request to start or stop replication on this partition. However, the requested replication group is different from the replication group to which this partition belongs. If this error is unexpected, restart Storage Replica service and retry.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`PartitionDBReplicationGroupId`	—
`Status`	—

Event ID 2205 — Detected invalid replication mode in the configuration exchange request, the connection will be rejected.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Detected invalid replication mode in the configuration exchange request, the connection will be rejected.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicationMode: %6

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicationMode`	—

Event ID 2206 — Configuration exchange request contains invalid partner, the connection will be rejected.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Configuration exchange request contains invalid partner, the connection will be rejected. Request contains partner that could not be found in the local group's partner list.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
DestinationReplicationGroupId: %6
Status:%7

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`DestinationReplicationGroupId`	—
`Status`	—

Event ID 2207 — Detected mismatching log disk logical sector size in the configuration exchange request, the connection will be rejected.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Detected mismatching log disk logical sector size in the configuration exchange request, the connection will be rejected.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
LogPath: %7
DestinationReplicationGroupId: %8
SourceLogDiskSectorSize: %9
SecondaryLogDiskSectorSize: %10

Guidance: Ensure that the logs for the replication groups are configured to reside on the disk with matching physical sector sizes.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`LogPathLength`	—
`LogPath`	—
`DestinationReplicationGroupId`	—
`SourceLogDiskSectorSize`	—
`DestinationLogDiskSectorSize`	—

Event ID 2208 — Detected mismatching log size (in bytes) in the configuration exchange request, the connection will be rejected.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Detected mismatching log size (in bytes) in the configuration exchange request, the connection will be rejected.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
LogPath: %7
DestinationReplicationGroupId: %8
SourceLogSize: %9
DestinationLogSize: %10

Guidance: Ensure that the logs for the replication groups are configured to have matching sizes.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`LogPathLength`	—
`LogPath`	—
`DestinationReplicationGroupId`	—
`SourceLogSize`	—
`DestinationLogSize`	—

Event ID 2209 — Detected mismatching replica set count in the configuration exchange request, the connection will be rejected.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Detected mismatching replica set count in the configuration exchange request, the connection will be rejected.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
DestinationReplicationGroupId: %6
SourceReplicaSetSize: %7
DestinationReplicaSetSize: %8

Guidance: Ensure that the replication groups in partnership contain matching number of volumes to be replicated.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`DestinationReplicationGroupId`	—
`SourceReplicaSetSize`	—
`DestinationReplicaSetSize`	—

Event ID 2210 — Detected mismatching data partition size (in bytes) in the configuration exchange request, the connection will be rejected.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Detected mismatching data partition size (in bytes) in the configuration exchange request, the connection will be rejected.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
DestinationReplicationGroupId: %6
ReplicaSetId: %7
SourceDataPartitionSize: %8
DestinationDataPartitionSize: %9
PartitionId: %10

Guidance: If you have just initiated a resize on the source data partition, this message is expected once per data partition resize.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`DestinationReplicationGroupId`	—
`ReplicaSetId`	—
`SourceDataPartitionSize`	—
`DestinationDataPartitionSize`	—
`PartitionId`	—

Event ID 2211 — Detected mismatching data disk physical sector size in the configuration exchange request, the connection will be rejected.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Detected mismatching data disk physical sector size in the configuration exchange request, the connection will be rejected.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
DestinationReplicationGroupId: %6
ReplicaSetId: %7
SourceDataDiskSectorSize: %8
DestinationDataDiskSectorSize: %9
PartitionId: %10

Guidance: Ensure that the data volumes in the replication groups are residing on the disks with matching physical sector sizes.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`DestinationReplicationGroupId`	—
`ReplicaSetId`	—
`SourceDataDiskSectorSize`	—
`DestinationDataDiskSectorSize`	—
`PartitionId`	—

Event ID 2212 — Failed to lookup partition during configuration exchange, the connection will be rejected.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Failed to lookup partition during configuration exchange, the connection will be rejected.The requested replica set could not be found in the group's configuration.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
DestinationReplicationGroupId: %6
ReplicaSetId: %7
Status: %8

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`DestinationReplicationGroupId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 2213 — Detected duplicate replica set entries in the configuration exchange response, the connection will not be established.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Detected duplicate replica set entries in the configuration exchange response, the connection will not be established.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaSetId: %6

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 2214 — Detected mismatching data partition size (in bytes) in the configuration exchange response, the connection will not be established.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Detected mismatching data partition size (in bytes) in the configuration exchange response, the connection will not be established.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaSetId: %6
SourceDataPartitionSize: %7
DestinationDataPartitionSize: %6

Guidance: If you have just initiated a resize on the source data partition, this message is expected once per data partition resize.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`SourceDataPartitionSize`	—
`DestinationDataPartitionSize`	—
`PartitionId`	—

Event ID 2215 — Detected mismatching log disk logical sector size in the configuration exchange response, the connection will not be established.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Detected mismatching log disk logical sector size in the configuration exchange response, the connection will not be established.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
LogPath: %7
SourceLogDiskSectorSize: %8
DestinationLogDiskSectorSize: %9

Guidance: Ensure that the logs for the replication groups are configured to reside on the disk with matching logical sector sizes.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`LogPathLength`	—
`LogPath`	—
`SourceLogDiskSectorSize`	—
`DestinationLogDiskSectorSize`	—

Event ID 2216 — Detected mismatching log size (in bytes) in the configuration exchange response, the connection will not be established.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Detected mismatching log size (in bytes) in the configuration exchange response, the connection will not be established.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
LogPath: %7
SourceLogSize: %8
DestinationLogSize: %9

Guidance: Ensure that the logs for the replication groups are configured to have matching sizes.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`LogPathLength`	—
`LogPath`	—
`SourceLogSize`	—
`DestinationLogSize`	—

Event ID 2217 — Detected mismatching replica set count in the configuration exchange response.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Detected mismatching replica set count in the configuration exchange response. Will attempt to resize the secondary data partition.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
SourceReplicaSetSize: %6
DestinationReplicaSetSize: %7

Guidance: If you have just initiated a resize on the source data partition, this message is expected.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`SourceReplicaSetSize`	—
`DestinationReplicaSetSize`	—

Event ID 2218 — Detected mismatching data disk physical sector size in the configuration exchange response, the connection will not be established.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Detected mismatching data disk physical sector size in the configuration exchange response, the connection will not be established.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaSetId: %6
SourceDataDiskSectorSize: %7
DestinationDataDiskSectorSize: %8
PartitionId: %9

Guidance: Ensure that the data volumes in the replication groups are residing on the disks with matching physical sector sizes.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`SourceDataDiskSectorSize`	—
`DestinationDataDiskSectorSize`	—
`PartitionId`	—

Event ID 2219 — Detected duplicate replica set entries in the configuration exchange request, the connection will be rejected.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Detected duplicate replica set entries in the configuration exchange request, the connection will be rejected.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
DestinationReplicationGroupId: %6
ReplicaSetId: %7

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`DestinationReplicationGroupId`	—
`ReplicaSetId`	—

Event ID 2220 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 2220 — Replica is attempting to join consistency group.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Replica is attempting to join consistency group.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaSetId: %6

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 2221 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 2221 — Write ordering is not possible at this time for this replica.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Write ordering is not possible at this time for this replica.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaSetId: %6

Guidance: The operation will be retried when all partners achieves synchronous replication state.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 2222 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 2222 — Replica successfully joined consistency group.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Replica successfully joined consistency group.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaSetId: %6

Guidance: Write ordering will be guaranteed across all volumes in this consistency group from this point forward

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 2223 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 2223 — Attempting to join replica to consistency group failed.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Attempting to join replica to consistency group failed.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaSetId: %6
Status: %7

Guidance: This event occurs when one or more data partitions or log partitions are not accessible or when system is low on memory. To resolve the condition, make sure all data partitions and log partitions are accessible and then try to bring replication group online.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 2224 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 2224 — Successfully removed the replica from the consistency group.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Successfully removed the replica from the consistency group.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaSetId: %6

Guidance: This operation was performed because the disk was taken offline. Replication will continue on other partitions in a replication group. When this partition comes online it will not maintain write ordering until it joins the consistency group.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 2225 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 2225 — Replica is successfully removed from the consistency group.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Replica is successfully removed from the consistency group.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaSetId: %6

Guidance: This operation was performed because the disk was taken offline. Replication will continue on other partitions in a replication group. When this partition comes online it will not maintain write ordering until it joins the consistency group.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 2226 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 2226 — Failed to remove replica from the consistency group.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Failed to remove replica from the consistency group.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaSetId: %6
Status: %7

Guidance: Possible causes include inaccessible data disk or low system memory. Other partitions in a replication group will not be accessible.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 2227 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DirectoryPathLength`	—
`DirectoryPath`	—

Event ID 2227 — Successfully removed orphan log container.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Successfully removed orphan log container.

Path: %2

Fields

Name	Description
`DirectoryPathLength`	—
`DirectoryPath`	—

Event ID 2228 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DirectoryPathLength`	—
`DirectoryPath`	—
`Status`	—

Event ID 2228 — Failed to remove orphan log container.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Failed to remove orphan log container.

Path: %2
Status: %3

Fields

Name	Description
`DirectoryPathLength`	—
`DirectoryPath`	—
`Status`	—

Event ID 2229 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`FilePathLength`	—
`FilePath`	—

Event ID 2229 — Successfully removed orphan log file for replication group.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Successfully removed orphan log file for replication group.

ReplicationGroupName: %2
ReplicationGroupId: %3
File: %5

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`FilePathLength`	—
`FilePath`	—

Event ID 2230 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`FilePathLength`	—
`FilePath`	—
`Status`	—

Event ID 2230 — Failed to remove orphan log file for replication group.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Failed to remove orphan log file for replication group.

ReplicationGroupName: %2
ReplicationGroupId: %3
File: %5
Status: %6%

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`FilePathLength`	—
`FilePath`	—
`Status`	—

Event ID 2231 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`Status`	—

Event ID 2231 — Replication group is online.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Replication group is online.

ReplicationGroupName: %2
ReplicationGroupId: %3

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`Status`	—

Event ID 2232 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 2232 — Failed to flush replication log for a partition.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Failed to flush replication log for a partition.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
PartitionId: %6
ReplicaSetId: %7
Status: %8n
Guidance: When removing a destination partition from replication, Storage Replica will attempt to flush replication log for the partition. There may be data loss when this operation fails. Verify that the storage is operating correctly

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 3000 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`LogPathLength`	—
`LogPath`	—
`Status`	—

Event ID 3000 — Unable to create a log on the log volume.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Unable to create a log on the log volume.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
LogPath: %7
Status: %8

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`LogPathLength`	—
`LogPath`	—
`Status`	—

Event ID 3001 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`LogPathLength`	—
`LogPath`	—
`Status`	—

Event ID 3001 — Log truncation failed.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Log truncation failed.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
LogPath: %7
Status: %8

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`LogPathLength`	—
`LogPath`	—
`Status`	—

Event ID 3002 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`LogPathLength`	—
`LogPath`	—
`Status`	—

Event ID 3002 — Log is corrupt.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Log is corrupt.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
LogPath: %7
Status: %8

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`LogPathLength`	—
`LogPath`	—
`Status`	—

Event ID 3003 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`LogPathLength`	—
`LogPath`	—
`Status`	—

Event ID 3003 — Log metadata is corrupt.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Log metadata is corrupt.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
LogPath: %7
Status: %8

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`LogPathLength`	—
`LogPath`	—
`Status`	—

Event ID 3004 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`LogFileNameLength`	—
`LogFileName`	—
`ClfsLsn`	—
`Status`	—

Event ID 3004 — Unable to read record from the log.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Unable to read record from the log.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
LogFile: %7
Record LSN: %8
Status: %9

Guidance: Possible causes include inaccessible log volume or log corruption. Storage Replica will not replicate corresponding data volumes until the issue is resolved. Make sure the log volume is accessible and there is nothing preventing access to the log files such as filesystem filter drivers. Once the condition is resolved try to bring the Replication Group online.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`LogFileNameLength`	—
`LogFileName`	—
`ClfsLsn`	—
`Status`	—

Event ID 3005 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`LogFileNameNameLength`	—
`LogFileName`	—
`LogRecordSize`	—
`Status`	—

Event ID 3005 — Unable to write a record to the log.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Unable to write a record to the log.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
LogFile: %7
Log Record Size: %8
Status: %9

Guidance: Possible causes include inaccessible log volume or log corruption. Storage Replica will not replicate corresponding data volumes until the issue is resolved. Make sure the log volume is accessible and there is nothing preventing access to the log files such as filesystem filter drivers. Once the condition is resolved try to bring the Replication Group online.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`LogFileNameNameLength`	—
`LogFileName`	—
`LogRecordSize`	—
`Status`	—

Event ID 3006 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`LogFileNameLength`	—
`LogFileName`	—
`Status`	—

Event ID 3006 — Unable to close the log file.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Unable to close the log file.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
LogFile: %7
Status: %8

Guidance: Possible causes include inaccessible log volume or log corruption. Storage Replica will not replicate corresponding data volumes until the issue is resolved. Make sure the log volume is accessible and there is nothing preventing access to the log files such as filesystem filter drivers. Once the condition is resolved try to bring the Replication Group online.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`LogFileNameLength`	—
`LogFileName`	—
`Status`	—

Event ID 3007 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`LogFileNameLength`	—
`LogFileName`	—
`Status`	—

Event ID 3007 — Unable to delete log file.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Unable to delete log file.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
LogFile: %7
Status: %8

Guidance: Possible causes include inaccessible log volume or log corruption. Storage Replica will not replicate corresponding data volumes until the issue is resolved. Make sure the log volume is accessible and there is nothing preventing access to the log files such as filesystem filter drivers. Once the condition is resolved try to bring the Replication Group online.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`LogFileNameLength`	—
`LogFileName`	—
`Status`	—

Event ID 3008 — Unable to close log read context.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Unable to close log read context.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
LogPath: %7
Status: %8

Guidance: Possible causes include inaccessible log volume or log corruption. Storage Replica will not replicate corresponding data volumes until the issue is resolved. Make sure the log volume is accessible and there is nothing preventing access to the log files such as filesystem filter drivers. Once the condition is resolved try to bring the Replication Group online.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`LogFileNameLength`	—
`LogFileName`	—
`Status`	—

Event ID 3009 — Unable to create marshalling area for log file.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Unable to create marshalling area for log file.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
LogFile: %7
Status: %8

Guidance: Possible causes include inaccessible log volume or log corruption. Storage Replica will not replicate corresponding data volumes until the issue is resolved. Make sure the log volume is accessible and there is nothing preventing access to the log files such as filesystem filter drivers. Once the condition is resolved try to bring the Replication Group online.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`LogFileNameLength`	—
`LogFileName`	—
`Status`	—

Event ID 3010 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`LogFileNameLength`	—
`LogFileName`	—
`Status`	—

Event ID 3010 — Unable to create the log file.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Unable to create the log file. 

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
LogFile: %7
Status: %8

Guidance: Possible causes include inaccessible log volume or insufficient space on log volume. Storage Replica will not replicate corresponding data volumes until the issue is resolved. Make sure the log volume is accessible and there is enough space for the specified log size. Once the condition is resolved try to bring the Replication Group online.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`LogFileNameLength`	—
`LogFileName`	—
`Status`	—

Event ID 3011 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`LogFileNameLength`	—
`LogFileName`	—
`Status`	—

Event ID 3011 — Unable to read the log file metadata.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Unable to read the log file metadata. 

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
LogFile: %7
Status: %8

Guidance: Possible causes include inaccessible log volume or log corruption. Storage Replica will not replicate corresponding data volumes until the issue is resolved. Make sure the log volume is accessible and there is nothing preventing access to the log files such as filesystem filter drivers. Once the condition is resolved try to bring the Replication Group online.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`LogFileNameLength`	—
`LogFileName`	—
`Status`	—

Event ID 3012 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 3012 — Failed to initialize the replication log path.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Failed to initialize the replication log path. 

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6
Status: %7
Guidance: Possible causes include inaccessible log volume or low system resources. Storage Replica will not replicate corresponding data volumes until the issue is resolved. Make sure the log volume is accessible and there is nothing preventing access to the log files such as filesystem filter drivers.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 4000 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ShareNameLength`	—
`ShareName`	—
`Status`	—
`SrpStatus`	—

Event ID 4000 — Failed to create network share for replication group.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Failed to create network share for replication group.

ReplicationGroupName: %2
ReplicationGroupId: %3
ShareName: %7
Status: %8
SrpStatus: %9

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ShareNameLength`	—
`ShareName`	—
`Status`	—
`SrpStatus`	—

Event ID 4001 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ShareNameLength`	—
`ShareName`	—
`Status`	—
`SrpStatus`	—

Event ID 4001 — Failed to delete network share for replication group.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Failed to delete network share for replication group.

ReplicationGroupName: %2
ReplicationGroupId: %3
ShareName: %7
Status: %8
SrpStatus: %9

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ShareNameLength`	—
`ShareName`	—
`Status`	—
`SrpStatus`	—

Event ID 4002 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ShareNameLength`	—
`ShareName`	—
`Status`	—
`SrpStatus`	—

Event ID 4002 — Failed to modify network share for replication group.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Failed to modify network share for replication group.

ReplicationGroupName: %2
ReplicationGroupId: %3
ShareName: %7
Status: %8
SrpStatus: %9

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ShareNameLength`	—
`ShareName`	—
`Status`	—
`SrpStatus`	—

Event ID 4003 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`SourceReplicationGroupNameLength`	—
`SourceReplicationGroupName`	—
`SourceReplicationGroupId`	—
`SourceReplicaNameLength`	—
`SourceReplicaName`	—
`ReplicaSetId`	—
`TargetReplicationGroupNameLength`	—
`TargetReplicationGroupName`	—
`TargetReplicationGroupId`	—
`Status`	—

Event ID 4003 — Connection request rejected from a partner.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Connection request rejected from a partner.

LocalReplicationGroupName: %2
LocalReplicationGroupId: %3
LocalReplicaName: %5
LocalReplicaSetId: %6
RemoteReplicationGroupName: %8
RemoteReplicationGroupId: %9
Status: %10

Fields

Name	Description
`SourceReplicationGroupNameLength`	—
`SourceReplicationGroupName`	—
`SourceReplicationGroupId`	—
`SourceReplicaNameLength`	—
`SourceReplicaName`	—
`ReplicaSetId`	—
`TargetReplicationGroupNameLength`	—
`TargetReplicationGroupName`	—
`TargetReplicationGroupId`	—
`Status`	—

Event ID 4004 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ComputerNameLength`	—
`ComputerName`	—
`SourceReplicationGroupNameLength`	—
`SourceReplicationGroupName`	—
`SourceReplicationGroupId`	—
`TargetReplicationGroupNameLength`	—
`TargetReplicationGroupName`	—
`TargetReplicationGroupId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 4004 — Failed to establish a connection to a remote computer.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Failed to establish a connection to a remote computer.

RemoteComputerName: %2
LocalReplicationGroupName: %4
LocalReplicationGroupId: %5
RemoteReplicationGroupName: %7
RemoteReplicationGroupId: %8
ReplicaSetId: %9
RemoteShareName:%8.%9
Status: %10

Guidance: Possible causes include network failures, share creation failures for the remote replication group, or firewall settings. Make sure SMB traffic is allowed and there are no connectivity issues between the local computer and the remote computer. You should expect this event when suspending replication or removing a replication partnership.

Fields

Name	Description
`ComputerNameLength`	—
`ComputerName`	—
`SourceReplicationGroupNameLength`	—
`SourceReplicationGroupName`	—
`SourceReplicationGroupId`	—
`TargetReplicationGroupNameLength`	—
`TargetReplicationGroupName`	—
`TargetReplicationGroupId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 4005 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 4005 — Storage Replica detected a configuration mismatch in a replication group.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Storage Replica detected a configuration mismatch in a replication group. Storage Replica will keep retrying till the issue is resolved.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaSetId: %4
Status: %5

Guidance: Possible causes include temperoray issues in a recent addition or removal of a volume to a write-ordered replication group that should fix by itself.
If you see an event that states that the group entering joining state, it means it has recovered by itself.
If the issue persists, please check the configuration of the replication group. You might have to remove and rebuild replication in worst case.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 5001 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 5001 — Entered preparation state.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Entered preparation state.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 5002 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 5002 — Source entered ready state.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Source entered ready state.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 5003 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 5003 — Source moved to failure state.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Source moved to failure state.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6
Status: %7

Guidance: After resolving the failure, you may need to run Sync-SRGroup to resume replication.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 5004 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 5004 — Source entered wait-for-quorum state.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Source entered wait-for-quorum state.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 5005 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 5005 — Destination entered stand-by state.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Destination entered stand-by state.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 5006 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 5006 — Destination entered joining state.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Destination entered joining state.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 5007 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 5007 — Destination entered asynchronous replication state.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Destination entered asynchronous replication state.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 5008 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 5008 — Destination moved to failure state.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Destination moved to failure state.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6
Status: %7

Guidance: After resolving the failure, you may need to run Sync-SRGroup to resume replication.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`Status`	—

Event ID 5009 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 5009 — Destination attempted to enter synchronous replication state.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Destination attempted to enter synchronous replication state.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 5010 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 5010 — Asynchronous destination entered wait state.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Asynchronous destination entered wait state.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 5011 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`Status`	—

Event ID 5011 — Attempted to take Replication Group offline.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Attempted to take Replication Group offline.

ReplicationGroup: %2
ReplicationGroupId: %3
Status: %4

Guidance: Replication is not performed when the Replication Group is offline. Administrators should not intentionally take replication groups offline.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`Status`	—

Event ID 5012 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`Status`	—

Event ID 5012 — Destination entered offline state.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Destination entered offline state.

ReplicationGroup: %2
ReplicationGroupId: %3
Status: %4

Guidance: Replication is not performed when the Replication Group is offline.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`Status`	—

Event ID 5013 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`Status`	—

Event ID 5013 — Source replication group lost quorum.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Source replication group lost quorum.

ReplicationGroup: %2
ReplicationGroupId: %3
Status: %4

Guidance: This message occurs when a source no longer has enough synchronous destination replicas available and has lost the necessary quorum. Replication is paused until enough destination replicas rejoin the source to achieve the configured quorum value. You can control this through the MinimumPartnersInSync parameter in the Storage Replica Windows PowerShell module.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`Status`	—

Event ID 5014 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`SourceReplicationGroupNameLength`	—
`SourceReplicationGroupName`	—
`SourceReplicationGroupId`	—
`SourceReplicaNameLength`	—
`SourceReplicaName`	—
`SourcePartitionId`	—
`ReplicaSetId`	—
`TargetReplicationGroupNameLength`	—
`TargetReplicationGroupName`	—
`TargetReplicationGroupId`	—

Event ID 5014 — Connection lost to the share hosting the partner replica.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Connection lost to the share hosting the partner replica.

LocalReplicationGroupName: %2
LocalReplicationGroupId: %3
LocalReplicaName: %5
LocalPartitionId: %6
ReplicaSetId: %7
RemoteReplicationGroupName: %9
RemoteReplicationGroupId: %10

Guidance: You should expect this event when changing replication direction between computers, when suspending a replication group, or when removing a replication partnership, or just after you resized a source data partition (once per resized data partition).

Fields

Name	Description
`SourceReplicationGroupNameLength`	—
`SourceReplicationGroupName`	—
`SourceReplicationGroupId`	—
`SourceReplicaNameLength`	—
`SourceReplicaName`	—
`SourcePartitionId`	—
`ReplicaSetId`	—
`TargetReplicationGroupNameLength`	—
`TargetReplicationGroupName`	—
`TargetReplicationGroupId`	—

Event ID 5015 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`SourceReplicationGroupNameLength`	—
`SourceReplicationGroupName`	—
`SourceReplicationGroupId`	—
`SourceReplicaNameLength`	—
`SourceReplicaName`	—
`SourcePartitionId`	—
`ReplicaSetId`	—
`TargetReplicationGroupNameLength`	—
`TargetReplicationGroupName`	—
`TargetReplicationGroupId`	—

Event ID 5015 — Successfully established a connection to a partner replica.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Successfully established a connection to a partner replica.

LocalReplicationGroupName: %2
LocalReplicationGroupId: %3
LocalReplicaName: %5
LocalPartitionId: %6
ReplicaSetId: %7
RemoteReplicationGroupName: %9
RemoteReplicationGroupId: %10

Fields

Name	Description
`SourceReplicationGroupNameLength`	—
`SourceReplicationGroupName`	—
`SourceReplicationGroupId`	—
`SourceReplicaNameLength`	—
`SourceReplicaName`	—
`SourcePartitionId`	—
`ReplicaSetId`	—
`TargetReplicationGroupNameLength`	—
`TargetReplicationGroupName`	—
`TargetReplicationGroupId`	—

Event ID 5016 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 5016 — Replica is offline.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Replica is offline.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 5018 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`OldState`	—
`NewState`	—
`Event`	—

Event ID 5018 — State machine processing an event for replica.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

State machine processing an event for replica.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaSetId: %6
Old State: %7
New State: %8
EventId: %9

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`OldState`	—
`NewState`	—
`Event`	—

Event ID 5019 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`PartitionId`	—
`OldState`	—
`NewState`	—
`ReplicationState`	—

Event ID 5019 — State machine state has changed.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

State machine state has changed.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaSetId: %6
PartitionId: %7
Old State: %8
New State: %9

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`PartitionId`	—
`OldState`	—
`NewState`	—
`ReplicationState`	—

Event ID 5020 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 5020 — Destination entered synchronous replication state.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Destination entered synchronous replication state.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaId: %6

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—

Event ID 5021 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`PartitionId`	—
`StateMachineState`	—
`OldReplicationState`	—
`NewReplicationState`	—

Event ID 5021 — Replication state has changed.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Replication state has changed.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaSetId: %6
PartitionId: %7
Old Replication State: %9
New Replication State: %10

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`PartitionId`	—
`StateMachineState`	—
`OldReplicationState`	—
`NewReplicationState`	—

Event ID 6001 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`IRPAddress`	—
`Offset`	—
`Length`	—

Event ID 6001 — Write IRP received

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

Write IRP received

Fields

Name	Description
`IRPAddress`	—
`Offset`	—
`Length`	—

Event ID 6002 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`TransactionId`	—

Event ID 6002 — IoContext initialized

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

IoContext initialized

Fields

Name	Description
`TransactionId`	—

Event ID 6003 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`TransactionId`	—
`PayloadSize`	—

Event ID 6003 — Write log workitem queued

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

Write log workitem queued

Fields

Name	Description
`TransactionId`	—
`PayloadSize`	—

Event ID 6004 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`TransactionId`	—

Event ID 6004 — Write log record completed

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

Write log record completed

Fields

Name	Description
`TransactionId`	—

Event ID 6005 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`TransactionId`	—

Event ID 6005 — Send commit message

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

Send commit message

Fields

Name	Description
`TransactionId`	—

Event ID 6006 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`TransactionId`	—

Event ID 6006 — Commit message send completion

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

Commit message send completion

Fields

Name	Description
`TransactionId`	—

Event ID 6007 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`TransactionId`	—

Event ID 6007 — Commit response received

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

Commit response received

Fields

Name	Description
`TransactionId`	—

Event ID 6008 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`TransactionId`	—

Event ID 6008 — Commit completion

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

Commit completion

Fields

Name	Description
`TransactionId`	—

Event ID 6009 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`IRPAddress`	—
`Offset`	—
`Length`	—

Event ID 6009 — Application write IRP completed

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

Application write IRP completed

Fields

Name	Description
`IRPAddress`	—
`Offset`	—
`Length`	—

Event ID 6010 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`TransactionId`	—

Event ID 6010 — Flush request issued

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

Flush request issued

Fields

Name	Description
`TransactionId`	—

Event ID 6011 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`TransactionId`	—
`Offset`	—
`Length`	—

Event ID 6011 — Write IRP issued to disk

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

Write IRP issued to disk

Fields

Name	Description
`TransactionId`	—
`Offset`	—
`Length`	—

Event ID 6012 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`TransactionId`	—

Event ID 6012 — Flush IRP completed

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

Flush IRP completed

Fields

Name	Description
`TransactionId`	—

Event ID 6013 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`TransactionId`	—

Event ID 6013 — Flush completion

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

Flush completion

Fields

Name	Description
`TransactionId`	—

Event ID 6014 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`MessageXId`	—

Event ID 6014 — WVR message send

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

WVR message send

Fields

Name	Description
`MessageXId`	—

Event ID 6015 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`MessageXId`	—

Event ID 6015 — WVR message received

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

WVR message received

Fields

Name	Description
`MessageXId`	—

Event ID 6016 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`TransactionId`	—

Event ID 6016 — Commit log record request received

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

Commit log record request received

Fields

Name	Description
`TransactionId`	—

Event ID 6017 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`TransactionId`	—

Event ID 6017 — Commit log record reply sent

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

Commit log record reply sent

Fields

Name	Description
`TransactionId`	—

Event ID 6018 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`TransactionId`	—

Event ID 6018 — Flush data request received

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

Flush data request received

Fields

Name	Description
`TransactionId`	—

Event ID 6019 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`TransactionId`	—

Event ID 6019 — Flush data reply sent

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

Flush data reply sent

Fields

Name	Description
`TransactionId`	—

Event ID 6020 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Event ID 6020 — Message indicated

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

Message indicated

Event ID 6021 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`TransactionId`	—
`PayloadSize`	—

Event ID 6021 — Write log workitem processing starts

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

Write log workitem processing starts

Fields

Name	Description
`TransactionId`	—
`PayloadSize`	—

Event ID 6024 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`Status`	—

Event ID 6024 — Upcall Pre

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

Upcall Pre

Fields

Name	Description
`Status`	—

Event ID 6025 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`Status`	—

Event ID 6025 — Upcall Post

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

Upcall Post

Fields

Name	Description
`Status`	—

Event ID 6026 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`TransactionId`	—
`PayloadSize`	—

Event ID 6026 — CLFS write log being

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

CLFS write log being

Fields

Name	Description
`TransactionId`	—
`PayloadSize`	—

Event ID 6027 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`Status`	—

Event ID 6027 — CLFS write log end

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

CLFS write log end

Fields

Name	Description
`Status`	—

Event ID 6028 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`TransactionId`	—

Event ID 6028 — IoContext Created

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

IoContext Created

Fields

Name	Description
`TransactionId`	—

Event ID 6029 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`IRPAddress`	—
`Offset`	—
`Length`	—

Event ID 6029 — IRP assigned to IoContext

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

IRP assigned to IoContext

Fields

Name	Description
`IRPAddress`	—
`Offset`	—
`Length`	—

Event ID 6030 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`IRPAddress`	—
`Offset`	—
`Length`	—

Event ID 6030 — IRP inserted into pending queue

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

IRP inserted into pending queue

Fields

Name	Description
`IRPAddress`	—
`Offset`	—
`Length`	—

Event ID 6031 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`IRPAddress`	—

Event ID 6031 — Read IRP overlap detection started

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

Read IRP overlap detection started

Fields

Name	Description
`IRPAddress`	—

Event ID 6032 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`IRPAddress`	—

Event ID 6032 — Read IRP overlap detection completed

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

Read IRP overlap detection completed

Fields

Name	Description
`IRPAddress`	—

Event ID 6033 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`IRPAddress`	—

Event ID 6033 — Read IRP forwarded to next driver

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

Read IRP forwarded to next driver

Fields

Name	Description
`IRPAddress`	—

Event ID 6034 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`IRPAddress`	—

Event ID 6034 — Read IRP completed

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

Read IRP completed

Fields

Name	Description
`IRPAddress`	—

Event ID 6035 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`TransactionId`	—

Event ID 6035 — IoContext completed

Provider: Microsoft-Windows-StorageReplica
Channel: Performance

Message

IoContext completed

Fields

Name	Description
`TransactionId`	—

Event ID 7001 — Created a raw partition manager.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Created a raw partition manager.

ReplicationGroupName: %2
ReplicationGroupId: %3
LogPartitionId: %4
Status: %5

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`LogPartitionId`	—
`Status`	—

Event ID 7002 — An error has occured when starting the raw ledger and stablizing the ledger entries.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

An error has occured when starting the raw ledger and stablizing the ledger entries.

ReplicationGroupName: %2
ReplicationGroupId: %3
LogPartitionId: %4
Create: %5
StabilizeLedger: %6
Status: %7

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`LogPartitionId`	—
`Create`	—
`StabilizeLedger`	—
`Status`	—

Event ID 7003 — An error has occured when starting the raw ledger and building the in-memory caches.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

An error has occured when starting the raw ledger and building the in-memory caches.

ReplicationGroupName: %2
ReplicationGroupId: %3
LogPartitionId: %4
Create: %5
StabilizeLedger: %6
Status: %7

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`LogPartitionId`	—
`Create`	—
`StabilizeLedger`	—
`Status`	—

Event ID 7004 — An error has occured when adding a raw log ledger.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

An error has occured when adding a raw log ledger.

ReplicationGroupId: %1
ReplicaSetId: %2
Status: %3

Fields

Name	Description
`ReplicationGroupId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 7005 — An error has occured when allocating the log file metadata handle.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

An error has occured when allocating the log file metadata handle.

ReplicationGroupId: %1
ReplicaSetId: %2
Status: %3

Fields

Name	Description
`ReplicationGroupId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 7006 — Same fileId exist when adding a raw log record ledger.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Same fileId exist when adding a raw log record ledger.

PhysicalFileId: %1
FileId: %2
Status: %3

Fields

Name	Description
`PhysicalFileId`	—
`FileId`	—
`Status`	—

Event ID 7007 — An error has occured when adding a raw log record ledger.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

An error has occured when adding a raw log record ledger.

PhysicalFileId: %1
FileId: %2
Status: %3

Fields

Name	Description
`PhysicalFileId`	—
`FileId`	—
`Status`	—

Event ID 7008 — An error has occured when allocating the log file handle.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

An error has occured when allocating the log file handle.

Status: %1

Fields

Name	Description
`Status`	—

Event ID 7009 — An error has occured when adding a raw bitmap ledger.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

An error has occured when adding a raw bitmap ledger.

ReplicationGroupId: %1
ReplicaSetId: %2
Status: %3

Fields

Name	Description
`ReplicationGroupId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 7010 — An error has occured when adding a raw bitmap record ledger.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

An error has occured when adding a raw bitmap record ledger.

ReplicationGroupId: %1
ReplicaSetId: %2
PartnerReplicationGroupId: %3
Status: %4

Fields

Name	Description
`ReplicationGroupId`	—
`ReplicaSetId`	—
`PartnerReplicationGroupId`	—
`Status`	—

Event ID 7011 — Log does not have any log records but the first log record offset is not zero.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Log does not have any log records but the first log record offset is not zero.

ReplicationGroupId: %1

Fields

Name	Description
`ReplicationGroupId`	—

Event ID 7012 — The next log record offset is not zero.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

The next log record offset is not zero.

ReplicationGroupId: %1

Fields

Name	Description
`ReplicationGroupId`	—

Event ID 7013 — Bitmap does not have any bitmap records but the first bitmap record offset is not zero.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Bitmap does not have any bitmap records but the first bitmap record offset is not zero.

ReplicationGroupId: %1

Fields

Name	Description
`ReplicationGroupId`	—

Event ID 7014 — The next bitmap record offset is not zero.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

The next bitmap record offset is not zero.

ReplicationGroupId: %1

Fields

Name	Description
`ReplicationGroupId`	—

Event ID 7015 — Destroyed a raw partition manager.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Destroyed a raw partition manager.

Event ID 7016 — An error has occured when destroying a raw partition manager.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

An error has occured when destroying a raw partition manager.

Event ID 7017 — No logs exist but bitmap file exists while destroying the raw ledger.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

No logs exist but bitmap file exists while destroying the raw ledger.

Event ID 7018 — Try to delete a log ledger while the log count is already 0.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Try to delete a log ledger while the log count is already 0.

ReplicationGroupId: %1

Fields

Name	Description
`ReplicationGroupId`	—

Event ID 7019 — Try to delete a bitmap ledger while the partition count is already 0.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Try to delete a bitmap ledger while the partition count is already 0.

ReplicationGroupId: %1

Fields

Name	Description
`ReplicationGroupId`	—

Event ID 7020 — Try to delete a raw bitmap ledger by property while the ledger is invalid.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Try to delete a raw bitmap ledger by property while the ledger is invalid.

ReplicaSetId: %1
PartnerReplicationGroupId: %2
Status: %3

Fields

Name	Description
`ReplicaSetId`	—
`PartnerReplicationGroupId`	—
`Status`	—

Event ID 7021 — Try to delete a raw bitmap ledger by property while the ledger header is invalid.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Try to delete a raw bitmap ledger by property while the ledger header is invalid.

ReplicaSetId: %1
PartnerReplicationGroupId: %2
Status: %3

Fields

Name	Description
`ReplicaSetId`	—
`PartnerReplicationGroupId`	—
`Status`	—

Event ID 7022 — Try to delete a raw bitmap ledger by handle while the ledger is invalid.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Try to delete a raw bitmap ledger by handle while the ledger is invalid.

Event ID 7023 — Try to delete a raw bitmap ledger by handle while the ledger header is invalid.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Try to delete a raw bitmap ledger by handle while the ledger header is invalid.

Status: %1

Fields

Name	Description
`Status`	—

Event ID 7024 — Try to delete a log metadata by handle while the ledger is invalid.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Try to delete a log metadata by handle while the ledger is invalid.

Event ID 7025 — Try to delete a log metadata by handle while the ledger is invalid.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Try to delete a log metadata by handle while the ledger is invalid.

Status: %1

Fields

Name	Description
`Status`	—

Event ID 7026 — Try to delete a log file by handle while the raw handle is invalid.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Try to delete a log file by handle while the raw handle is invalid.

RawHandleFileOffset: %1
RawHandleFileSize: %2
FileOffset: %3
FileSize: %4

Fields

Name	Description
`RawHandleFileOffset`	—
`RawHandleFileSize`	—
`FileOffset`	—
`FileSize`	—

Event ID 7027 — Try to delete a log file by handle while the ledger handle is invalid.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Try to delete a log file by handle while the ledger handle is invalid.

Status: %1

Fields

Name	Description
`Status`	—

Event ID 7028 — Try to destroy a log file by handle while the raw handle is invalid.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Try to destroy a log file by handle while the raw handle is invalid.

RawHandleFileOffset: %1
RawHandleFileSize: %2
FileOffset: %3
FileSize: %4

Fields

Name	Description
`RawHandleFileOffset`	—
`RawHandleFileSize`	—
`FileOffset`	—
`FileSize`	—

Event ID 7029 — Try to destroy a log file by handle while the ledger handle is invalid.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Try to destroy a log file by handle while the ledger handle is invalid.

Status: %1

Fields

Name	Description
`Status`	—

Event ID 7030 — Clean up orphaned raw log ledgers for all replication groups or specific replication group.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Clean up orphaned raw log ledgers for all replication groups or specific replication group.

ReplicationGroupId: %1
SpecificReplicationGroup: %2
Status: %3

Fields

Name	Description
`ReplicationGroupId`	—
`SpecificReplicationGroup`	—
`Status`	—

Event ID 7031 — Clean up orphaned raw log ledger and its related log files.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Clean up orphaned raw log ledger and its related log files.

ReplicationGroupId: %1
ReplicaSetId: %2
Status: %3

Fields

Name	Description
`ReplicationGroupId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 7032 — Clean up orphaned raw bitmap ledger and its related bitmap files.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Clean up orphaned raw bitmap ledger and its related bitmap files.

ReplicationGroupId: %1
ReplicaSetId: %2
Status: %3

Fields

Name	Description
`ReplicationGroupId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 7033 — Reconcile the raw ledger entries.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Reconcile the raw ledger entries.

ReplicationGroupName: %2
ReplicationGroupId: %3
LogPartitionId: %4
Create: %5
StabilizeLedger: %6
Status: %7

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`LogPartitionId`	—
`Create`	—
`StabilizeLedger`	—
`Status`	—

Event ID 7034 — The ledger entry is in transition state while buiding the in-memory ledger.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

The ledger entry is in transition state while buiding the in-memory ledger.

Event ID 7035 — Log record ledger validation failed due to invalid entry type, status or checksum.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Log record ledger validation failed due to invalid entry type, status or checksum.

Event ID 7036 — Log ledger validation failed due to invalid entry type, status or checksum.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Log ledger validation failed due to invalid entry type, status or checksum.

Event ID 7037 — Bitmap record ledger validation failed due to invalid entry type, status or checksum.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Bitmap record ledger validation failed due to invalid entry type, status or checksum.

Event ID 7038 — Bitmap ledger validation failed due to invalid entry type, status or checksum.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Bitmap ledger validation failed due to invalid entry type, status or checksum.

Event ID 7039 — Ledger entry cannot be in deleted state but with invalid entry type.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Ledger entry cannot be in deleted state but with invalid entry type.

LedgerEntryStartingOffset: %1
LedgerEntryType: %2
Status: %3

Fields

Name	Description
`LedgerEntryStartingOffset`	—
`LedgerEntryType`	—
`Status`	—

Event ID 7040 — Ledger entry type is invalid and is in use.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Ledger entry type is invalid and is in use.

LedgerEntryStartingOffset: %1
LedgerEntryType: %2
Status: %3

Fields

Name	Description
`LedgerEntryStartingOffset`	—
`LedgerEntryType`	—
`Status`	—

Event ID 7041 — Max ledger size must be zero for log or bitmap ledger entries.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Max ledger size must be zero for log or bitmap ledger entries.

LedgerEntryStartingOffset: %1
LedgerEntryType: %2
MaxLedgerSize: %3
Status: %4

Fields

Name	Description
`LedgerEntryStartingOffset`	—
`LedgerEntryType`	—
`MaxLedgerSize`	—
`Status`	—

Event ID 7042 — Log partition is full and cannot accomodate this file.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Log partition is full and cannot accomodate this file.

LedgerEntryType: %1
FileSize: %2
Status: %3

Fields

Name	Description
`LedgerEntryType`	—
`FileSize`	—
`Status`	—

Event ID 7043 — A Ledger entry status cannot be any intermediate status right now.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

A Ledger entry status cannot be any intermediate status right now.

LedgerEntryStartingOffset: %1
LedgerEntryStatus: %2
LedgerEntryType: %3
Status: %4

Fields

Name	Description
`LedgerEntryStartingOffset`	—
`LedgerEntryStatus`	—
`LedgerEntryType`	—
`Status`	—

Event ID 7044 — Could not find a slot to fit in this file.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Could not find a slot to fit in this file.

Status: %1

Fields

Name	Description
`Status`	—

Event ID 8001 — Raw Log Initialized.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Raw Log Initialized.

PartitionOffset: %1
PartitionLength: %2
Create: %3
Status: %4

Fields

Name	Description
`PartitionOffset`	—
`PartitionLength`	—
`Create`	—
`Status`	—

Event ID 8002 — Raw Log Initialization Failed.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Raw Log Initialization Failed.

PartitionOffset: %1
PartitionLength: %2
Create: %3
Status: %4

Fields

Name	Description
`PartitionOffset`	—
`PartitionLength`	—
`Create`	—
`Status`	—

Event ID 8003 — Writting an empty log record completed with status.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Writting an empty log record completed with status: %4 .

RecordLength: %1
PayloadLength: %2
Lsn: %3

Fields

Name	Description
`RecordLength`	—
`PayloadLength`	—
`Lsn`	—
`Status`	—

Event ID 8004 — Writting an empty log record completed with status.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Writting an empty log record completed with status: %4 .

RecordLength: %1
PayloadLength: %2
Lsn: %3

Fields

Name	Description
`RecordLength`	—
`PayloadLength`	—
`Lsn`	—
`Status`	—

Event ID 8005 — Raw Log reconcile completed with status.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Raw Log reconcile completed with status: %2 .

ReconcileStartLsn: %1

Fields

Name	Description
`ReconcileStartLsn`	—
`Status`	—

Event ID 8006 — Raw Log reconcile completed with status.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Raw Log reconcile completed with status: %2 .

ReconcileStartLsn: %1

Fields

Name	Description
`ReconcileStartLsn`	—
`Status`	—

Event ID 8007 — Raw Log truncate completed with status.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Raw Log truncate completed with status: %2 .

TruncateLsn: %1

Fields

Name	Description
`TruncateLsn`	—
`Status`	—

Event ID 8008 — Raw Log truncate completed with status.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Raw Log truncate completed with status: %2 .

TruncateLsn: %1

Fields

Name	Description
`TruncateLsn`	—
`Status`	—

Event ID 8009 — Reading the last checkpoint completed with status.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Reading the last checkpoint completed with status: %2 .

 CheckpointLsn: %1

Fields

Name	Description
`Lsn`	—
`Status`	—

Event ID 8010 — Reading the previous checkpoint completed with status.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Reading the previous checkpoint completed with status: %2 .

 CheckpointLsn: %1

Fields

Name	Description
`Lsn`	—
`Status`	—

Event ID 8011 — Writing a log record to raw log completed with status.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Writing a log record to raw log completed with status: %2 .

 RecordLsn: %1

Fields

Name	Description
`Lsn`	—
`Status`	—

Event ID 8012 — Flushing control area failed with status.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Flushing control area failed with status: %2 .

 Last Checkpoint Lsn: %1

Fields

Name	Description
`Lsn`	—
`Status`	—

Event ID 8013 — Unable to dispatch write packet at this time.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Unable to dispatch write packet at this time. Adding it back to the queue for later processing.

 Lsn: %1

Fields

Name	Description
`Lsn`	—

Event ID 9000 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`SourceReplicationGroupNameLength`	—
`SourceReplicationGroupName`	—
`SourceReplicationGroupId`	—
`SourceReplicaNameLength`	—
`SourceReplicaName`	—
`ReplicaSetId`	—
`TargetReplicationGroupNameLength`	—
`TargetReplicationGroupName`	—
`TargetReplicationGroupId`	—
`Status`	—

Event ID 9000 — Failed to create metadata files for managing block copy operations.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Failed to create metadata files for managing block copy operations.

LocalReplicationGroupName: %2
LocalReplicationGroupId: %3
ReplicaName: %5
ReplicaSetId: %6
RemoteReplicationGroupName: %8
RemoteReplicationGroupId: %9
Status: %10

Fields

Name	Description
`SourceReplicationGroupNameLength`	—
`SourceReplicationGroupName`	—
`SourceReplicationGroupId`	—
`SourceReplicaNameLength`	—
`SourceReplicaName`	—
`ReplicaSetId`	—
`TargetReplicationGroupNameLength`	—
`TargetReplicationGroupName`	—
`TargetReplicationGroupId`	—
`Status`	—

Event ID 9001 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`SourceReplicationGroupNameLength`	—
`SourceReplicationGroupName`	—
`SourceReplicationGroupId`	—
`SourceReplicaNameLength`	—
`SourceReplicaName`	—
`ReplicaSetId`	—
`TargetReplicationGroupNameLength`	—
`TargetReplicationGroupName`	—
`TargetReplicationGroupId`	—
`Status`	—

Event ID 9001 — Failed to update metadata files for managing block copy operations.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Failed to update metadata files for managing block copy operations.

LocalReplicationGroupName: %2
LocalReplicationGroupId: %3
ReplicaName: %5
ReplicaSetId: %6
RemoteReplicationGroupName: %8
RemoteReplicationGroupId: %9
Status: %10

Fields

Name	Description
`SourceReplicationGroupNameLength`	—
`SourceReplicationGroupName`	—
`SourceReplicationGroupId`	—
`SourceReplicaNameLength`	—
`SourceReplicaName`	—
`ReplicaSetId`	—
`TargetReplicationGroupNameLength`	—
`TargetReplicationGroupName`	—
`TargetReplicationGroupId`	—
`Status`	—

Event ID 9002 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`SourceReplicationGroupNameLength`	—
`SourceReplicationGroupName`	—
`SourceReplicationGroupId`	—
`SourceReplicaNameLength`	—
`SourceReplicaName`	—
`ReplicaSetId`	—
`TargetReplicationGroupNameLength`	—
`TargetReplicationGroupName`	—
`TargetReplicationGroupId`	—
`Status`	—

Event ID 9002 — Detected corruption in the metadata files for managing block copy operations.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Detected corruption in the metadata files for managing block copy operations.

LocalReplicationGroupName: %2
LocalReplicationGroupId: %3
ReplicaName: %5
ReplicaSetId: %6
RemoteReplicationGroupName: %8
RemoteReplicationGroupId: %9
Status: %10

Fields

Name	Description
`SourceReplicationGroupNameLength`	—
`SourceReplicationGroupName`	—
`SourceReplicationGroupId`	—
`SourceReplicaNameLength`	—
`SourceReplicaName`	—
`ReplicaSetId`	—
`TargetReplicationGroupNameLength`	—
`TargetReplicationGroupName`	—
`TargetReplicationGroupId`	—
`Status`	—

Event ID 9003 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`BitmapFileNameLength`	—
`BitmapFileName`	—
`Status`	—

Event ID 9003 — Unable to delete the metadata files used for managing block copy operations.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Unable to delete the metadata files used for managing block copy operations.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
MetadataFile: %7
Status: %8

Guidance: When removing partition from replication, Storage Replica also attempts to delete the metadata file associated with the partition. Since this action failed, you must delete the file manually.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`BitmapFileNameLength`	—
`BitmapFileName`	—
`Status`	—

Event ID 9004 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`SourceReplicationGroupNameLength`	—
`SourceReplicationGroupName`	—
`SourceReplicationGroupId`	—
`SourceReplicaNameLength`	—
`SourceReplicaName`	—
`ReplicaSetId`	—
`TargetReplicationGroupNameLength`	—
`TargetReplicationGroupName`	—
`TargetReplicationGroupId`	—
`Status`	—

Event ID 9004 — Resetting the recovery bitmap.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Resetting the recovery bitmap.

LocalReplicationGroupName: %2
LocalReplicationGroupId: %3
ReplicaName: %5
ReplicaSetId: %6
RemoteReplicationGroupName: %8
RemoteReplicationGroupId: %9

Guidance: You should expect this event when configuring  replication for the first time or when Storage Replica has detected errors in the bitmap metadata files used to manage block copy operations. If the destination cannot recover using the log, it will copy all delta blocks from the source partition.

Fields

Name	Description
`SourceReplicationGroupNameLength`	—
`SourceReplicationGroupName`	—
`SourceReplicationGroupId`	—
`SourceReplicaNameLength`	—
`SourceReplicaName`	—
`ReplicaSetId`	—
`TargetReplicationGroupNameLength`	—
`TargetReplicationGroupName`	—
`TargetReplicationGroupId`	—
`Status`	—

Event ID 9005 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 9005 — Failed to query disk provision map when initializing metadata files for managing block copy operations.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Failed to query disk provision map when initializing metadata files for managing block copy operations.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
PartitionId: %6
ReplicaId: %7
Status: %8

Guidance: If the allocation map can be queried for the replicated partition, the initial block copy will only copy allocated blocks. If this operation fails, the initial block copy will copy all blocks.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 9006 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`AllocationSize`	—

Event ID 9006 — The disk is thinly-provisioned.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

The disk is thinly-provisioned.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
PartitionId: %6
ReplicaId: %7
Allocation Size: %8

Guidance: When a disk is thinly-provisioned, the initial block copy will only copy allocated blocks.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`AllocationSize`	—

Event ID 9007 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 9007 — The disk is not thinly-provisioned.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

The disk is not thinly-provisioned.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
PartitionId: %6
ReplicaId: %7

Guidance: When a disk is not thinly-provisioned, the initial block copy will copy all blocks.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 10001 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`Status`	—

Event ID 10001 — Filter driver failed to start.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Filter driver failed to start.

Status: %1

Fields

Name	Description
`Status`	—

Event ID 10002 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Event ID 10002 — Filter driver started successfully.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Filter driver started successfully.

Event ID 10003 — Memory now available.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Memory now available.

Guidance: The previous low memory condition announced in event 10004 has been resolved. Storage Replica performance may no longer be degraded.

Event ID 10004 — There is not enough available memory.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

There is not enough available memory.

Available memory: %1

Guidance: When system memory is low, Storage Replica operates in a degraded state and reduces its own memory usage. Initial replication and block copy recovery will be slower than normal when in this state. To determine the cause of unknown memory conditions, use Resource Monitor, Performance Monitor, or the Windows Performance Analyzer tools. If the condition is expected, consider adding more physical memory.

Fields

Name	Description
`Size`	—

Event ID 10005 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`StringLength`	—
`String`	—
`Status`	—

Event ID 10005 — The filter Resource Manager subsystem has started but the registry based overrides for the default driver configuration values is missing.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

The filter Resource Manager subsystem has started but the registry based overrides for the default driver configuration values is missing.

RegistryKey: %2

Guidance: The driver uses optional values stored under the indicated registry key to provide overrides for the built in default values. While it is not an error, the driver expects the RegistryKey indicated to exist even if there are no values stored under that key. The key should be created with the default values for the security information to prevent a reoccurence of this message.

The driver will continue to operate but will use the built in defaults for any configurable information.

Note: This does not affect the presence of any configured Storage Replicas, groups or partnerships.

Fields

Name	Description
`StringLength`	—
`String`	—
`Status`	—

Event ID 10007 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`StringLength`	—
`String`	—
`Status`	—

Event ID 10007 — The filter Resource Manager subsystem has started but their was a serious error attempting to start the driver configuration manager.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

The filter Resource Manager subsystem has started but their was a serious error attempting to start the driver configuration manager.

RegistryKey: %2
Status: %3

Guidance: The driver uses optional values stored under the indicated registry key to provide overrides for the built in default values. A serious error has occured when attempting to load the configuration information. Check the registry to ensure the keys and values are present and properly configured.

Note: This does not affect the presence of any configured Storage Replicas, groups or partnerships.

Fields

Name	Description
`StringLength`	—
`String`	—
`Status`	—

Event ID 10011 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`DeviceNameLength`	—
`DeviceName`	—

Event ID 10011 — Filter driver received partition surprise removal request.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Filter driver received partition surprise removal request.

ReplicaName: %2
PartitionId: %3
DeviceName: %5

Fields

Name	Description
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`DeviceNameLength`	—
`DeviceName`	—

Event ID 10020 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceObject`	—
`PhysicalDeviceObject`	—
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`DeviceType`	—
`Characteristics`	—
`Status`	—

Event ID 10020 — AddDevice driver routine called.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

AddDevice driver routine called.

DeviceObject: %1
PhysicalDeviceObject: %2
PhysicalDeviceName: %4
TargetDeviceName: %6
DeviceType: %7
Characteristics: %8
Status: %9

Fields

Name	Description
`DeviceObject`	—
`PhysicalDeviceObject`	—
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`DeviceType`	—
`Characteristics`	—
`Status`	—

Event ID 10021 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceObject`	—
`PhysicalDeviceObject`	—
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`DeviceType`	—
`Characteristics`	—
`Status`	—

Event ID 10021 — AddDevice driver routine called.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

AddDevice driver routine called.

DeviceObject: %1
PhysicalDeviceObject: %2
PhysicalDeviceName: %4
TargetDeviceName: %6
DeviceType: %7
Characteristics: %8
Status: %9

Fields

Name	Description
`DeviceObject`	—
`PhysicalDeviceObject`	—
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`DeviceType`	—
`Characteristics`	—
`Status`	—

Event ID 10022 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceObject`	—
`PhysicalDeviceObject`	—
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`DeviceType`	—
`Characteristics`	—
`Status`	—

Event ID 10022 — AddDevice driver routine called but has determined that device is not a candidate for attachment.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

AddDevice driver routine called but has determined that device is not a candidate for attachment.

DeviceObject: %1
PhysicalDeviceObject: %2
PhysicalDeviceName: %4
TargetDeviceName: %6
DeviceType: %7
Characteristics: %8
Status: %9

Fields

Name	Description
`DeviceObject`	—
`PhysicalDeviceObject`	—
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`DeviceType`	—
`Characteristics`	—
`Status`	—

Event ID 10031 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceObject`	—
`PhysicalDeviceObject`	—
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`DeviceType`	—
`Characteristics`	—
`Status`	—

Event ID 10031 — AddDevice call to IocreateDevice() failed to create a Storage Replica device for the underlying device.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

AddDevice call to IocreateDevice() failed to create a Storage Replica device for the underlying device.

DeviceObject: %1
PhysicalDeviceObject: %2
PhysicalDeviceName: %4
TargetDeviceName: %6
DeviceType: %7
Characteristics: %8
Status: %9

Fields

Name	Description
`DeviceObject`	—
`PhysicalDeviceObject`	—
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`DeviceType`	—
`Characteristics`	—
`Status`	—

Event ID 10041 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceObject`	—
`PhysicalDeviceObject`	—
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`DeviceType`	—
`Characteristics`	—
`Status`	—

Event ID 10041 — AddDevice call to IoAttachDeviceToDeviceStack() failed to attach to the underlying device.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

AddDevice call to IoAttachDeviceToDeviceStack() failed to attach to the underlying device.

DeviceObject: %1
PhysicalDeviceObject: %2
PhysicalDeviceName: %4
TargetDeviceName: %6
DeviceType: %7
Characteristics: %8
Status: %9

Fields

Name	Description
`DeviceObject`	—
`PhysicalDeviceObject`	—
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`DeviceType`	—
`Characteristics`	—
`Status`	—

Event ID 10050 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`IoControlCode`	—

Event ID 10050 — Perform DevIoControl.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Perform DevIoControl.

PhysicalDeviceName: %2
TargetDeviceName: %4
IoControlCode: %5

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`IoControlCode`	—

Event ID 10060 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`IoControlCode`	—
`Status`	—

Event ID 10060 — Perform DevIoControl.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Perform DevIoControl.

PhysicalDeviceName: %2
TargetDeviceName: %4
IoControlCode: %5
Status: %6

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`IoControlCode`	—
`Status`	—

Event ID 10061 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`IoControlCode`	—
`Status`	—

Event ID 10061 — Perform DevIoControl.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Perform DevIoControl.

PhysicalDeviceName: %2
TargetDeviceName: %4
IoControlCode: %5
Status: %6

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`IoControlCode`	—
`Status`	—

Event ID 10070 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`MinorFunction`	—

Event ID 10070 — DispatchPnp for minor function started.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

DispatchPnp for minor function started.

PhysicalDeviceName: %2
TargetDeviceName: %4
MinorFunction: %5

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`MinorFunction`	—

Event ID 10080 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`MinorFunction`	—
`Status`	—

Event ID 10080 — DispatchPnp for minor function completed.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

DispatchPnp for minor function completed.

PhysicalDeviceName: %2
TargetDeviceName: %4
MinorFunction: %5
Status: %6

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`MinorFunction`	—
`Status`	—

Event ID 10090 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—

Event ID 10090 — StartDevice entered.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

StartDevice entered.

PhysicalDeviceName: %2
TargetDeviceName: %4

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—

Event ID 10100 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`Status`	—

Event ID 10100 — StartDevice completed.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

StartDevice completed.

PhysicalDeviceName: %2
TargetDeviceName: %4
Status: %5

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`Status`	—

Event ID 10101 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`Status`	—

Event ID 10101 — StartDevice completed.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

StartDevice completed.

PhysicalDeviceName: %2
TargetDeviceName: %4
Status: %5

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`Status`	—

Event ID 10110 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`Status`	—

Event ID 10110 — StartDevice failed to forward the IRP to the underlying device.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

StartDevice failed to forward the IRP to the underlying device.

Status: %1

Fields

Name	Description
`Status`	—

Event ID 10111 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`Status`	—

Event ID 10111 — PnP device arrival failed to complete processing the device.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

PnP device arrival failed to complete processing the device.

PhysicalDeviceName: %2
TargetDeviceName: %4
Status: %5

Guidance: A serious problem has been identified with the contents of the Storage Replica partition database on the disk device. Until the problem is fixed Storage Replica will continue to block write access to the data partitions in an attempt to protect the disk against any further damage. The potential issues include internal consistency check failures, multiple instances of the database (there should be exactly one), disk block alignment issues or even corruption. Many of the potential problems can be the result of a disk based backup/restore cycle where the device onto which the backup was restored has different physical characteristics (e.g. differing physical sector sizes). If this error follows a recent restoration of a physical disk backup, verify that the physical sector size (typically either 512 bytes or 4096 bytes (4KB)) of both the original disk and the replacement disk are the same and that the replacement disk is the same size as the original or larger.

To restore write access to data partitions, the DiskPart.exe utility can be used to delete the Storage Replica Partition (GPT Partition Type Id 558d43c5-a1ac-43c0-aac8-d1472b2923d1) however doing so will prevent the disk being involved in replication until the replication configuration is repaired. After removing the Storage Replica Partition, the disk should be disabled and then re-enabled (or detached/re-attached) after which the disk should be accessible as normal.

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`Status`	—

Event ID 10120 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—

Event ID 10120 — RemoveDevice entered.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

RemoveDevice entered.

PhysicalDeviceName: %2
TargetDeviceName: %4

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—

Event ID 10121 — RemoveDevice completed.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

RemoveDevice completed.

PhysicalDeviceName: %2
TargetDeviceName: %4
Status: %5

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`Status`	—

Event ID 10130 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—

Event ID 10130 — SurpriseRemoveDevice entered.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

SurpriseRemoveDevice entered.

PhysicalDeviceName: %2
TargetDeviceName: %4

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—

Event ID 10131 — SurpriseRemoveDevice completed.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

SurpriseRemoveDevice completed.

PhysicalDeviceName: %2
TargetDeviceName: %4
Status: %5

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`Status`	—

Event ID 10132 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`Status`	—

Event ID 10132 — SurpriseRemoveDevice completed.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

SurpriseRemoveDevice completed.

PhysicalDeviceName: %2
TargetDeviceName: %4
Status: %5

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`Status`	—

Event ID 10160 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—

Event ID 10160 — IOCTL_DISK_GET_DISK_ATTRIBUTES entry.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_GET_DISK_ATTRIBUTES entry.

DeviceName: %2
DiskReplicationState: %3

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—

Event ID 10170 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10170 — IOCTL_DISK_GET_DISK_ATTRIBUTES exit.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_GET_DISK_ATTRIBUTES exit.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10171 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10171 — IOCTL_DISK_GET_DISK_ATTRIBUTES exit.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

IOCTL_DISK_GET_DISK_ATTRIBUTES exit.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10180 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`DiskAttributeOffline`	—
`DiskAttributeReadOnly`	—
`Status`	—

Event ID 10180 — IOCTL_DISK_GET_DISK_ATTRIBUTES completed.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_GET_DISK_ATTRIBUTES completed.

DeviceName: %2
DiskReplicationState: %3
DiskAttributeOffline: %4
DiskAttributeReadonly: %5
Status: %6

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`DiskAttributeOffline`	—
`DiskAttributeReadOnly`	—
`Status`	—

Event ID 10181 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`DiskAttributeOffline`	—
`DiskAttributeReadOnly`	—
`Status`	—

Event ID 10181 — IOCTL_DISK_GET_DISK_ATTRIBUTES completed.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

IOCTL_DISK_GET_DISK_ATTRIBUTES completed.

DeviceName: %2
DiskReplicationState: %3
DiskAttributeOffline: %4
DiskAttributeReadonly: %5
Status: %6

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`DiskAttributeOffline`	—
`DiskAttributeReadOnly`	—
`Status`	—

Event ID 10190 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—

Event ID 10190 — IOCTL_DISK_SET_DISK_ATTRIBUTES entry.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_SET_DISK_ATTRIBUTES entry.

DeviceName: %2
DiskReplicationState: %3

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—

Event ID 10200 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10200 — IOCTL_DISK_SET_DISK_ATTRIBUTES exit.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_SET_DISK_ATTRIBUTES exit.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10201 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10201 — IOCTL_DISK_SET_DISK_ATTRIBUTES exit.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

IOCTL_DISK_SET_DISK_ATTRIBUTES exit.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10202 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10202 — IOCTL_DISK_SET_DISK_ATTRIBUTES completion callback.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_SET_DISK_ATTRIBUTES completion callback.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10203 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10203 — IOCTL_DISK_SET_DISK_ATTRIBUTES completion callback.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

IOCTL_DISK_SET_DISK_ATTRIBUTES completion callback.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10210 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskAttributeOffline`	—
`DiskAttributeReadOnly`	—
`DiskAttributesMask`	—
`DiskAttributes`	—
`DiskAttributeRelinquishOwnership`	—
`DiskOwnerGuid`	—
`Status`	—

Event ID 10210 — IOCTL_DISK_SET_DISK_ATTRIBUTES state change.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_SET_DISK_ATTRIBUTES state change.

DeviceName: %2
DiskAttributeOffline: %3
DiskAttributeReadonly: %4
DiskAttributesMask: %5
DiskAttributes: %6
DiskAttributeRelinquishOwnership: %7
DiskOwnerGuid: %8

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskAttributeOffline`	—
`DiskAttributeReadOnly`	—
`DiskAttributesMask`	—
`DiskAttributes`	—
`DiskAttributeRelinquishOwnership`	—
`DiskOwnerGuid`	—
`Status`	—

Event ID 10220 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`Status`	—

Event ID 10220 — IrpAllocateForAsynchronousIoctlRequest completed.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IrpAllocateForAsynchronousIoctlRequest completed.

DeviceName: %2
Status: %3

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`Status`	—

Event ID 10221 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`Status`	—

Event ID 10221 — IrpAllocateForAsynchronousIoctlRequest completed.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IrpAllocateForAsynchronousIoctlRequest completed.

DeviceName: %2
Status: %3

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`Status`	—

Event ID 10240 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionId`	—
`PartitionNumber`	—
`ExistingDeviceNameLength`	—
`ExistingDeviceName`	—
`ExistingDiskId`	—
`ExistingPartitionId`	—
`ExistingPartitionNumber`	—
`Status`	—

Event ID 10240 — A duplicated partition was detected when processing a newly arrived disk.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

A duplicated partition was detected when processing a newly arrived disk.

DeviceName: %2
DiskId: %3
PartitionId: %4
PartitionNumber: %5
ExistingDeviceName: %7
ExistingDiskId: %8
ExistingPartitionId: %9
ExistingPartitionNumber: %10
Status: %11

Guidance: This event occurs when a partition with a specific GPT Partition ID is detected as a duplicate of a partition that has already been seen and connected. This can occur for example if the newly arrived disk is visible to the system over multiple paths as can occur for hardware providing multiple access paths and the Multipath I/O feature is not installed, or the disk is a clone of an existing disk. To resolve the condition, install the Multipath I/O feature or modify the GPT disk and partition identifiers to be unique across all disks visible to the system.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionId`	—
`PartitionNumber`	—
`ExistingDeviceNameLength`	—
`ExistingDeviceName`	—
`ExistingDiskId`	—
`ExistingPartitionId`	—
`ExistingPartitionNumber`	—
`Status`	—

Event ID 10244 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10244 — IOCTL_DISK_SET_DRIVE_LAYOUT completion callback.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

IOCTL_DISK_SET_DRIVE_LAYOUT completion callback.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10250 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—

Event ID 10250 — IOCTL_DISK_SET_DRIVE_LAYOUT entry.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_SET_DRIVE_LAYOUT entry.

DeviceName: %2
DiskReplicationState: %3

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—

Event ID 10251 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10251 — IOCTL_DISK_SET_DRIVE_LAYOUT exit.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_SET_DRIVE_LAYOUT exit.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10252 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10252 — IOCTL_DISK_SET_DRIVE_LAYOUT exit.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

IOCTL_DISK_SET_DRIVE_LAYOUT exit.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10253 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10253 — IOCTL_DISK_SET_DRIVE_LAYOUT completion callback.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_SET_DRIVE_LAYOUT completion callback.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10254 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10254 — IOCTL_DISK_SET_DRIVE_LAYOUT completion callback.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

IOCTL_DISK_SET_DRIVE_LAYOUT completion callback.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10255 — IOCTL_DISK_SET_DRIVE_LAYOUT was called for a disk involved in replication (which requires a GPT layout) with a new layout formatted as an MBR disk.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

IOCTL_DISK_SET_DRIVE_LAYOUT was called for a disk involved in replication (which requires a GPT layout) with a new layout formatted as an MBR disk.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Guidance: This event occurs when an attempt is made to reinitialize a disk as an MBR disk while the disk is initialized as a GPT style disk and replication is active on one or more of the partitions on that disk. For the operation to succeed, there must be no replication configurations associated with any of the partitions present on the disk.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10260 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—

Event ID 10260 — IOCTL_DISK_SET_DRIVE_LAYOUT_EX entry.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_SET_DRIVE_LAYOUT_EX entry.

DeviceName: %2
DiskReplicationState: %3

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—

Event ID 10261 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10261 — IOCTL_DISK_SET_DRIVE_LAYOUT_EX exit.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_SET_DRIVE_LAYOUT_EX exit.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10262 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10262 — IOCTL_DISK_SET_DRIVE_LAYOUT_EX exit.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

IOCTL_DISK_SET_DRIVE_LAYOUT_EX exit.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10263 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10263 — IOCTL_DISK_SET_DRIVE_LAYOUT completion callback.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_SET_DRIVE_LAYOUT completion callback.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10265 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10265 — IOCTL_DISK_SET_DRIVE_LAYOUT_EX was called for a disk involved in replication and one or more partitions in the updated layout are currently in an a...

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

IOCTL_DISK_SET_DRIVE_LAYOUT_EX was called for a disk involved in replication and one or more partitions in the updated layout are currently in an active replication configuration.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Guidance: This event occurs when an attempt is made to delete or modify one or more partitions that are currently involved in an active replication configuration. For the layout modification operation to succeed, there must be no replication configurations associated with any of the partitions being modified.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10266 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10266 — IOCTL_DISK_SET_DRIVE_LAYOUT_EX was called for a disk involved in replication where the supplied layout is invalid in some way.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_SET_DRIVE_LAYOUT_EX was called for a disk involved in replication where the supplied layout is invalid in some way.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Guidance: This event occurs when an attempt is made to update the layout of a GPT disk currently involved with replication where there was an issue with the requested layout being structurally invalid or inconsistent in some way. This is likely an issue with the application making the call.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10267 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10267 — IOCTL_DISK_SET_DRIVE_LAYOUT_EX was called for a disk involved in replication where the supplied layout is requesting that the disk GPT identifier b...

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_SET_DRIVE_LAYOUT_EX was called for a disk involved in replication where the supplied layout is requesting that the disk GPT identifier be changed.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Guidance: This event can occur when an attempt is made to re-initialize a disk or an attempt is made to alter the identification for a GPT disk currently involved with replication. To allow the operation to succeed, all the partitions on the disk must be removed from any replication configuration they might be part of.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10268 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10268 — IOCTL_DISK_SET_DRIVE_LAYOUT_EX was called for a disk involved in replication where the supplied layout is requesting that the Storage Replica Parti...

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

IOCTL_DISK_SET_DRIVE_LAYOUT_EX was called for a disk involved in replication where the supplied layout is requesting that the Storage Replica PartitionDb partition be removed.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Guidance: This event can occur when an attempt is made to remove the Storage Replica PartitionDb from a disk that has one or more partitions that are currently involved in an active replication configuration. The partition database contains some metadata that is required by the replication process while there are any replicating partitions so the attempt to remove the Storage Replica PArtitionDb was blocked. To remove the partition containing the Storage Replica PartitionDb there must be no replication configurations associated with any of the data partitions on the disk.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10269 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`PartitionId`	—
`CurrentOffset`	—
`CurrentLength`	—
`RequestedOffset`	—
`RequestedLength`	—
`Status`	—

Event ID 10269 — IOCTL_DISK_SET_DRIVE_LAYOUT_EX was called for a disk involved in replication where the supplied layout is requesting that the location or size of a...

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

IOCTL_DISK_SET_DRIVE_LAYOUT_EX was called for a disk involved in replication where the supplied layout is requesting that the location or size of a partition involved in a replication configuration be changed.

DeviceName: %2
DiskReplicationState: %3
PartitionId: %4
CurrentOffset: %5
CurrentLength: %6
RequestedOffset: %7
RequestedLength: %8
Status: %9

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`PartitionId`	—
`CurrentOffset`	—
`CurrentLength`	—
`RequestedOffset`	—
`RequestedLength`	—
`Status`	—

Event ID 10270 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`PartitionId`	—
`Status`	—

Event ID 10270 — IOCTL_DISK_SET_DRIVE_LAYOUT_EX was called for a disk involved in replication where the supplied layout is requesting that a partition involved in a...

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

IOCTL_DISK_SET_DRIVE_LAYOUT_EX was called for a disk involved in replication where the supplied layout is requesting that a partition involved in a replication configuration be removed.

DeviceName: %2
DiskReplicationState: %3
PartitionId: %4
Status: %5

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`PartitionId`	—
`Status`	—

Event ID 10271 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10271 — IOCTL_DISK_SET_DRIVE_LAYOUT_EX was called for a disk involved in replication where the supplied layout is requesting that the location or size of t...

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

IOCTL_DISK_SET_DRIVE_LAYOUT_EX was called for a disk involved in replication where the supplied layout is requesting that the location or size of the Storage Replica PartitionDb partition be changed.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Guidance: This event can occur when an attempt is made to alter the layout of the partitions on a GPT disk either previously or currently involved with replication. To allow the operation to succeed, all the partitions on the disk must be removed from any replication configuration they might be part of and then the disk must be cleaned and re-initialized or the WvrPartitionDb be removed explicitly. This can be achieved using the DiskPart.exe utility.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10290 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—

Event ID 10290 — IOCTL_DISK_GROW_PARTITION entry.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_GROW_PARTITION entry.

DeviceName: %2
DiskReplicationState: %3

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—

Event ID 10291 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10291 — IOCTL_DISK_GROW_PARTITION exit.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_GROW_PARTITION exit.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10292 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10292 — IOCTL_DISK_GROW_PARTITION exit.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

IOCTL_DISK_GROW_PARTITION exit.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10293 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`PartitionNumber`	—
`PartitionId`	—
`Status`	—

Event ID 10293 — IOCTL_DISK_GROW_PARTITION partition validation completed.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_GROW_PARTITION partition validation completed.

DeviceName: %2
DiskReplicationState: %3
PartitionNumber: %4
PartitionId: %5
Status: %6

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`PartitionNumber`	—
`PartitionId`	—
`Status`	—

Event ID 10294 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10294 — IOCTL_DISK_GROW_PARTITION was called for a disk which may be involved in replication with one or more partitions in an active replication configura...

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

IOCTL_DISK_GROW_PARTITION was called for a disk which may be involved in replication with one or more partitions in an active replication configuration. However, due to an earlier error when processing the disk arrival, the current replication status of the partitions cannot be determined. As a result, partition updates are blocked until such a determination can be made.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Guidance: This event occurs when an attempt is made to modify the size of a partition on a disk whose replication state is undetermined. Typically this is due to an error (such as a disk read failure) occuring when the system was processing the disk attachment to the system. As a precaution to prevent data corruption on the partition and any potential replication partners, the resizing operation has been blocked. For the partition size change to succeed there must be no replication configurations associated with any of the partitions being modified and the disk arrival processing must complete succesfully. Try using Device Manager to disabe and then re-enable the disk with the problem or failing that, a system reboot may clear the condition.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10295 — Partition resize called on a partition in Storage Replica configuration.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Partition resize called on a partition in Storage Replica configuration.

DeviceName: %2
PartitionNumber: %3
PartitionId: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`PartitionNumber`	—
`PartitionId`	—
`Status`	—

Event ID 10296 — Partition resize called on a partition in Storage Replica configuration completed.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Partition resize called on a partition in Storage Replica configuration completed.

DeviceName: %2
PartitionNumber: %3
PartitionId: %4
Status: %5

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`PartitionNumber`	—
`PartitionId`	—
`Status`	—

Event ID 10297 — Partition resize called on a partition in Storage Replica configuration completed.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Partition resize called on a partition in Storage Replica configuration completed.

DeviceName: %2
PartitionNumber: %3
PartitionId: %4
Status: %5

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`PartitionNumber`	—
`PartitionId`	—
`Status`	—

Event ID 10298 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`PartitionNumber`	—
`PartitionId`	—
`Status`	—

Event ID 10298 — Partition size mismatch with the corresponding data partition on source replication group resulted in resize of the following destination data part...

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Partition size mismatch with the corresponding data partition on source replication group resulted in resize of the following destination data partition.

DeviceName: %2
PartitionNumber: %3
PartitionId: %4
Status: %5

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`PartitionNumber`	—
`PartitionId`	—
`Status`	—

Event ID 10299 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`PartitionNumber`	—
`PartitionId`	—
`Status`	—

Event ID 10299 — Partition size mismatch with the corresponding data partition on source replication group resulted in a resize attempt of the following destination...

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Partition size mismatch with the corresponding data partition on source replication group resulted in a resize attempt of the following destination data partition. However, the resize operation failed. 

DeviceName: %2
PartitionNumber: %3
PartitionId: %4

 Guidance: Make sure there is enough storage space for the destination data partition to resize. If that is not possible, remove the partnership, revert the source data partition size, and re-enable partnership to continue replication.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`PartitionNumber`	—
`PartitionId`	—
`Status`	—

Event ID 10300 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`PartitionNumber`	—
`PartitionId`	—
`ExpectedSize`	—
`ActualSize`	—

Event ID 10300 — Source data partition resize succeeded.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Source data partition resize succeeded. However, the partition's size is unexpected. Moving the source replication group to failed state. 

DeviceName: %2
PartitionNumber: %3
PartitionId: %4
ExpectedSizeInBytes: %5
ActualSizeInBytes: %6

 Guidance: Ensure the source data partition matches in the intended size. You may have to remove partnership, resize data partitions, and recreate partnership.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`PartitionNumber`	—
`PartitionId`	—
`ExpectedSize`	—
`ActualSize`	—

Event ID 10301 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`PartitionNumber`	—
`PartitionId`	—
`ExpectedSize`	—
`ActualSize`	—

Event ID 10301 — Source data partition resize failed.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Source data partition resize failed. However, the partition no longer matches the original size. Moving the source replication group to failed state. 

DeviceName: %2
PartitionNumber: %3
PartitionId: %4
ExpectedSizeInBytes: %5
ActualSizeInBytes: %6

 Guidance: Ensure the source data partition matches in the intended size. You may have to remove partnership, resize data partitions, and recreate partnership.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`PartitionNumber`	—
`PartitionId`	—
`ExpectedSize`	—
`ActualSize`	—

Event ID 10302 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`PartitionNumber`	—
`PartitionId`	—
`Status`	—

Event ID 10302 — Shrinking data partition under replication is not supported.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Shrinking data partition under replication is not supported. The partition resize request failed. 

DeviceName: %2
PartitionNumber: %3
PartitionId: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`PartitionNumber`	—
`PartitionId`	—
`Status`	—

Event ID 10303 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`SourceDataPartitionSize`	—
`DestinationDataPartitionSize`	—
`PartitionId`	—

Event ID 10303 — Partition size mismatch during configuration exchange.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Partition size mismatch during configuration exchange. The destination data partition size is greater than the source data partition size. Shrinking of destination data partition under replication is not supported. The destination data partition resize request will be failed. 

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
ReplicaSetId: %6
SourceDataPartitionSize: %7
DestinationDataPartitionSize: %8

Guidance: You may have to remove partnership, match sizes of both source and destination data partitions and recreate partnership.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`ReplicaSetId`	—
`SourceDataPartitionSize`	—
`DestinationDataPartitionSize`	—
`PartitionId`	—

Event ID 10304 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`PartitionNumber`	—
`PartitionId`	—
`Status`	—

Event ID 10304 — Partition resize called on a source data partition in Storage Replica configuration failed.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Partition resize called on a source data partition in Storage Replica configuration failed.

DeviceName: %2
PartitionNumber: %3
PartitionId: %4

Guidance: Ensure there is enough storage space left for the source data partition to resize.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`PartitionNumber`	—
`PartitionId`	—
`Status`	—

Event ID 10305 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`PartitionNumber`	—
`PartitionId`	—
`Status`	—

Event ID 10305 — Attempt to shrink destination data partition.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Attempt to shrink destination data partition. Secondary shrink operation should never happen and is not supported. 

DeviceName: %2
PartitionNumber: %3
PartitionId: %4

 Guidance: Remove the partnership, ensure the source and destination data partition sizes matches and re-enable partnership to continue replication.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`PartitionNumber`	—
`PartitionId`	—
`Status`	—

Event ID 10306 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`PartitionNumber`	—
`PartitionId`	—
`Status`	—

Event ID 10306 — Attempted to resize a partition that is protected by Storage Replica.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Attempted to resize a partition that is protected by Storage Replica .

DeviceName: %2
PartitionNumber: %3
PartitionId: %4

Guidance: To grow a source data partition, set the policy on the replication group containing the data partition.

Set-SRGroup -ComputerName [ComputerName] -Name [ReplicationGroupName] -AllowVolumeResize $true

Before you grow the source data partition, ensure that the destination data partition has enough space to grow to an equal size. Shrinking of data partition protected by Storage Replica is blocked.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`PartitionNumber`	—
`PartitionId`	—
`Status`	—

Event ID 10307 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`PartitionNumber`	—
`PartitionId`	—
`Status`	—

Event ID 10307 — Attempted to resize a partition that is protected by Storage Replica.

Provider: Microsoft-Windows-StorageReplica
Channel: System

Message

Attempted to resize a partition that is protected by Storage Replica .

DeviceName: %2
PartitionNumber: %3
PartitionId: %4

Guidance: To grow a source data partition, set the policy on the replication group containing the data partition.

Set-SRGroup -ComputerName [ComputerName] -Name [ReplicationGroupName] -AllowVolumeResize $true

Before you grow the source data partition, ensure that the destination data partition has enough space to grow to an equal size. Shrinking of data partition protected by Storage Replica is blocked.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`PartitionNumber`	—
`PartitionId`	—
`Status`	—

Event ID 10310 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionNumber`	—
`PartitionStyle`	—
`PartitionOffset`	—
`PartitionLength`	—

Event ID 10310 — A non-GPT partition was detected when processing a newly arrived disk formatted with a GPT disk layout.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

A non-GPT partition was detected when processing a newly arrived disk formatted with a GPT disk layout.

DeviceName: %2
DiskId: %3
PartitionNumber: %4
PartitionStyle: %5
PartitionOffset: %6
PartitionLength: %7

Guidance: This event is triggered when a mismatch between the disk layout and the partition style is detected. In this case a non-GPT style partition has been detected on a disk with a GPT style layout. This is an unexpected condition and should be considered a configuration error. To correct the issue, the partition style should match the disk layout type and may require the disk to be reinitialized, possibly leading to data loss. All data should be backed up as necessary before taking any remedial action.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionNumber`	—
`PartitionStyle`	—
`PartitionOffset`	—
`PartitionLength`	—

Event ID 10311 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionNumber`	—
`PartitionStyle`	—
`PartitionOffset`	—
`PartitionLength`	—
`PartitionId`	—
`PartitionTypeGuid`	—
`PartitionType`	—
`PartitionNameLength`	—
`PartitionName`	—

Event ID 10311 — A GPT partition was detected when processing a newly arrived disk which is suitable for use with replication.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

A GPT partition was detected when processing a newly arrived disk which is suitable for use with replication.

DeviceName: %2
DiskId: %3
PartitionNumber: %4
PartitionStyle: %5
PartitionOffset: %6
PartitionLength: %7
PartitionId: %8
PartitionTypeGuid: %9
PartitionType: %10
PartitionName: %12

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionNumber`	—
`PartitionStyle`	—
`PartitionOffset`	—
`PartitionLength`	—
`PartitionId`	—
`PartitionTypeGuid`	—
`PartitionType`	—
`PartitionNameLength`	—
`PartitionName`	—

Event ID 10312 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionNumber`	—
`PartitionStyle`	—
`PartitionOffset`	—
`PartitionLength`	—
`PartitionId`	—
`PartitionTypeGuid`	—
`PartitionType`	—
`PartitionNameLength`	—
`PartitionName`	—

Event ID 10312 — A GPT partition was detected when processing a newly arrived disk that is not suitable for use with replication.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

A GPT partition was detected when processing a newly arrived disk that is not suitable for use with replication. This partition will be ignored.

DeviceName: %2
DiskId: %3
PartitionNumber: %4
PartitionStyle: %5
PartitionOffset: %6
PartitionLength: %7
PartitionId: %8
PartitionTypeGuid: %9
PartitionType: %10
PartitionName: %12

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionNumber`	—
`PartitionStyle`	—
`PartitionOffset`	—
`PartitionLength`	—
`PartitionId`	—
`PartitionTypeGuid`	—
`PartitionType`	—
`PartitionNameLength`	—
`PartitionName`	—

Event ID 10320 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionId`	—
`PartitionNumber`	—
`PartitionNameLength`	—
`PartitionName`	—
`PartitionState`	—
`PartitionEvent`	—
`StateMachinePhase`	—
`StateMachinePhaseStatus`	—

Event ID 10320 — Partition state current value.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Partition state current value.

DeviceName: %2
DiskId: %3
PartitionId: %4
PartitionNumber: %5
PartitionName: %7
PartitionState: %8
PartitionEvent: %9
StateMachinePhase: %10
StateMachinePhaseStatus: %11

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionId`	—
`PartitionNumber`	—
`PartitionNameLength`	—
`PartitionName`	—
`PartitionState`	—
`PartitionEvent`	—
`StateMachinePhase`	—
`StateMachinePhaseStatus`	—

Event ID 10321 — Partition state current value.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Partition state current value.

DeviceName: %2
DiskId: %3
PartitionId: %4
PartitionNumber: %5
PartitionName: %7
PartitionState: %8
PartitionEvent: %9
StateMachinePhase: %10
StateMachinePhaseStatus: %11

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionId`	—
`PartitionNumber`	—
`PartitionNameLength`	—
`PartitionName`	—
`PartitionState`	—
`PartitionEvent`	—
`StateMachinePhase`	—
`StateMachinePhaseStatus`	—

Event ID 10330 — A GPT partition was detected and prepared for replication operations.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

A GPT partition was detected and prepared for replication operations.

DeviceName: %2
DiskId: %3
PartitionNumber: %4
PartitionStyle: %5
PartitionOffset: %6
PartitionLength: %7
PartitionId: %8
PartitionTypeGuid: %9
PartitionType: %10
PartitionName: %12
PartitionState: %13

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionNumber`	—
`PartitionStyle`	—
`PartitionOffset`	—
`PartitionLength`	—
`PartitionId`	—
`PartitionTypeGuid`	—
`PartitionType`	—
`PartitionNameLength`	—
`PartitionName`	—
`PartitionState`	—
`Status`	—

Event ID 10331 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionNumber`	—
`PartitionStyle`	—
`PartitionOffset`	—
`PartitionLength`	—
`PartitionId`	—
`PartitionTypeGuid`	—
`PartitionType`	—
`PartitionNameLength`	—
`PartitionName`	—
`PartitionState`	—
`Status`	—

Event ID 10331 — A GPT partition was detected but preparation for replication operations failed.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

A GPT partition was detected but preparation for replication operations failed.

DeviceName: %2
DiskId: %3
PartitionNumber: %4
PartitionStyle: %5
PartitionOffset: %6
PartitionLength: %7
PartitionId: %8
PartitionTypeGuid: %9
PartitionType: %10
PartitionName: %12
PartitionState: %13
Status: %14

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionNumber`	—
`PartitionStyle`	—
`PartitionOffset`	—
`PartitionLength`	—
`PartitionId`	—
`PartitionTypeGuid`	—
`PartitionType`	—
`PartitionNameLength`	—
`PartitionName`	—
`PartitionState`	—
`Status`	—

Event ID 10340 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—

Event ID 10340 — IOCTL_DISK_DELETE_DRIVE_LAYOUT entry.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_DELETE_DRIVE_LAYOUT entry.

DeviceName: %2
DiskReplicationState: %3

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—

Event ID 10341 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10341 — IOCTL_DISK_DELETE_DRIVE_LAYOUT exit.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_DELETE_DRIVE_LAYOUT exit.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10342 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10342 — IOCTL_DISK_DELETE_DRIVE_LAYOUT exit.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

IOCTL_DISK_DELETE_DRIVE_LAYOUT exit.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10343 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10343 — IOCTL_DISK_DELETE_DRIVE_LAYOUT was called for a disk involved in replication and one or more partitions in the updated layout are currently in an a...

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_DELETE_DRIVE_LAYOUT was called for a disk involved in replication and one or more partitions in the updated layout are currently in an active replication configuration.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Guidance: This event occurs when an attempt is made to delete or modify one or more partitions that are currently involved in an active replication configuration. For the layout modification operation to succeed, there must be no replication configurations associated with any of the partitions being modified.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10350 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—

Event ID 10350 — IOCTL_DISK_CREATE_DISK entry.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_CREATE_DISK entry.

DeviceName: %2
DiskReplicationState: %3

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—

Event ID 10351 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10351 — IOCTL_DISK_CREATE_DISK exit.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_CREATE_DISK exit.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10352 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10352 — IOCTL_DISK_CREATE_DISK exit.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

IOCTL_DISK_CREATE_DISK exit.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10353 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10353 — IOCTL_DISK_CREATE_DISK was called for a disk involved in replication and one or more partitions in the updated layout are currently in an active re...

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_CREATE_DISK was called for a disk involved in replication and one or more partitions in the updated layout are currently in an active replication configuration.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Guidance: This event occurs when an attempt is made to delete or modify one or more partitions that are currently involved in an active replication configuration. For the layout modification operation to succeed, there must be no replication configurations associated with any of the partitions being modified.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10360 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—

Event ID 10360 — IOCTL_WVR_PARTITION_DB_CREATE entry.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_WVR_PARTITION_DB_CREATE entry.

DeviceName: %2
DiskReplicationState: %3

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—

Event ID 10361 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10361 — IOCTL_WVR_PARTITION_DB_CREATE exit.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_WVR_PARTITION_DB_CREATE exit.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10362 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10362 — IOCTL_WVR_PARTITION_DB_CREATE exit.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

IOCTL_WVR_PARTITION_DB_CREATE exit.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10370 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—

Event ID 10370 — IOCTL_WVR_PARTITION_DB_DESTROY entry.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_WVR_PARTITION_DB_DESTROY entry.

DeviceName: %2
DiskReplicationState: %3

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—

Event ID 10371 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10371 — IOCTL_WVR_PARTITION_DB_DESTROY exit.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_WVR_PARTITION_DB_DESTROY exit.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10372 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10372 — IOCTL_WVR_PARTITION_DB_DESTROY exit.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

IOCTL_WVR_PARTITION_DB_DESTROY exit.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10373 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10373 — IOCTL_WVR_PARTITION_DB_DESTROY called with the NoSafetyInterlocks option enabled.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

IOCTL_WVR_PARTITION_DB_DESTROY called with the NoSafetyInterlocks option enabled.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Guidance: The primary intended use for this option is the forcible removal of the persisted partition database for cleanup purposes. After this option is used one of the following three actions must be taken

 - the disk must be taken offline and then brought back online
 - the disk must be disabled and then re-enabled
 - the computer must be rebooted.

Failure to take one of these actions will lead to unpredictable behavior, including loss of all data on the affected disk and possibly other disks on both the local system and on remote partners.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10380 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`DiskId`	—
`Status`	—

Event ID 10380 — Storage Replica filter driver discovered a serious error with an on-disk database used to identify partitions/volumes involved in recovery and has ...

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Storage Replica filter driver discovered a serious error with an on-disk database used to identify partitions/volumes involved in recovery and has blocked write access to the affected disk device to prevent damage to data.

DeviceName: %2
DiskReplicationState: %3
Status: %5

Guidance: A serious problem has been identified with the contents of the Storage Replica partition database on the disk device. Until the problem is fixed Storage Replica will continue to block write access to the data partitions in an attempt to protect the disk against any further damage. The potential issues include internal consistency check failures, multiple instances of the database (there should be exactly one), disk block alignment issues or even corruption. Many of the potential problems can be the result of a disk based backup/restore cycle where the device onto which the backup was restored has different physical characteristics (e.g. differing physical sector sizes). If this error follows a recent restoration of a physical disk backup, verify that the physical sector size (typically either 512 bytes or 4096 bytes (4KB)) of both the original disk and the replacement disk are the same and that the replacement disk is the same size as the original or larger.

To restore write access to data partitions, the DiskPart.exe utility can be used to delete the Storage Replica Partition (GPT Partition Type Id 558d43c5-a1ac-43c0-aac8-d1472b2923d1) however doing so will prevent the disk being involved in replication until the replication configuration is repaired. After removing the Storage Replica Partition, the disk should be disabled and then re-enabled (or detached/re-attached) after which the disk should be accessible as normal.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`DiskId`	—
`Status`	—

Event ID 10381 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10381 — Storage Replica filter driver discovered a serious problem with the existing on-disk partition layout (missing the Microsoft Reserved Partition) wh...

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Storage Replica filter driver discovered a serious problem with the existing on-disk partition layout (missing the Microsoft Reserved Partition) when attempting to prepare one or more partitions on a disk for replication.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Guidance: A serious problem has been identified with the contents of the disk partitioning layout resulting from a missing Microsoft Reserved (MSR) partition. Storage Replica requires that the disk have an MSR partition prior to the creation of the Storage Replica partition database. Without the MSR partition, Storage Replica cannot create the Storage Replica partition database which prevents the disk, or any of the partitions or volumes contained by the disk, being involved in replication. To correct the problem, the MSR partition must be created on the disk. This is typically achieved by (re-)initializing the disk or using the Diskpart.exe utility. Note that initializing the disk will involve the destruction of all the contained partitions and volumes on that disk. To use the disk for Storage Replica, the disk must have been initialized with the GPT layout. Once this has been done, the required partitions and volumes can be created, and the partitions and/or volumes can be provisioned for replication as normal. Until this problem is corrected, this disk cannot be used for replication.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10382 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10382 — Storage Replica filter driver discovered an incompletely initialized Storage Replica partition database when attempting to provision one or more pa...

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Storage Replica filter driver discovered an incompletely initialized Storage Replica partition database when attempting to provision one or more partitions on a disk.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Guidance: Storage Replica requires that a properly initialized partition database be present on a disk prior to any of the partitions on that disk becoming involved in replication. Storage Replica will attempt to automatically complete the Storage Replica partition database initialization after which the provisioning action can proceed. If no further errors occur, the automatic repair was successful and no action to repair the partition database is required.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10383 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`PartitionId`	—
`Status`	—

Event ID 10383 — Filter driver discovered an improper disk layout where a GPT initialized disk contains one or more non-GPT style partitions.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Filter driver discovered an improper disk layout where a GPT initialized disk contains one or more non-GPT style partitions.

DeviceName: %2
DiskReplicationState: %3
Status: %4
PartitionId: %5

Guidance: Storage Replica requires that a disk be initialized with a GPT style layout and that all the contained partition have a matching layout style. To correct this problem all the affected partitions should be deleted and then re-created, after which the partitions and/or volumes can be provisioned for replication as normal. Until the problem is fixed Storage Replica will not make any changes to the provisioning state of the disk and will be unable to begin replication for any of the partitions or volumes on that disk.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`PartitionId`	—
`Status`	—

Event ID 10384 — Filter driver was unable to bring a partition online.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Filter driver was unable to bring a partition online.

DeviceName: %2
DiskReplicationState: %3
PartitionId: %4
Status: %5

Guidance: Until the problem is fixed, the partition and any volume it contains will not be available for use.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`PartitionId`	—
`Status`	—

Event ID 10385 — Filter driver was unable to take a partition offline.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Filter driver was unable to take a partition offline.

DeviceName: %2
DiskReplicationState: %3
PartitionId: %4
Status: %5

Guidance: Until the problem is fixed, the partition and any volume it contains may cause issues either moving the parent to another cluster node or changing the replication role of partitions involved in replication.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`PartitionId`	—
`Status`	—

Event ID 10386 — Filter driver was unable to remove a partition from replication.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Filter driver was unable to remove a partition from replication.

DeviceName: %2
DiskReplicationState: %3
PartitionId: %4
Status: %5

Guidance: Until the problem is fixed, the partition and any volume it contains may cause issues with either moving the parent to another cluster node or changing the replication role of partitions involved in replication.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`PartitionId`	—
`Status`	—

Event ID 10387 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`PartitionId`	—
`Status`	—

Event ID 10387 — Storage Replica filter driver discovered a serious error with a mismatch between the database used to identify partitions/volumes involved in recov...

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Storage Replica filter driver discovered a serious error with a mismatch between the database used to identify partitions/volumes involved in recovery and some internal state used to control access to a partition.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Guidance: A serious problem has been identified with multiple pieces of internal state and potentially the contents of the Storage Replica partition database on the disk device. It may be possible to reconcile the internal state by disabling and then re-enabling (or detaching/re-attaching) the disk device containing the affected partition. If that does not succeed in clearing the mismatch, the system should be restarted.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`PartitionId`	—
`Status`	—

Event ID 10388 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10388 — Storage Replica filter driver could not find a Storage Replica partition database on the disk being discovered or brought online.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Storage Replica filter driver could not find a Storage Replica partition database on the disk being discovered or brought online.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Guidance: Storage Replica records asserted control information about replicated partition on the disk containing those partitions in a special partition. If that special partition is not present on the disk then none of the partitions on that disk are involved in replication.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10389 — The replica partnership is synchronized but the attempt to update the on-disk metadata failed.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

The replica partnership is synchronized but the attempt to update the on-disk metadata failed.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
PartitionId: %6
ReplicaId: %7
Status: %8

Guidance: This is not a fatal error.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 10390 — The replica partnership is no longer synchronized but the attempt to update the on-disk metadata failed.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

The replica partnership is no longer synchronized but the attempt to update the on-disk metadata failed.

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
PartitionId: %6
ReplicaId: %7
Status: %8

Guidance: This is not a fatal error.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—
`Status`	—

Event ID 10400 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—

Event ID 10400 — IOCTL_DISK_GET_CLUSTER_INFO entry.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_GET_CLUSTER_INFO entry.

DeviceName: %2
DiskReplicationState: %3

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—

Event ID 10401 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10401 — IOCTL_DISK_GET_CLUSTER_INFO exit.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_GET_CLUSTER_INFO exit.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10402 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10402 — IOCTL_DISK_GET_CLUSTER_INFO exit.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_GET_CLUSTER_INFO exit.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10403 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`ValidMask`	—
`Flags`	—
`Status`	—

Event ID 10403 — IOCTL_DISK_GET_CLUSTER_INFO request completed.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_GET_CLUSTER_INFO request completed.

DeviceName: %2
DiskReplicationState: %3
ValidMask: %4
Flags: %5
Status: %6

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`ValidMask`	—
`Flags`	—
`Status`	—

Event ID 10410 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—

Event ID 10410 — IOCTL_DISK_SET_CLUSTER_INFO entry.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_SET_CLUSTER_INFO entry.

DeviceName: %2
DiskReplicationState: %3

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—

Event ID 10411 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10411 — IOCTL_DISK_SET_CLUSTER_INFO exit.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_SET_CLUSTER_INFO exit.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10412 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10412 — IOCTL_DISK_SET_CLUSTER_INFO exit.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_SET_CLUSTER_INFO exit.

DeviceName: %2
DiskReplicationState: %3
Status: %4

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`Status`	—

Event ID 10413 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`ValidMask`	—
`Flags`	—
`Status`	—

Event ID 10413 — IOCTL_DISK_SET_CLUSTER_INFO request completed.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

IOCTL_DISK_SET_CLUSTER_INFO request completed.

DeviceName: %2
DiskReplicationState: %3
ValidMask: %4
Flags: %5
Status: %6

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`ValidMask`	—
`Flags`	—
`Status`	—

Event ID 10420 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`PartitionId`	—
`ReplicationGroupId`	—
`Status`	—

Event ID 10420 — Filter driver configured the partition to be available for replication operations once the remaining configuration steps are completed.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Filter driver configured the partition to be available for replication operations once the remaining configuration steps are completed.

DeviceName: %2
DiskReplicationState: %3
PartitionId: %4
ReplicationGroupId: %5
Status: %6

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`PartitionId`	—
`ReplicationGroupId`	—
`Status`	—

Event ID 10421 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`PartitionId`	—
`ReplicationGroupId`	—
`Status`	—

Event ID 10421 — Filter driver attempted to configure the partition to be available for replication operations but was unable to complete the necessary steps.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Filter driver attempted to configure the partition to be available for replication operations but was unable to complete the necessary steps.

DeviceName: %2
DiskReplicationState: %3
PartitionId: %4
ReplicationGroupId: %5
Status: %6

Guidance: Ensure the disk is online, writeable, and is initialised with a GPT style layout.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`PartitionId`	—
`ReplicationGroupId`	—
`Status`	—

Event ID 10422 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`PartitionId`	—
`ReplicationGroupId`	—
`Status`	—

Event ID 10422 — Filter driver was unable to locate the specified partition.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Filter driver was unable to locate the specified partition.

PartitionId: %1
ReplicationGroupId: %2
Status: %3

Fields

Name	Description
`PartitionId`	—
`ReplicationGroupId`	—
`Status`	—

Event ID 10430 — Filter driver has configured the partition as no longer eligible for replication operations once the remaining configuration steps are completed.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Filter driver has configured the partition as no longer eligible for replication operations once the remaining configuration steps are completed.

DeviceName: %2
DiskReplicationState: %3
PartitionId: %4
ReplicationGroupId: %5
Status: %6

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

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`PartitionId`	—
`ReplicationGroupId`	—
`Status`	—

Event ID 10431 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`PartitionId`	—
`ReplicationGroupId`	—
`Status`	—

Event ID 10431 — Filter driver attempted to configure the partition to be available for regular (non-replication related) operations but was unable to complete the ...

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Filter driver attempted to configure the partition to be available for regular (non-replication related) operations but was unable to complete the necessary steps.

DeviceName: %2
DiskReplicationState: %3
PartitionId: %4
ReplicationGroupId: %5
Status: %6

Guidance: Ensure the disk is online, writeable, and is initialised with a GPT style layout.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskReplicationState`	—
`PartitionId`	—
`ReplicationGroupId`	—
`Status`	—

Event ID 10432 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`PartitionId`	—
`ReplicationGroupId`	—
`Status`	—

Event ID 10432 — Filter driver was unable to locate the specified partition.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Filter driver was unable to locate the specified partition.

PartitionId: %1
ReplicationGroupId: %2
Status: %3

Fields

Name	Description
`PartitionId`	—
`ReplicationGroupId`	—
`Status`	—

Event ID 10440 — A partition state change occured which caused the partition GPT attributes to be updated to mark the partition as hidden.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

A partition state change occured which caused the partition GPT attributes to be updated to mark the partition as hidden.

DeviceName: %2
DiskId: %3
PartitionId: %4
PartitionNumber: %5
PartitionState: %6

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionId`	—
`PartitionNumber`	—
`PartitionState`	—
`Status`	—

Event ID 10441 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionId`	—
`PartitionNumber`	—
`PartitionState`	—
`Status`	—

Event ID 10441 — A partition state change occured where an attempt to update the partition GPT attributes to mark the partition as hidden failed.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

A partition state change occured where an attempt to update the partition GPT attributes to mark the partition as hidden failed.

DeviceName: %2
DiskId: %3
PartitionId: %4
PartitionNumber: %5
PartitionState: %6
Status: %7

Guidance: This event is triggered during a partition state change such as provisioning, stopping replication, or a role switch, when the driver is unable to update the GPT attributes for the partition to mark the partition as hidden. The Diskpart.exe utility can be used to correct this condition.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionId`	—
`PartitionNumber`	—
`PartitionState`	—
`Status`	—

Event ID 10442 — A partition state change occured which caused the partition GPT attributes to be updated to mark the partition as visible.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

A partition state change occured which caused the partition GPT attributes to be updated to mark the partition as visible.

DeviceName: %2
DiskId: %3
PartitionId: %4
PartitionNumber: %5
PartitionState: %6

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionId`	—
`PartitionNumber`	—
`PartitionState`	—
`Status`	—

Event ID 10443 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionId`	—
`PartitionNumber`	—
`PartitionState`	—
`Status`	—

Event ID 10443 — A partition state change occured where an attempt to update the partition GPT attributes to mark the partition as visible failed.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

A partition state change occured where an attempt to update the partition GPT attributes to mark the partition as visible failed.

DeviceName: %2
DiskId: %3
PartitionId: %4
PartitionNumber: %5
PartitionState: %6
Status: %7

Guidance: This event is triggered during a partition state change such as de-provisioning, starting replication, or a role switch when the driver is unable to update the GPT attributes for the partition to mark the partition as visible. The Diskpart.exe utility can be used to correct this condition.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionId`	—
`PartitionNumber`	—
`PartitionState`	—
`Status`	—

Event ID 10444 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionId`	—
`PartitionNumber`	—
`PartitionState`	—
`Status`	—

Event ID 10444 — Locking the volume for partition surfacing has failed.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Locking the volume for partition surfacing has failed.

DeviceName: %2
DiskId: %3
PartitionId: %4
PartitionNumber: %5
PartitionState: %6
Status: %7

Guidance: This event is triggered when Storage Replica is not able to lock the replicated partition in order to set GPT_BASIC_DATA_ATTRIBUTE_HIDDEN flag, this is not a fatal error if the status code is STATUS_ACCESS_DENIED

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionId`	—
`PartitionNumber`	—
`PartitionState`	—
`Status`	—

Event ID 10445 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionId`	—
`PartitionNumber`	—
`PartitionState`	—
`Status`	—

Event ID 10445 — Locking the volume for partition submerging has failed.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Locking the volume for partition submerging has failed.

DeviceName: %2
DiskId: %3
PartitionId: %4
PartitionNumber: %5
PartitionState: %6
Status: %7

Guidance: This event is triggered when Storage Replica is not able to lock the replicated partition in order to clear its GPT_BASIC_DATA_ATTRIBUTE_HIDDEN flag, this is not a fatal error if the status code is STATUS_ACCESS_DENIED

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionId`	—
`PartitionNumber`	—
`PartitionState`	—
`Status`	—

Event ID 10446 — A partition state change occured which caused volume dismount on the replicated partition.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

A partition state change occured which caused volume dismount on the replicated partition.

DeviceName: %2
DiskId: %3
PartitionId: %4
PartitionNumber: %5
PartitionState: %6

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionId`	—
`PartitionNumber`	—
`PartitionState`	—
`Status`	—

Event ID 10447 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionId`	—
`PartitionNumber`	—
`PartitionState`	—
`Status`	—

Event ID 10447 — A partition state change occured where an attempt to dismount the volume on the replicated partition failed.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

A partition state change occured where an attempt to dismount the volume on the replicated partition failed.

DeviceName: %2
DiskId: %3
PartitionId: %4
PartitionNumber: %5
PartitionState: %6
Status: %7

Guidance: This event is triggered during a partition state change such as provisioning, stopping replication, or a role switch, when the driver is unable to dismount volume on the partition.

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionId`	—
`PartitionNumber`	—
`PartitionState`	—
`Status`	—

Event ID 10448 — Storage Replica has failed an application IO.

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Message

Storage Replica has failed an application IO.

DeviceName: %2
DiskId: %3
PartitionId: %4
PartitionNumber: %5
PartitionState: %6
WriteIO:%7
Status: %8%

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`DiskId`	—
`PartitionId`	—
`PartitionNumber`	—
`PartitionState`	—
`WriteIO`	—
`Status`	—

Event ID 11001 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`PartitionId`	—
`TransactionId`	—
`IoCount`	—
`IoSize`	—
`IoCost`	—
`Status`	—

Event ID 11001 — Submitting an I/O context for flush failed.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Submitting an I/O context for flush failed.
I/O partition: %1
TransactionId: %2
I/O count: %3
I/O size: %4
I/O Cost: %5
Status: %6

Fields

Name	Description
`PartitionId`	—
`TransactionId`	—
`IoCount`	—
`IoSize`	—
`IoCost`	—
`Status`	—

Event ID 11002 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`PartitionId`	—
`TransactionId`	—
`IoCount`	—
`IoSize`	—
`IoCost`	—
`Status`	—

Event ID 11002 — Submitting an I/O context for flush succeeded.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Submitting an I/O context for flush succeeded.
I/O partition: %1
TransactionId: %2
I/O count: %3
I/O size: %4
I/O Cost: %5
Status: %6

Fields

Name	Description
`PartitionId`	—
`TransactionId`	—
`IoCount`	—
`IoSize`	—
`IoCost`	—
`Status`	—

Event ID 11003 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`PartitionId`	—
`TransactionId`	—
`IoCount`	—
`IoSize`	—
`IoCost`	—
`Status`	—

Event ID 11003 — Flush for an I/O context completed.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Flush for an I/O context completed.
I/O partition: %1
TransactionId: %2
I/O count: %3
I/O size: %4
I/O Cost: %5
Status: %6

Fields

Name	Description
`PartitionId`	—
`TransactionId`	—
`IoCount`	—
`IoSize`	—
`IoCost`	—
`Status`	—

Event ID 11004 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`PartitionId`	—
`TransactionId`	—
`IoCount`	—
`IoSize`	—
`IoCost`	—

Event ID 11004 — An I/O context overlaps with an in-flight I/O, it will be flushed when the conflicting I/O completes.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

An I/O context overlaps with an in-flight I/O, it will be flushed when the conflicting I/O completes.
I/O partition: %1
TransactionId: %2
I/O count: %3
I/O size: %4
I/O Cost: %5%

Fields

Name	Description
`PartitionId`	—
`TransactionId`	—
`IoCount`	—
`IoSize`	—
`IoCost`	—

Event ID 11005 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`PartitionId`	—
`TransactionId`	—
`IoCount`	—
`IoSize`	—
`IoCost`	—

Event ID 11005 — Flush for an I/O context is resumed as the conflicting in-flight I/O has completed.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

Flush for an I/O context is resumed as the conflicting in-flight I/O has completed.
I/O partition: %1
TransactionId: %2
I/O count: %3
I/O size: %4
I/O Cost: %5%

Fields

Name	Description
`PartitionId`	—
`TransactionId`	—
`IoCount`	—
`IoSize`	—
`IoCost`	—

Event ID 11006 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—

Event ID 11006 — A flush dequeue thread is started, replica information: ReplicationGroupName: %2 ReplicationGroupId: %3 ReplicaName: %5 PartitionId: %6 ReplicaId: %7.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

A flush dequeue thread is started, replica information:

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
PartitionId: %6
ReplicaId: %7

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—

Event ID 11007 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—

Event ID 11007 — A flush dequeue thread is stopped as the flush submit queue is empty, replica information: ReplicationGroupName: %2 ReplicationGroupId: %3 ReplicaN...

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

A flush dequeue thread is stopped as the flush submit queue is empty, replica information:

ReplicationGroupName: %2
ReplicationGroupId: %3
ReplicaName: %5
PartitionId: %6
ReplicaId: %7

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`ReplicaNameLength`	—
`ReplicaName`	—
`PartitionId`	—
`ReplicaSetId`	—

Event ID 11020 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—

Event ID 11020 — RegisterDevice driver routine called.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

RegisterDevice driver routine called.

PhysicalDeviceName: %2
TargetDeviceName: %4

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—

Event ID 11021 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`Status`	—

Event ID 11021 — RegisterDevice failed to pre-allocate the disk update context required for device removal.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

RegisterDevice failed to pre-allocate the disk update context required for device removal.

PhysicalDeviceName: %2
TargetDeviceName: %4
Status: %5

Guidance: When processing a disk device arrival, Storage Replica must be able to allocate the resources (such as memory) required to properly manage the life-time of the device. If any of those allocations fail then the device cannot be started. Ensure there is some free memory, detach and then re-attach the disk device to resume device arrival processing

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`Status`	—

Event ID 11030 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`Status`	—

Event ID 11030 — RegisterDevice driver routine completed.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

RegisterDevice driver routine completed.

PhysicalDeviceName: %2
TargetDeviceName: %4
Status: %5

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`Status`	—

Event ID 11040 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—

Event ID 11040 — RegisterDevice driver routine identified target device.

Provider: Microsoft-Windows-StorageReplica
Channel: Debug

Message

RegisterDevice driver routine identified target device.

PhysicalDeviceName: %2
TargetDeviceName: %4

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—

Event ID 11100 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`Operation`	—
`Status`	—

Event ID 11100 — Driver device operation request failure.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Driver device operation request failure.

PhysicalDeviceName: %2
TargetDeviceName: %4
Operation: %5
Status: %6

Fields

Name	Description
`PhysicalDeviceNameLength`	—
`PhysicalDeviceName`	—
`TargetDeviceNameLength`	—
`TargetDeviceName`	—
`Operation`	—
`Status`	—

Event ID 12000 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`Status`	—

Event ID 12000 — Filter driver failed to contact Storage Replica user mode service to update the health status of the replication group.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Filter driver failed to contact Storage Replica user mode service to update the health status of the replication group.

ReplicationGroupName: %2
ReplicationGroupId: %3
Status: %4

Guidance: Make sure that the Storage Replica service is running. If the replication group is configured on Failover Cluster, make sure that the cluster service is running and in a healthy state.

Fields

Name	Description
`ReplicationGroupNameLength`	—
`ReplicationGroupName`	—
`ReplicationGroupId`	—
`Status`	—

Event ID 12100 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`PartitionNumber`	—
`PartitionId`	—
`Status`	—

Event ID 12100 — Partition size mismatch with the corresponding data partition on source replication group resulted in a resize attempt of the following destination...

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Partition size mismatch with the corresponding data partition on source replication group resulted in a resize attempt of the following destination data partition. However, the resize operation failed since partition has been mounted. 

DeviceName: %2
PartitionNumber: %3
PartitionId: %4

Guidance: Please dismount replication group.

Dismount-SRDestination -ComputerName [ComputerName] -Name [ReplicationGroupName].

Fields

Name	Description
`DeviceNameLength`	—
`DeviceName`	—
`PartitionNumber`	—
`PartitionId`	—
`Status`	—

Event ID 12200 —

Provider: Microsoft-Windows-StorageReplica
Channel: Operational

Fields

Name	Description
`Status`	—

Event ID 12200 — Storage Replica Windows Server Standard Edition requirement violated.

Provider: Microsoft-Windows-StorageReplica
Channel: Admin

Message

Storage Replica Windows Server Standard Edition requirement violated. 

Status: %1

Fields

Name	Description
`Status`	—