AOMEI Centralized Backupper FAQs
You have already set numbers of the computers that can be backed up in parallel, why does not it work while performing backup? (How do you improve backup speed when there are a batch of computers backing up simultaneously?)
A: Generally, if there are too many clients (such as, 10 or 20 computers) backing up to the same NAS or Network share storage simultaneously, it may lead to backup speed slow due to bandwidth pressure within the same LAN. Therefore, AOMEI Backupper Network allows you to set the suitable numbers of clients that can be backed up at the same time based on the LAN bandwidth and the storage server's capacity. However, the feature only works for these clients on which you perform backup manually via the AOMEI Backupper Network console. If these clients are performing schedule backup, it will be invalid. So, the actual numbers of clients performing backup may be greater than the one you set. And, for schedule backups, you can set a different time for each computer in the same task or you can set a different time for each group to run this task so it can resolve the backup speed problem indirectly.
Could AOMEI Centralized Backupper back up dynamic disks?
A: AOMEI Backupper doesn’t support backing up dynamic disks with disk backup and you can back up dynamic volumes with partition backup.
When the disk/partition information (such as drive letter, volume label and so on) of the clients have changed, why AOMEI Centralized Backupper doesn’t update it timely.
A: Please reboot the AOMEI Centralized Backupper program on the server-side, select and double click the client computer with changing disk/partition information under Computers-->Controlled Computer, and then click the Refresh button to update.
The client computers always show "offline" on AOMEI Centralized Backupper.
A: It might be that the "Backupper Service" of the client has stopped. Please start the Windows Task Manager, select Services, and then restart "Backupper Service". If clients are still "offline", please reinstall AOMEI Backupper standard beta on clients.
And, you can try to change the value CLEAN_VIRTUAL_ADAPTER from 1 to 0 under the path AOMEIBr\net\Global.ini on the server machine.
If the problem remains, you can try to set the property of AOMEI Backupper Server to "Delay Start" under Windows Task Scheduler.
Why the error "Initialization failed" occurs when loading AOMEI Centralized Backupper?
A: The network card might get a problem. You can change the ABNET CLEAN_VIRTUAL_ADAPTER value to 0 under the path C:\ProgaramData\AomeiBR\net\Global.ini and retry.
Why the error “Occupied by another server” occurs when requesting control?
A: Please check if there is another AOMEI Centralized Backupper under the same LAN and the client machine has been occupied by another AOEMI Centralized Backupper. You can first cancel control on another server-side or on the agent and request control again.
Or, we advise you to directly delete the Login file under the path C:\ProgramData\AomeiBR\net (on the client machine).
Could AOMEI Centralized Backupper supports to back up these partitions with no drive letters on client computers?
A: You can match the label of these partitions with no drive letters to back up. But, AOMEI Centralized Backupper currently can’t back up partitions with no drive letters and volume labels. In this situation, you can run AOMEI Partition Assistant on clients to assign drive letters or volume labels for these partitions manually.
Why do you receive "The network share/NAS username or password is incorrect…" during backup?
A: It might be that the username and password of the Share/NAS you added have changed, please click "new task" and then modify the username and password in "Share/NAS device" panel under "Step 3: Select the destination location to save the backup". After that, back up again. Please noted that there is no need to create a new task, you just need to modify the username and password in Step 3.
Why does it fail when you remotely install/update/uninstall AOMEI Backupper Standard on the client computers?
1) Please check if you are using the account under Administrators and the password should be not null. And, please right-click "This PC"-->Manage-->Local Users and Groups to confirm the administrator account un-checks "account is disabled" option.
2) There is no enough access permission for the clients' computers, Windows service of clients is closed or prevention software are running on clients (for example, firewall and antivirus program are running, UAC remote is disabled and etc). Please modify these settings on clients: you can copy from “C:\Program Files (x86)\AOMEI Centralized Backupper\tools\PreInstall.exe” on the server side to clients and then run it, close anti-virus programs and personal firewall and so on. After that, please try to remotely install/ update again.
3) Please confirm if your client account has write/read permission for installation location when doing the remote installation.
4) If AOMEI Centralized Backupper is installed onWindows XP/Server 2003 system and the clients are running Windows 10, then you need to enable "SMB1.0/CIFS File Sharing Support" on your clients because of Windows XP/Server 2003 useSMB1.0/CIFS protocol. Please check the "SMB1.0/CIFS File Sharing Support" option and you can find it under Control Panel-->Programs and Features-->Turn Windows features on or off. And, please press "Win+R" to open the Run box, run "gpedit.msc" to open local Group, and then Enable insecure guest logons under Administrative Templates-->Network-->Lanman Workstation. And then, reboot client computers.
Note: You need to temporarily enable "SMB 1.0 / CIFS File Sharing Support". After installation is completed, we suggest you turn off the "SMB 1.0 / CIFS File Sharing Support" for the sake of system security.