The virtual environment storage status has changed to '<details.Status>'

The creation of Rapid Appliance Self Recovery USB key at path '<details.TargetPath>' for disk <details.TargetDisk> has been canceled

The creation of Rapid Appliance Self Recovery USB key at path '<details.TargetPath>' for disk <details.TargetDisk> has failed

The creation of Rapid Appliance Self Recovery USB key at path '<details.TargetPath>' for disk <details.TargetDisk> has finished successfully; now use the Windows "Eject Drive" function, physically remove the drive and then store it in a safe location

The creation of Rapid Appliance Self Recovery USB key has started at path '<details.TargetPath>' for disk <details.TargetDisk>

Download of the package file <details.ArchiveFileName> has been canceled

Download of the package file <details.ArchiveFileName> has failed

Download of the package file <details.ArchiveFileName> has finished

Download of the package file <details.ArchiveFileName> has started

<eventMessage>

Account information for hypervisor '<details.HostName>' has been successfully updated

Storage location '<details.StorageLocationName>' has been successfully removed

Storage location '<details.StorageLocationName>' has been successfully updated

<eventMessage>

<eventMessage>

<eventMessage>

<details.Message>

<details.Message>

Windows Backup Policy has been configured. Configuration schedule: <details.EventMessage>

Windows Backup Policy configuration has been deleted

Cannot enable application support for the machine '<details.AgentName>'. The feature is only available for Windows machines.

Checking of '<details.ArchivePhysicalLocation>' has been canceled

Checking of '<details.ArchivePhysicalLocation>' has failed

Checking of '<details.ArchivePhysicalLocation>' has finished

Checking of '<details.ArchivePhysicalLocation>' has started

A <details.ArchiveTypeFriendlyName> backup of protected machine '<agentName>' has been canceled

A <details.ArchiveTypeFriendlyName> backup of the protected machine '<agentName>' has failed.

A <details.ArchiveTypeFriendlyName> backup of the protected machine '<agentName>' has finished

A <details.ArchiveTypeFriendlyName> backup of the protected machine '<agentName>' has started

Import of the recovery points for protected machine '<agentName>' from an archive has been canceled

Import of the recovery points for protected machine '<agentName>' from an archive has failed.
<details.ImportFailureReason>

Import of the recovery points for protected machine '<agentName>' from an archive has finished

Cannot import the archive to the selected repository. Recovery points for '<agentName>' are already present in the '<repositoryName>'

Archive import has been skipped because all volume images are already present

Import of the recovery points for protected machine '<agentName>' from an archive has started

The safe data storage option has been ignored for <agentProductName> '<details.AgentDisplayName>'due to the presence of the recovery points.

The attachability check on '<agentName>' has been cancelled

The attachability check failed on '<agentName>'.

The attachability check on '<agentName>' has finished

Nightly attachability check for '<agentName>' has been skipped. Reason: <details.SkipReason>

Starting the attachability check on '<agentName>'

The <details.JobType> has been canceled

Attachability check configuration has been changed according to new license constraints. Please contact your account manager for more information.

The <details.JobType> has failed.

The <details.JobType> has finished

One or more SQL Server databases failed the nightly attachability check

The <details.JobType> cannot be started. Reason: <details.Reason>

The <details.JobType> has been skipped. Reason: <details.Reason>

The <details.JobType> has started

Attachability check of SQL database '<details.DatabaseName>' for SQL Server instance '<details.InstanceName>' for the recovery point '<details.RecoveryPointName>' has been canceled

Attachability check of SQL database '<details.DatabaseName>' for SQL Server instance '<details.InstanceName>' for the recovery point '<details.RecoveryPointName>' has failed.

Successfully finished attachability check of SQL database '<details.DatabaseName>' for SQL Server instance '<details.InstanceName>' for the recovery point '<details.RecoveryPointName>'

Skipped attachability check of SQL database '<details.DatabaseName>' for SQL Server instance '<details.InstanceName>' for the recovery point '<details.RecoveryPointName>'. Reason: <details.SkipReason>

Started attachability check of SQL database '<details.DatabaseName>' for SQL Server instance '<details.InstanceName>' for the recovery point '<details.RecoveryPointName>'

Attachability check of the recovery point '<details.RecoveryPointName>' has been canceled

Failed attachability check of the recovery point '<details.RecoveryPointName>'.

Finished attachability check of the recovery point '<details.RecoveryPointName>'

Attachability check of the recovery point '<details.RecoveryPointName>' has been skipped. Reason: <details.SkipReason>

Started the attachability check for the recovery point '<details.RecoveryPointName>'

A scheduled report "<details.ConfigurationName>" has been added

Scheduled report  "<details.ConfigurationName>" configuration has been changed

Scheduled report  "<details.ConfigurationName>" has been deleted

Generating the scheduled report '<details.ConfigurationName>' has failed

Scheduled report  "<details.ConfigurationName>" has been paused

Scheduled report  "<details.ConfigurationName>" has been resumed

Scheduled report '<details.ConfigurationName>' has  failed while sending by email

Scheduled report '<details.ConfigurationName>' has been sent by email

Scheduled report '<details.ConfigurationName>' has failed while saving to file

Scheduled report '<details.ConfigurationName>' has been saved to file

The update to the version <details.AvailableVersion> has been canceled

The update to the version <details.AvailableVersion> has failed

The update to the version <details.AvailableVersion> has finished

The new version <details.AvailableVersion> is found and available for update

Restarting <coreProductName> service. All active jobs will be canceled.

Update to the version <details.AvailableVersion> has started

Archive repository '<details.RepositoryName>' was created

Archive repository '<details.RepositoryName>' was deleted

Archive repository '<details.RepositoryName>' was mounted

Archive repository '<details.RepositoryName>' was unmounted

