public:vmware
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
public:vmware [2018/05/04 13:41] yuk.cheng |
public:vmware [2019/08/08 14:19] ronnie.chan |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | =====VMware===== | + | ===== VMware ===== |
| - | [[public:5048_faq:how_to_create_a_vmware_backup_set_to_be_used_with_the_run_direct_feature|FAQ: How to create a VMware backup set to be used with the Run Direct feature?]] | + | Below are the FAQs and Issues related to VMware backup set type. |
| - | [[public:5049_faq:how_to_instantly_startup_a_vmware_virtual_machine_with_the_run_direct_feature_with_migration|FAQ: How to instantly startup a VMware virtual machine with the Run Direct feature (with migration)?]] | + | ===== FAQs ===== |
| - | [[public:5050_faq:how_to_instantly_startup_a_vmware_virtual_machine_with_the_run_direct_feature_without_migration|FAQ: How to instantly startup a VMware virtual machine with the Run Direct feature (without migration)?]] | + | * [[public:5048_faq:how_to_create_a_vmware_backup_set_to_be_used_with_the_run_direct_feature|How to create a VMware backup set to be used with the Run Direct feature?]] |
| - | [[public:5072_issue:incorrect_error_message_another_backup_job_is_still_running_is_displayed_vmware_vm_backup|ISSUE: Incorrect error message 'Another backup job is still running' is displayed (VMware VM backup)]] | + | * [[public:5049_faq:how_to_instantly_startup_a_vmware_virtual_machine_with_the_run_direct_feature_with_migration|How to instantly startup a VMware virtual machine with the Run Direct feature (with migration)?]] |
| - | [[public:5083_issue:vmware_vm_backup_job_cannot_run_to_completion_for_backup_set_with_backup_schedule_disabled|ISSUE: VMware VM backup job cannot run to completion (for backup set with backup schedule disabled)]] | + | * [[public:5050_faq:how_to_instantly_startup_a_vmware_virtual_machine_with_the_run_direct_feature_without_migration|How to instantly startup a VMware virtual machine with the Run Direct feature (without migration)?]] |
| - | [[public:5176_doc:ahsayobm_v7_user_guide_-_vmware_vm_backup_and_restore|DOC: AhsayOBM v7 User Guide - VMware VM Backup and Restore]] | + | ===== Issues ===== |
| - | [[public:5205_issue:guest_virtual_machines_are_not_shown_in_ahsayobm_backup_source_when_creating_a_vmware_workstation_backup_set|ISSUE: Guest virtual machines are not listed in AhsayOBM backup source when creating a VMware Workstation backup set]] | + | * [[public:5072_issue:incorrect_error_message_another_backup_job_is_still_running_is_displayed_vmware_vm_backup|Incorrect error message 'Another backup job is still running' is displayed (VMware VM backup)]] |
| - | [[public:5206_issue:cannot_connect_ssh_please_check_the_ssh_settings_error_when_creating_a_backup_set_on_a_vmware_esxi_6.0_update_2_host|ISSUE: "Cannot connect SSH, please check the SSH settings" error when creating a backup set on a VMware ESXi 6.0 Update 2 host]] | + | * [[public:5083_issue:vmware_vm_backup_job_cannot_run_to_completion_for_backup_set_with_backup_schedule_disabled|VMware VM backup job cannot run to completion (for backup set with backup schedule disabled)]] |
| - | [[public:5222_issue:vmware_esxi_vcenter_vm_cannot_start_up_properly_with_operation_system_not_found_error_run_direct_restore_failing_where_the_backup_destination_is_located_on_a_network_drive|ISSUE: VMware VM cannot start up properly with Operation System not found error (Run Direct restore failing when the backup destination is located on a network drive)]] | + | * [[public:5205_issue:guest_virtual_machines_are_not_shown_in_ahsayobm_backup_source_when_creating_a_vmware_workstation_backup_set|Guest virtual machines are not listed in AhsayOBM backup source when creating a VMware Workstation backup set]] |
| - | [[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:5206_issue:cannot_connect_ssh_please_check_the_ssh_settings_error_when_creating_a_backup_set_on_a_vmware_esxi_6.0_update_2_host|"Cannot connect SSH, please check the SSH settings" error when creating a backup set on a VMware ESXi 6.0 Update 2 host]] |
| - | [[public:5234_issue:cannot_connect_ssh_please_check_the_ssh_settings_error_when_creating_a_backup_set_on_a_vmware_esxi_host|ISSUE: "Cannot connect SSH, please check the SSH settings" error when creating a backup set on a VMware ESXi host]] | + | * [[public:5222_issue:vmware_esxi_vcenter_vm_cannot_start_up_properly_with_operation_system_not_found_error_run_direct_restore_failing_where_the_backup_destination_is_located_on_a_network_drive|VMware VM cannot start up properly with Operation System not found error (Run Direct restore failing when the backup destination is located on a network drive)]] |
| - | [[public:5240_issue:unable_to_find_vmrun.exe_in_c:program_files_x86_vmware_vmware_player_or_c:program_files_x86_vmware_vmware_vix_when_creating_a_vmware_workstation_backupset|ISSUE: Unable to find vmrun.exe in "‘C:\Program Files (x86)\VMware\VMware Player’ or ‘C:\Program Files (x86)\VMware\VMware VIX’” when creating a VMware Workstation BackupSet ]] | + | * [[public:5232_nfs_service_on_this_machine_is_not_started|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: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:5234_issue:cannot_connect_ssh_please_check_the_ssh_settings_error_when_creating_a_backup_set_on_a_vmware_esxi_host|"Cannot connect SSH, please check the SSH settings" error when creating a backup set on a VMware ESXi host]] |
| - | [[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:5240_issue:unable_to_find_vmrun.exe_in_c:program_files_x86_vmware_vmware_player_or_c:program_files_x86_vmware_vmware_vix_when_creating_a_vmware_workstation_backupset|Unable to find vmrun.exe in "‘C:\Program Files (x86)\VMware\VMware Player’ or ‘C:\Program Files (x86)\VMware\VMware VIX’” when creating a VMware Workstation BackupSet ]] |
| - | [[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: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: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: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:5257_issue:hostname_cannot_be_empty_error_is_shown_when_starting_vmware_esxi_vcenter_run_direct_restore_from_ahsaycbs_user_web_console|ISSUE: “Hostname cannot be empty” error is shown when starting VMware Run Direct restore from AhsayCBS web console]] | + | * [[public:5245_issue:vmware_esxi_scheduled_backup_job_missed_with_current_license_or_esxi_version_prohibits_execution_error|VMware ESXi scheduled backup job missed with 'Current license or ESXi version prohibits execution' error]] |
| - | [[public:5265_issue:failed_to_restore_new_virtual_machine_._reason_fail_to_set_entity_permission._error_unknown_error_from_class_com.vmware.vim25.usernotfound_when_restoring_a_guest_vm_to_another_vmware_esxi_host|ISSUE:"Failed to restore "New Virtual Machine". Reason = "Fail to set entity permission. Error=Unknown error from class "com.vmware.vim25.UserNotFound" when restoring a guest VM to another VMware ESXi host]] | + | * [[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|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:5267_issue:no_backup_set_can_start_run_direct_message_shown_when_initiating_a_vmware_esxi_vcenter_run_direct_restore_on_ahsaycbs_user_web_console|ISSUE:"No backup set can start Run Direct" message shown when initiating a VMware ESXi/vCenter Run Direct restore on AhsayCBS user web console]] | + | * [[public:5257_issue:hostname_cannot_be_empty_error_is_shown_when_starting_vmware_esxi_vcenter_run_direct_restore_from_ahsaycbs_user_web_console|“Hostname cannot be empty” error is shown when starting VMware Run Direct restore from AhsayCBS web console]] |
| - | [[public:5268_issue:ip_address_xxx.xxx.xxx.xxx_of_the_virtualcenter_server_managing_this_host._please_either_connect_this_host_through_it_or_disconnect_this_host_from_it._error_is_shown_when_creating_a_vmware_esxi_backup_set|ISSUE: "IP address "xxx.xxx.xxx.xxx" of the VirtualCenter server managing this host. Please either connect this host through it or disconnect this host from it." error is shown when creating a VMware ESXi backup set]] | + | * [[public:5265_issue:failed_to_restore_new_virtual_machine_._reason_fail_to_set_entity_permission._error_unknown_error_from_class_com.vmware.vim25.usernotfound_when_restoring_a_guest_vm_to_another_vmware_esxi_host|ISSUE:"Failed to restore "New Virtual Machine". Reason = "Fail to set entity permission. Error=Unknown error from class "com.vmware.vim25.UserNotFound" when restoring a guest VM to another VMware ESXi host]] |
| - | [[public:5270_issue:cloudexception.connectfailedexpt_sftpmanager.login_failed_to_access_sftp_error_when_create_vmware_esxi_backup_set|ISSUE: "[CloudException.ConnectFailedExpt[SFtpManager.login] Failed to access SFTP" error when create VMware ESXi backup set]] | + | * [[public:5267_issue:no_backup_set_can_start_run_direct_message_shown_when_initiating_a_vmware_esxi_vcenter_run_direct_restore_on_ahsaycbs_user_web_console|ISSUE:"No backup set can start Run Direct" message shown when initiating a VMware ESXi/vCenter Run Direct restore on AhsayCBS user web console]] |
| - | [[public:5275_issue:falied_to_list_file_the_media_is_write_protected._when_mounting_a_vmware_esxi_vcenter_window_10_guest_vm_virtual_disk_using_granular_restore|ISSUE:"Falied to list file (the media is write protected" when mounting a VMware ESXi/vCenter Window 10 guest VM virtual disk using Granular Restore]] | + | * [[public:5268_issue:ip_address_xxx.xxx.xxx.xxx_of_the_virtualcenter_server_managing_this_host._please_either_connect_this_host_through_it_or_disconnect_this_host_from_it._error_is_shown_when_creating_a_vmware_esxi_backup_set|"IP address "xxx.xxx.xxx.xxx" of the VirtualCenter server managing this host. Please either connect this host through it or disconnect this host from it." error is shown when creating a VMware ESXi backup set]] |
| + | * [[public:5270_issue:cloudexception.connectfailedexpt_sftpmanager.login_failed_to_access_sftp_error_when_create_vmware_esxi_backup_set|"[CloudException.ConnectFailedExpt[SFtpManager.login] Failed to access SFTP" error when create VMware ESXi backup set]] | ||
| + | * [[public:5275_issue:falied_to_list_file_the_media_is_write_protected._when_mounting_a_vmware_esxi_vcenter_window_10_guest_vm_virtual_disk_using_granular_restore|ISSUE:"Falied to list file (the media is write protected" when mounting a VMware ESXi/vCenter Window 10 guest VM virtual disk using Granular Restore]] | ||
public/vmware.txt · Last modified: 2022/11/28 11:11 by kirk.lim