Access to a NAS or network shares in general is via the account of the accessing service. Accessing services can be
- Disaster Recovery Imaging
- NovaStor NovaBACKUP Backup/Copy Engine
Provide the Disaster Recovery Imaging service with an account that has local admin privileges and remote (on the NAS) read and write privileges.
The account can be a local account if the same account with identical password is created on the NAS. First, configure ONLY the "Disaster Recovery Imaging" service to run with this user. As a rule, the second service only needs to be changed in certain situations (see below).
On an AD server the AD users are also local users! If the NAS authenticates against the AD, the AD user must also be given full access to the share!
Set up LOCAL users with the same name and password on the systems.
Create new user "BackupAdmin".
Grant full access to the shares.
If this user exists in the domain AND as a local user on the NAS, and the NAS has access to the domain, please also look into the domain in the NAS rights management and grant full access rights to the domain user of the same name!
On Windows system
Create new LOCAL user "BackupAdmin".
On a domain controller, create a new domain user with this name.
Make this new user a member of the groups "Administrators" and "Backup Operators".
Create on an AD Server:
On an AD server, create a new user in the AD; these are the local users on an AD server. On an SBS you set up the user via "Active Directory Computer and User" under "Users", NOT under "MyBusiness\Users".
Enter this new user "BackupAdmin" into the NovaBACKUP network device. Please do NOT enter any domain or hostname, ONLY username and password!
Enter the new user "BackupAdmin" in all backup/image jobs and schedules (also for retention rules), WITHOUT domain names or host names! As a rule, this is sufficient to give the backup jobs the corresponding access rights. If this is not the case, go through the following points.
If the image job does not write to the share:
Change the service "Disaster Recovery Imaging" to run with user "BackupAdmin", without specifying a domain or hostname. This service can also be changed permanently.
If it is not possible to mount an image file:
Switch service "Disaster Recovery Imaging" to user "BackupAdmin" without specifying a domain or hostname.
If the backup/retention rule does not work:
As a rule, it is sufficient to enter the new user and password in the time schedule of the retention rule. If the rule does not delete any data, please check the login data again. Please enter only the username and password. Only if this also does not lead to success:
Change the service "NovaStor NovaBACKUP Backup/Copy Engine" to this new user "BackupAdmin". Again, do NOT enter a domain or hostname! Please note that the conversion of BOTH services can lead to the Image Job not working. In such cases you should change the service "NovaStor NovaBACKUP Backup/Copy Engine" back to the local system account and contact the NovaStor support.
If a restore/import of backups fails:
Enter the new user in the recovery settings (button "Settings" below), only the name/password. Start the import or recovery process.
Alternatively, change the service "NovaStor NovaBACKUP Backup/Copy Engine" for recovery to this new user "BackupAdmin" without specifying a domain or hostname. After restoring, reset this service to the local system account.
If the Virtual Dashboard (VD) does not delete old generations on the share or cannot mount a backup as a drive:
Change the service "NovaStor NovaBACKUP Backup/Copy Engine" also to this new user "BackupAdmin" without specifying a domain or hostname.
ATTENTION Side effect of service change
(does not apply if you have changed the service from the outset and create the jobs afterwards):
If you change the service "NovaStor NovaBACKUP Backup/Copy Engine" to the new user, the VD no longer finds the jobs => VD only displays white entries instead of red/green.
Eliminate side effect:
Delete the current VD jobs and create them again. Clean up the target directories.
The VD jobs are stored here by default:
Move the job to the directory of the user with which the service was configured, e.g. user "BackupAdmin":
After the PD has been closed/opened, the status of the jobs should be displayed correctly again.