A Boot CD '<details.FilePath>' has been cancelled

The Boot CD '<details.FilePath>' has been created 

The creation of a Boot CD on '<details.FilePath>' has started

The Boot CD '<details.FilePath>' has been deleted

The Boot CD '<details.FilePath>' creation has failed

The deletion of temporary files in '<details.CurrentTemporaryPath>' has been canceled. Please, take into account that a new attempt to clean up this path will be made after the next Boot CD creation. The related Boot CD: <details.BootCdFilePath>

The temporary files in '<details.CurrentTemporaryPath>' have been removed successfully. The related Boot CD: <details.BootCdFilePath>

The deletion of temporary files in '<details.CurrentTemporaryPath>' has failed. Please, take into account that a new attempt to clean up this path will be made after the next Boot CD creation. The related Boot CD: <details.BootCdFilePath>

The deletion of temporary files in '<details.CurrentTemporaryPath>' has started. The related Boot CD: <details.BootCdFilePath>

Start cloud replication job of '<agentName>' has failed.

Cloud account configuration was modified 

Cloud Configuration has been changed

Deployment of '<details.VirtualMachineNamesSummary>' virtual machine(s) to <details.CloudType> cloud has been canceled

Failed to enqueue deployment of a cloud virtual machine '<details.VirtualMachineNamesSummary>' due to following error: <details.ErrorDetails.Message>.

Deployment of '<details.VirtualMachineNamesSummary>' virtual machine(s) to <details.CloudType> cloud has failed

Deployment of '<details.VirtualMachineNamesSummary>' virtual machine to <details.CloudType> cloud has been queued.

Deployment of '<details.VirtualMachineNamesSummary>' virtual machine(s) to <details.CloudType> cloud has started

Deployment of '<details.VirtualMachineNamesSummary>' virtual machine(s) to <details.CloudType> cloud has succeeded

<agentProductName> '<details.ClusterNodeName>' has been converted to the cluster  <details.ClusterName> node

The Cluster '<details.ClusterName>' has been protected with '<details.ProtectedNodesCount>' node(s)

Protection of the cluster '<details.ClusterName>' has failed

The Cluster Node '<details.ClusterNodeName>' has been converted to <agentProductName>

Protection of the cluster node '<details.ClusterNodeName>' from the cluster '<details.ClusterName>' has failed

The configuration backup has failed.
Target location(s): <details.BackupPath>.
Error: <details.ErrorMessage>

The configuration backup has been skipped: <details.ErrorMessage>

The configuration backup has been successfully written to <details.BackupPath>

<coreProductName> configuration restore failed

Restoring configuration of service '<details.ServiceName>'

<coreProductName> configuration restore has started

<coreProductName> configuration has been restored successfully and the <coreProductName> service should be restarted to fully apply these changes

<coreProductName> configuration was restored successfully

Failed to restore <details.ServiceName> configuration due to following error: <details.ErrorDetails.Message>

Localization for <coreProductName>  has been changed.

The <coreProductName> service on <hostName> has started

The <coreProductName> service on <hostName> is stopping due to a service shutdown command

The <coreProductName> service on <hostName> is stopping due to a serious error

The <coreProductName> service on <hostName> was not shut down cleanly. The system is running checks to ensure the data integrity.

Settings for <coreProductName> have been changed.

Account with user name "<details.UserName>" and description "<details.AccountDescription>" has been created

Account with user name "<details.UserName>" and description "<details.AccountDescription>" has been removed

Account with user name "<details.SourceAccountUserName>" and description "<details.SourceAccountDescription>" has been merged with account with user name "<details.TargetAccountUserName>" and description "<details.TargetAccountDescription>"

Events, alerts, reports and background jobs older than <details.OlderThen> were deleted from database

Deduplication cache initialization on <details.CoreDisplayName> has failed. Ensure that dedupe cache files <details.DedupeCachePrimaryPath>, <details.DedupeCacheSecondaryPath> are available and there is enough free space on <details.TargetDiskName>. The required storage space is <details.RequiredStorageSpace>

<details.JobType> operation on <details.CoreDisplayName> has finished

<details.JobType> operation on <details.CoreDisplayName> has failed. Ensure that there is enough free space on <details.TargetDiskName>. The required storage space is <details.RequiredStorageSpace>

<details.JobType> operation on <details.CoreDisplayName> has started

Existing repositories were added

Recovery points of <details.AgentDisplayName> are present in multiple repositories: <details.RepositoryNames>. This configuration is not supported. Please contact support to resolve the issue

Failed to open the existent repository '<details.RepositoryName>' because its specifications contain invalid metadata or/and data paths

Overlapped records have been found in '<details.RepositoryName>'

Repository cache parameters have been set.

A checksum mismatch was detected on repository '<details.RepositoryName>'. The error occurred while performing a <if(details.WasRawOperation)>raw <endif><if(details.WasReadOperation)>read<else>write<endif> operation on '<details.VolumeImageDisplayName>'<if(!details.WasRawOperation)> at byte offset <details.ByteOffset> with a byte length <details.ByteLength><endif>. The checksum mismatch was detected on record index <details.RecordIndex>. This may indicate corruption in the recovery point.

New '<details.RepositoryName>' location has been added

The settings for repository '<details.RepositoryName>' have been changed

The repository '<details.RepositoryName>' was deleted

An error occurred when deleting the file <details.FileId>

The file specification for repository <details.RepositoryName> has been changed

The Repository '<details.RepositoryName>' is <details.PercentFull>% full.

The '<details.RepositoryName>' repository contains historical data that is no longer needed. Refer to the log files for more information and contact the Rapid Recovery Support team for additional assistance in cleaning up the repository.

