DonatShell
Server IP : 180.180.241.3  /  Your IP : 216.73.216.252
Web Server : Microsoft-IIS/7.5
System : Windows NT NETWORK-NHRC 6.1 build 7601 (Windows Server 2008 R2 Standard Edition Service Pack 1) i586
User : IUSR ( 0)
PHP Version : 5.3.28
Disable Function : NONE
MySQL : ON  |  cURL : ON  |  WGET : OFF  |  Perl : OFF  |  Python : OFF  |  Sudo : OFF  |  Pkexec : OFF
Directory :  /Program Files/CA/arcserve Unified Data Protection/Engine/BIN/MUI/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :

[ HOME SHELL ]     

Current File : /Program Files/CA/arcserve Unified Data Protection/Engine/BIN/MUI/AFMSG.ENU.dll
MZ@	!L!This program cannot be run in DOS mode.

$M!	@	@	@f6
@f6I@8p@	@@f6H
@f6y@f6~@Rich	@PEd=VU" 

`߰@h"<P@P  .text `.rdata @@.dataX0@.pdata@@@.rsrcP@@.relocP@B@SH HHH H
 HuC#H#H
H
3H [HHXHhHxL` AUAVAWH 3ML8}#DjeH%0HXH;tS3H`uAHtgH
ELHH
$MLHHI;rZH9}t@H9EtHMH'HEH
H
HL;uL;tLLIHH=EH=w3eH%0HXH;t)3H6ut?>HH
uHwH
hu
HHH9=t!H
tMĺI{H\$@Hl$HH|$PLd$XH A_A^A]HHXHpHxATH0ILXu9u
3ۉXtu7H
HtЋ؉D$ LƋI0؉D$ LƋI؉D$ u5u1L3IL3IL}
MtL3IAӅtu7LƋI#ˋىL$ tHB
HtLƋIЋ؉D$ 3ۉ\$ H\$@Ht$HH|$PH0A\H\$Ht$WH IHuOLNjHH\$0Ht$8H _H
@SH HH
HD$8HuH~H
HD$8H
HD$@HHLD$@HT$8nHHL$8`HqHL$@NHW7HH [H(GHH(H\$WH HSH=LHHtHH;rH\$0H _H\$WH H+H=$HHtHH;rH\$0H _HMZf9t3HcH<H39PEuf9QLcA<E3LLA@EXJLEtQL;r
AL;rAH(E;r3HH(LL
Ijt"M+IIHt@$Ѓ3H(%@
%2
%
%
%	H\$WH HHd$0H2-+H;tHHpvHL$0	H\$0H	DI3D	DI3@	HL$8DI37	L\$8L3HL#H3-+L;LDLILH\$@H _%.	%	%	%d	@UH HHHM(HM$
H ]@UH H}H ]@UH HH ]@UH HH3Ɂ8H ]$$v$\$T$D$4$$#$#$#####z#n#$`#=VUb!
RSDSGF1
W
D:\Oolong_Agent\source\D2D\Native\RCModules\AFMSG\amd64.USA.rel\AFMSG.pdb20t
T	422Pt
d	4Rd@pd42p20dB

4
2p	BdJJ

4
2p"&$H "$ $$v$\$T$D$4$$#$#$#####z#n#$`#_malloc_crt_initterm_initterm_ecfree_encoded_null_amsg_exit__C_specific_handler__CppXcptFilter@__clean_type_info_names_internal[_unlockH__dllonexit_lock_onexitMSVCR100.dllEncodePointerDecodePointerSleepQueryPerformanceCounterGetTickCountGetCurrentThreadIdGetCurrentProcessIdGetSystemTimeAsFileTimeKERNEL32.dll2-+] ff!h!!=!L"("L0"L0"Q<"p#\"@e!p!!!P	XpPh&(	@
Xp
		0	H	`	x						
 
8
P
 h
!
"
#
$
%
&
yy(x@xXxpx!"#Q0qHr`sxtuvw
 
