Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

Backup & Restore jobs that use 'Local Backup' or 'Cloud Backup' device, if a network path is in the job selection, or is the target path, may need a local user created on the client machine, and requi

Backup & Restore jobs that use 'Local Backup' or 'Cloud Backup' device, if a network path is in the job selection, or is the target path, may need a local user created on the client machine, and require "Run as specified user" job setting set to that user. Please keep in mind that the modern FPI backup & restore engine in NovaBACKUP 21.x does not know what user does have the permission to the target network share (NAS) in question, and just know that the backup client GUI (and CMon UI) run as a different user to what the backup and restore will utilize for the user credentials. Do not assume that just because your currently logged in to Windows user does have Full access rights on the target network share (NAS) that the backup and/or restore function will try to authenticate (the "Run As" tab > "Run as logged in user" job Setting) the actual backup/restore call with that same logged in to Windows user, because it sometimes will not, and hence the need to perform this workaround to make it work, with the "Run as specified user" job Setting set to that local client machine user that you will need to create first instead.

This is a permissions issue, even though it doesn't seem like anything is entered incorrectly and the user should have full access either to backup or to restore.  This is common with Backup Jobs that utilize a a network share as the target path to copy to (such as a protected NAS share as the target path that is utilized in the Backup job), And it can also cause an issue depending on what the restore target is, if the target device is a NAS share in that case you may also need to do this.

To resolve this you will need to set the Backup and/or Restore job (when we state "Backup job", that is interchangeable with "Restore job" for the most part, since the same need could be true for the "Restore" job, but that is dependent on if the Restore job will utilize a network share as the target path to restore to, and I want to be clear that the need for the job "Run As" to be specified to a specific user in either of those job types may be necessary to do in that case) in NovaBACKUP to run the job as a new local administrator account (or a new domain administrator account if working on a Domain Controller, if the network share is active directory aware for the latter case, but we have found that a local administrator account does tend to work better):

  1. First verify on the network share (such as what a NAS uses), inside the admin website for that NAS, what user has full control Read/Write/Modify access to the Share path that your Backup and/or Restore job uses as the target path, and typically on a NAS that would at least be the user named "admin". However, it is up to you right now if you want to create a new user that is only meant for the NovaBACKUP application to have access to that share, or just utilize an existing user for that purpose.
  2. You will now need to decide if you want to utilize an already existing user on the network share machine or device (such as in this example which is a NAS device), if you want to use the built in "admin" user that is on a typical NAS, which is an admin user, that does have full control rights to the share in question that your Backup job uses as the target share, as that must exist correctly on the NAS share first, you have to decide that now, as the next step will have you create that same user in Windows on the backup client machine that runs those two Backup jobs in that case. If you want to create a new user JUST for this one purpose of backup, you can create a new user on the NAS side and assign that user to that same network share (NAS), with full control R/W/D access, such as "NovaBACKUP" or "backup_service" for the username, and set a password, and add that new user to the Admin group on the NAS itself, and that new user to the network share in question (that is utilized by the 'Local Backup' device). And for the case of restoring data from S3 to a network share (NAS) the same user account creation may be needed, and the Restore job Setting "Run as specified user" set to that user as well, but only if the target device to restore to is in fact a network share (NAS).
  3. Run the 'lusrmgr.msc' command ("Control Panel > Users") in Windows to create a NEW local administrator user account (or use the 'ADUC' app to create a new domain administrator user account if working on a Domain Controller) on the system that NovaBACKUP is running on, with the same username and password as on the NAS share in question, and assign the same password as the NAS has for that new user; the password for this account cannot be blank. Make sure that new user is added to the "Administrators" group after it is created.
  4. In the backup client GUI switch to the "Backup" tab and do an "Open" command to locate and then open to be able to edit each unmanaged ("unmanaged" means that the backup job was created in the client GUI, not via the CMon UI, which for the latter would be a "managed" job) Backup job that does utilize that same network share as the target path of the Backup job, that you get the access denied to CreateDirectory error on, and with that Copy job open go to "Settings" at the bottom of the Backup tab, and then click on the "Run As" tab, and change the "Run As" setting in the Backup and/or Restore job to set it to use "Run As Specified User" and then specify the correct username and password for the user that you created in Step 3, and then save the Backup job.
  5. Repeat that Step # 4 for any other Backup jobs that do utilize that same network share and required user to be able to write to the target and work.
  6. Run the Backup job(s), one at a time, and they should work now, now that they have the required permission to write to the target network share (NAS) path. Do not assume that just because your currently logged in to Windows user does have Full access rights on the target network share (NAS) that the backup and/or restore function will try to authenticate (the "Run As" tab > "Run as logged in user" job Setting) the actual backup/restore call with that same logged in to Windows user, because it sometimes will not, and hence the need to perform this workaround to make it work, with the "Run as specified user" job Setting set to that local client machine user that you will need to create first instead.
  7. If on Step 6 for running the Backup job you still run into an issue, you will first need to confirm if the errors are the same as what you were seeing before. And if it is the same errors as before then you will next need to confirm that the target Backup to path in the Backup job is defined properly, and that the target share and folder actually exists at the target, and that either the existing or new user on the NAS that you dealt with in Step 2 is A. added to the share in question, and B. has the needed Read/Write/Modify access on that share as well, even if he does exist as a user on that share; and then run the Backup job again after that. If the error is different then there must be something else wrong other than the permissions to write to the target share path.