The <details.JobType> has been canceled for a repository '<details.RepositoryName>'.

The <details.JobType> has failed for a repository '<details.RepositoryName>'.

The <details.JobType> has started for a repository '<details.RepositoryName>'.

The <details.JobType> has finished for a repository '<details.RepositoryName>'.

The Repository Service configuration has been changed

The repository '<details.RepositoryName>' is not available

An error occurred when deleting the file version <details.VersionNumber>

<agentProductName> mountability check configuration has been changed according to new license constraints. Please contact your account manager for more information.

Exchange server settings for the <agentProductName> '<agentName>' have been set

Export Configuration for protected machine '<agentName>' has been changed

Export Configuration for <agentProductName> '<agentName>' has been deleted

Export Configuration for <agentProductName> '<agentName>' has been changed according to new license constraints. Please contact your account manager for more information.

Export Configuration for protected machine '<agentName>' has been set

The export of '<agentName>' to <details.ExportTargetDescription> has been canceled

Export of '<details.AgentDisplayName>' to <details.ExportTargetDescription> has been cancelled, but wasn't cleaned up properly. Reason: <details.ErrorMessage>

The export of '<agentName>' to <details.ExportTargetDescription> cannot start because the chain of RP is not full

Failed to enqueue continuous export of '<details.AgentDisplayName>' to <details.ExportTargetDescription>. Reason: <details.ErrorMessage>

The export of '<details.AgentDisplayName>' to <details.ExportTargetDescription> has failed.

The export of '<agentName>' to <details.ExportTargetDescription> has finished

Export of '<agentName>' to <details.ExportTargetDescription> has been queued

The export of '<agentName>' to <details.ExportTargetDescription> has started

<details.Message>

<details.Message>

Restoring files has been canceled

Restoring files has failed

Restoring files has started

Restoring files has been succeeded

File search has been canceled

One of child jobs has failed during file search

File search has failed

Volumes <details.VolumeNames> have file systems that are not supported by the OS. A special driver is needed, otherwise search can fail or ignore these volumes

Stopping file search because it yields too many results

Search results have been found

File search has started

File search has succeeded

'<details.AgentName>' has one or more cloned disk. See summary tab.

Registry clean for '<details.AgentName>' has been skipped. See summary tab.

<agentProductName> is unreachable on Hyper-V host '<details.AgentName>'.

Node for Hyper-V cluster '<details.AgentName>' is not protected. Please see summary tab of the protected Hyper-V cluster for details.

Hyper-V virtual machine '<details.AgentName>' is corrupted.

VSS has failed on '<details.AgentName>'Hyper-V virtual machine. Data corruption may occur.

Hyper-V VSS Writer is missing on Hyper-V Server

<coreProductName> has detected that machine '<details.AgentName>' is not protected which prevents the transfer of new backups for virtual disks located on this machine. To continue backing up please protect '<details.AgentName>'.

A background job of the type '<details.JobType>', summary '<details.JobSummary>', was canceled

Failed to cancel a background job of type <details.JobType>. Job summary: <details.JobSummary>

Background job of type <details.JobType> does not support cancellation. Job summary: <details.JobSummary>

A background job of type '<details.JobType>', summary '<details.JobSummary>', has completed

A background job of type '<details.JobType>', summary '<details.JobSummary>', has been delayed.

A background job of type '<details.JobType>', summary '<details.JobSummary>', has failed.

<details.JobName> has failed to start: <details.ErrorMessage>

A background job of type '<details.JobType>', summary '<details.JobSummary>', has been put in queue.

Background job settings for '<details.JobType>' have been updated

The task scheduler on this <coreProductName> has been resumed

The task scheduler on this <coreProductName> has been suspended

A background job of type '<details.JobType>', summary '<details.JobSummary>', has started

The snapshots for '<agentName>' have been resumed on the license portal.

The snapshots for '<agentName>' have been paused on the license portal. To continue backing up this machine, please resume snapshots on the 'Machines' tab or log into the license portal.

License state has been updated for one or more <agentProductNamePlural>

Attention, your capacity limit has been exceeded by <details.CapacityExceededLimitPercent>%! <productName> is no longer protecting your machines with new snapshots. Please contact your Account Manager to add additional capacity.

Congratulations, your company is still growing! Your capacity limit has been exceeded, and new <productName> snapshots will be disabled soon. Please contact your Account Manager to add additional capacity.

Congratulations, your company is growing! We noticed that you have reached <details.CapacityExceededLimitPercent>% of your licensed capacity. Now is a great time to ensure the continuity of your data protection by evaluating your capacity limits.

The <coreProductName> failed to contact the License Portal

License constraints have been changed. Please contact your account manager for more information.

The License Key has been changed

The License Portal has been contacted

Privacy policy has been changed to '<details.PrivacyPolicy>' state

Product name has been changed

Transfer for '<agentName>' blocked due to an exceeded repository used space limit

Transfer for '<agentName>' blocked due to VM only license restrictions. VM only license allows to protect only virtual machines.

The backup of '<details.VolumeNames>' on '<agentName>' has been disabled because your capacity limit has been exceeded by '<details.CapacityExceededLimitPercent>'%! <productName> is no longer protecting your machines with new snapshots. Please contact your Account Manager to add additional capacity.

The backup of '<details.VolumeNames>' on '<agentName>' has been disabled because this <coreProductName> has not successfully checked in with the license portal in at least <details.GracePeriod> days.  Go to the License Information section of the <coreProductName>'s Configuration tab for more information.

Backup of '<details.VolumeNames>' on '<agentName>' has been disabled because the license key for this <coreProductName> has expired. Go to the License Information section of the <coreProductName>'s Configuration tab for more information.

Backup of '<details.VolumeNames>' on '<agentName>' has been disabled because the license key for this <coreProductName> is invalid.

