Category
제품 버전
항목
하위 항목
Restore of Hyper-V VM fails with error: No network card was found that met the specified criteria (4043696)
When restoring Hyper-V virtual machines, the virtual machine creation fails with the following message: ... Creating virtual machine 'Virtual Machine Name' failed: No network card that meets the specified criteria was found.
VM added to exclusion list without being selected (4041066)
VM's being added to exclusion list, even though the VM's are in a different host. ... Example ... alphatest (vmname) ... The disk name is the same for both, even if they are located in a different location (folder), vranger will see it the same for both VM's, so when you go ahead exclude one VM (alphatest), once saved even though the other vm (alpha) was not selected it will check it automatically Change the disk name needs to be different so the VM's can be exluded individually
Editing job shows "There are no machines included in the current state." (4038471)
When editing a job, see message, "There are no machines included in the current state." <div>The most likely cause of this issue is due to changes in the VirtualCenter Infrastructure (i.e., removing and re-adding an inventory item from the VirtualCenter or Host will cause ID mismatches).</div><div></div><div>If this is a physical machine then verify it is in the inventory.</div> Refresh inventory and recreate the job.
How to restore VM to a datastore lacking space for provisioned disk (4039319)
Customer would like to restore VM to a datastore that lack free space for provisioned disks. ... There is only one datastore available with 300GB free. ... Configured restore job fails due to lack of space.
Creating a Replication job not possible with following message: "Target host is not compatible with the VM hardware version" (4034257)
It is observed that when selecting a target host in the vRanger Replication wizard, it is not possible to select a destination host. ... Following message appears: "Target host is not compatible with VM hardware version"
Upgrade DR operating system for compatibility to vRanger 7.2 (4039347)
When an upgrade to vRanger 7.2 is performed the RDA repository operating system will require an upgrade to ensure compatibility. ... DR operating system required for compatibility to vRanger 7.2 is minimum if version 3.2.0194.0
VM is in an invalid power state for the current operation (4039334)
When restoring a VM from the repository, the following error is observed "VM is in an invalid power state for the current operation". ... The restore options selected were ‘Power on VM’ and the ‘Overwrite’ option was not selected.
Connection refused trying to add RDA repository (4039363)
When trying to add an RDA type repository for DR4100 or DR6000, receive "Connection refused" error. ... RDA device is on the latest 3.2 version of firmware. ... Upgrade vRanger to 7.2 to be able to access RDA on 3.2 firmware.
Failed to connect to repository. (4041078)
After upgrading or installing vRanger version 7.2 adding a RDA container as a repository results in the following error being observed: ... DR operating system required for compatibility to vRanger 7.2 is minimum if version 3.2.0194.0
Error: VSSUTIL_VOL_NOT_SNAPSHOTABLE (4038500)
The backup is also attempting to backup this device. ... Remove the USB device from the physical machine.
Backup and restore SQL database (4032721)
How to perform a backup and restore of the SQL database. ... which is a free download.</div><div></div><div></div><div><p> </p><p><strong>Back up the current vRanger DB.</strong></p></div><div>1.
Best practices for backup jobs to a Deduplication device with Cataloging enabled (4038490)
When running a backup of a VM with a large amount of files to a Deduplication device, default timeout of 10 minutes requires a significant increase. ... In some cases Cataloging process would take almost 20 hours.
Individual disk exclusion in a group backup (4040127)
In a vRanger backup that contains multiple VM’s, sometimes there is a necessity to exclude a certain disk from an individual VM. ... It is not possible to exclude individual disks on a single VM in a group backup.
Replication fails with "Object reference not set to an instance of an object" (4037258)
It is observed that a Replication job fails immediately with "Object reference not set to an instance of an object". ... Only source and destination hosts are added to vRanger inventory. ... When the Replication job is created, destination is shown as N/A - There should be an IP or FQDN of the destination host.
“A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond xx.xx.xx.xx”. (IP Address) (4033975)
When deploying a new Virtual Appliance from the vRanger GUI, the above error can be seen. ... The vRanger machine gets the IP address from VMware tools and attempts to connect to the IP address of the deployed Virtual Appliance on port 22.
vRanger Backup: Slow Catalog Performance During Backup (4037636)
When performing a backup of a VM, the cataloging process takes a long time to complete. ... Backups do complete successfully vRanger cataloging process and deduplication storage devices <div>vRanger catalogs the filesystem after the backup process completes, reading the information from the backup file.
How to restore archived backups in secondary devices (4043601)
As it may be required by the organization, backups can also be saved to a secondary device or location, like tape devices, external USB drives, among others. ... When these backup files are required to be restored (Full VM restore or file level restore), a manifest restore must be performed with all the files and folders that compose a savepoint.
Samba Remote Coe Execution Vulnerability - CVE-2015-0240 (4040131)
Versions: SAll versions of Samba from 3.5.0 to 4.2.0rc4 are vulnerable to an ... unexpected code execution vulnerability in the smbd file server daemon. ... A malicious client could send packets that may set up the stack in such a way that the freeing of memory in a subsequent anonymous netlogon packet could allow execution of arbitrary code.
Incremental backup runs full instead "The disk size has changed; a full backup will be performed" (4041011)
It has been observed that an incremental backup runs a full backup instead. ... Following message is present in the task log: "The disk size has changed; a full backup will be performed" ... Possible causes of the error message are:
Unable to set up restore task (4033370)
Unable to select a network during restore , you will not be able to proceed to the next tab . ... Depends on the customer vm network setting and Vmware setup By Selecting the option , "Select a network.." in the drop down you will be able to proceed further .
Transport methods available in vRanger (4037633)
This article outlines the transport methods available in vRanger Backup & Replication. ... Hot-add is a VMware feature which allows an administrator to add devices to a running Virtual Machine without having to power off the virtual machine.
Sweep to tape for vRanger 7.X.X and Symantec Backup Exec (4037266)
How to configure and use the sweep-to-tape feature in vRanger using Symantec Backup Exec? ... Last update to the original article was applied on 9/11/2014, no updates available for this. ... Wants to configure the use of vRanger integrating with Symantec BAckup EXEC.
Hyper-V group backup fails with: "VSS_E_Flush_Writes_Timeout" (4039279)
When backing up Hyper-V virtual machines located in CSV and non-CSV volumes, the tasks created fail immediately with the following message: ... Backing up individual VM's can be performed and complete successfully.
Replication job fails with ‘This replication was cancelled, and has now ended.’ (4038328)
Replication job has cancelled and the job has failed. ... The job has reached the default 24 hour timeout threshold. ... Increase the task timeout from the vRanger GUI. ... 2) Increase the task timeout from the default of ‘24’ hours to a larger value.
vRanger Notification: No task is created (4044629)
When running scheduled backup jobs with notifications enabled, you may receive an alert with the following message: ... vRanger Notification: No task is created When a job runs, vRanger will refresh the connection with vCenter in order to retrieve the objects required in order to perform the task.
신제품 조합