(And am considering calling them to help me now, even though I don't really think it is their problem. I even had to have WD talk me thru the transfer process. Needles to say, I'm sure you can tell that I am not very tech-savvy. To "move" my documents file from the backup folder on my desktop to list them under "My PC". Now I am unable to open my documents because I do not have permission! I also haven't been able
Downloaded files from old computer (HP - Windows7) using WD Passport Ultra. In case of a disaster you would simply power up the VM on the recovery server without the need to go through a restore operation, as would be the case when using backups.I am having the same exact problem as you did. Many users set up their “move task” to run nightly and send the VHDX to another host. This is in fact a common method used to create a backup recovery server. You could set “number of backups” to 1 and have BackupChain move each VHD over to another host and then delete the older VM copy. The above table allows users to fine-tune their retention settings as necessary. The default setting in BackupChain “Number of Backups” is 10, and it’s stored in the File Types tab: When you create a task to move the VHDs elsewhere, it is possible to keep more than one copy of each VHD. If you need this task to be repeated again, you can use the Scheduler tab in the main screen of BackupChain to set up a schedule.īonus: Move And Keep Just One or More Copies For example, \\MyServerOrNas\mySharedFolder would be rewritten as: \\MyServerOrNas.MyDomainName\mySharedFolderĪfter entering the task details, click through all following screens and click ‘Start Now’ at the end and the task will start automatically. On some larger networks with multiple domains you may need to append the domain name to the server UNC path. If that’s how the network is configured or if you get write access errors when running the task, you’ll need to switch ‘Always Authenticate’ on. The “Always authenticate” option is useful when the network server permits read-only access to everyone but write access is only permitted to authenticated users. Very Important: To prevent authorization issues you would want to enter the user name as ServerName\UserName as shown above, or DomainName\UserName if the servers are all part of a domain. In the latter case, you’ll need to first set up a network share on the receiving server, then enter the network details as shown below: The example below shows a network target sample setting, that you would select when you want to move the VHD to a NAS device or another Hyper-V host on the LAN network. If the target is another local disk, use “Local Folder” and browse to the folder. If the target is a cloud server, select FTP and enter the FTP user name, password, and the address and port number of the FTP site. This is the step where you select the target folder or device. “No file processing” basically means that VHDs will be copied and not compressed or de-duplicated to save space. However, if you want to move the VHD over to a new server or disk for the purpose of running it there, you need “No File Processing” selected. If the purpose of moving the VHD is for archiving or backup, you would now accept the default settings as shown below. Step #4: Decide Whether You Need a Copy or a Backup In our example, we are moving an Ubuntu Server VM VHD: Now you simply place a check mark of the VMs you need moved. Step #3: Select Virtual Machines to be Moved
Then skip the Hyper-V Backup settings, accepting the defaults as they are: The task settings will remain in BackupChain hence, the task may be repeated if necessary in the future, either manually or based on an automatic schedule: Select Hyper-V Backup and enter the task name. Now you need to set up a simple task that will move the VM data (VHD and/or VHDX) over to the other side, whether it is a cloud server, new Hyper-V server, or another disk. Step #2: Create a New Task to Move VHDs Over
#What folders to copy for migrating backup exec 16 install#
0 kommentar(er)