Backup of '<details.VolumeNames>' on '<agentName>' has been blocked in the license portal, which prevents the transfer of new backups. To continue backing up this machine, please log in to the license portal.

Backup of '<details.VolumeNames>' on '<agentName>' has been blocked in the license portal, which prevents the transfer of new backups. To continue backing up this machine, please log in to the license portal.

Backup of '<details.VolumeNames>' on '<agentName>' has been disabled because the license for '<agentName>' has expired. Log into the license portal to extend the license for this machine.

Backup of '<details.VolumeNames>' on '<agentName>' has been deactivated, which prevents the transfer of new backups. To continue backing up this machine, please resume snapshots on the 'Machines' tab or log in to the license portal and activate this machine.

Backup of '<details.VolumeNames>' on '<agentName>' has been disabled because the trial for '<agentName>' has expired. Log into the license portal to purchase a license for this machine, or to request a trial extension.

All recovery points for <agentProductName> '<agentName>' have been dismounted

All recovery points on this <coreProductName> have been dismounted

The '<details.LocalizedMountType>' recovery point '<details.MountedValueName>' on '<details.AgentHomeName>' has been dismounted

The Mount Recovery Point of <details.VolumeNames> on <agentProductName> '<agentName>' has started

The <details.LogTruncationTargets> log truncation for the protected machine '<agentName>' on volumes '<details.VolumeNames>' has been cancelled. <details.WarningMessage>

The <details.LogTruncationTargets> log truncation for the protected machine '<agentName>' on volumes '<details.VolumeNames>' has completed successfully. <details.WarningMessage>

<agentProductName> log truncation configuration has been changed according to new license constraints. Please contact your account manager for more information.

The <details.LogTruncationTargets> log truncation for the protected machine '<agentName>' on volumes '<details.VolumeNames>' has failed. <details.WarningMessage>

The <details.LogTruncationTargets> log truncation for the protected machine '<agentName>' on volumes '<details.VolumeNames>' has been forced. <details.WarningMessage>

The <details.LogTruncationTargets> log truncation for the protected machine '<agentName>' on volumes '<details.VolumeNames>' has been skipped, because <details.Reason>

The <details.LogTruncationTargets> log truncation for the protected machine '<agentName>' has been skipped, because <details.Reason>

The <details.LogTruncationTargets> log truncation for the protected machine '<agentName>' on volumes '<details.VolumeNames>' has been skipped, because <details.Reason>

An Exchange database '<details.Database.DisplayName>' has been opened.

Started opening an Exchange database '<details.Database.DisplayName>'.

The metadata for '<agentName>' has been updated

Refresh metadata for '<agentName>' has been forced

Refresh Oracle metadata for '<agentName>' has been forced

Download of logs for: (<agentName>) has finished

Download of logs for: (<agentName>) has started

Nightly job configuration setup failed on job '<details.NightlyJobName>' for <details.NightlyJobConfigurationTarget>

Nightly jobs settings have been updated

Failed to send an e-mail notification due to system issues

Failed to send an e-mail notification to the following recipients: <details.FailedRecipients>

Events configuration has been changed

Nightly Oracle integrity check for '<details.AgentDisplayName>' has been skipped. Reason: <details.SkipReason>

Enabling archive log mode has failed on protected machine '<details.AgentDisplayName>'

Enabling archive log mode has finished on protected machine '<details.AgentDisplayName>'

Enabling archive log mode has started on protected machine '<details.AgentDisplayName>'

Oracle integrity check has been canceled

Oracle integrity check has failed

Oracle integrity check has finished

Oracle integrity check request for Oracle database(s) on <details.RecoveryPointName> has been updated

Oracle integrity check has been skipped for protected machine

Oracle integrity check has started

Oracle log truncation has been canceled

Oracle log truncation has failed

Oracle log truncation has finished

Oracle log truncation request for Oracle database(s) on protected machine '<details.AgentDisplayName>' has been updated

Oracle log truncation has been skipped for protected machine '<details.AgentDisplayName>'

Oracle log truncation has started

Remount Oracle databases has failed on protected machine '<details.AgentDisplayName>'

Remount Oracle databases has finished on protected machine '<details.AgentDisplayName>'

Remount Oracle databases has started on protected machine '<details.AgentDisplayName>'

Oracle integrity check settings for protected machine '<details.AgentDisplayName>' were set

Oracle log truncation settings for protected machine '<details.AgentDisplayName>' were set

Cannot start scheduled persist <coreProductName> state due to <details.Reason>

The protected machine '<agentName>' does not support PowerShell scripts execution. The Pre- and Post-snapshot scripting functionality will not be available, but all other product functionality will not be effected

Bulk Protect has errors: <details.Exceptions>

Direct to target option is unavailable for the '<details.AgentDisplayName>'

Transfer encryption is enabled for the protected machine '<details.AgentDisplayName>' but  <agentProductName> does not support it. Transmitting unencrypted data

Checksum check of Exchange database(s) on <details.RecoveryPointName> has been canceled

Checksum check of a single Exchange database on <details.RecoveryPointName> has been canceled

Checksum check of Exchange database(s) on <details.RecoveryPointName>has failed.

Checksum check of a single Exchange database on <details.RecoveryPointName> failed due to the corrupted pages <details.FailedPages>

Checksum check of a single Exchange database on <details.RecoveryPointName> failed due to an internal error.

Checksum check has completed for the Exchange database(s) on <details.RecoveryPointName> 

Checksum check has completed for the Exchange database <details.DatabaseName> on <details.RecoveryPointName>

Checksum check request for Exchange database(s) on <details.RecoveryPointName> has been updated

Checksum check of Exchange database(s) on <details.RecoveryPointName> has been skipped