8
P
!h
"
#
$
%
&
'
()(*@+X,p-./0123708H9`:x;Aqrs 8Ph(@Xp0H`x!1ABCQR S8TPahqrvw(@Xp			

0
H
`
x






 
8PhAQa(@Xp
0H`x/yyyy y8yPyhyy	y
yyyyy(y@yXypyyyyy y!y"y0#yH`x										 	0	@	P	`	p											 	0	@	P	`	p											 	0	@	P	`	p											 	0	@	P	`	p									 	 	  	0 	@ 	P 	` 	p 	 	 	 	 	 	 	 	 	!	!	 !	0!	@!	P!	`!	p!	!	!	!	!	!	!	!	!	"	"	 "	0"	@"	P"	`"	p"	"	"	"	"	"	"	"	"	#	#	 #	0#	@#	P#	`#	p#	#	#	#	#	#	#	#	#	$	$	 $	0$	@$	P$	`$	p$	$	$	$	$	$	$	$	$	%	%	 %	0%	@%	P%	`%	p%	%	%	%	%	%	%	%	%	&	&	 &	0&	@&	P&	`&	p&	&	&	&	&	&	&	&	&	'	'	 '	0'	@'	P'	`'	p'	'	'	'	'	'	'	'	'	(	(	 (	0(	@(	P(	`(	p(	(	(	(	(	(	(	(x4$zz4||4}~44āxx,,H4|04d4L44444P4444 4T4444$أDԥ`Z4tȽV p|Pp4|	 dd $"$+l/3"(4`8=E(MD\em<8vD~Pd^ę>
 @LV	@( $L(6.P6>	?<J,
T]l~slsp	l}4$Pt	4z.	ػ
 	l r	T> 8',	d0v8X4:?B\F@HIDI	S^btc^h\0mpwdy^ćTb
6
4&RDzn		 
HdL $jl"0'd(*(*$8+J+l0d258678\=(?,?<DE"(E"LE"pE"E"E"E"F"$F"HF"lF"F"FFFFGG,G@GTGhG|GGGGGLKZ( @80p`????? p( HxHd)9|x0!?( @@ pL)JOyOy)JLp @?3113?( @ x*TNrNr*Tx @?##?( @%UU%( -MM-( @@  @????( @ pp @??( @ C  D @A@B"@DB@H@1@"1C ?>?<?8<?0|??( ?<>|<9??( @DTbUJDBA#s( h2-""!?g( @ABDJUbTDs#( ~BDDZe0( @@  @????( @  @??( @ PP ( 0((OO((0( @@ &RR& @?7cc7?( @ x*TNrNr*Tx @?##?( @@M(==(M@ȀCfv~~|xp`@?oo ?=|?8??( @x0??( @@@@  @???( @@  @@  @???
( @@ b

b @??( @ @@ sa@@as( @$BB$$D ?Ã( @0$(B$B"$!  @     ?ǁÁ?( @? $DB$B$Ã
( @@@@ @@@AB0DHHP`H0?( @0P
	@ H((H @	P
0?p00p?( @@  @@  @@  @????( @@  ?@@@A BBD"D"BBA @@@?  @?????>|<<88<<>|?????( @p?00p?( @????( @???>|?<<<<>|????	( @?????( `  @@@@  `q(
Pwww(!wwwwwwwxwwwxwwwwxwwwwwwwȀ	FNewMS Shell DlgP{&New P}1dP(OKP(CancelP+(F&Help
WMS Shell DlgPPrintingPADocument :PO_PAPage :PO_P+APrinter :PO+_P7APort :PO7_PFC(CancelPAD@VMS Shell DlgP.&Print...P2.&Next PagePb.Pre&v PageP.P.Zoom &InP.Zoom &OutP".&ClosePAȀ	FMS Shell DlgGStarting node data purge on Arcserve UDP Recovery Point Server [%1!s!].%Purging nodes from data store [%1!s!]OThe Backup Data Format for the data store is configured in the Advanced format.oThe Backup Data Format for the data store is configured in the Advanced format with Data Deduplication enabled.+Node data purge job completed successfully."Node data purge job is incomplete.Node data purge job failed.2Total number of agent nodes to be purged: [%1!d!].$Failed to purge agent node: [%1!s!].:Total number of agent nodes that failed to purge: [%1!d!].CTotal number of agent nodes that were successfully purged: [%1!d!].Total freed space:[%1!s!].[Total freed space:[%1!s!],Deduplication enabled data store will reclaim disk automatically.Failed to delete file: [%1!s!].RFailed to purge data from the data store for node [%1!s!], session number [%2!d!].PA(Successfully purged agent node: [%1!s!].0Successfully purged Host-Based VM node: [%1!s!].,Failed to purge Host-Based VM node: [%1!s!].Node data purge job crashed.sUnable to delete agent node:[%1!s!]because it is currently in use or its backup destination path is not accessible.|Unable to delete Host-Based VM node:[%1!s!] because it is currently in use or its backup destination path is not accessible.KTotal number of Host-Based VM nodes that were successfully purged: [%1!d!].:Total number of Host-Based VM nodes to be purged: [%1!d!].BTotal number of Host-Based VM nodes that failed to purge: [%1!d!].&The agent node [%1!s!] does not exist..The Host-Based VM node [%1!s!] does not exist.InformationWarningError Hr Min SecUpdates InformationUpdates Warning
Updates ErrorHost-Based VM Backup,Error details: (EC=[0x%1!08x!], MSG=[%2!s!])There are %1!d! existing activity log messages from previous release detected, which are not imported to current activity log database. Please contact arcserve support to import them after installation. Mbps KbpsPAFailed to locate file: %1!s!.9Another instance of Updates process is currently running.File %1!s! is corrupted.File %1!s! is not signed.Environment check failed. Required space is not available.Invalid path %1!s! for updates.?Failed to write file. Required disk space may not be available.Memory allocation failed.+%1!s!. Failed to connect to network: %2!s!.:Download failed. Maximum number of retry attempts reached.$Failed to create download directory.#Failed to generate status.xml file.Internet Error Code: %1!d!.A timeout failure has occurred.2Failed to connect and log on to HTTP server %1!s!.PAMServer %1!s! response could not be parsed. Contact your server administrator.Failed to connect to server %1!s!. Verify that the server is up and running and the proxy settings and server IP/Name are correct.1Connection with server %1!s! has been terminated.1Server %1!s! is requesting client authentication.CThe URL scheme could not be recognized, or is not supported: %1!s!.mServer %1!s! could not be resolved. Verify the proxy server settings are correct and no network errors exist.Server encountered an unexpected condition which prevented it from completing the request. Check the ARCUpdates.Log file for more information or contact arcserve support.QServer %1!s! may be temporarily unavailable, or there could be a network problem.Invalid URL: %1!s! Please contact arcserve support.;New update (Version %1!d!) has been successfully installed.-Download of new update  was successful: %1!s! Check for update was successful.\None of the configured servers are available. Please verify D2DUpdates.Log for more details.!Arcserve UDP Agent is up to date.Updates:PA4Latest available update has already been downloaded.WNone of the configured servers are available. Please verify PMLog.log for more details.[The latest available patch for %2!s! is %1!s!. The patch (%1!s!) was downloaded previously.OEncryption password length is too long. The maximum length is %1!u! characters.=Network adapter changes detected: [%1!s!] media disconnected.:Network adapter changes detected: [%1!s!] media connected.DSession resources are being used by process %1!s! on computer %2!s!.FThe backup destination is data store %1!s!(%2!s!) on RPS server %3!s!.7Session password is incorrect. (Session Number=[%1!u!])TData store hash key is incorrect. (Data Store Name=[%1!s!], Data Store GUID=[%2!s!])Network adapter [%1!s!] has been detected. As a result, the TCP segmentation offload (TSO) feature (also known as the Large Send Offload) of this adapter has been disabled to avoid any potential data corruption.Network adapter [%1!s!] has been detected. This adapter may cause data corruption. To avoid this problem, change the network adapter or manually disable the TCP segmentation offload (TSO) feature of the adapter (also known as the Large Send Offload).4An unknown error occurred. Contact arcserve support.BMemory allocation failed: out of memory. Contact arcserve support.<One of the parameters was invalid. Contact arcserve support.NA file %1!s! was not found. Please trigger a new virtual machine recovery job.mThis function cannot be performed because the handle is executing another function. Contact arcserve support.9The operation is not supported. Contact arcserve support.tA file access error occurred on the host or guest operating system, %1!s!. Start a new virtual machine recovery job.An error occurred while writing a file %1!s!; the disk is full. The data was not saved. There is not enough space in the data store. To correct this problem, free disk space.LThe file %1!s! is write-protected. Start a new virtual machine recovery job.You do not have access rights to this file %1!s!. Verify that the SAN is configured properly on the proxy machine. Then start a new virtual machine recovery job.bThe VMFS file system does not support sufficiently large files. The disk file is greater than 2TB.YThe file %1!s! is in use by  another operation. Start a new virtual machine recovery job.yThe system returned an error. Communication with the virtual machine may have been interrupted. Contact arcserve support.The file %1!s! is too big for the file system. Verify the maximum file size supported by the version of VMFS. The disk file is greater than 2TB.bThe request refers to an object that no longer exists or  never existed. Contact arcserve support.Unable to connect to the host %1!s!. Verify that the vSphere proxy machine and the ESX/vCenter server are connected to network._This operation is not supported with the current license. Verify that the license is installed.Unable to communicate with the virtual machine's host; it appears to be  disconnected. Verify that the vSphere proxy machine and the ESX/vCenter server are connected to network.?The handle is not a valid VIX object. Contact arcserve support.PThe operation is not supported on this type of handle. Contact arcserve support.:There are too many handles open. Contact arcserve support.SInvalid file - a required section of the file is missing. Contact arcserve support.qA timeout error occurred. Verify that the vSphere proxy machine and  ESX/vCenter server are connected to network.sInsufficient permissions for the operating system on host %1!s! Verify that the user name and password are correct.The virtual machine is blocked waiting for a user operation. Verify that the virtual machine user operation pending pop up in VI Client. Contact arcserve support.HThe command is not allowed by this login type. Contact arcserve support.>The virtual machine cannot be found. Contact arcserve support.ZThe operation is not supported for this virtual machine version. Contact arcserve support.EThe virtual machine was  loaded previously. Contact arcserve support.5Disk sector size check failed. Perform a full backup.,Error in protocol. Contact arcserve support.Unable to create socket. Verify that proxy and the host can communicate with each other via the network. Verify that the vSphere proxy machine and the ESX/vCenter server are connected to the network.PAThe specified server %1!s! cannot be contacted. Verify that the network connection and port setting of the ESX or vCenter server are configured properly.The server %1!s! refused the connection. Verify that the network connection and port setting of the ESX or vCenter server are configured properly. Verify that the vSphere proxy machine and the ESX/vCenter server are connected to the network.A communication error occurred. Verify that the proxy and the host can communicate with each other via the network. Verify that the vSphere proxy machine and the ESX/vCenter server are connected to the network.The connection was lost. Verify that the ESX/vCenter server can communicate via the network. Try reconnecting. Verify that the vSphere proxy machine and the ESX/vCenter server are connected to the network.OVDDK write failed with error NBD_ERR_HASHFILE_VOLUME. Contact arcserve support.MVDDK write failed with error NBD_ERR_HASHFILE_INIT. Contact arcserve support.DOne of the parameters supplied is invalid. Contact arcserve support.@The disk library was not  initialized. Contact arcserve support.]The called function requires the virtual disk to be opened for I/O. Contact arcserve support.sThe called function cannot be performed on partial chains.  Open the parent virtual disk. Contact arcserve support.BThe specified virtual disk needs repair. Contact arcserve support.eYou  requested access to an area of the virtual disk that is out of bounds. Contact arcserve support.The parent virtual disk was modified after  the child was created. Verify that the parent disk was not corrupted by another operation.hThe specified virtual disk cannot be shrunk because it is not the parent disk. Contact arcserve support.The partition table on the physical disk  changed after the disk was created. Remove the physical disk from the virtual machine, and then add it again.Ethan the version supported by this program. Contact arcserve support.NThe parent of this virtual disk could not be opened. Contact arcserve support.QThe specified feature is not supported by this version. Contact arcserve support.FOne or more required keys were not provided. Contact arcserve support.uAn unencrypted child of the encrypted disk will not be created without an explicit request. Contact arcserve support.0Not an encrypted disk. Contact arcserve support.?No keys supplied for encrypting disk. Contact arcserve support.9The partition table is invalid. Contact arcserve support.YOnly sparse extents with embedded descriptors may be encrypted. Contact arcserve support.;Not an encrypted descriptor file. Contact arcserve support.6The file system is not VMFS. Contact arcserve support.XThe physical disk is too big. The maximum size allowed is 2TB. Contact arcserve support.WThe  limit for open files on the host was  exceeded. The disk file is greater than 2TB.7Too many levels of redo logs. Contact arcserve support.9The physical disk is too small. Contact arcserve support.tThe  disk chain is not valid: cannot mix hosted and managed style disks in the same chain. Contact arcserve support.OThe specified key is not found in the disk data base. Contact arcserve support.VOne or more of the required subsystems failed to initialize. Contact arcserve support.FAn invalid connection handle error occurred. Contact arcserve support.9A disk encoding error occurred. Contact arcserve support.AThe disk is corrupted and unrepairable. Contact arcserve support.CThe specified file is not a virtual disk. Contact arcserve support.EThe host is not licensed for this feature.  Contact arcserve support.5The device does not exist.  Contact arcserve support.PThe operation is not supported on this type of device. Contact arcserve support.Cannot connect to host. Verify that the proxy and the ESX/vCenter server can communicate with each other via the network.  Verify that the vSphere proxy machine and the ESX/vCenter server are connected to the network.3File %1!s! name too long. Contact arcserve support.The VMDK IO connection failed. VMware reported the following error: %1!s!. For more information, see the debug log %2!s!. If necessary, contact arcserve support.Unable to open VMDK file %1!s!. VMware reported the following error: %2!s!. For more information, see the debug log %3!s!. If necessary, contact arcserve support.Unable to read from VMDK file %1!s!. VMware reported the following error: %2!s!. For more information, see the debug log %3!s!. If necessary, contact arcserve support.VM recovery job was unable to read the D2D backup session. The session may be inaccessible or corrupt. To  correct the problem, submit a new backup job using the new backup session. If the problem persists, contact arcserve support.An error occurred while reading source session. For more information, see the VM recovery logs located in %1!s!\Logs. Additionally, see Troubleshooting in the User Guide.wUnable to create directory %1!s! in the guest operating system on the virtual machine. VMware VIX reports error: %2!s!.wUnable to delete directory %1!s! in the guest operating system on the virtual machine. VMware VIX reports error: %2!s!.Changed block tracking was enabled with virtual machine snapshots present. The full backups will now include the used and unused blocks of data contained in the VMDK files of the virtual machine.The application will backup all the blocks for VMDK %1!s! because VMware cannot retrieve the used blocks if there are snapshots when enabling changed block tracking on the virtual machine.Changed block tracking was reset with virtual machine snapshots present. The full backups will now include the used and unused blocks of data contained in the VMDK files of the virtual machine.The VMDK files of the virtual machine were opened for backup. Migration using Storage vMotion cannot be performed until the backup completes or is canceled.The VMDK files of the virtual machine cannot be opened. The VMDK files may be migrating using Storage vMotion or a maintenance task is in progress. The backup of the virtual machine cannot continue until the current operation completes.2The VMDK files of the virtual machine were closed.VMware cannot retrieve the used blocks of data for full backups when changed block tracking was reset while virtual machine snapshots were present.VMware cannot retrieve the used blocks of data for full backups when changed block tracking was enabled while virtual machine snapshots were present.BBacking up virtual machine %1!s! on %2!s!. <VMInstance UUID=%3!s!>VMware does not support application-level quiescing of Windows 2008 and later virtual machines with dynamic disks that are running on ESX server 4.1 or later.VESX server %1!s! is in maintenance mode. Try backup later after maintenance completes.rThe user-defined transport mode %1!s! is not available. The backup job will use the best available transport mode.wThe snapshot of the virtual machine cannot be deleted at this time; it will be deleted the next time a backup job runs.The VMDK IO cleanup operation failed. VMware reported the following error: %1!s!. For more information, see the debug log %2!s!. If necessary, contact arcserve support.BAn unknown error has occurred. See the VDDK debug log file: %1!s!.The application with process Id %1!d! failed to respond within %2!d! second(s). Please stop the process and retry running the job.CHECKSUM VALUE DOES NOT MATCHINCORRECT DISK NAMEINCORRECT DISK FILEINCORRECT DESCRIPTION FILEINCORRECT METADATA FILEDESTINATION NOT FOUNDINCORRECT COMMANDSPARSE FORMAT NOT SUPPORTEDMAXIMUM FILE SIZE EXCEEDEDINVALID FOOTERINVALID PARAMETERINVALID DISK TYPEROOLBACK FAILEDCAN NOT FOUND PARENT DISKCAN NOT FOUND DISKMEMORY NOT ENOUGHINVALID DESTINATIONAttempt to open file %1!s! failed. Another process (such as Arcserve Replication and High Availability) may currently be using this file.WOperations (create, close, read, write) on file %1!s! failed, Error code:%2!d!,[%3!s!]."An invalid data block is detected.PREFLIGHT CHECK (PFC) FAILEDeDuring the merge operation, the folder rename from %1!s! to %2!s! failed. Error code: %3!d!, [%4!s!].+An invalid parent disk [%1!s!] is detected.bDuring the merge operation, failed to rename file from %1!s! to %2!s!. Error code: %3!d!, [%4!s!].8Failed to delete file %1!s!. Error code: %2!d!, [%3!s!].`During the merge operation, failed to move file from %1!s! to %2!s!. Error code: %3!d!, [%4!s!].3Failed to merge virtual disk. System error=[%1!s!].5Failed to merge virtual disk. Internal error=[%1!s!].INVALID ENCRYPTION INFORMATIONFAILED TO ENCRYPTPURGE IS NOT ALLOWEDFAILED TO UNCOMPRESSUNKNOWN INTERNAL ERRORFAILED TO INIT DISK FORMAT INVALID DATA STORE CONFIGURATIONFailed to merge data.-Failed to write data. Internal error=[%1!s!].+Failed to write data. System error=[%1!s!].,Failed to read data. Internal error=[%1!s!].*Failed to read data. System error=[%1!s!].8Failed to open the virtual disk. Internal error=[%1!s!].6Failed to open the virtual disk. System error=[%1!s!].*FAILED TO ROLLBACK THE PREVIOUS MERGER JOBFAILED TO DECRYPTAn Intel(R) 82574 network adapter has been detected. The TCP segmentation offload (TSO) feature (also known as the Large Send Offload) of this adapter, has been disabled to avoid any potential data corruption.An Intel(R) 82574 network adapter has been detected. This adapter can cause data corruption. Change the network adapter or manually disable the TCP segmentation offload (TSO) feature of this adapter (also known as Large Send Offload).PAJob crashed.The system is shutting down.YCurrent job will be canceled because another job with the same type is currently running.PATaking snapshot ...Creating virtual disks ...Backing up volumes ...Deleting snapshot ...Created new session %1!d!.Backup job failed."Backup job completed successfully.$Beginning backup of volume %1!s! ....Backup of volume %1!s! completed successfully.Backup of node %1!s! started./Will perform backup of %1!d! volume(s) - %2!s!.Dump volume %1!s! metadata."Dump volume %1!s! metadata failed.%Unable to execute command. (EC=%1!s!)BJob Aborted.  Generic Task process could not be stopped.(EC=%1!s!)8Job Aborted.  Generic Task process successfully stopped.Job name: %1!s!.Full backupIncremental backup
Verify backupCompression level is noneCompression level is standardCompression level is maximumIConverting to a full backup because virtual disk format has been changed.*Converting the first job to a full backup.*Local destination volume %1!s! is skipped.RAID 5 volume %1!s! is skipped.;Non NTFS volume %1!s! is skipped, the file system is %2!s!.&Volume %1!s! hosted in VHD is skipped.XFailed to locate backup destination. (Path=[%1!s!], Username=[%2!s!], EC=[%3!d!: %4!s!])6Failed to write to virtual disk. System error=[%1!s!].5Estimated backup data size. Volume=%1!s!, size=%2!s!.'Elapsed time. Volume=%1!s!, time=%2!s!.Backup destination is %1!s!.iBackup job processed total of %1!s! of source data in %2!s!, and the backup job throughput was %3!s!/Min.Backup job canceled.XConverting to a verify backup because system was just restored from Bare Metal Recovery.IConverting the first job after installation / upgrade to a verify backup.1Collect Bare Metal Recovery information finished.mCollect Bare Metal Recovery information failed, this recovery point cannot be used to do Bare Metal Recovery.SFound data CRC error on volume %1!s! within offset %2!I64d! and length %3!d! bytes. Started transaction log pruning.9Purged Microsoft SQL Server log for database %1!s!\%2!s!.2Purged Microsoft Exchange log under %1!s! (%2!s!).4Job Pre-Command has exit code %1!d!.  Abort the job.pDelay to merge session because virtual disks are being read for catalog generation of Exchange Granular Restore.:Failed to create virtual disk %1!u!. System error=[%2!s!].8Failed to write to virtual disk. Internal error=[%1!s!].PA<Failed to create virtual disk %1!u!. Internal error=[%2!s!].TLicense failure. Please contact your account representative to obtain a new license.KMerge Sessions Failed. Retention count setting=%1!d!, System error=[%2!s!].-Executing the pre backup command. (CMD=%1!s!)0Executing the post snapshot command. (CMD=%1!s!).Executing the post backup command. (CMD=%1!s!)"Removable volume %1!s! is skipped.FFailed to locate backup destination. (Path=[%1!s!], EC=[%2!d!: %3!s!])_Converting to a verify backup because unexpected shutdown or error occurred during last backup.EUser configured value for the destination threshold has been reached.unrecognizeddThe %1!s! is encrypted by BitLocker Drive Encryption, please unlock it before submitting backup job.=Compression reduced the size by %1!d!%2!c!%3!02d!%% to %4!s!.GThere is no Bare Metal Recovery to Original license in current machine.QThere is no Bare Metal Recovery to Alternate Hardware license in current machine.MMerge Sessions Failed. Retention count setting=%1!d!, Internal error=[%2!s!].Your current licensing only supports block-level incremental (BLI) backups at an minimum interval of one per hour. To perform more frequent BLI backups (as often as every 15 minutes), please upgrade your licensing.The current licensing will cause Agent to automatically convert your scheduled incremental backup to a full backup if there has not been a full backup performed during the last 7 days. To avoid forced full backups, please upgrade your licensing.The current licensing will cause Agent to automatically convert your scheduled verify backup to a full backup as there has not been a full backup performed during the last 7 days. To avoid forced full backups, please upgrade your licensing.~Free space on %1!s! is too low and the backup may fail. Free up some space or change the backup destination to another volume.Will perform a Verify Backup of volume %1!s! because the last system shutdown was unexpected or the removable device is reconnected.Convert Incremental Backup to a Verify Backup because the last system shutdown was unexpected or some removable devices are reconnected.#Source volume %1!s! is unavailable.+No source volumes are available for backup.ESession %1!d! is purged because the retention count %2!d! is reached.HFailed to read shadow copy of volume %1!s!, the system error is [%2!s!].|The merging sessions process has been canceled, the current session count is %1!d! and the retention count setting is %2!d!.Source volume %1!s! is skipped because it resides on a disk larger than 2TB. Please use a compressed virtual disk to support a disk larger than 2TB. Total backup data size is %1!s!.Failed to write to virtual disk. Internal error=[%1!s!]. Please check disk space of the backup destination volume, or the network connection to the remote backup destination folder.Encryption is not enabled.Encryption type is AES-128.Encryption type is AES-192.Encryption type is AES-256.;Convert to full backup because encryption password changed.7Convert to full backup because encryption type changed.VFailed to initialize performance counter module. Throughput data may not be available.-Found invalid session. (Session Path=[%1!s!])7Failed to purge invalid session. (Session Path=[%1!s!]):Purge invalid session successfully. (Session Path=[%1!s!])lFailed to clear force full backup flag from Registry, please manually remove registry item HKLM\%1!s!\%2!s!.~Convert to full backup according to force full backup flag. For example, update Virtual Conversion setting will set this flag.XVMware Virtual Disk Development Kit not found! Please check if it is installed properly.sThe 64 bit binaries are not found in VMware Virtual Disk Development Kit! Please check if it is installed properly.KOnly VMware Virtual Disk Development Kit 1.2 or later version is supported!?VMware VIX not found! Please check if it is installed properly.yVMware VIX version is lower than 1.13.3. The application cannot perform application log truncation and Pre/Post commands.TGenerate Exchange Granular Restore catalog automatically after each backup: Enabled.UGenerate Exchange Granular Restore catalog automatically after each backup: Disabled.JConverting to full backup because disk has been changed since last backup.5Get volume information from virtual machine Guest OS.?Could not get volume information from virtual machine Guest OS.*Failed to create virtual machine snapshot.:Get application information from virtual machine snapshot.Could not get application-related information from the virtual machine snapshot. Your backup may not contain application-specific sessions, such as Microsoft SQL Server or Exchange Server. Check the status of the Microsoft Volume Shadow Copy service in the Guest Operating System.Backing up virtual disk %1!s!.'Finished backing up virtual disk %1!s!.$Failed to backup virtual disk %1!s!.-Backup source virtual machine %1!s! at %2!s!.4Purge Microsoft SQL Server log from virtual machine.>Could not purge Microsoft SQL Server log from virtual machine.9Purge Microsoft Exchange Server log from virtual machine.CCould not purge Microsoft Exchange Server log from virtual machine.PAVMware Tools is not installed.@The version of VMware Tools is out-dated and should be upgraded.VMware Tools is up to date.'Unable to check status of VMware Tools.Virtual machine is powered off.Virtual machine is powered on.Virtual machine is suspended.3Unable to determine power state of virtual machine.Convert Incremental Backup to a Verify Backup because the virtual machine snapshots either changed from the last backup job or needs consolidation.&Begin to backup virtual machine %1!s!.*Finished backing up virtual machine %1!s!.'Failed to backup virtual machine %1!s!.Skipped volume %1!s!.The application cannot enable changed block tracking on the virtual machine because there are snapshots on the virtual machine. To correct this problem, delete the snapshots and then resubmit the backup.nCould not take snapshot of the virtual machine. ESX Server/vCenter Server reported the following error: %1!s!.Merge session is skipped because the session is locked by another operation. Verify if any recovery points are mounted and dismount them.
This is a No Charge Edition of arcserve UDP for workstations, and as a result is running in a limited capability mode. To upgrade to the arcserve UDP Workstation Edition with full functionality, please visit arcserve.com or contact your partner/sales representative.The No Charge Edition of arcserve UDP for workstation doesn't support RPS destination, please change backup destination to non-RPS destination.1Starting copy of recovery point created on %1!s!.(Copy recovery point from %1!s! to %2!s!.Copy recovery point finished.Copy recovery point failed.,Copy recovery point for volume %1!s! failed./Copy recovery point for volume %1!s! succeeded.Copy session meta data success.Copy catalog files failed. Copy session block files failed.Copy recovery point canceled..Copy file %1!s! to %2!s! failed, Reason:%3!s!.V%1!s! does not have enough free space. Please make sure you allocate %2!s! free space.a%1!s! may be not have enough free space. Please make sure you allocate at least %2!s! free space.Open metablock failed.Read metablock failed.Open virtual disk %1!s! failed.Read data failed.Seek file pointer failed.Write data failed. %1!s!+Failed to copy recovery point. Error:%1!s!.?Failed to write data to the destination folder, will retry now. %1!s! for copied recovery point.OTotal copied data %1!s!, Elapsed time %2!s!, Average read throughput %3!s!/Min.qTotal copied data %1!s!, Elapsed time %2!s!, Average throughput %3!s!/Min, Space saved using compression:%4!s!%%.1The recovery point being copied is not encrypted.=The encryption type for the copied recovery point is AES-128.=The encryption type for the copied recovery point is AES-192.=The encryption type for the copied recovery point is AES-256.FConverting to verify backup because last successful backup is missing.This is an upgrade from the previous release. Use the Create Boot Kit utility to create a bootable BMR ISO image that is used to perform a Bare Metal Recovery (BMR) for any recovery points that were created from the current release.PAJUnable to lock session %1!u!. The session may have been merged or removed.Unable to lock session %1!u!.iVirtual disk %1!s! does not contain volume information. The next copy session will skip the virtual disk.LIt is not ready for backup because previous merge operation is not complete.pBackup is skipped because session %1!u! is being merged. A makeup job will be scheduled for this skipped backup.5The session on %1!s! was locked by a user from %2!s!.<Failed to read data from virtual disk. System error=[%1!s!].>Failed to read data from virtual disk. Internal error=[%1!s!].Failed to read data from virtual disk. Internal error=[%1!s!]. Please check disk space of the backup destination volume, or the network connection to the remote backup destination folder.BNon NTFS / ReFS volume %1!s! is skipped, the file system is %2!s!.bThe size of volume %1!s! (%2!s!) was changed from %3!s! to %4!s! while the backup job was running.Failed to get the snapshot bitmap for volume %1!s!(%2!s!). This can be caused by not enough space for the storage area of the snapshot. Check the application/system event log for more information.nSkip copying disks (%1!s!) from the copy recovery point job. These disks were configured using storage spaces.aFailed to locate copy of recovery point destination. (Path=[%1!s!], Username=[%2!s!], EC=[%3!d!])^Convert the current backup to a Full Backup because a new data store has been used for backup.Convert the current backup to a Full Backup because the backup destination has been changed from local disk or shared folder to a data store.Convert the current backup to a Full Backup because the backup destination has been changed from a data store to local disk or shared folder.The current backup job is converted to a Full Backup because a new data store has been used for backup or the backup proxy machine has been changed.The current backup job is converted to a Full Backup because the backup destination has been changed from a data store to local disk or shared folder or the backup proxy machine has been changed.The current backup job is converted to a Full Backup because the backup destination has been changed from local disk or shared folder to a data store or the backup proxy machine has been changed.oCopy recovery point from Arcserve UDP Recovery Point Server [%1!s!], data store [%2!s!], node [%3!s!] to %4!s!.Windows Failover Cluster share disk status change detected since last successful backup. A full backup of volume %1!s! will be performed.PAUnable to log in to the guest operating system on the virtual machine. ESX/vCenter reports error: %1!s!. This could also happen if your VMware Tools is out-of-date.;Metadata for the Microsoft SQL Server writer was not found.@Metadata for the Microsoft Exchange Server writer was not found.Warning: This backup session cannot be used for application level restore. For virtual machines running client versions of Microsoft Windows operating systems (XP, Vista, 7, 8, 8.1), VMware snapshot technology does not generate application meta-data required to perform application-level restores. If you require application-level restores and are running the client versions of Microsoft Windows operating systems listed, perform a local Agent backup.VMware VIX is not installed. The application cannot perform application log truncation and Pre/Post commands without VMware VIX.Microsoft Exchange Server logs will be purged inside virtual machine %1!s! with file pattern %2!s! until log sequence number %3!I64d! is reached.YMicrosoft SQL Server logs will be purged inside virtual machine for database %1!s!\%2!s!.RFailed to save the catalog job script. (This failure will not affect backup jobs).Unable to identify the blocks that were used or changed on the virtual machine. Please check VMware logs for more details. Performing backup of all blocks.OThe application was unable to retrieve information about virtual machine %1!s!.,Failed to create metadata of backup session.dThe backup failed because changed block tracking cannot be enabled on the specified virtual machine.EA license check failure occurred on virtual machine ESX server %1!s!.1Virtual machine ESX server %1!s! is not licensed.PA9The application did not back up unformatted volume %1!s!.BThe application did not back up the metadata for FAT volume %1!s!.8The application did not back up iSCSI disk volume %1!s!.qThe application did not back up volume %1!s! because the virtual disk where the volume resides was not backed up.|Unable to backup virtual disk %1!s! because it is an independent disk. VMware does not support backing up independent disks.Unable to back up virtual disk %1!s!. The virtual disk is configured in physical compatibility mode raw device mapping (RDM). VMware does not support backing up virtual disks that are configured as physical compatibility mode RDM.Cannot open VMDK file.DLicense Check Failure. The %1!s! license is invalid in this machine.Transport mode is %1!s!.No sufficient free space on the destination %1!s! to merge sessions %2!u! and %3!u!. Merge will be skipped till enough space is freed for the destination.bUnable to check free space for the destination %1!s!. Will skip to merge sessions %2!u! and %3!u!.0Connected to ESX or vCenter Server successfully.Cannot connect to ESX or vCenter Server. If you are connecting to an ESX server, verify that the VMware Management Service is running on that server. If you are connecting to a vCenter Server, verify that the vCenter Service is running on that server.Cannot connect to ESX or vCenter Server. The server is unreachable. Verify that the VMware Management Service or vCenter Service is running, the server is connected to the network and the credentials are valid.NCannot connect to ESX or vCenter Server. Credentials are invalid or incorrect.Failed to read VMDK. Check network connection between the Proxy and ESX or vCenter Server. If you are using a SAN, check network connection between the Proxy and SAN. Resubmit the backup job.Backup job is skipped.Virtual disk %1!s! is configured as a virtual compatibility raw device mapping (vRDM) disk and will be backed up as full disk. VMware cannot retrieve the used blocks of disks that are configured as vRDM. If the job is a full backup, the entire disk is included in the backup session. If the job is an incremental backup, only the changed blocks of data are included in the backup session.The backup cannot continue at this time. The application cannot delete the data related to previous failed backup session because the previous backup job stopped unexpectedly. The system error is %1!s!. The application will correct the problem the next time a backup job runs.ZThe ESX Server version is %1!s!. The application requires ESX Server version 4.0 or later.The virtual machine version is %1!s!. The application requires virtual machine with version 7 or later to back up the virtual machines.The application must reset changed block tracking. The application will perform a verify backup operation instead of an incremental backup operation.GResetting changed block tracking. Performing backup of all used blocks.The application cannot reset changed block tracking because there are snapshots present. To reset changed block tracking, delete the snapshots and then resubmit the backup job.oThe application cannot reset changed block tracking because it cannot create a snapshot of the virtual machine.qThe application cannot reset changed block tracking because it cannot delete the snapshot of the virtual machine.The application cannot delete the snapshot of the virtual machine. ESX Server/vCenter Server reports the following error: %1!s!.cVirtual disk %1!s! is located in an NFS data store and will be backed up as full disk. VMware cannot retrieve the used blocks of disks that are located in NFS data store. If the job is a full backup, the entire disk is included in the backup session. If the job is an incremental backup, only the changed blocks of data are included in the backup session.;Backup destination for %1!s! (VM Name is "%2!s!") is %3!s!.+Backup destination for VM "%1!s!" is %2!s!.YConverting to a Verify backup because some data blocks can be corrupted at session %1!u!.Unable to find snapshot for volume [%1!s!]. Check the Volume Shadow Copy Service (VSS) related Windows event log for more details.(The file system of volume %1!s! is ReFS.>The file system of volume %1!s! is Deduplication-Enabled NTFS.DThe application did not back up the metadata for FAT32 volume %1!s!.TThe bitmap file for file system %1!s!, volume %2!s! has been successfully generated.DThe application did not back up the metadata for RAID5 volume %1!s!.The application did not back up the metadata for volumes that were built on the storage pool. As a result, you cannot perform a file-level restore for these volumes.PThe job [PID: %1!d!] name is %2!s! and the source virtual machine name is %3!s!.KConvert the first job after an operating system upgrade to a Verify backup.RUnable to back up the sub session metadata for volume %1!s!, System error=[%2!s!].oFailed to get the bitmap for volume %1!s! (%2!s!). Check the application/system event log for more information.GThe backup operation is enforced to use NBD transport mode for VDDK IO.Virtual disk %1!s! was added recently, or, the overall size of the virtual disk changed. Host-Based VM Backup will now perform a full backup of the virtual disk.The system volume [%1!s!] is configured as a mirrored volume. As a result, the system will fail to boot if you are attempting to restore data using BMR. ^Converted to a Verify Backup. Failed to generate the file system catalog for the last session.PA'The restore job completed successfully.Restore job failed.6Writer does not allow restore to alternative location.Restore job was canceled.NFailed to locate restore source. (Path=[%1!s!], Username=[%2!s!], EC=[%3!d!]).Start Restore Operation.Restore files from %1!s!.Restore to original location.9Restore to alternate location. (Destination Path=[%1!s!])Restore options:YesNo.Conflict resolution: overwrite existing files.DConflict resolution: overwrite existing files, replace active files.Create root directory: %1!s!.k%1!d! directories %2!d! files(%3!s!) restore to disk, elapsed time %4!s!, restore job throughput %5!s!/Min.PA*Dump file only. (Destination Path=[%1!s!]) Restore to alternative location. Restore %1!s! as %2!s! at %3!s!.=Cannot do restore now because merging session is in progress.UFailed to open session. (EC=[%1!s!], Session Number=[%2!u!], Session Folder=[%3!s!]).\Failed to restore file because unable to find sub-session for this file. (File Path=[%1!s!])Restore job is incomplete.Restoring files from an unlabeled and un-mounted volume to the original location is not supported. Skipping restore files from such volume. (Volume=[%1!s!])Merge Sessions Failed.RFailed to locate restore destination. (Path=[%1!s!], Username=[%2!s!], EC=[%3!d!])!Mapped %1!s! to %2!s! internally.%Unmapped %1!s! from %2!s! internally."Conflict resolution: rename files.&%1!d! Directories %2!d! Files Skipped.)Conflict resolution: skip existing files.JNo more drive letters are available to mount the remote destination %1!s!.PA\Unable to lock session %1!u! for restore. It is possible session has been merged or removed.\Files or directories were skipped. See %1!s! for the files or directories that were skipped.cRestore files from Arcserve UDP Recovery Point Server [%1!s!], data store [%2!s!], Session [%3!d!].The file system catalog was not created for this recovery point. As a result, this recovery point will be mounted as a volume for recovery.The file system of the volume is NTFS and it enables Windows Data Deduplication feature. As a result, it will be mounted as a volume for recovery.;The option, Overwrite existing virtual machine, is enabled.?The option, Power on the recovered virtual machine, is enabled.IThe option, Recover virtual machine to its original location, is enabled. The destination server is %1!s!..The destination virtual machine name is %1!s!.=The source session path is %1!s! and session number is %2!u!.Source session initializing./Initializing virtual machine manager libraries.9Virtual Machine %1!s! already exists at ESX server %2!s!.4The virtual machine was renamed to %1!s! from %2!s!.sVirtual machine %1!s! already exists at ESX server %2!s!. To recover this VM, you must enable the Overwrite option.*Create new virtual machine. (Name=[%1!s!])Recovering virtual disks.=VM recovery job was unable to create the new virtual machine. Failed to recover virtual disks."Finished recovering virtual disks.PAERecovery succeeded. Delete the original virtual machine %1!s!(%2!s!).&Powering on recovered virtual machine.4Delete the unsuccessfully recovered virtual machine.The virtual machine recovery did not complete successfully. The virtual machine was renamed back to its original name (from %1!s! to %2!s!).HA virtual machine named %1!s! already exists on the target server %2!s!.)Virtual Machine will be restored to %1!s!9The protocol used is %1!s! and port number used is %2!d!.oThe total size of the recovered data %1!s!, the elapsed time is %2!s!, and the average throughput is %3!s!/Min.0The virtual machine was powered on successfully.OUnable to power on recovered virtual machine. The VM may already be powered on.%1!s! is missing from the copied backup destination and will be skipped during VM recovery. If you wish to include this file in the recovery process, perform Recover VM from the original backup destination.AVirtual disk #%1!u! recovery finished using transport mode %2!s!.VM recovery job was unable to create the new virtual machine. The ESX/vCenter Server system reported the following error: %1!s!VM recovery job was unable to create the new virtual machine. The ESX/vCenter Server system reported the following error: An unknown error occurred.&Virtual Machine was configured with Virtual Distributed Switch during backup. The recover VM operation will skip the network configuration associated with Virtual Distributed Switch. Please add the network configuration of Virtual Distributed Switch manually after the VM recovery is completed.NVM direct restore job will be started,target machine:%1!s!,host machine:%2!s!.PAFVM direct restore job failed, target machine:%1!s!,host machine:%2!s!.BVM direct restore job succeed on machine:%1!s!,host machine:%2!s!.2VM direct restore failed to connect VM host:%1!s!.-VM direct restore failed to connect VM:%1!s!.dVM direct restore failed, the target VM:%1!s! is power off or VM tools out of date on VM host %2!s!.KVM direct restore job is canceled, target machine:%1!s!,host machine:%2!s!.LThe VM recovery operation is enforced to use NBD transport mode for VDDK IO.+Unable to delete the virtual machine %1!s!.Some network adapters are not assigned to any of the available networks. The network adapters will be restored as part of the VM recovery, but not connected.Failed to notify the host that a backup job is going to start. The ESX/vCenter Server system reported the following error: %1!s!The Virtual Flash Resource (%1!s!) on the target ESX host (%2!s!) is not sufficient for the virtual disks' Virtual Flash Read Cache (%3!s!) . The VM (%4!s!) cannot be powered on. Change the Virtual Flash Read Cache settings after the recovery job is done.There is no Virtual Flash Resource on the target ESX host (%1!s!). As a result, the Virtual Flash Read Cache of the VM (%2!s!)'s virtual disks will be set to 0.mRestore virtual machine from Arcserve UDP Recovery Point Server [%1!s!], data store [%2!s!], Session [%3!d!].'Failed to rename virtual machine %1!s!.8Delete the original virtual machine %1!s! on host %2!s!.Unable to restore the instance UUID for the new virtual machine because another virtual machine named [%1!s!] with the same instance UUID already exists in the inventory.PA(Begin to restore Active Directory items.+Finished to restore Active Directory items.PRestored %1!d! objects %2!d! attributes, skipped %3!d! objects %4!d! attributes.&Open Active Directory database(%1!s!).PA=The option to allow restoring of Renamed Objects is selected.AThe option to allow restoring of Renamed Objects is not selected.;The option to allow restoring of Moved Objects is selected.?The option to allow restoring of Moved Objects is not selected.=The option to allow restoring of Deleted Objects is selected.AThe option to allow restoring of Deleted Objects is not selected.bThe backup destination you specified is currently in use, please enter another backup destination.ZFailed to mount volume to the directory. The directory must be NTFS volume or ReFS volume.YThe selected drive letter is already in use by another user. Select another drive letter.RVolume[%1!s!] from recovery point[%2!s!] has been mounted to [%3!s!] successfully.\Failed to mount volume[%1!s!] from recovery point[%2!s!] to [%3!s!] with error %4!d![%5!s!].0Volume [%1!s!] has been dismounted successfully.:Failed to dismount volume [%1!s!] with error %2!d![%3!s!].mFailed to mount the specified recovery point because another (backup/catalog/merge) operation is in progress.sThe driver used to mount the recovery point to the volume is not functioning. Verify that it is installed properly.^The selected recovery point is invalid. Ensure that a valid full recovery point is accessible.Volume [%1!s!] from Arcserve UDP Recovery Point Server [%2!s!], data store [%3!s!], Session [%4!d!] has been successfully mounted to drive [%5!s!].Failed to mount volume [%1!s!] from Arcserve UDP Recovery Point Server [%2!s!], data store [%3!s!], Session [%4!d!] to drive [%5!s!] with error %6!d![%7!s!].PARestore Item %1!d!: %2!s!8Invalid node type. Client Agent cannot continue the job.(Skip file/dir <%1!s!>. Path is too long.Source volume is empty*Failed to locate the $FILE_NAME attribute.TFailed to allocate memory to read a block of data. An IndexAlloc Error has occurred.Failed to map an index block to the correct volume block. An IndexAlloc Error has occurred. Cannot locate VCN. (VCN=[virtual cluster number])*Invalid index allocation header signature.BSetFilePointer (Offset=[%1!lu!, %2!lu!], File=[%3!s!], EC=[%4!d!])FFailed to locate a file record segment in the Master File Table (MFT).ZFailed to locate the security attribute for a file record segment from the attribute list.EFailed to move the file. (Source=[%1!s!], Target=[%2!s!], EC=[%3!d!])VFailed to open the directory to set compression level. (Directory=[%1!s!], EC=[%2!d!])RFailed to set compression level for the directory. (Directory=[%1!s!], EC=[%2!d!])*Unknown file system. (File System=[%1!s!])PA2DeCompressBuffer Error. (EC=[%1!d!], File=[%2!s!])#Skipping file.(File=[%1!s!]). %2!s!4Invalid partition type for the drive.(Drive=[%1!s!])4Failed to read the drive. (Drive=[%1!s!],EC=[%2!d!]),GetVHDSector failed for file. (File=[%1!s!])9Failed to write to the Image Meta Data file. (EC=[%1!d!])0Failed to write to Dir Struct file. (EC=[%1!d!])5Failed to write to Cluster Mapping File. (EC=[%1!d!])9Error restoring file fragment. (EC=[%1!d!], File=[%2!s!])UFailed to locate the reparse point for a file record segment from the attribute list.YFailed to restore the encrypted file. (EC=[%1!d!], File for which restore failed=[%2!s!])XFailed to restore the reparse point. (EC=[%1!d!], File for which restore failed=[%2!s!])XFailed to restore the object id. (EC=[%1!d!], File for which the restore failed=[%2!s!])EFailed to locate the logged utility stream for a file record segment.File level restore is not possible for the RAID volume. Only RAW mode backup will be available for this volume. (Volume=[%1!s!]) 8An unexpected exception error occurred in vmdkimgdll.dlljSystem files were skipped. If necessary, you can use the Bare Metal Recovery (BMR) option to restore them.[Insufficient space for restore. Free Space Required %1!d! KB, Free Space Available %2!d! KBCannot freeze Backup Volume: Unable to create the Preview file because no drive has sufficient free space or a Disk Inactivity Period Timeout error occurred.-Cannot open drive.(Drive=%1!s!, Error=%2!ld!)Problems with the file system were discovered. Please run CHKDSK with the /F (fix) option to correct these problems and then perform a Full Backup.!The Drive [%1!s!] does not exist.mInsufficient space for restore on Local Disk %1!s! ,Free Disk Space=%2!I64u! MB, Total Disk Space=%3!I64u! MBFile level restore is not supported for the (Volume=[%1!s!]) because RAID/Striped volumes have more than one disk extent per disk.OFailed to write to Cluster Mapping File. Not enough free space on volume %1!s!.IFailed to write to Cluster Mapping File. Not enough free space on volume.Application restore begins..."Application successfully restored!(Application restore failed. (EC=[%1!d!])Application restore finished.-Begin to stop service. (Service Name=[%1!s!])4Service successfully stopped! (Service Name=[%1!s!]):Failed to stop service. (EC=[%1!d!], Service Name=[%2!s!]).Begin to start service. (Service name=[%1!s!])4Service successfully started! (Service name=[%1!s!]);Failed to start service. (EC=[%1!d!], Service Name=[%2!s!])3Begin to dismount database. (Database Name=[%1!s!])9Database successfully dismounted! (Database Name=[%1!s!])@Failed to dismount database. (EC=[%1!d!], Database Name=[%2!s!])0Begin to mount database. (Database Name=[%1!s!])6Database successfully mounted! (Database Name=[%1!s!])=Failed to mount database. (EC=[%1!d!], Database Name=[%2!s!])PAeSelect writer(Writer Name=[%1!s!], Writer ID=[%2!s!], Writer Instance Name=[%3!s!]) to be restored...BWriter(Name=[%1!s!], ID=[%2!s!]) does not exist or is not running.HComponent(Logical Path=[%1!s!], Component Name=[%2!s!]) cannot be found.SWriter(Name=[%1!s!], ID=[%2!s!]) will be excluded because no component is selected.9Begin to restore master database. (Instance Name=[%1!s!])>Master database successfully restored! (Instance Name=[%1!s!])FFailed to restore master database! (EC=[%1!d!], Instance Name=[%2!s!])Restore to original location.Restore to alternate location.Pre-Restore stage...Post-Restore stage..."Restoring selected files succeeds!,Restore of the selected files is incomplete.{Writer(Name=[%1!s!], ID=[%2!s!]) has a bad status, please refer to Windows Event log for more details. (Status=[0x%3!08x!])Cannot find any application writer running in system. Start writer service or re-register COM components may help resolve this problem.#Including volume %1!s! in snapshot.The creation of snapshot is in progress, and only one snapshot creation operation can be in progress at one time. retry after %1!u! seconds-Start snapshot set. (Snapshot Set ID=[%1!s!])Failed to start snapshot set.DVolume %1!s! has been added into snapshot set, (Snapshot ID=[%2!s!])kThe provider returned an unexpected error code. This can be a transient problem. Retry after %1!u! seconds.xThe provider was unable to perform the request at this time. This can be a transient problem. Retry after %1!u! seconds.Error during the last asynchronous operation, please refer to Windows Event log for more details. (EC=[0x%1!08x!], MSG=[%2!s!])Prepare for backup stage...Failed to prepare for backup.(Create snapshots for selected volumes.../Failed to create snapshot for selected volumes.;Save writer metadata. (Metadata Name=[%1!s!], Size=[%2!u!]).Failed to save metadata. (Writer Name=[%1!s!])SQL writer service is not installed, SQL server will be skipped to back up. If you want to back SQL server up, please install SQL writer and make sure it is running.GSQL writer service will be started automatically to back up SQL server.0Unable to find recovery database. (Name=[%1!s!])PAXMaster database should be restored after SQL server relevant services have been stopped.AApplication restore option is not licensed. (Option Name=[%1!s!])~Writer has been skipped from this backup job because the application protection feature is not licensed. (Writer Name=[%1!s!])gWriter cannot be restored because application protection feature is not licensed. (Writer Name=[%1!s!])ZApplication backup will be skipped because application protection feature is not licensed._Application restore cannot be performed because application protection feature is not licensed.CApplication restore option has been licensed. (Option Name=[%1!s!])JLicence check for application restore option passed. (Option Name=[%1!s!])jVSS Component [%1!s!] is not included in backup because related volume [%2!s!] is not part of this backup.~Skipping to restore database because target SQL server instance does not exist. (Database Name=[%1!s!], Instance Name=[%2!s!])AUnable to query information from Active Directory, Username=%1!s!KThe mailbox database "%1!s!" is being restored to recovery database "%2!s!"GThis Exchange restore operation can only be performed on an active nodeSnapshot storage area for volume does not have enough free space. The snapshot storage area will be switched to another volume to continue the backup. (Storage Area=[%1!s!], Volume Name=[%2!s!])Restore option: Dump Files.2Restore option: Dump Files (Replay database logs).-Restore option: Restore to original location..Restore option: Restore to alternate location.,Restore option: restore exchange to RSG/RDB.+Dismount/Mount database option is selected./Dismount/Mount database option is not selected.4Restore SQL database %1!s!\%2!s!, Destination=%3!s!.6Restore SQL database %1!s!\%2!s! to original location.MRestore SQL database %1!s!\%2!s!, New Database Name=%3!s!, Destination=%4!s!.ARestore Exchange storage group/database %1!s!, Destination=%2!s!.CRestore Exchange storage group/database %1!s! to original location.[The storage group/mailbox database "%1!s!" is being restored to the recovery storage group.The system or provider has insufficient storage space. Try again after deleting any old or unnecessary persistent shadow copies or adjusting the snapshot storage area.vThe system was unable to hold I/O writes. This may be caused by a transient problem. Please retry after %1!u! seconds.The system failed to freeze the Distributed Transaction Coordinator (DTC) or the Kernel Transaction Manager (KTM). Please retry after %1!u! seconds.The system failed to thaw the Distributed Transaction Coordinator (DTC) or the Kernel Transaction Manager (KTM). Please retry after %1!u! seconds.LThe provider encountered an error that requires you to restart the computer.6The caller is out of memory or other system resources.DThe service "%1!s!" must be started in order to complete SQL backup.!Begin to restore master database."Begin to restore system databases. Begin to restore user databases.+There is no database needed to be restored.7Select SQL database to restore. (Database Name=[%1!s!])OExchange writer has been disabled, Whole Exchange server will not be backed up.ZExchange information store service is not running. Active databases will not be backed up.XExchange replication service is not running. Replicated databases will not be backed up.The writer reports a retryable problem. Retry after %1!u! seconds. If the writer continues to return the error after several retries, try restarting the service that hosts the writer._The writer "%1!s!" has been skipped during the backup process because it is in an error status.@SQL server is skipped because it is not supported on Windows XP.3Application restore is not supported on Windows XP.CVolume cannot be added into snapshot set because it does not exist./Volume %1!s! cannot be added into snapshot set.PAUnable to load VSS metadata because the Microsoft VSS on the current system is not compatible with the one on the original backed up system.rVolume shadow copy provider specified is not registered. Please ensure all VSS relevant components are registered.FMicrosoft Exchange Server Mailbox Database: [%1!s!] will be backed up.Restore Exchange storage group/database [%1!s!] to its original location is skipped because it does not exist in the Active Directory.kExchange storage group/database [%1!s!] has been restored to its original location, but failed to mount it.LMicrosoft Exchange Server Public Folder Database: [%1!s!] will be backed up.NMicrosoft Exchange Server Mailbox Database: [%1!s!] is not included in backup.TMicrosoft Exchange Server Public Folder Database: [%1!s!] is not included in backup.Restore of the Microsoft Exchange storage group/database [%1!s!] to its original location is skipped. It is in a Mounted status and the "Dismount the database before restore and mount the database after restore" option is unchecked.VThe check for proper account privileges failed. Cannot access Microsoft Exchange data.The current account :%1!s! does not have enough privilege to access the Exchange data.  Please grant proper privilege for this account or switch to another one.The Storage Group:[%1!s!] being restored is renamed or removed after the backup, either restore from a latest recovery point or restore to the diskThe Database:[%1!s!] being restored is renamed or removed after the backup, either restore from a latest recovery point or restore to the disk!Application restore is incomplete5Failed to mount Microsoft Exchange database: [%1!s!].Snapshot storage area for volume is not on NTFS volume. The snapshot storage area will be switched to another volume to continue the backup. (Storage Area=[%1!s!], Volume Name=[%2!s!])>Snapshot storage Area for volume [%1!s!] is on volume [%2!s!].iFailed to initialize backup manager, please refer to Windows Event log for more details. (EC=[0x%1!08x!])The Oracle VSS Writer service "%1!s!" is not installed, the Oracle database "%2!s!" will be skipped to back up. If you want to back it up, please install the writer and make sure it is running.kThe Oracle VSS Writer service "%1!s!" will be started automatically to back up the Oracle database "%2!s!".nThe Oracle VSS Writer service "%1!s!" must be started in order to complete the Oracle database "%2!s!" backup.Unable to query the database, please check if the Domain Controller (DC) is accessible and the current account "%1!s!" has privileges to query the Active Directory (AD). (EC=[0x%2!08x!]).Unable to query the database, please check if the Domain Controller (DC) is accessible and the current account has privileges to query the Active Directory (AD). (EC=[0x%1!08x!]).PAEFI System PartitionRecovery Partition.Successfully moved old backup data of [%1!s!].*Failed to move old backup data of [%1!s!].cBackup destination[%1!s!] is already in a backup chain. Unable to back up data to this destination.Backup destination[%1!s!] contains previously backed up data. Session numbers will be assigned based on the sessions already applied to the old backup data.(The account[%1!s!] for Agent is invalid.+Unable to initialize key management module.MKey management is inactive because of mismatched master key for this machine.RUnable to find session password in key management database. (Session GUID=[%1!s!])DSession password retrieved by key management. (Session GUID=[%1!s!])VUnable to remove session password from key management database. (Session GUID=[%1!s!])QSession password successfully removed from key management. (Session GUID=[%1!s!])[Unable to shrink key management database file and remove all passwords marked as "removed".gAble to successfully shrink key management database file and removed all passwords marked as "removed".WUnable to update administration account for key management database. (UserName=[%1!s!])[Successfully updated administration account for key management database. (UserName=[%1!s!])QUnable to add session password to key management database. (Session GUID=[%1!s!])WSuccessfully added session password to key management database. (Session GUID=[%1!s!]).Copy of recovery point destination[%1!s!] contains previously backed up data. Session numbers will be assigned based on the sessions already applied to the old backup data.,Start to generate catalog. Job id is: %1!u!.'Parse process of job script successful.Failed to parse job script.aFailed to run job script for generating catalog because there is no more job script in job queue.3Current job script is invalid. (Session is invalid)XInitialization of backup destination successful. (Destination=[%1!s!], UserName=[%2!s!])PFailed to initialize backup destination. (Destination=[%1!s!], UserName=[%2!s!])*Start to generate catalog for file system.8Start to generate catalog for Exchange Granular Restore.fSession information: Session Number=[%1!u!], Job ID=[%2!u!], Backup Time=[%3!s!], Backup Name=[%4!s!].HSession information: Session Number=[%1!u!], Sub-Session Number=[%2!u!]."Start to verify existing sessions.#Purge of failed session successful.&Failed to verify purge failed session. Start to verify merged sessions.#Merge of failed session successful.Failed to merge failed session..Start to verify the number of recovery points.Merge of sessions successful.Failed to merge sessions.(Start to merge sessions %1!u! and %2!u!.-Merge of sessions %1!u! and %2!u! successful.)Failed to merge sessions %1!u! and %2!u!.7Generation of catalog file for volume %1!s! successful.Generate catalog file failed because internal error. Please check backup log to confirm if data is in a consistent state. (Volume=[%1!s!], Backup Job ID=[%2!u!])5Generation of index file for volume %1!s! successful./Failed to generate index file for volume %1!s!.2Move of catalog file to session folder successful..Failed to move catalog file to session folder.)Update of session information successful.%Failed to update session information.-Update of cluster map information successful.)Failed to update cluster map information.&Catalog generation process successful.Failed to generate catalog.Merge session is skipped because the session is locked by another operation. Verify if any recovery points are mounted and dismount them.2Session %1!u! is merged. (Retention Count=[%2!u!]):Total %1!u! sessions are merged. (Retention Count=[%2!u!])KMerge of failed sessions is skipped. Maybe these sessions have been purged.CMerge of sessions is skipped. Maybe these session have been purged.7Catalog job is skipped because session has been purged.*Pick one new valid job script for catalog.Failed to generate catalog file for volume %1!s! because of something wrong with data. To solve this problem please submit a full backup after performing chkdsk command.@Generation of the catalog file for ReFS volume %1!s! is skipped.QGeneration of the catalog file for Deduplication-Enabled volume %1!s! is skipped.NVolume %1!s! is Deduplication-Enabled volume, file copy will skip this volume.mFailed to check volumes %1!s! to determine if the volumes are a file copy source. File copy will be disabled.3Failed to save catalog job script to %1!s!. (%2!s!)=Volume %1!s! is ReFS volume, File Copy will skip this volume.Catalog job canceled.FInitialization of backup destination successful. (Destination=[%1!s!])>Failed to initialize backup destination. (Destination=[%1!s!])6Open virtual disk failed. (Volume=[%1!s!], EC=[%2!u!])@Read data from virtual disk failed. (Volume=[%1!s!], EC=[%2!u!])>Seek data on virtual disk failed. (Volume=[%1!s!], EC=[%2!u!])Generate index file failed, cause available memory is not enough. Currently in used memory is [%1!u!MB], need [%2!u!MB] free memory for this operation.Generate index file failed, cause physical memory is too small. Currently in used memory is [%1!u!MB], recommend to enlarge memory to at least [%2!u!MB].PCatalog job failed because of backup destination is under deleting by purge job.0Failed to Create File Copy Policy Error = %1!s!.MTotal processed data size is %1!s!, elapsed time %2!s!, throughput %3!s!/Min.Total files copied :%1!d!.CFailed to convert File Copy xml to job script (Error Code = %1!d!).oNext scheduled File Copy job will be converted to full as it is the first File Copy job for the volume (%1!s!). User canceled the File Copy job. File Copy Purge job has started.File Copy Purge job has ended.Total files Purged is : %1!d!.File Copy job started running.File Copy job has completed.File Copy job has failed.File Copy job is incomplete.Converting your scheduled File Copy job to full because File Copy destination has changed or this job is the first File Copy job.Will be skipping incremental File Copy because File Copy destination has changed, incremental File Copy will be automatically convert to a full File Copy in next backup.'Mount virtual disk failed. Error %1!d!.*Will perform File Copy from session %1!s!.(Will perform File Copy for Volume %1!s!.,File Copy destination for this job is %1!s!.2Backup Session No for this File Copy job is %1!d!.&Unable to reach File Copy destination.File Copy Purge job has failed.0File Copy catalog resync successfully completed. File Copy catalog resync failed.cFile Copy will use the existing catalogs as the user changed back to the old File Copy destination.JClock skew detected on machine. Please adjust the system time or timezone.An error (error = %1!d!) has been encountered that prevent File Copy operation to continue, please contact arcserve support if the problem persist.@File Copy Catalog Resync job for alternate location has started.AFile Copy Catalog Resync job for alternate location has finished.PA?File Copy Catalog Resync job for alternate location has failed.FFile Copy Catalog Resync job for alternate location has been canceled.NFile Copy destination change has been detected, File Copy job will be skipped.]File Copy destination is corrupted or has not been initialized, File Copy job will be failed.5The destination is not a valid File Copy destination.FFile Copy Purge job has been skipped - destination is not initialized.RTotal files not deleted for filecopy job on source (Delete Source option) : %1!d!.4There is not enough space on the destination device.NA connection is active to the same network resource with different credential.3The specified network resource username is invalid.3The specified network resource password is invalid.The network is unavailable.rSource %1!s! selected in policy does not exist. This source might not be FileCopied in current or subsequent jobs.tTotal files File-copied (Delete Source) is : %1!d!. Total Disk Space Saved After File Copy (Delete Source) is %2!s!.Total files copied :%1!d!.=Failed to copy file: %1!s! error = %2!d!, skipping this file.PACThis is a stub file created by Agent File Copy feature.

The File [3] is moved to the following filecopy destination.

Destination Path : Cloud Dest URL   : Cloud Container   : fFile Copy destination for this job is Amazon Cloud and the details are URL:: %1!s! and Bucket:: %2!s!.hFile Copy destination for this job is Azure Cloud and the details are URL:: %1!s! and Container:: %2!s!._File Copy cannot write to the specified device due to problem with network or service provider.`File Copy cannot read from the specified device due to problem with network or service provider.)The filecopy destination is not writable.qFile Copy destination for this job is Eucalyptus-Walrus Cloud and the details are URL:: %1!s! and Bucket:: %2!s!.]The File Copy Encryption settings on the destination and the ones in restore job don't match.4Incorrect File Copy destination encryption password.SThe File Copy destination encryption settings validation failed with CCI error [%d]:Total data size written to File Copy destination is %1!s!.D2D2D (File Copy to a local or network drive) feature license is not available for the current configured destination, skipping the file copy job.PAHEncryption feature license is not available, skipping the file copy job.The total download size is %1!s! and the size of %2!d! files restored to disk is %3!s! The elapsed time for the restore job is %4!s!, with an average speed (throughput) of %5!s!/min.%1!d! Files Skipped.-Invalid File Copy destination path specified.A makeup job will be created for this job because the current File Copy job was not completed. This makeup job will be run after 30 minutes.Total files skipped : %1!d! Failed to create file %1!s! at specified destination. Please ensure destination can support all characters in the file/folder name.dSkipping file %1!s!. File path exceeds the maximum length %2!d! supported by the destination device.fFailed to copy file %1!s!. There is not enough available space at the specified File Copy destination.]Failed to copy file %1!s!. Make sure you are properly connected to the network and try again.zFile Copy destination for this job is Fujitsu Cloud (Windows Azure) and the details are URL:: %1!s! and Container:: %2!s!.An error (error = %1!d!) has been encountered with Cloud connection that prevent File Copy operation to continue, please contact arcserve support if the problem persist.The total processed data size on the source disks is %1!s! and the total data size written is %2!s!. The space saved from compression is %3!d!%4!c!%5!02d!%%.PAFPlease make sure that the folder (%1!s!) has users group access right.=Failed to lock the session %1!d! at backup destination %2!s!./The credential information of %1!s! is invalid.
SQL Option
EncryptionSimple Virtual ConverterExchange DB RecoveryExchange Granular RecoveryBackup configuration modified.!Email has been successfully sent.QA job is currently running. A new job named "%1!s!" at %2!s! cannot be performed.%1!s![License failure. The schedule intervals of full backup job has been adjusted to %1!s! days.\License failure. The schedule intervals of full backup job has been adjusted to %1!s! hours.^License failure. The schedule intervals of full backup job has been adjusted to %1!s! minutes.cLicense failure. The schedule intervals of incremental backup job has been adjusted to %1!s! hours.eLicense failure. The schedule intervals of incremental backup job has been adjusted to %1!s! minutes.zHost-Based VM backup job failed because of a license failure. Contact your account representative to obtain a new license.#Could not check VMware Tools state.VMware Tools is not installed.VMware Tools is out of date.)Unable to communicate with server  %3!s!.VMware VIX is not installed. The application cannot perform application log truncation and Pre/Post commands without VMware VIX.xVMware VIX version is lower than 1.1.0. The application cannot perform application log truncation and Pre/Post commands.6Current %1!s! version: %2!s! (Build %3!s!.%4!s!.%5!s!)TFailed to connect to %1!s! to check license,please make sure %2!s! can be connected.CCurrent %1!s! version: %2!s! (Build %3!s!.%4!s!.%5!s!) Update %6!s!xHost-Based VM copy job failed because of a license failure. Contact your account representative to obtain a new license.Failed to copy the recovery point for virtual machine %1!s!. The recovery point of session number %2!s! contains no volume information.AFailed to mount virtual disk of session %1!I64u! in folder %2!s!."Failed to recover EDB file(%1!s!).(Restore Failed: Mailbox %1!s! not found.hFailed to generate Exchange Granular Restore catalog for EDB File %1!s!. session=%2!d!, subsession=%3!d!@There are %1!d! mailbox(es) in the current database file(%2!s!).Exchange Granular Restore cannot be done because Microsoft Exchange Server MAPI Client is not installed.  Please download MAPI from Microsoft, install it and retry.SBegin generating Exchange Granular Restore catalog. session=%1!d!, subsession=%2!d!VFinished generating Exchange Granular Restore catalog. session=%1!d!, subsession=%2!d!Restore Item(s) to Disk(%1!s!).+Restore Item(s) to Original Mailbox(%1!s!)..Restore Item(s) to Alternative Mailbox(%1!s!).%1!d! folder(s) %2!d! email(s)(%3!s!) from %4!d! mailbox(es) restored to Exchange server, elapsed time %5!s!, throughput %6!s!/Min.#Restore Mailbox Item(s) from %1!s!.Restore item(s) to disk failed due to lack of disk space,please ensure that restore destination volume( %1!s!)  has sufficient disk space.The Mounted DB Path is too long, please create registry HKEY_LOCAL_MACHINE\SOFTWARE\CARCserve Unified Data Protection\Engine\ExGRT\MountPoint, and assign MountPoint to folder path of short length.PA^The mailbox:%1!s! has exceeded the mailbox storage quota limit,some items may not be restored.EMicrosoft Exchange Information Store Service is not in running state.The service is invalid: please check whether the Microsoft Exchange Information Store Service is in running state and whether the database which the current user(%1!s!) belongs to is in mounted state.x%1!d! folder(s) %2!d! email(s)(%3!s!) from %4!d! mailbox(es) restored to disk, elapsed time %5!s!, throughput %6!s!/Min.)Restore message %1!s! to disk error:%2!s!/Restore message %1!s! fail, it's name too long.hThe MAPI package is installed improperly. please uninstall the MAPI package, and then reinstall it again^Please check the License of Exchange Granular Recovery, make sure it is valid and not expired.XPlease check the License of Exchange DB Recovery, make sure it is valid and not expired. Installed MAPI Version is %1!s!.The Exchange Server installation volume (%1!c!:) on the virtual machine is REFS file system. However, the backup proxy host does not support REFS. As a result, the Exchange Server binaries cannot be processed and the catalog job will fail.The Exchange Server installation volume (%1!c!:) on the virtual machine has NTFS Data Deduplication enabled. However, the proxy system does not support the Windows Data Deduplication function. As a result, the Exchange Server binaries cannot be parsed and the catalog job will fail.The Exchange Server database volume (%1!c!:) on the virtual machine is a REFS file system. However, the backup proxy host does not support REFS. As a result, the Exchange information cannot be parsed and the catalog job will fail.The Exchange Server database volume (%1!c!:) on the virtual machine has NTFS Data Deduplication enabled. However, the proxy system does not support the Windows Data Deduplication function. As a result, the Exchange information cannot be parsed and the catalog job will fail.The Exchange Server database volume (%1!c!:) on the virtual machine is a REFS file system. However, the backup proxy host does not support REFS. As a result, the Exchange information cannot be identified and the restore job will fail.The Exchange Server database volume (%1!c!:) on the virtual machine has NTFS Data Deduplication enabled. However, the proxy system does not support the Windows Data Deduplication function. As a result, the Exchange information cannot be identified and the restore job will fail.The Exchange database needs to be defragmented before the open operation, but there is not enough available free space in the defragmentation temporary folder (volume:%1!c!:) to proceed. As a result, the defragmentation process may fail. Usage: %1!s! %2!s!
%1!s! Console%1!s! Host-Based VM Backup%1!s! Virtual StandbyThe processing of breaking the management relationship between Agent and Arcserve UDP Web Server did not complete successfully.xThe processing of breaking the management relationship between Agent and Arcserve UDP Web Server completed successfully.`The processing of breaking the management relationship between Agent and Console is in progress.mThe processing of breaking the management relationship between Agent and Host-Based VM Backup is in progress.hThe processing of breaking the management relationship between Agent and Virtual Standby is in progress.,The Arcserve UDP Web Server type is unknown.OThe synchronization process was unable to retrieve the data for the backup job.]The synchronization process was unable to retrieve the data for the Host-Based VM Backup job.LThe synchronization process was unable to retrieve the Virtual Standby data.IThe synchronization process was unable to retrieve the Activity Log data.RThe synchronization process was unable to retrieve the data for the file copy job.Cannot log in to the Console service on node %1!s!. The problem may occur when Console is reinstalled. To correct this problem, open Console, delete the Arcserve UDP Agent node, and then add the Arcserve UDP Agent node.The Arcserve UDP Agent service cannot communicate with the Console service running on node %1!s!. This problem can occur when the Console service is not running, or, the Arcserve UDP Agent node cannot communicate with the Console node using the host name of the Console node.The Arcserve UDP Agent service cannot communicate with the Console service running on node %1!s!. The version of Arcserve UDP Agent is not compatible with the version of Console.`The synchronization process was unable to synchronize the Backup job data on Console node %1!s!.nThe synchronization process was unable to synchronize the Host-Based VM Backup job data on Console node %1!s!.eThe synchronization process was unable to synchronize the Virtual Standby data on Console node %1!s!.bThe synchronization process was unable to synchronize the Activity Log data on Console node %1!s!.cThe synchronization process was unable to synchronize the File Copy job data on Console node %1!s!.sThe synchronization process cannot synchronize data with the Console. The node is not managed by a Console product.VThe synchronization process was unable to synchronize data with Console on node %1!s!.+The merge job started. (Process ID=[%1!u!])The merge job stopped.The merge job ended.%The merge job completed successfully.The merge job failed.5The merge job skipped. No session needs to be merged.CInitialize of the backup destination was successful. (Path=[%1!s!])Failed to initialize backup destination [%1!s!]. Please verify if your backup destination is reachable or if you have ever changed the credentials of backup destination.!Lock session for merge succeeded.Lock session for merge failed.KContinue to merge the session from the last incomplete or failed merge job.JThe retention count is %1!u!. Sessions from %2!u! to %3!u! will be merged.Merge session data started.Merge session data ended.:A total of %1!u! disks in %2!u! sessions have been merged.7Un-initialize of the backup destination was successful.PA/Un-initialize of the backup destination failed.,A total of %1!s! unique data will be merged.The merge job stopped at %1!s!.The merge job failed at %1!s!.The merge job crashed.The merge job skipped because the session is locked by another operation. Verify if any recovery points are mounted and dismount them.iNot enough free space on the backup destination. (Path=[%1!s!], Space Needed=[%2!s!], Free Space=[%3!s!])VThe recovery set count is %1!u!. The recovery set before session %2!u! will be purged.8Approximately %1!s! of disk space will become available.The merge job was skipped because the session is currently locked by the filecopy operation. Verify if any filecopy job failed or was cancelled.7Failed to delete catalog folder. (Folder [%1!s!]) %2!s!ILock session for merge failed. The session is locked by computers: %1!s!.XThe merge job skipped because there was not enough free space on the backup destination.YSome operations failed because there was not enough free space on the backup destination.Failed to get recovery points for merge. Verify that the backup destination folder is available, all recovery points are reachable, and the network connection is working properly.1A total of %1!s! incremental data will be merged./Total freed disk space on destination is %1!s!.[Initialize of the backup destination was successful. (RPS Server[%1!s!], Data Store[%2!s!])Failed to initialize backup destination (RPS Server[%1!s!], Data Store[%2!s!] ). Please verify if your backup destination is reachable or if you have ever changed the credentials of backup destination.7%1!u! session range(s) will be merged. (Ranges=[%2!s!])4Session range %1!u! is being merged. (Range=[%2!s!])8Session range %1!u! successfully merged. (Range=[%2!s!])DFailed to merge session range %1!u!. (Range=[%2!s!]. EC=[0x%3!08x!])`Session range %1!u! was skipped because it was already merged in a previous job. (Range=[%2!s!])AThe previous merge job was incomplete and will resume from %1!s!.=Session range %1!u! is being merged. (Session Number=[%2!u!])ASession range %1!u! successfully merged. (Session Number=[%2!u!])MFailed to merge session range %1!u!. (Session Number=[%2!u!]. EC=[0x%3!08x!])iSession range %1!u! was skipped because it was already merged in a previous job. (Session Number=[%2!u!])PAfReplication job started for node %1!s! to the destination server (server = %2!s!, data store = %3!s!).>The source server is %1!s! and the source data store is %2!s!.DReplication job failed for node %1!s! because machine was shut down.IReplication of session %1!u! (total size = %2!s!) successfully completed.PFailed to replicate session %1!u! (total size = %2!s!, replicated size = %3!s!).MAn error occurred while connecting to the destination server. Error: '%1!s!'.Replication job crashed.;Replicating session %1!u! to the destination data store ...wReplication from deduplication enabled data store %1!s! to non-deduplication enabled data store %2!s! is not supported.EFailed to get the GDD configuration file from the destination server.x .x .x .XReplication from an encrypted data store to a non-encrypted data store is not supported.x .PAUReplication job is skipped because there are no new recovery points to be replicated.8Replication job was canceled on the source server %1!s!.=Replication job was canceled on the destination server %1!s!.GConnecting to the destination server (server = %1!s!, port = %2!u!) ...*Preparing the replication session list ...!Start to replicate session %1!u!.uStart to replicate sessions. The session range to replicate is from [start session = %1!u!] to [end session = %2!u!].8Replicating session %1!u! from the source data store ...&Replication job failed for node %1!s!.cReplication job started for node %1!s! from the source server (server = %2!s!, data store = %3!s!).VOnly catalog files for session %1!u! will be replicated to the destination data store.bFailed to replicate catalog files for session %1!u! (total size = %2!s!, replicated size = %3!s!).SOnly catalog files for session %1!u! will be replicated from the source data store.#There is no session for node %1!s!.*Failed to get session list for node %1!s!.Failed to replicate the file: %1!s!. Error: '%2!s!'. Insufficient free disk space where Recovery Point Server is installed or at the destination data store.HThe destination server is %1!s! and the destination data store is %2!s!.yReplication job skipped because the node data is consistent between the source data store and the destination data store..Failed to access the data store (%1!s!\%2!s!).4Failed to replicate the file: %1!s!. Error: '%2!s!'.-Failed to lock session %1!u!. Error: '%2!s!'.5Replication job finished successfully for node %1!s!.BReplicated %1!s! in %2!s! with an average throughput of %3!s!/Min.L%1!s! could not be replicated and will be processed during next replication.x .x .VFailed to lock session %1!u!. The session has already been locked by computers: %2!s!.qThe amount of data actually transferred over the network was %1!s!, and the average network throughput was %2!s!.nThe amount of space saved due to deduplication and compression is %1!s!%%. %2!s! has been written to the disk.^The amount of space saved due to deduplication is %1!s!%%. %2!s! has been written to the disk.\The amount of space saved due to compression is %1!s!%%. %2!s! has been written to the disk.#%1!s! has been written to the disk.PASource RPS error: %1!s!.Source RPS warning: %1!s!.QAnother job is currently running for the node to the same destination data store.The source is from %1!s!.hRPSJumpstart job started for node %1!s! to the destination server (server = %2!s!, data store = %3!s!).4RPSJumpstart job started for node %1!s! from %2!s!.RPSJumpstart job crashed.:RPSJumpstart job was canceled on the source server %1!s!.?RPSJumpstart job was canceled on the destination server %1!s!.(RPSJumpstart job failed for node %1!s!.7RPSJumpstart job finished successfully for node %1!s!.rData for node %1!s! is already included in the target data store. As a result, the Jumpstart job will be skipped. WRPSJumpstart job is skipped because there are no new recovery points to be replicated.PAThe parameter is incorrect.Create File failed.Read D2D FOOTER failed. Invalid disk type in D2D FOOTER.Read D2D HEADER failed.Checksum error while read D2D.Read BAT of D2D failed.Read bitmap of D2D failed.Invalid MAGIC number in D2D.Create Index file failed.More input buffer is needed.,Invalid path type while set D2D parent path.,Invalid path type while get D2D parent path.D2D Parent path not exist.This is a FULL D2D, cannot to get parent path.PA+This is a FULL D2D, cannot set parent path.0This is a FULL D2D, cannot set parent timestamp.0This ia a FULL D2D, cannot get parent timestamp.Parent timestamp not exists.Write D2D file HEADER failed.Set file position failed.Write D2D FOOTER failed.$Cannot position to unused BAT entry.Not enough memory is available.1Not enough free disk space to split the idx file.Internal error.Read D2D data failed.Update MTA file failed.+Failed to lock session on destination side.PAMore data range is available.<The authentication process failed on the destination server.EThe job count exceeded the specified limit on the destination server..The plan was paused on the destination server.DFailed to run another job, because a purge job is currently running.hThe specified timeout period expired while communicating with the web service on the destination server.Unspecified error.PThe restore process failed to mount the Volume. (Volume [%1!s!], Error [%2!d!]).RThe restore process failed to unmount the Volume. (Volume [%1!s!], Error [%2!d!]).`Failed to set compression level for the File/Directory. (File/Directory [%1!s!], Error [%2!d!]).<An unexpected exception error occurred in GRTMntBrowser.dll.:Failed to restore the File. (File [%1!s!], Error [%2!s!]).-Skipping restore of the File. (File [%1!s!]).7Skipping restore of the Directory. (Directory [%1!s!]).<Failed to read from the File. (File [%1!s!], Error [%2!s!]).;Failed to write to the File. (File [%1!s!], Error [%2!s!]).7Failed to open the File. (File [%1!s!], Error [%2!s!]).9Failed to create the File. (File [%1!s!], Error [%2!d!])._Failed to set sparse attribute for the File/Directory. (File/Directory [%1!s!], Error [%2!d!]).LPerform an optimized restore. Source volume %1!s!, Destination volume %2!s!.sThe destination volume is not empty. Perform an unoptimized restore. Source volume %1!s!, Destination volume %2!s!.NPerform an unoptimized restore. Source volume %1!s!, Destination volume %2!s!.Perform an optimized restore. After the restore job completes, install the Data Deduplication Feature before you access the restored data. Source volume %1!s!, Destination volume %2!s!.This is not supported. The Data Deduplication Feature is not installed or the destination volume is not empty. Source volume %1!s!, Destination volume %2!s!.vThis is not supported. The Data Deduplication Feature is not installed. Source volume %1!s!, Destination volume %2!s!.Arcserve UDP does not support a restore of data that was backed up from a deduplication-enabled volume %1!s! on a Server 2012 or later to a target volume %2!s! on a system that is running an operating system earlier than Server 2012.<Skipping restore encrypted file[%1!s!] into Non-NTFS volume.HSkipping restore Alternate Data Stream file[%1!s!] into Non-NTFS volume.dAs the system limitation, file [%1!s!] will lose Compress attribute after restored into ReFS Volume.eAs the system limitation, file [%1!s!] will lose Integrity attribute after restored into NTFS Volume.hAs the system limitation, file [%1!s!] can not be restored into volume that doesn't support sparse file.aSkipping restore of named file streams of Alternate Data Stream file[%1!s!] into Non-NTFS volume.uSkip recovery of hard link: [%1!s!]. For information about how to recover a hard link, see the product documentation.NSkipping restore of extended attribute data of [%1!s!] into a non-NTFS volume.The restore process failed to mount Volume [%1!s!] because the session [%2!d!] failed to lock. Please verify that there are no other jobs running on this session.PAYou are attempting to restore data that was backed up from an NTFS deduplication volume to a system that does not have the Windows 8 Data Deduplication server role installed and enabled(%1!s!  drive). As a result, you will not be able to access the restored deduplication files until this role is enabled at the restore destination. After the Data Deduplication role is enabled, these restored files will be automatically displayed and no additional restore job is necessary.PAUBackup destination is Arcserve UDP Recovery Point Server [%1!s!], data store [%2!s!].PA?Failed to communicate with deduplication %1!s! on server %2!s!.BUnexpected error [%1!d!] from deduplication %2!s! on server %3!s!.XAn error has occurred from deduplication %1!s! on server %2!s!. Error message = [%3!s!].XFailed to communicate with deduplication %1!s! on server %2!s!. Network error = [%3!s!].Invalid parameter.#The requested operation is invalid.6Failed to lock file. The file may currently be in use.System call returns an error.SYSTEM CALL FAILED+This version of the agent is not supported.?This job is not allowed because of a conflict with another job.)This data store configuration is invalid.AThe operations for this file (create, close, read, write) failed.PA/Unexpected data size detected from this server.FAILED TO LOAD ZIP LIBRARYFAILED TO COMPRESS DATAUnable to access file.8The operations on hash database (search, insert) failed.
Disk is full.Insufficient memory.Hash role is initializing.Unexpected error.Hash server is Full.'An unknown internal error has occurred.?Deduplication reduced the size by %1!d!%2!c!%3!02d!%% to %4!s!.ECompression further reduced the size by %1!d!%2!c!%3!02d!%% to %4!s!.eTotal %1!s! written to destination after %2!d!%3!c!%4!02d!%% saving by deduplication and compression.
Index role	Hash role	Data role8The %1!s! of "%2!s!": Role has initialized successfully..The %1!s! of "%2!s!": %3!s! is not accessible..The %1!s! of "%2!s!": %3!s! is not accessible.AThe %1!s! of "%2!s!": Failed to initialize communication library.<The %1!s! of "%2!s!": Failed to create %3!s!. Error=[%4!s!].9The %1!s! of "%2!s!": Failed to open %3!s!.Error=[%4!s!].+The %1!s! of "%2!s!": Failed to initialize./The %1!s! of "%2!s!": Unexpected error [%3!d!].The %1!s! of "%2!s!": Data deduplication capacity has reached %3!d!%% of its full capacity. Please increase either the memory or the SSD size to extend the data deduplication capacity.The %1!s! of "%2!s!": Data deduplication capacity has reached its full capacity. Please increase either the memory or the SSD size to extend the data deduplication capacity.OThe %1!s! of "%2!s!": Role is already running and and is unable to start again.4The %1!s! of "%2!s!": Role has stopped successfully.$The %1!s! of "%2!s!": %3!s! is full.*The %1!s! of "%2!s!": Insufficient memory.'The %1!s! of "%2!s!": Role is starting.'The %1!s! of "%2!s!": Role is stopping.3The %1!s! of "%2!s!": Data store is out of service.gThe %1!s! of "%2!s!": Data store is experiencing a problem. As a result, only a restore job is allowed.4The %1!s! of "%2!s!": Data store has been recovered.[The %1!s! of "%2!s!": The operations (create, close, read, and write) failed for this file.|The %1!s! of "%2!s!": The configured memory size is bigger than the total physical memory. It might run out of memory later.PANThe Data Store Management Service is started on Recovery Point Server "%1!s!".QThe Data Store Management Service fail to start on Recovery Point Server "%1!s!".NThe Data Store Management Service is stopped on Recovery Point Server "%1!s!".PThe Data Store Management Service fail to Stop on Recovery Point Server "%1!s!".Failed to start the deduplication data store "%1!s!" because the physical memory is not sufficient on the current server. You must have at least %2!d! MB of free physical memory space to start the data store.Failed to create the new deduplication data store "%1!s!". The maximum number (%2!d!) of deduplication data stores has been reached.QFailed to start data store "%1!s!" because it is owned by another server "%2!s!".RFailed to modify data store "%1!s!" because it is owned by another server "%2!s!".iFailed to start data store "%1!s!" because the destination path has been taken over by other data store. Failed to start the data store because of an invalid data store path. Verify the verification files exist and have not been changed in the backup destination folder or any of the deduplication folders.Failed to start data store "%1!s!" because of an invalid data store path. Verify the verification files exist and have not been changed in the backup destination folder or any of the deduplication folders.WFailed to lock the data store "%1!s!", verify the network connection to the data store.Failed to lock data store "%1!s!" because it is already owned by another server "%2!s!". The data store is stopped automatically.Failed to start the data store because an invalid Windows user name or an invalid password was provided. Update node and retry manually.Failed to start data store "%1!s!" because an invalid Windows user name or an invalid password was provided. Update node and retry manually.PAANot enough free space exists in the destination hash path: %1!s!.wFailed to copy the hash files from the source hash path %1!s! to the destination hash path %2!s!. System error=[%3!s!].BFailed to import the data store because the path is inaccessible. |Failed to import the data store because no valid configuration information was retrieved from the backup destination folder.TFailed to import the data store because an invalid data store password was provided.HFailed to import the data store because it is locked by server: "%1!s!".gFailed to import the data store because the specified path is already being used by another data store.\Failed to import the data store for the assigned physical memory is larger than actual one. [Failed to import the data store because the assigned physical memory space is insufficient.Failed to import the data store because the data store could not be locked. Check that the lock file "DSExc.lck" (located in the destination path) is accessible.yFailed to import the data store because invalid data store paths were provided. Check the data store paths and try again.Failed to import the data store because the data consistency in the provided paths are not matched. Verify the data store paths and try again. PA`Failed to get physical location of volume [%1!s!]. This volume will be excluded from the backup.sVolume [%1!s!] contains a common path for data store [%2!s!]. As a result, it will be excluded from the backup job.vVolume [%1!s!] contains a hash file path for data store [%2!s!]. As a result, it will be excluded from the backup job.vVolume [%1!s!] contains a data file path for data store [%2!s!]. As a result, it will be excluded from the backup job.xVolume [%1!s!] contains an index file path for data store [%2!s!]. As a result, it will be excluded from the backup job.TThe space is not enough on the VM backup proxy machine where the agent is installed.#Data backup successfully completed.1Start collecting Bare Metal Recovery information.KConverting to a full backup because the compression level has been changed.aConverting the verify backup to a full backup because deduplication is enabled on the data store.The boot volume [%1!s!] is configured as a mirrored volume. As a result, the system will fail to boot if you are attempting to restore data using BMR. JThe job [PID: %1!d!] started and the source virtual machine name is %2!s!.$The session data format is standard.$The session data format is advanced.?The session data format is advanced with deduplication enabled.PA%The destination type is a data store.)The destination type is a non-data store./Failed to save session key file. (EC=[%1!08x!])SThe free space on drive %1!s! is less than %2!d! MB. As a result backup might fail.BBackup job failed because of backup destination is under deletion.+The Active Directory database is protected.The size of virtual disk %1!s! has changed. The next time a backup job is performed, Host-Based VM Backup will reset the Changed Block Tracking (CBT) functionality and automatically perform a Verify Backup.PA,Backup in remote mode on Hyper-V host %1!s!.(Failed to connect to Hyper-V host %1!s!.0Failed to connect to the Hyper-V backup utility.4Failed to prepare for backup of the virtual machine.CSuccessfully connected to the Hyper-V backup utility on host %1!s!.^The current version of the Change Block Tracking (CBT) feature on Hyper-V host %1!s! is %2!s!.The status of the Change Block Tracking (CBT) functionality is Inactive on the Hyper-V host and cannot be reset for the current backup job. As a result, if the next backup job is an Incremental Backup, it will automatically be changed to a Verify Backup.EFailed to perform backup of virtual disk %1!s!. System error=[%2!s!].4Backup of virtual disk %1!s! successfully completed.The Change Block Tracking feature failed for the previous backup. As a result the Incremental Backup will be changed to a Verify Backup.-Failed to initialize the Hyper-V environment.The Change Block Tracking feature is Inactive on the Hyper-V host. As a result, redundant data may be backed up and if the next backup job is an Incremental Backup, it will automatically be changed to a Verify Backup.+Backup in local mode on Hyper-V host %1!s!.%Initializing the Hyper-V environment.-The Hyper-V backup utility is not responding.8Performing a consistent backup using Hyper-V VSS writer.The Hyper-V VSS writer does not support the taking of data consistency snapshots on this virtual machine. As a result, the backed up data may not be in a consistent state. (For more information about creating application-consistent snapshots, refer to the product documentation).Taking VSS snapshot.2Failed to take VSS snapshot. System error=[%1!s!].?Failed to open virtual disk file [%1!s!]. System error=[%2!s!].PABackup of physical hard disks are not supported. Host-Based VM Backup will skip any physical hard disks that are attached to this virtual machine.Backing up virtual disk %1!s!.There was an error reported during the reconfiguration of the virtual machine to enable the "disk.EnableUUID" parameter (which is required for an application-consistent backup). This could occur when the virtual environment has recovered from an error (e.g. an unexpected power cycle of the ESX server while the VM was running). This error can be resolved by shutting down the VM and running a new backup job. (To reduce the down time of the VM, the VM can be powered on during or after the "Taking Snapshot" phase of the new backup job).This is a daily backup.This is a weekly backup.This is a monthly backup.VThe reset of the changed block tracking function has started for the first backup job.MFailed to reset the changed block tracking function for the first backup job.YThe changed block tracking function for the first backup job has been successfully reset.@Taking snapshot to reset the changed block tracking function ...BDeleting snapshot to reset the changed block tracking function ...{The user %1!s! may not have sufficient permissions to perform backup. A user with administrative privileges is recommended.The Hyper-V VSS writer has encountered an error when processing this virtual machine. (For more information about Hyper-V VSS writer errors, refer to the product documentation).HFailed to back up the VM configuration file %1!s!. System error=[%2!s!].MFailed to connect Hyper-V server %1!s!. Pre/Post commands cannot be executed.lFailed to get virtual machine by GUID %1!s! from Hyper-V server %2!s!. Pre/Post commands cannot be executed.PANFailed to get virtual machine host name. Pre/Post commands cannot be executed.UThe virtual machine is not in powered on state. Pre/Post commands cannot be executed.eFailed to connect to the virtual machine using host name %1!s!. Pre/Post commands cannot be executed.OThe virtual machine GUID is not expected. Pre/Post commands cannot be executed.OThe virtual machine name is not expected. Pre/Post commands cannot be executed._The guest OS of virtual machine is not a Windows machine. Pre/Post commands cannot be executed.gThe disk.EnableUUID parameter for virtual machine %1!s! was configured for application-level quiescing.User specified not to reconfigure the disk.EnableUUID parameter for virtual machine %1!s!. As a result, the backed up data may not be in a consistent state if the parameter was not set.The file system of volume %1!s! is a deduplication-enabled NTFS. Due to a limitation from Microsoft, the file-level restore in this volume from a non Windows 2012 R2 proxy will fail. (For more information about troubleshooting this problem, refer to the Solutions Guide document).Verify backup job scanned a total of %1!s! of source data and processed %2!s! changed data in %3!s!. The verify backup job throughput was %4!s!/min.Collecting backup data.0The VM will be backed up in the standalone mode.-The VM will be backed up in the cluster mode.
The current backup job has been denied because of a CBT compatibility problem internal to the Hyper-V host. Please upgrade all of your backup proxies which are used to protect this Hyper-V host to the latest version to resolve this problem and continue your backups.Converting the Incremental Backup to a Verify Backup because the Change Block Tracking (CBT) functionality on the Hyper-V host was either Inactive or denied to serve this backup job.Host-Based VM Backup does not support the protection of Windows 2008 Hyper-V virtual machines. You need to upgrade your Hyper-V host to a Windows 2008 R2 operating system or later.PAHost-Based VM Backup does not support the protection of Windows 2008 R2 Hyper-V cluster virtual machines. You need to upgrade your Hyper-V host to a Windows 2012 operating system or later.VThe Change Block Tracking function is Inactive and has been reset on the Hyper-V host.The virtual machine has part of its configuration file and virtual disk files in Cluster Shared Volumes (CSV) and the other part in a local disk. This situation is not supported by the Hyper-V VSS Writer.yThe Change Block Tracking (CBT) function failed. One or more clustered nodes were added or removed during the backup job.EThe backup job is cancelled. For a VSS snapshot, the Hyper-V VSS writer needs to save the virtual machine and this is not applied in the current plan. To restart the backup job, change the Hyper-V Snapshot Method setting in the plan. For details on how to set Hyper-V Snapshot Method in a plan, see the product documentation.iThe virtual machine will be saved during the VSS snapshot creation as required by the Hyper-V VSS writer.The backup job has prevented the Hyper-V VSS writer from saving the VM during snapshot creation. As a result, the backed up data may not be in a consistent state.tThe Hyper-V VSS writer failed to process this VM because the VM is currently being backed up by another application.hThe Change Block Tracking (CBT) feature has been upgraded. As a result, redundant data may be backed up.PA?The virtual machine will be restored to the Hyper-V host %1!s!.,Successfully connected to the Hyper-V host .,Failed to connect to the Hyper-V host %1!s!.Virtual machine %1!s! already exists on Hyper-V host %2!s!. To recover this virtual machine, you must enable the Overwrite option.PA;Virtual machine %1!s! already exists on Hyper-V host %2!s!.4The virtual machine was renamed from %1!s! to %2!s!.&Preparing the virtual disk recovery...;Failed to add the SCSI controllers for the virtual machine. Recovering virtual disk %1!u!...0Attaching the disk %1!u! to the virtual machine.*Configuring the processor (count = %1!u!).)Configuring the memory (size = %1!u! MB).!Configuring the network adapters.The virtual machine will be restored to an earlier version of the target Hyper-V server. (The target Hyper-V server version is %1!s!, while the original Hyper-V server version is %2!s!. Recovery job may fail in some cases, for more details please refer to the product document).8Deploying the restore utility on the Hyper-V host %1!s!.{Failed to deploy the restore utility. System error=[%1!s!]. Verify that \\%2!s!\%3!s! is accessible from the proxy machine.DSuccessfully connected to the Hyper-V restore utility on host %1!s!.?Failed to connect to the Hyper-V restore utility on host %1!s!.9Failed to create the virtual disk [%1!s!]. Error=[%2!s!].8Failed to write the virtual disk [%1!s!]. Error=[%2!s!].PA8Failed to close the virtual disk [%1!s!]. Error=[%2!s!].WThe operation (open, read, or close) on the source backup disk file [%1!s!] has failed.,Adding the virtual machine to the cluster...1Unable to add the virtual machine to the cluster.DUnable to connect the network adapter '%1!s!' to the virtual switch.}Failed to find the specified path [%1!s!]. Verify the volume state on the Hyper-V host is mounted and try the recovery again.PAThe backup proxy host [%1!s!] is not on a 64 bit platform. As a result, the subsequent Exchange catalog job will fail if the Generate Catalog option is enabled in the plan.The Windows version of proxy [%1!s!] is an earlier version than virtual machine [%2!s!]. As a result, the subsequent Exchange catalog job may fail, and you will need to install the related Windows update package to resolve the problem.nVirtual machine [%1!s!] is not running. As a result, the subsequent Exchange catalog job will not be launched.The VMware Tools for virtual machine [%1!s!] is not installed or out of date. As a result, the subsequent Exchange catalog job will not be launched.Failed to communicate with the Exchange Server. Please verify that the Exchange Server certificate is installed on the proxy server. If necessary, install this certificate into the Trusted Root Certification Authorities store of the proxy server.ERecovery point check for node [%1!s!], session number [%2!d!] startedLRecovery point check for node [%1!s!], session number [%2!d!] was successfulDRecovery point check for node [%1!s!], session number [%2!d!] failedaRecovery point check result: Volume: [%1!s!], File System: [%2!s!], Volume Type: [%3!s!], SkippedjRecovery point check result: Volume: [%1!s!], File System: [%2!s!], Volume Type: [%3!s!], no problem foundxRecovery point check result: Volume: [%1!s!], File System: [%2!s!], Volume Type: [%3!s!], Error on mounting disk [%4!s!]PAxRecovery point check result: Volume: [%1!s!], File System: [%2!s!], Volume Type: [%3!s!], Error on checking disk [%4!s!]{Recovery point check result: Volume: [%1!s!], File System: [%2!s!], Volume Type: [%3!s!], Error on dismounting disk [%4!s!]bRecovery point check for node [%1!s!], session number [%2!d!] skipped. The guest OS is not WindowsgRecovery point check result: Volume: [%1!s!], File System: [%2!s!], Volume Type: [%3!s!], Error [%4!s!]WRecovery point check for node [%1!s!], session number [%2!d!] failed with error [%3!d!]SimpleSpannedStripedMirroredRAID-5UnknownFRecovery point check for node [%1!s!], session number [%2!d!] canceledFThe backup job will use the "Microsoft VSS inside VM" snapshot method.;The backup job will use the "VMware Tools" snapshot method.~Backup job unable deploy/undeploy tools for the "Microsoft VSS inside VM" snapshot method. The VMware Tools is not up to date.Abort backup because backup job has been configured to use the "Microsoft VSS inside VM" snapshot method. However, only the "VMware Tools" snapshot method is applicable because Host-Based VM Backup failed to deploy the necessary tools into the VM.Abort backup because backup job has been configured to use the "VMware Tools" snapshot method. However, only the "Microsoft VSS inside VM" snapshot method is applicable because Host-Based VM Backup failed to undeploy tools from inside VM.iThe VM is not a Windows machine. As a result, the backup job will use the "VMware Tools" snapshot method.BThe VM guest operation failed. ESX/vCenter reports error: "%1!s!".xHost-Based VM Backup failed to deploy the necessary tools for the "Microsoft VSS inside VM" snapshot method into the VM.Host-Based VM Backup failed to undeploy the tools for the "Microsoft VSS inside VM" snapshot method to enable the "VMware Tools" snapshot method from inside the VM .[Host-Based VM Backup failed to detect the current snapshot method from inside the VM guest.The ESX server version is 4.x; however, VIX of version 1.13.3 or later is not installed (but required) in the backup proxy machine. As a result, Host-Based VM Backup cannot perform VM guest operations to configure the snapshot method from inside the VM.The guest VM credentials are empty. As a result, Host-Based VM Backup cannot perform VM guest operations to configure the snapshot method from inside the VM. Please update the credentials via the console UI.zRecovery point %1!d! cannot support an application restore because the "Microsoft VSS inside VM" snapshot method was used.The chkdsk command was unable to complete the process within the expected time. The possible reason could be high system load. Please refer to the Arcserve UDP Solutions Guide for details.hData inconsistency found in recovery point %1!d!, the next job will be converted to a verify backup job.cData inconsistency was found in the previous job, the job will be converted to a verify backup job.The snapshot is taken without quiescing the file system in the virtual machine. As a result, the snapshot cannot represent a consistent state of the guest file systems. In case the virtual machine is powered off or VMware Tools are not available, the quiesce flag is ignored.PA%The operation completed successfully.An unknown error occurred.!An unknown server error occurred.Bad application parameters.PALost acknowledgement.Connection broken.&Connection to remote server is closed.Connection timeout.Invalid socket.CA non-blocking socket operation could not be completed immediately.Too many open sockets..A socket operation encountered a dead network.~An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.KNo connection could be made because the target machine actively refused it.>An existing connection was forcibly closed by the remote host.hA connection attempt failed because the connected party did not properly respond after a period of time.A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call.;A socket operation was attempted to an unreachable network.2The requested address is not valid in its context.Failed to initialize SSL.Failed to send data via SSL.The parameter is incorrect.$Connection handshake error occurred.PAAttempt to connect the proxy server failed. Please make sure the proxy configuration is correct and can connect to the destination server.:The proxy server requires user credential to authenticate.+The configuration file format is incorrect.*The transport type parameter is incorrect.The file type is incorrect.-The system cannot allocate the needed memory."Unable to load the file interface.MAn attempt to connect the server timed out without establishing a connection.0The target file size is larger than source size.6The client context or the server context is incorrect.'The received packet is out of sequence.bThe asynchronous sending has not get the expected reply from the server within the timeout period.>An existing connection was forcibly closed by the remote host.>The size of GDD configure file is too large. The limit is 4MB.PA#An invalid file command was caught.$The server is down or not available.9The target file size is larger than the source file size.CThe asynchronous sending method has encountered the internal error.bThe asynchronous sending has not get the expected reply from the server within the timeout period.PACFailed to create session lock file %1!s!. Error code:%2!d! (%3!s!).KFailed to read data from session lock file %1!s!. Error code:%2!d! (%3!s!).JFailed to write data to session lock file %1!s!. Error code:%2!d! (%3!s!).@Failed to create session lock on %1!s!. Error code:%2!d!(%3!s!).BackupMergeCatalogRestoreCopy Recovery PointHost Base VM Backup	File CopyMount Recovery PointBare Metal RecoveryLite IntegrationVirtual StandbyReplicationFailed to lock session on %1!s! (detail information:%2!s!). Session was already locked by %3!s! job, Computer name:%4!s!, Process Id:%5!d!.The SQLite database (which is used for saving the activity log) is damaged and cannot be accessed. Please contact arcserve support to repair the database.The SQLite database (which is used for saving the job history) is damaged and cannot be accessed. Please contact arcserve support to repair the database.PA!The transport mode used is %1!s!.LA VMware VDDK error has occurred. Error message [%1!s!]. Error code [%2!d!].uFailed to open the virtual disk [%1!s!]. A VMware VDDK error has occurred. Error message [%2!s!]. Error code [%3!d!].vFailed to write the virtual disk [%1!s!]. A VMware VDDK error has occurred. Error message [%2!s!]. Error code [%3!d!].{Failed to connect to node [%1!s!]. Error=[%2!s!]. Error code=[%3!d!]. Verify that the server is up, running, and reachable.Failed to write the virtual disk [%1!s!]. A VMware VDDK error has occurred. Error message [%2!s!]. Error code [%3!d!]. Retry time=[%4!d!].+Begin to convert backup disk image [%1!s!].OpenSave AsAll Files (*.*)Untitledan unnamed filePA&HidePANo error message is available.#Attempted an unsupported operation.$A required resource was unavailable.Out of memory.An unknown error has occurred.!Encountered an improper argument.on %1	&One Page	&Two PagePage %uPage %u
Pages %u-%u
prn
Output.prn1Printer Files (*.prn)|*.prn|All Files (*.*)|*.*||
Print to Fileto %1	Linked %sUnknown TypePAIncorrect filename.Failed to open document.Failed to save document.Save changes to %1? Failed to create empty document.The file is too large to open.Could not start print job.Failed to launch help.Internal application error.Command failed.)Insufficient memory to perform operation.PSystem registry entries have been removed and the INI file (if any) was deleted.BNot all of the system registry entries (or INI file) were removed.FThis program requires the file %s, which was not found on this system.tThis program is linked to the missing export %s in the file %s. This machine may have an incompatible version of %s.PAEnter an integer.Enter a number.#Enter an integer between %1 and %2.!Enter a number between %1 and %2.!Enter no more than %1 characters.Select a button.#Enter an integer between 0 and 255.Enter a positive integer.Enter a date and/or time.Enter a currency.
Enter a GUID.
Enter a time.
Enter a date.Unexpected file format.O%1
Cannot find this file.
Verify that the correct path and file name are given.Destination disk drive is full.5Unable to read from %1, it is opened by someone else.AUnable to write to %1, it is read-only or opened by someone else.1Encountered an unexpected error while reading %1.1Encountered an unexpected error while writing %1.PA%1: %2
Continue running script?Dispatch exception: %1PA6The file is not supported by a Document Object server.A%1
Unable to register document.
The document may already be open.#Unable to read write-only property.#Unable to write read-only property.PA#Unable to load mail system support.Mail system DLL is invalid.!Send Mail failed to send message.PANo error occurred.-An unknown error occurred while accessing %1.%1 was not found.%1 contains an incorrect path.8Could not open %1 because there are too many open files.Access to %1 was denied.0An incorrect file handle was associated with %1.8Could not remove %1 because it is the current directory.2Could not create %1 because the directory is full.Seek failed on %14Encountered a hardware I/O error while accessing %1.3Encountered a sharing violation while accessing %1.3Encountered a locking violation while accessing %1.Disk full while accessing %1.$Attempted to access %1 past its end.No error occurred.-An unknown error occurred while accessing %1.%Attempted to write to the reading %1.$Attempted to access %1 past its end.&Attempted to read from the writing %1.%1 has a bad format."%1 contained an unexpected object. %1 contains an incorrect schema.pixelsUncheckCheckMixed,One or more auto-saved documents were found.These are more recently saved than the currently open documents and contain changes that were made before the application closed.2Do you want to recover these auto-saved documents?Note that if you choose to recover the auto-saved documents, you must explicitly save them to overwrite the original documents.  If you choose to not recover the auto-saved versions, they will be deleted.fRecover the auto-saved documents
Open the auto-saved versions instead of the explicitly saved versions^Don't recover the auto-saved documents
Use the last explicitly saved versions of the documents%s [Recovered]"! @4 PA @4% &PA @4 PA @4 PA @4 PA @4	 
PA @ PA @
 PA @ PA @ PA @4 PA @4 PA @4 @4 @4 @4 @4! @4 @4 @4 @4 @4 @4  @4" @4# @4$4VS_VERSION_INFO>i?StringFileInfo040904E4>FileVersionr5.0.1897.1086j!FileDescriptionArcserve Unified Data Protection4
InternalNameAFMSG.DLL<
OriginalFilenameAFMSG.DLLVCommentsBuild 1897.1086 Fri 05/15/2015&CompanyNameCAr'LegalCopyrightCopyright (C) 2015 Arcserve (USA), LLCb!ProductNameArcserve Unified Data Protection.ProductVersionr5.0DVarFileInfo$Translation	<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
  <trustInfo xmlns="urn:schemas-microsoft-com:asm.v3">
    <security>
      <requestedPrivileges>
        <requestedExecutionLevel level="asInvoker" uiAccess="false"></requestedExecutionLevel>
      </requestedPrivileges>
    </security>
  </trustInfo>
</assembly>PAPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGX Р0	*H
010	+0h
+7Z0X03
+70% <<<Obsolete>>>0!0	+7e3\XV龚}H:00R3=#0
	*H
0o10	UUS10U
DigiCert Inc10Uwww.digicert.com1.0,U%DigiCert Assured ID Code Signing CA-10
150305000000Z
151220120000Z0r10	UUS10U	Minnesota10UEden Prairie10U
Arcserve (USA) LLC10UArcserve (USA) LLC0"0
	*H
0
ph%léWaS؊lI.~队y1:ޫ^Cj}wmR9Ta˲\b,ҙy1"wjVli؋?]aYQ/oٞެT?4pdj$/GkhZMtG+;-~R[chv/Yt(aOmg⒚Qm<bǕ(H!X^<'{}00U#0{h)Iz?֧E520U_o}Q⣳TX0U0U%0
+0mUf0d00.,*http://crl3.digicert.com/assured-cs-g1.crl00.,*http://crl4.digicert.com/assured-cs-g1.crl0BU ;0907	`Hl0*0(+https://www.digicert.com/CPS0+v0t0$+0http://ocsp.digicert.com0L+0@http://cacerts.digicert.com/DigiCertAssuredIDCodeSigningCA-1.crt0U00
	*H
O}81ѹeu'XH~"hTE>|:2z͌"V|8WsF`E6bZA{1՗p$ŗ{{F"46ڴ}:jm=

g<0(s/ӉEfhae1b5ы6Ƽ&/qU) C}BPTmϽ?f'lbl酫QO6?gf(`9W4	9-32	l2xR0j0R:Xkf0
	*H
0b10	UUS10U
DigiCert Inc10Uwww.digicert.com1!0UDigiCert Assured ID CA-10
141022000000Z
241022000000Z0G10	UUS10U
DigiCert1%0#UDigiCert Timestamp Responder0"0
	*H
0
d]|5*Iu;nSdY|kkUZc[IPكof˅_ԇtD;9$K,^(dPs
gaxu[E#DU}UyHFN_⨶-Yaarh|4/1w06'L1d~6[zzx.Fȍ`ۼstN@pF@Y:	WV0akbBw5010U0U00U%0
+0U 00	`Hl00(+https://www.digicert.com/CPS0d+0VRAny use of this Certificate constitutes acceptance of the DigiCert CP/CPS and the Relying Party Agreement which limit liability and are incorporated herein by reference.0	`Hl0U#0+ߢW
+g0UaZM$I2J*yK}0}Uv0t08642http://crl3.digicert.com/DigiCertAssuredIDCA-1.crl08642http://crl4.digicert.com/DigiCertAssuredIDCA-1.crl0w+k0i0$+0http://ocsp.digicert.com0A+05http://cacerts.digicert.com/DigiCertAssuredIDCA-1.crt0
	*H
%~3M&\# j,1:qͩZ9lZ@7$~ W[`&iW!]4/qk5{?Ab'=8(o:R	pbbKsӎ1/mCq!]Aљt
&w(ؓU
\H'fȣ
ڮ.YamamUT@+kQ
Hn
:=ʯj{D00I!vm0
	*H
0e10	UUS10U
DigiCert Inc10Uwww.digicert.com1$0"UDigiCert Assured ID Root CA0
110211120000Z
260210120000Z0o10	UUS10U
DigiCert Inc10Uwww.digicert.com1.0,U%DigiCert Assured ID Code Signing CA-10"0
	*H
0
|
ʉKS<"HD?"nO$RrFūxz&|S/j(̠K ˸@EO9;oi\.f馸ޮbD'&Iq8mN\gwofdkIh~!	K1jZBG}`+١]Vr>2*,2F^cиL5P_CD|DP*=tzrKVc?NI#%(Ad;]C0?0U0U%0
+0U 00`Hl00:+.http://www.digicert.com/ssl-cps-repository.htm0d+0VRAny use of this Certificate constitutes acceptance of the DigiCert CP/CPS and the Relying Party Agreement which limit liability and are incorporated herein by reference.0U00y+m0k0$+0http://ocsp.digicert.com0C+07http://cacerts.digicert.com/DigiCertAssuredIDRootCA.crt0Uz0x0:864http://crl3.digicert.com/DigiCertAssuredIDRootCA.crl0:864http://crl4.digicert.com/DigiCertAssuredIDRootCA.crl0U{h)Iz?֧E520U#0E뢯˂1-Q!m0
	*H
{rd:ć۔אY3+ި[%?|C9>;!%{$r]GF?jQ8޴%(TyF$8&aM(?Ī5SO=l#Mg	:=<6Lv:V5/Leȑj-#O7;՜<ձkx͜Q[B&rZ
J#@"“:ԛh)<ĆGBq2	r	yKqiA9wd񄍾}h00
?'0
	*H
0e10	UUS10U
DigiCert Inc10Uwww.digicert.com1$0"UDigiCert Assured ID Root CA0
061110000000Z
211110000000Z0b10	UUS10U
DigiCert Inc10Uwww.digicert.com1!0UDigiCert Assured ID CA-10"0
	*H
0
-Bs@pҞVT\A3ME\,Yߞ$˜wI܉
گ^kq1:@FMz64I1H|PƇ6?0os#V2!p}C;=A?ەH+]Bns?&KYf
čoHO@L@]\/"kes
t\Bh~w
'V|b?2`	z0v0U0;U%402+++++0U 00
`Hl00:+.http://www.digicert.com/ssl-cps-repository.htm0d+0VRAny use of this Certificate constitutes acceptance of the DigiCert CP/CPS and the Relying Party Agreement which limit liability and are incorporated herein by reference.0	`Hl0U00y+m0k0$+0http://ocsp.digicert.com0C+07http://cacerts.digicert.com/DigiCertAssuredIDRootCA.crt0Uz0x0:864http://crl3.digicert.com/DigiCertAssuredIDRootCA.crl0:864http://crl4.digicert.com/DigiCertAssuredIDRootCA.crl0U+ߢW
+g0U#0E뢯˂1-Q!m0
	*H
FP>ɷ($8[)RR1GV\{
Aut8\aP䂹#Ѻ:r8xu]4rGV6w$Ub-ҵ^O=[1b39xv%s*ϜvK_KKpLyLW_]8O
]gEփ
iOY#Ҫ|Bϑ'ý|
,U"M*!I1GwqܱKKwO/Z)&100,00o10	UUS10U
DigiCert Inc10Uwww.digicert.com1.0,U%DigiCert Assured ID Code Signing CA-1R3=#0	+p0
+7100	*H
	1
+70
+710
+70#	*H
	1E632+0
	*H
u)USqWMcag2'1zZ{͐TJ]m82V9(a(vVg¸0L?@1%L ԣ-5S'ŠPCkVpe)`V" YULW{_S%F -zLb ^2y.ԧdNBa0)տ,%gϳ'$%edk
@p$ $ P)W6+,2ś0	*H
	100v0b10	UUS10U
DigiCert Inc10Uwww.digicert.com1!0UDigiCert Assured ID CA-1:Xkf0	+]0	*H
	1	*H
0	*H
	1
150515184854Z0#	*H
	15IhMZtN0
	*H
6	'E|$"o;bWns8R'@:G@#G~Fc+8F[8[ +&Y+ingӣ˩:*qbc*K"f;UԵ%Kwӷ2%jjV@שyJa6Il|	zjܘF~CfCPy8b'"lPHݐ$52̀:$RvPd'>iZt

Anon7 - 2022
AnonSec Team