Seeing the live OS conversion seems to work pretty well and quickly, and also bearing in mind that M$'s in-built backup system (if I recall correctly) is just creating a virtual disk, other than for the case of external data drives (which can be handled by other means anyway), why couldn't VMware cCenter Converter be used as an alternative back-up tool to something like Acronis? I'm talking specifically about the home office use case just a couple of computers that I need to keep backed up. After seeing that in action I might avoid using Acronis in future. The best part of that is that compared to the other processes it was very quick to run (even twice) so that part of the converter gets a thumbs up. The image created by VMware vCenter Converter seems to be solid which is pleasing. (Acronis did mention those, but only at the restore stage). As mentioned above it failed first time, but my guess that was due to some disk issues that were resolved with a CHKDSK run. In the end the only option that worked was the VMware VCenter Converter conversion of the powered on OS. * Ran a chkdsk on the problem laptop and it repaired some stuff after which the conversion completed so I have a VM that I will try out tomorrow. FAIL (took forever to restore then couldn't get it to boot without blue screening). Failing #2 on the replacement machine, try the new VM/Acronis boot restore approach. Download v4.3 of the converter and try that with the Acronis Image (which is currently on the replacement machine for the laptop). Use VMware vCenter Converter to convert the OS live (it's a laptop that has shown some signs of dying). In the meantime I'll try the Acronis recovery disk and new VM route to see if that will get me going.ĮDIT: In interim to any thoughts from you experts, I am going to try these things (some in parallel).ġ. Is there anything I can try (besides concluding that the converter doesn't work?). I am using a supported version of Acronis, yet the converter fails at the first hurdle! Have found many posts pointing out that 2010 is not version 10, and 2011 is not version 11, which is fine because those 20xx versions are not the versions I am using. FAILĪcronis True Image 11 Home is definitely listed as compatible here: Please note that ampersand &, dollar sign $, and a few other special characters are already forbidden to be used in a TIBX name as per the User Guide: see Backup file name > Limitations for backup file names.I'm trying to use the converter (5.0.0 build 470252) now on an Acronis True Image 11 (Home version) image which is supposedly compatible, but am getting the same "The source parameters are invalid." message that others keep seeing.
#Acronis true image 2015 upgrade archive#
(which is already fixed in the new agent release C22.02 ) This is about the general handling of TIBX archive names whose filenames contain an &/ampersand/"and" character.ĭo not use an &/ampersand/"and" character or any other special characters in the name of a TIBX archive or in the name of any object from which such name can be (automatically) derived, such as: Exchange database name, plan name, mailbox name, etc.Browsing of Exchange DB backup fails if there is "&" in the name of DB.Issues in the product about how the &/ampersand/"and" character is handled.
#Acronis true image 2015 upgrade full#
Only full backups are always created, even when backup scheme involves incremental and/or differential backups.For example, if the TIBX has a filename of "Something & TheRest" , expand the details of the error message stack, and at you will find lines which say that an archive of name "Something" cannot be found/loaded - with the "TheRest" part of the filename ignored/missing. refreshing the storage location with such a backup would typically fail (but may succeed on some attempts, occasionally) the details of the error message in the red popup window in the Backup Console web UI make it clear that the TIBX for which the agent is looking has its name truncated after the first occurrence of the ampersand character, and naturally a file with such truncated name cannot be found.browsing details/restore points of an Exchange backup may fail with error " Cannot find archive".If the name of Exchange mailbox database contains an &/ampersand/"and" character, several issues may occur (some of them intermittently, i.e.
0 kommentar(er)