Starting checksum check of Exchange database(s) on <details.RecoveryPointName> 

Checksum checking of a single Exchange database <details.DatabaseName> on <details.RecoveryPointName>

<details.JobType> on <details.RecoveryPointName> has been canceled

<details.JobType> on <details.RecoveryPointName> has failed.

<details.JobType> for '<details.MailStoreName>', '<details.DatabaseFile>' on <details.RecoveryPointName> has failed due to corruption.

<details.JobType> for '<details.MailStoreName>', '<details.DatabaseFile>' on <details.RecoveryPointName> has failed

<details.JobType> on <details.RecoveryPointName> has finished

<details.JobType> on <details.RecoveryPointName> has passed

<details.JobType> for '<details.MailStoreName>', '<details.DatabaseFile>' on <details.RecoveryPointName> has passed

<details.JobType> on <details.RecoveryPointName> has started

Nightly checksum check for '<agentName>' has been skipped. Reason: <details.SkipReason>

Configuration of agents groups was changed

The protected machine '<agentName>' has been added 

Credentials have been changed for <agentProductName> '<agentName>'

The display name has been changed for this <agentProductName> 

The host has been changed for <agentProductName> '<agentName>'

Notification group settings of the protected machine '<agentName>' have been changed

The protected machine '<agentName>' was offline during deletion

The port has been changed for <agentProductName> '<agentName>'

The protection of <agentProductName> '<agentName>'  cannot be paused. There are no protected volumes

<agentProductName> '<agentName>' protection configuration has been changed

<agentProductName> '<agentName>' protection configuration has been set

The protection of <agentProductName> '<agentName>' has been paused. The pause start time '<details.StartProtectionPauseTime>' (server local time). The protection resume time '<details.EndProtectionPauseTime> (server local time)'

The protection of <agentProductName> '<agentName>' has been paused until it is resumed

The protection of <agentProductName> '<agentName>' has been resumed

The protected machine '<agentName>' has been removed

<agentProductName> '<agentName>' is being removed

The protected machine '<agentName>' has been repaired

Repository of <agentProductName> '<agentName>' has been changed because there are recovery points in another repository

Repository of <agentProductName> '<agentName>' is unreachable

Status of <agentProductName> '<agentName>' has been changed

Protected machine transfer configuration has been updated

The <coreProductName> was unauthorized during deletion of the protected machine '<agentName>'

The version of the <agentProductName> '<agentName>' is older than the version of the <coreProductName>, please update the <agentProductName>

The protected vCenter/ESXi host '<agentName>' was offline during deletion

The protected vCenter/ESXi host '<agentName>' has been removed

vCenter/ESXi host '<agentName>' is being removed

SMB server protection failed due to '<details.ErrorDetails.Message>'.

Removing SMB server from protection failed due to '<details.ErrorDetails.Message>'.

Taking VSS <details.SnapshotType> snapshot of '<details.VolumeNames>' on '<agentName>'

VSS <details.SnapshotType> snapshot of '<details.VolumeNames>' on '<details.AgentName>' was taken with excluded VSS writers '<details.FailedWritersAndStatusesMessage>'

VSS <details.SnapshotType> snapshot of '<details.VolumeNames>' on '<agentName>' failed due to VSS error: <details.VssError>

VSS <details.SnapshotType> snapshot of '<details.VolumeNames>' on '<agentName>' was taken successfully

VSS <details.SnapshotType> snapshot of '<details.VolumeNames>' on '<agentName>' failed due to writer '<details.WriterName>' VSS error: <details.VssError>

'<details.InvalidExcludedPathMessage>' - invalid path(s) to excluded folder on '<details.AgentName>'. 'filename' or 'folder\subfolder\filename' is expected. The 'filename' may contain the wildcards "*" and "?"

Transfer for the cluster '<agentName>' is incomplete, because the shared volume(s) '<details.VolumeNames>' are not placed on protected nodes.

The transfer from agent '<agentName>' failed: <details.ErrorDetails.Message>

<productName> has detected the presence of <details.IncompatibleProducts> on '<agentName>'. Some customers have experienced configuration difficulties between this software and <productName>, preventing backups or causing incorrect behavior. Please review the KB article at https://support.quest.com/appassure/kb?k=third+party+software+conflicts+with+appassure+5 for more details.

The scheduled transfer from '<agentName>' has been skipped, because protection is in pause

The transfer of the  backup of '<details.VolumeNames>' on '<agentName>' has been canceled

The transfer of the backup of '<details.VolumeNames>' on '<agentName>' failed

Transferred the backup of '<details.VolumeNames>' on '<agentName>'

Transfer of '<details.VolumeNames>' on '<agentName>' doesn't include all related volumes. Recovery point may not contain all needed information. To avoid this - add '<details.DeficiencyVolumes>' to transfer.

Transfer of the backup of '<details.VolumeNames>' on '<agentName>' failed for some volumes

Request for a <details.RequestType> transfer <details.WithLogTruncationLabel>of '<details.ImageType>' of '<details.VolumeNames>' of '<agentName>' has been put in queue

The transfer of the backup on '<agentName>' has been skipped because the protected machine is offline

The transfer of a backup of '<agentName>' has been skipped due to an authentication error. The pairing relationship with the core is likely broken. Try re-pairing with the agent.

The transfer of the backup on '<agentName>' has been skipped because max snapshots per day limit has been reached

This protected machine <details.AgentName> cannot be backed up because it's metadata has not been gathered yet

Transfer has been skipped because protection groups have been changed for the '<agentName>'

Transfer has been skipped because repository of '<agentName>' is unreachable

This protected machine <details.AgentName> cannot be backed up because it has an unsupported version of the agent. Please upgrade the agent to 5.4.3 or higher

