2/13/2023 0 Comments Backup exec 16 restore queued![]() ![]() If you have to have agents on both the server and the in the VM, then make sure you aren't licening per agent install.etc. I am guessing that you are doing a feature comparison (or looking to)?īut, be careful what is involved, and how things have to be setup to enable it. And at that time I was doing virtual disk level backups with no agent within the VM, so no file detail from within the disk. ![]() I have not used the latest BackupExec myself, but my past experience has taught me that if it didn't end up in the backup exec catalogue int he first place, then you couldn't restore it. Thus taking changed bits as they chagne and carting them off to the backup store. Mount the virtual disk and drill within it to restore an individual file.ĭata Protection Manager offers continuous backup. After the restore has finished you should review the hardware settings of the restored VM, especially if you restored from one Hyper-V failover cluster to a different one. Or, are you thinking that the tool would do all this for you. Pay attention to the free space of the system drive (usually C:) of the Hyper-V node, which Backup Exec chosen as target to recover to, because the standard restore path points to the system drive. If you backup the VHD, then you restore the VHD to the moment in time, mount it, and extract the file. If the product runs as an agent within the VM, then you have file level restore (just lke on hardware). In my mind this all has to do with how you do your backups. Not just restoring the VHD to a point in time. You mean file level restore within the VM itself? ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |