User Tools

Site Tools


public:faqs_v7

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
public:faqs_v7 [2019/09/26 15:48]
ronnie.chan
public:faqs_v7 [2019/09/26 15:51] (current)
ronnie.chan
Line 341: Line 341:
   * [[public:​5230_issue:​curl:​not_found_file_does_not_exist_error_when_installing_ahsayobm_v7_on_linux_freebsd_using_cli|ISSUE:​ ‘curl: not found File does not exist’ error when installing AhsayOBM v7 on Linux or FreeBSD using CLI  ]]   * [[public:​5230_issue:​curl:​not_found_file_does_not_exist_error_when_installing_ahsayobm_v7_on_linux_freebsd_using_cli|ISSUE:​ ‘curl: not found File does not exist’ error when installing AhsayOBM v7 on Linux or FreeBSD using CLI  ]]
  
-  * [[public:​5231_issue:​when_performing_a_backup_job_on_ahsayobm_ahsayacb_the_following_error_is_shown_chunkedoutputstream.flushdata.execute_failed_to_flush_buffer_to_this_destination_error_com.ahsay.afc.cloud.d_failed_to_get_outputstream_of_file|ISSUE: When performing a backup job on AhsayOBM/​AhsayACB the following error is shown (ChunkedOutputStream.FlushData.execute Failed to flush buffer to this destination Error=com.ahsay.afc.cloud.d Failed to get OutputStream of file" ]]+  * [[public:​5231_issue:​chunkedoutputstream.flushdata.execute_failed_to_flush_buffer_to_this_destination_error|ISSUE: When performing a backup job on AhsayOBM/​AhsayACB the following error is shown (ChunkedOutputStream.FlushData.execute Failed to flush buffer to this destination Error=com.ahsay.afc.cloud.d Failed to get OutputStream of file" ]]
  
   * [[public:​5232_nfs_service_on_this_machine_is_not_started|ISSUE:​ When perform a VMware Run Direct restore on AhsayOBM the following error is shown “The NFS Service on this machine is not started or not functioning properly. This service is required for VM Run Direct. ​ ]]   * [[public:​5232_nfs_service_on_this_machine_is_not_started|ISSUE:​ When perform a VMware Run Direct restore on AhsayOBM the following error is shown “The NFS Service on this machine is not started or not functioning properly. This service is required for VM Run Direct. ​ ]]
Line 361: Line 361:
   * [[public:​5242_issue:​invalid_license_error_is_shown_when_logging_into_ahsayobm_on_a_synology_nas_device|ISSUE:​ “Invalid license” error is shown when logging into AhsayOBM on a Synology NAS device ​  ]]   * [[public:​5242_issue:​invalid_license_error_is_shown_when_logging_into_ahsayobm_on_a_synology_nas_device|ISSUE:​ “Invalid license” error is shown when logging into AhsayOBM on a Synology NAS device ​  ]]
  
-  * [[public:5243_ISSUE:%22The%20specified%20virtual%20machine%20could%20not%20be%20found.%22%20warning%20is%20shown%20on%20VMware%20Workstation%20scheduled%20backup%20job|ISSUE:"​The specified virtual machine could not be found."​ warning is shown on VMware Workstation scheduled backup job  ]]+  * [[public:5243_issue:the_specified_virtual_machine_could_not_be_found._warning_is_shown_on_vmware_workstation_scheduled_backup_job|ISSUE:"​The specified virtual machine could not be found."​ warning is shown on VMware Workstation scheduled backup job  ]]
  
-  * [[public:5244_ISSUE:%22Reason%20=%20%22UUID%20conflict%20on%20Virtual%20Machine.%22%20error%20is%20shown%20on%20VMware%20ESXi%20backup%20job|ISSUE:"​Reason = "UUID conflict on Virtual Machine."​ error is shown on VMware ESXi backup job ]]+  * [[public:5244_issue:reason_uuid_conflict_on_virtual_machine._error_is_shown_on_vmware_esxi_backup_job|ISSUE:"​Reason = "UUID conflict on Virtual Machine."​ error is shown on VMware ESXi backup job ]]
  
   * [[public:​5245_issue:​vmware_esxi_scheduled_backup_job_missed_with_current_license_or_esxi_version_prohibits_execution_error|ISSUE:​ VMware ESXi scheduled backup job missed with '​Current license or ESXi version prohibits execution'​ error ]]   * [[public:​5245_issue:​vmware_esxi_scheduled_backup_job_missed_with_current_license_or_esxi_version_prohibits_execution_error|ISSUE:​ VMware ESXi scheduled backup job missed with '​Current license or ESXi version prohibits execution'​ error ]]
  
-  * [[public:5246_ISSUE:%20AhsayOBM/​AhsayACB%20v7%20file%20backup%20jobs%20ends%20with%20%22Snapshot%20for%20Shadow%20Copy%20Set%20is%20missing,​%20backup%20terminate.%22%20error|ISSUE: AhsayOBM/​AhsayACB v7 file backup jobs ends with "​Snapshot for Shadow Copy Set is missing, backup terminate."​ error ]]+  * [[public:5246_issue:ahsayobm_ahsayacb_v7_file_backup_jobs_ends_with_snapshot_for_shadow_copy_set_is_missing_backup_terminate._error|ISSUE: AhsayOBM/​AhsayACB v7 file backup jobs ends with "​Snapshot for Shadow Copy Set is missing, backup terminate."​ error ]]
  
   * [[public:​5247_faq:​tips_on_how_to_setup_the_temporary_directory_for_your_backup_set|FAQ:​ Tips On How To Setup The Temporary Directory For Your Backup Set ]]   * [[public:​5247_faq:​tips_on_how_to_setup_the_temporary_directory_for_your_backup_set|FAQ:​ Tips On How To Setup The Temporary Directory For Your Backup Set ]]
Line 381: Line 381:
   * [[public:​5252_issue:​vmware_esxi_vcenter_vddk_mode_backup_job_ends_with_error_snapshot_not_taken_since_the_state_of_the_virtual_machine_has_not_changed_since_the_last_snapshot_operation|ISSUE:​ VMware ESXi/​vCenter VDDK mode backup job ends with "​Error=Snapshot not taken since the state of the virtual machine has not changed since the last snapshot operation."​ ]]   * [[public:​5252_issue:​vmware_esxi_vcenter_vddk_mode_backup_job_ends_with_error_snapshot_not_taken_since_the_state_of_the_virtual_machine_has_not_changed_since_the_last_snapshot_operation|ISSUE:​ VMware ESXi/​vCenter VDDK mode backup job ends with "​Error=Snapshot not taken since the state of the virtual machine has not changed since the last snapshot operation."​ ]]
  
-  * [[public:5253_ISSUE:%20%22VHD%20Mounter%20-%20Administrator%20Privilege%20(No)%22%20error%20when%20performing%20a%20granular%20restore%20on%20a%20Hyper-V%20guest%20VM|ISSUE: "VHD Mounter - Administrator Privilege (No)" error when performing a granular restore on a Hyper-V guest VM ]]+  * [[public:5253_issue:vhd_mounter_-_administrator_privilege_no_error_when_performing_a_granular_restore_on_a_hyper-v_guest_vm|ISSUE: "VHD Mounter - Administrator Privilege (No)" error when performing a granular restore on a Hyper-V guest VM ]]
  
   * [[public:​5254_issue:​failed_to_mount_virtual_disk_virtual_disk_name_.vhd_no_valid_partition_found_when_performing_a_granular_restore_on_a_linux_or_unix_guest_vm_on_hyper-v|ISSUE:​ "​Failed to mount virtual disk "​%virtual_disk_name%.vhd"​ (No Valid Partition Found)"​ when performing a granular restore on a Linux or Unix guest VM on Hyper-V ]]   * [[public:​5254_issue:​failed_to_mount_virtual_disk_virtual_disk_name_.vhd_no_valid_partition_found_when_performing_a_granular_restore_on_a_linux_or_unix_guest_vm_on_hyper-v|ISSUE:​ "​Failed to mount virtual disk "​%virtual_disk_name%.vhd"​ (No Valid Partition Found)"​ when performing a granular restore on a Linux or Unix guest VM on Hyper-V ]]
public/faqs_v7.txt · Last modified: 2019/09/26 15:51 by ronnie.chan