Transferring backup of '<details.VolumeNames>' on '<agentName>'

Transfer for '<agentName>' is incomplete, because the following volume(s) cannot be obtained from '<agentName>' metadata: <details.VolumeNames>.
Please, check the machine device configuration or change the transfer settings

The transfer of the backup on '<agentName>' has been deactivated

The <details.RequestType> transfer <details.WithLogTruncationLabel>of '<details.ImageType>' of '<details.VolumeNames>' of '<agentName>' was ignored because the relevant transfer is <details.RelevantTransferStatus>

The <details.RequestType> transfer <details.WithLogTruncationLabel>of '<details.ImageType>' of '<details.VolumeNames>' of '<agentName>' was promoted to '<details.PromotedTo>'

Volume files are not synchronized due to obsolete <agentName> version on the '<details.AgentName>' machine. Base image may be transferred.

Transfer of <details.ImageSize> <details.ImageType> of '<details.VolumeDisplayName>' on '<agentName>' has been canceled

Transfer of <details.ImageSize> <details.ImageType> of '<details.VolumeDisplayName>' on '<agentName>' failed

Transfer of <details.ImageSize> <details.ImageType> of '<details.VolumeDisplayName>' on '<agentName>' has finished

Transferring <details.ImageSize> <details.ImageType> of '<details.VolumeDisplayName>' on '<agentName>'

Deployment of <shortProductName> <agentProductName> on '<details.HostName>' has been cancelled.

The Cluster IP address(es) '<details.HostName>' couldn't be used for bulk deploy.

Deployment of <shortProductName> <agentProductName> on '<details.HostName>' is already running.

Deployment of <shortProductName> <agentProductName> on '<details.HostName>' has failed.

Deployment of <shortProductName> <agentProductName> on '<details.Machines>' has started

Deployment of <shortProductName> <agentProductName> on '<details.HostName>' has succeeded

A warning message was received during the deployment of <coreProductName> <agentProductName> on '<details.HostName>' : <details.Message>

Starting the migration for machine '<details.AgentName>' failed: <details.ErrorDetails.Message>

Corrupted data encountered during migration of '<details.AgentName>' machine

Migration of '<details.AgentName>' machine has encountered some problems. Retrying...

Migration of '<details.AgentName>' machine needs user intervention

Nightly job settings changes have been ignored because migration for the machine '<details.AgentName>' is in progress.

Migration of '<details.AgentName>' machine has started 

Repository performance check done

<details.Reason>

The Repository '<details.RepositoryName>' was deleted

The Repository '<details.RepositoryName>' was disconnected

Repository <details.RepositoryName> is almost full.

The repository  <details.RepositoryName> has been opened

Repository settings have been changed for '<details.RepositoryName>' repository

RDS Server Maintenance job is already running for the server <details.ServerName>. RDS Server Maintenance start request will be ignored.

RDS Server Maintenance was skipped for host '<details.ServerName>'. Reason '<details.Reason>'.

RDS Server Maintenance did not complete for '<details.ServerName>'. Please increase the RDS Server Maintenance timeouts under RDS Server settings or reduce the workload on the dependent repositories

RDS server '<details.ServerName>' entered maintenance mode

Nightly recovery points check for '<agentName>' on volumes '<details.VolumeNames>' has been skipped because there is no available (new) recovery point for check

Recovery points of <agentProductName> '<agentName>' contains broken volume image(s).

<details.CheckJobName> for '<agentName>' has been skipped: <details.VolumeNames>

<details.CheckJobName> for '<agentName>'  has been skipped because there are no available volumes

The '<details.RemoteMountType>' remote mount point <details.MountPoint> on <details.RemoteMachineIpAddress> has been added

All remote mount points on this <coreProductName> have been disconnected

All remote mount points  for <agentProductName> <details.AgentHomeName> have been disconnected

All remote mount points  for repository '<details.RepositoryId>' have been disconnected

The '<details.RemoteMountType>' remote mount point <details.MountPoint> on <details.RemoteMachineIpAddress> has been disconnected

Remote <agentProductName> '<agentName>' has been added to replication

<agentProductName> '<agentName>' has been added to replication

Adding <agentProductName> '<agentName>' to replication was denied on the Target <coreProductName> '<remoteSlaveCoreName>'.

Failed to add remote replicated <agentProductName> '<details.DisplayName>' to replication.

Adding protected machine '<agentName>' to replication was ignored on the Target <coreProductName> '<remoteSlaveCoreName>'.

Adding protected machine '<agentNameToReplicate>' to replication was denied on this <coreProductName>

Replication of  <agentProductName> '<agentName>' has failed back by the Source <coreProductName>  '<details.RemoteMasterCoreName>' to this <coreProductName> '<details.RemoteSlaveCoreName>'

Conversion of replicated <agentProductName> '<agentName>' to failover has failed

Replication of  <agentProductName> '<agentName>' has failed over by the Source <coreProductName>  '<details.RemoteMasterCoreName>' to this <coreProductName> '<details.RemoteSlaveCoreName>'

Replication of  <agentProductName> '<agentName>' has been paused by the Target <coreProductName> '<remoteSlaveCoreName>'.

Replication of  <agentProductName> '<agentName>' has been pending failed over by the Source <coreProductName>  '<details.RemoteMasterCoreName>' to this <coreProductName> '<details.RemoteSlaveCoreName>'

Replication of  <agentProductName> '<agentName>' has been resumed by the Target <coreProductName> '<remoteSlaveCoreName>'.

Conversion of replicated <agentProductName> '<agentName>' to failover has started by this <coreProductName> 

Cannot fix orphans on <remoteSlaveCoreName> for replicated <agentProductName> '<agentName>'. See log for details.

<agentProductName> '<agentName>' has been deleted from replication

