This is the third time now, I'm using standard edition 4.0.4. I had four backup routines scheduled and today (and previous times) Backupper opens but there are no scheduled backups showing on the home page. So once again I have to set all my backups .
Why is this happening? Is it to do with this latest build? Anyone else getting this?
Windows 10 very latest version.
When using CBackupper 1.1.0.0 Desktop App to backup files on my pc to the AOMEI Cloud, the task:
1.) Prevents Windows Screensaver from starting.
2.) Overrides Windows power plan setting “Turn off display” after x mins.
These are two very important features that should not be interfered with by CBackupper. I can certainly understand perhaps why it might want to prevent “Sleep” or “Hibernation”, as that could disrupt the backup process; BUT, why prevent the screensaver from starting, and why disallow the display to turn off, when neither comprises the backup process?
As, an example, CBackupper allows local backup pc files to cloud, up to 1,000GB’s. That amount of data being backed up can take a considerable amount of time, many hours in fact.
Am I supposed to just leave my display/monitor on the entire time, perhaps multiple hours, with a static screen? That could cause serious damage to any display/monitor (burn-in); and not to mention a waste of power and resources.
My System:
OS Name Microsoft Windows 10 Pro
Version 10.0.19042 Build 19042
Processor Intel Core i7-8700
Security Windows Defender
Windows Power Plan High performance
Turn off the display: 10 minutes
Could you add such an option in the next Aomei Data Backupper release?
Thank you
Leo
Q1: Unable to activate Windows 10 successfully and access the F11 AOEMEI Onekey Recovery function after cloning it to a new SSD from the original one through AOMEI Backupper Standard Edition .
Q2: Windows 10 runs normally after cloning it from the original SSD to a new one via 3rd party software (e.g. Acronis, True Image, Ghost, Easeus todo backup). However we are unable to find the BOOT record after powering up the system after recovering the operating system by AOMEI Onekey Recovery.
In such case, running Windows 10 startup repair is required to fix the issue.
Test environment:
Windows 10 which UEFI is installed under GPT format, and is completed with built-in F11 recovery function via AOMEI OneKey Recovery v1.62. The system SSD is able to run AOMEI Recovery successfully and can access Windows 10 without issue after being recovered.
Some different about before and after:Hi, i was looking for a descent backup utility, and Aomei looked a quite powerfull, usefull and friendly user interface program, however i run into 1 problem, if i try the free version ( standard edition 2.0.2 ) it suddenly asks for registration ( buy the Pro version ) , i get the "Trial expiration notice" , and i cant recover or backup aymore ( within Windows that is ) , i tried it on several systems, new installations, all the same...
Any1 else have this problem? ( bug??) , on the homepage it says clearly "freeware" , not TRIAL, and even after using/testing 3 recovery's i already get the msg.
I emailed the helpdesk and they are friendly and all, but quite slowly, i need to make a decision soon to choose a new backup program ( im an Acronis user for years now ) , and im postponing backups atm already, so i post here on the forum to find a quick solution.
thanks in advance,
Andy
I have used several versions of AOMEI backupper from around 4.5 to the latest 5.0
I have always found it to be one of the fastest backup programs for creating a disk image and the restore process is usually fairly speedy also.
However, I have found that verifying a disk image takes 2 or 3 times as long as it does to create it. This seems bizarre given that most other disk imaging software I have used, the verification time is usually shorter than the time taken to create the disk image.
Is there any reason why AOMEI backupper is so much slower at verifying the image? Can anything be done to speed it up?
I should add that I have tried it on a few PCs (decent spec with i5 or i7 CPU) and have always found it to be slow verifying the image.
It doesn' seem to make much difference if the backup image is on an internal hard drive or an external USB drive. The only time, the verify was even remotely acceptable is when I tried creating an image onto a SSD. Obviously this isn't viable for regular backups because of the cost of SSD storage vs standard hard drives.
I have also tried booting from a WInPE disk and running the verify from there with the same slow verify performance.
Any thoughts?
