text/microsoft-resx 2.0 System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 Bad sorting of backup times detected Bad sort order on volumes detected When using cleanup the manifests and hashes must be verified Deleting backup at {0} The option {0} is deprecated: {1} The option --{0} exists more than once, please report this to the developers Failed to find control files in: {0} A hash check failed, this is an indication of a corrupt file: {0} Files are not deleted, use the --force command to actually remove files An internal error occured, and the operation was aborted to protect the backup sets It is not allowed to disable manifest reading when performing a backup. Disabling manifests is only possible on restores, and it should only be used as a last resort. One or more manifests are from version 1, which requires that filenames searched are relative The signature file for a content volume was missing, date: {0}, volumenumber: {1}, content volume filename: {2} No filenames given for find-last-file No source folders specified for backup Not deleting backup at time: {0}, because later backups depend on it The backup at time {0} is not removed because it is the last full backup, use --allow-full-removal to include this backup in the delete The number of source folders in the latest backup is {0}, but the number of specified folders is now {1}. It is not allowed to change source folders for a backup. Failed after uploading {0} volume(s). Error message: {1} Failed to read the primary manifest {0}, attempting secondary, if available. Error message: {1} Secondary manifest file found: {0}, attempting read. Removing partial file: {0} Failed to read the secondary manifest {0}. Error message: {1} Signature cache path was not given as an argument The content volume {0} is not present in the manifest and is not used The signature file {0} was skipped because the signature file was not found in the manifest The source folder {0} does not exist, aborting backup Building filelist ... Completed Creating volume {0} Downloading content, volume {0} Downloading signatures, volume {0} Loading remote filelist Patching restore with #{0} Processing: {0} Reading incremental data ... Reading incremental data from: {0} Reading incremental data Reading manifest file: {0} Reading signatures: {0}, vol {1} Started Uploading content, volume {0} Uploading manifest, volume {0} Uploading signatures, volume {0} Waiting for upload to complete ... The backup contains {0} folders but {1} target folders were supplied The backup contains {0} folder(s) but {1} target folders were supplied Unexpected compression mode: {0} The operation mode {0} was not expected The value "{1}" supplied to --{0} does not parse into a valid boolean, this will be treated as if it was set to "true" The option --{0} does not support the value "{1}", supported values are: {2} The value "{1}" supplied to --{0} does not represent a valid integer The option --{0} is not supported because the module {1} is not currently loaded The supplied option --{0} is not supported and will be ignored The value "{1}" supplied to --{0} does not represent a valid path The value "{1}" supplied to --{0} does not represent a valid size The value "{1}" supplied to --{0} does not represent a valid time Hash checks cannot be disabled while performing a backup Unable to verfiy the backup chain when the option --dont-read-manifests is active Hash checks cannot be disabled while performing a verification The signature cache is disabled when performing verification Disabling manifests is only possible on restores, and it should only be used as a last resort. The manifest file {0} indicates that the previous manifest file should be {1} but it was {2} The manifest file {0} indicates that the previous manifest hash should be {1} but it was {2} The file {0} has size {1} but should have size {2} The manifest report that the file should be named {0} but it was named {1} Uploading verification file If this error cannot be resolved, you can either create a new full backup or delete the offending manifests manually, followed by a cleanup command. The offending manifest files are: A full backup is made because no existing backup chains were found on the destination A full backup was forced with the --{0} flag A full backup is made because the latest full backup is from {0} and the full backup threshold is {1} A full backup is made because the source folders have changed A full backup is made because the current chain has {0} incremental backups and the full backup threshold is {1} An incremental backup is made because the latest full backup is from {0} and the full backup threshold is {1} An incremental backup is made because no full backup criteria was found An incremental backup is made because the current chain has {0} incremental backups and the full backup threshold is {1} An error occurred while running the backup, no files were uploaded: {0} The operation {0} has started The specified compression module was not found: {0}. Avaliable compression modules: {1} The specified encryption module was not found: {0}. Avaliable encryption modules: {1} The manifest file {0} is invalid, as it specifies that there should be {1} signature volumes and {2} content volumes. Additionally these files were found but are not listed in the manifest: The manifest file {0} specifies that there should be {1} volume pairs, but the following pairs were not found: {2} Failed to download signature file {0}, error message: {1} Failed to apply content file {0}, error message: {1} Hash mismatch on file "{0}", recorded hash: {1}, actual hash {2} The file {0} was downloaded and had size {1} but the size was expected to be {2} Invalid path: "{0}" ({1})