<agentProductName> '<agentName>' has been deleted from replication

Replication has been disabled for '<agentName>'

Replication has been disabled on this <coreProductName>

Replication has been enabled for '<agentName>'

Replication has been enabled on this <coreProductName>

Replication has been paused on this <coreProductName>

Check on maximum transfer data size for replication has failed on '<agentName>'. Replication for this agent will be paused and all active jobs will be cancelled.

Replication has been paused for '<agentName>'

Replication has been paused on this <coreProductName>

The replication has been resumed for '<agentName>'

The replication has been resumed on this <coreProductName>

Scheduled replication configuration has been changed for the '<details.RemoteSlaveCoreName>'

<agentProductName> replication request of the Source <coreProductName>  <remoteMasterCoreName> was ignored by this <coreProductName>.

The Source <coreProductName> <remoteMasterCoreName> has requested permission to replicate one or more machines to this <coreProductName>

The Source <coreProductName> <remoteMasterCoreNameValue> has been deleted from replication

Target <coreProductName> <remoteSlaveCoreNameValue> has been deleted from replication

Replication from Source <coreProductName> <remoteMasterCoreName> has been paused

The replication request of a Source <coreProductName> <remoteMasterCoreName> has denied by this Core

Source <coreProductName> <remoteMasterCoreName> has been granted permission to replicate one or more machines to this <coreProductName>

Replication from Source <coreProductName> <remoteMasterCoreName> has been resumed

Replication has been deleted by Target <coreProductName> <remoteSlaveCoreName>

Replication has been deleted from Target <remoteSlaveCoreName>

Cannot establish replication. The source core must be version 6.0 or later to replicate with that target.

Replication has been paused by Target <coreProductName> <remoteSlaveCoreName>

The Target <coreProductName> <remoteSlaveCoreName> has denied permission to replicate one or more machines to it

Target <coreProductName> <remoteSlaveCoreName> has granted permission to replicate one or more machines to it

The Replication Request was ignored by Target <coreProductName> <remoteSlaveCoreName>

The Replication request of a Source <coreProductName>  <remoteMasterCoreNameValue> was ignored by this <coreProductName>.

A new replication request has been received from a Source <coreProductName> <remoteMasterCoreName>.

The Replication Request was sent to Target <coreProductName> <remoteSlaveCoreName>

The replication has been resumed by Target <coreProductName> <remoteSlaveCoreName>

The Target <coreProductName> <remoteSlaveCoreName> became offline

The Target <coreProductName> <remoteSlaveCoreName> became online

The Target <coreProductName> <remoteSlaveCoreName> reachability was changed

Seed drive to <details.RelatedSlaveCores> has been abandoned successfully on this <coreProductName>

Seed Drive has skipped for the protected machine '<agentName>'. Replication is not configured

A copy to Seed Drive for agents <details.AgentsId> has not been started because they don't have recovery points

An attempt to force the replication of the <agentProductName> '<details.DisplayName>' from the Source <coreProductName> '<details.RemoteMasterCoreName>' failed because the replication for this <agentProductName> is paused.

An attempt to force the replication of the <agentProductName> to the Target <coreProductName> <remoteSlaveCoreName> has failed. Make sure that the replication of this <agentProductName> is available.

A replication job to receive data for '<agentName>' from the Source <coreProductName> <remoteMasterCoreName> has been canceled

The Source <remoteMasterCoreName> has failed to send data for '<agentName>' to this <coreProductName>  

The Source <coreProductName> <remoteMasterCoreName> has finished sending data for '<agentName>' to this <coreProductName>

The Source <coreProductName> <remoteMasterCoreName> has started sending data for '<agentName>' to this <coreProductName>

A replication job to send data for '<agentName>' to the Target <coreProductName> <remoteSlaveCoreName> has been canceled

A replication job has failed to send data for '<agentName>' to  the Target <coreProductName> <remoteSlaveCoreName>

A replication job has finished sending data for '<agentName>' to  the Target <coreProductName> <remoteSlaveCoreName>

A replication job has started sending data for '<agentName>' to the Target <coreProductName> <remoteSlaveCoreName>

Failed generating report document by request: <details.RequestDescription>

Report document has been successfully generated by request: <details.RequestDescription>

The repository '<details.RepositoryName>' was created

The creation of the repository '<details.RepositoryName>' has started

Repository '<details.RepositoryName>' has changed frozen status to '<details.IsFrozen>'

Repository '<details.RepositoryName>' has changed status to '<details.RepositoryStatus>'

An unspecified error occurred while dismounting/remounting databases during the restore job . Error details: <details.ErrorMessage>

Failed to dismount database <details.DatabaseName> on the Exchange server '<agentName>'

Successfully dismounted database <details.DatabaseName> on the Exchange server '<agentName>'

Failed to start  the MS Exchange server on '<agentName>'

Successfully started the MS Exchange server on '<agentName>'. Started services: '<details.ProcessedServices>'. Excluded services: '<details.ExcludedServices>'

Failed to stop the MS Exchange server on '<agentName>'

Successfully stopped the MS Exchange server on '<agentName>'. Stopped services: '<details.ProcessedServices>'

The dismount of database <details.DatabaseName> has been skipped -- the database had already been dismounted.

Failed to mount the database <details.DatabaseName> for the Exchange server on '<agentName>' after the Restore job has failed

Successfully mounted the database <details.DatabaseName> for the Exchange server on '<agentName>' after the Restore job has failed

Failed to mount the database <details.DatabaseName> to Exchange '<agentName>'

Successfully mounted the database <details.DatabaseName> to the Exchange '<agentName>'

Oracle database failed to start

Oracle database successfully started

Oracle database failed to stop

Oracle database successfully stopped

Oracle instance service failed to start

Oracle instance service successfully started

Oracle instance service failed to stop

Oracle instance service successfully stopped

Failed to attach the database <details.DatabaseName> back to the SQL Server instance <details.ServerName> on '<agentName>' after  the restore job's failure

Successfully attached the database <details.DatabaseName> back to the SQL Server instance <details.ServerName> on '<agentName>' after  the restore job's failure

Failed to attach the database <details.DatabaseName> to the SQL Server instance <details.ServerName> on '<agentName>'

Successfully attached the database <details.DatabaseName> to the SQL Server instance <details.ServerName> on '<agentName>'

Failed to detach database <details.DatabaseName> from SQL Server instance <details.ServerName> on '<agentName>'

Successfully detached the database <details.DatabaseName> from SQL Server instance <details.ServerName> on '<agentName>'

Failed to start back the SQL Server instance <details.ServerName> on '<agentName>' after the restore job's failure

Successfully started back the SQL Server instance <details.ServerName> on '<agentName>' after the restore job's failure

Failed to start the SQL Server instance <details.ServerName> on '<agentName>'

Successfully started the SQL Server instance <details.ServerName> on '<agentName>'

Failed to stop the SQL Server instance <details.ServerName> on '<agentName>'

Successfully stopped the SQL Server instance <details.ServerName> on '<agentName>'

Failed to take back offline the database <details.DatabaseName> on the SQL Server instance <details.ServerName> on '<agentName>' after the restore job failure

Successfully took offline the database <details.DatabaseName> on the SQL Server instance <details.ServerName> on '<agentName>' after the restore job's failure

Failed to take offline the database <details.DatabaseName> on SQL Server instance <details.ServerName> on '<agentName>'

Successfully took offline the database <details.DatabaseName> on the SQL Server instance <details.ServerName> on '<agentName>'

The restore of volume(s) <details.VolumeNames> for '<agentName>' for the recovery point as of <details.LocalTimestamp> has been cancelled

The restore of volume(s) <details.VolumeNames> for '<agentName>' for the recovery point as of <details.LocalTimestamp>  failed.

Finished the restore of volume(s) <details.VolumeNames> for '<agentName>' for the recovery point as of <details.LocalTimestamp>

The restoring volume(s) <details.VolumeNames> for '<agentName>' for the recovery point as of <details.LocalTimestamp>

The restore of '<agentName>' volume(s) <details.VolumeNames> to the recovery instance for the  recovery point as of <details.LocalTimestamp> has been cancelled

The restore of '<agentName>'  volume(s) <details.VolumeNames> to the recovery instance for the recovery point as of <details.LocalTimestamp> failed.

Finished the restore of '<agentName>' volume(s) <details.VolumeNames>  to the recovery instance for the recovery point as of <details.LocalTimestamp>

The restoring of '<agentName>' volume(s) <details.VolumeNames> to the recovery instance for the recovery point as of <details.LocalTimestamp>

Ad hoc delete of one or more recovery points has been skipped because the recovery points of '<agentName>' have not yet been replicated

Ad hoc delete of one or more recovery points of '<agentName>' has been skipped because they are in an outstanding seed drive

The Nightly rollup job has been skipped. Reason: <details.SkipReason>

Retention policy settings have been changed

The rollup job for '<agentName>' has failed

The rollup job for '<agentName>' has started

Rollup of one or more recovery points has been skipped because the recovery points of '<agentName>' have not yet been replicated

Rollup of one or more recovery points of '<agentName>' has been skipped because they are in outstanding seed drive

Rollup has been skipped for: (<details.AgentNames>) because agent was replicated with old replication mode

Scheduled <details.JobName> has been added

Scheduled <details.JobName> configuration has been changed

Scheduled <details.JobName> has been deleted

Scheduled <details.JobName> has been forced

Scheduled <details.JobName> has been paused

Scheduled <details.JobName> has been resumed

Scheduled <details.JobName> has started. Checking preconditions.

Cannot start scheduled <details.JobName>: <details.Reason>

The scheduled <details.JobName> was skipped: <details.Reason>

Encryption key has been created

The Encryption Key '<details.EncryptionKeyName>' has been locked on this <coreProductName>

The Passphrase has been changed for the Encryption Key '<details.EncryptionKeyName>' on this <coreProductName> 

The Status of the Encryption Key '<details.EncryptionKeyName>' has been changed to '<details.EncryptionKeyStatus>' on this <coreProductName>. <details.StatusChangeReason>

The Encryption Key '<details.EncryptionKeyName>' has been unlocked on this <coreProductName>

The collect server logs job has been canceled

The collect server logs job has failed

The collect server logs job has completed

The collect server logs job has started

The <coreProductName> service state has been changed

Some volume images failed to load from the repository. This may indicate corruption. See log for details.

Volume images range was locked.

Volume images range was unlocked.

Auto-protection for <details.ObjectsCount> vCenter/ESXi objects has been added

Auto-protection for <details.ObjectsCount> vCenter/ESXi objects has been merged

Auto-protection for <details.ObjectsCount> vCenter/ESXi objects has been removed

The Datastore '<details.DatastoreName>' is <details.PercentFull>% full.

Storage profiles were not obtained for the vCenter '<details.AgentName>'. Storage profile selection will not be available on export. Please verify that the account has the necessary privileges as described in KB article at https://support.quest.com/rapid-recovery/kb/190381/rapid-recovery-esxi-6-6-5-permissions

The vCenter/ESXi '<details.AgentName>' has been protected

The vCenter/ESXi Virtual Machine '<details.AgentName>' has been protected

The vCenter/ESXi Virtual Machine '<details.AgentName>' has been merged

Nightly snapshots consolidation for protected virtual machines has been skipped, because <details.Reason>