Forum Discussion

NCCIT's avatar
NCCIT
Level 3
16 years ago
Solved

Backup a NAS device: Unable to install remote agent


Hi,

My company currently has a Thecus N4100PRO NAS device  with firmware version 3.01.01.  I have Backup Exec 12.5(SP3) on a Windows 2008 32bit server.

After resolving a Authentication issue with the NAS device and Backup Exec, I am not faced with the problem of the Backup Exec error out stating that the remote agent is not installed.  This happens during the credentials check and when teh job is submitted. 

e000846b - The resource could not be backed up because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent. Make sure that the correct version of the Remote Agent is installed and running on the target computer. If the server or
For additional information regarding this error refer to link V-79-57344-33899

I have added my "User defined selection" and I am able to see the files on the NAS device from backup exec.

I've bin browsing through serveral forums and tech documents and there are some that say that backup exec is flat out not compatible with the NAS device, which is linux based; some other articles say that you can install the RAWS serial on the media server as a work around, which i have done via command prompt, but Backup Exec still tries to look for the agent on the NAS device.

My only working, work around was to copy 750GB of data to an exsisting server with windows 2003 and do a  backup from that.

12.x and Earlier
Agents
Backing Up
Backup and Recovery
Backup Exec
Error messages
Installing
  • NCCIT's avatar
    NCCIT
    16 years ago

    Thanks for the reply, but that also did not work for us, that was the very first thing we checked.  We did however find a nice workaround simply create a “symbolic link” using Microsoft’s own built-in tools. 

    Here is the command:

        Mklink /d {Symbolic_Link_Location} {Actual_Location}

    For instance, if you would like to backup the \\10.10.11.162\images share, do the following:

    1.     Start an elevated command-prompt
    2.    Type the following:  mklink /d c:\Images \\10.10.11.162\images
    3.    Start Backup Exec, and create a job to backup c:\Images

    Works nicly, I had to create a account on the server and the NAS device for this, both with the same password and user name.

10 Replies

Sort By
  • Ken_Putnam's avatar
    Ken_Putnam
    Level 6
    16 years ago
    some other articles say that you can install the RAWS serial on the media server as a work around, which i have done via command prompt, but Backup Exec still tries to look for the agent on the NAS device.

    If you do this and create a User Defined Share, you should be able to backup data from this NAS, but you will still get the warning.  Symantec tech Colin on another thread re-iterates that there is no way to suppress the message reagarding the lack of a RAWS running when connecting to a remote machine
  • NCCIT's avatar
    NCCIT
    Level 3
    16 years ago
    Thank you for the quick reply

    This is the procedure I followed
    http://seer.entsupport.symantec.com/docs/308439.htm

    using the -- setupaa.cmd; Windows 32-bit agent

    I rebooted and recreated the User Defined Share, the files get listed, I run the credentials check and get the same error message (see attached)

    Is there a way to verify that the RAWS was installed correctly?
  • Ken_Putnam's avatar
    Ken_Putnam
    Level 6
    16 years ago
    You aren't supposed to run setupaa.cmd on the media server.  the "remote agent" is already installed during setup.  This cmd file can be used on remote Windows machines that for some reason have a problem during push installs from the media server

    What I meant was, install a RAWS (remote agent) serial number on the media server, then set up a "User Defined Share" pointing to the share(s) on the NAS
     
    See http://seer.entsupport.symantec.com/docs/242619.htm
  • NCCIT's avatar
    NCCIT
    Level 3
    16 years ago

    I see, that could be my whole issue then, Ive just realied that Im on a 32/60day trail of the RAWS.  Going back through my licenses I dont see one for RAWS, so this would prevent me form doing this then?
  • Ken_Putnam's avatar
    Ken_Putnam
    Level 6
    16 years ago
    As long as you are still within the trial period, you should stil be able to use the functionality of any of the agents or options   But you WILL need to purchase and install a serial after that to be able to connect to a remote machine

    Go ahead and create a User Defined Share and try connecting via that
  • NCCIT's avatar
    NCCIT
    Level 3
    16 years ago

    Hmm I figured as much, but it still fails.

    Let me outline what I've done to create this job

    From the Job Setup section in BE
    Right click, "New Backup Job..."
    Right click on "User-defined Selections", select "Manage User-defined Selections..."

    Ive added an entry into my HOST file for my NAS device "Images 10.10.11.162"

    I enter for "Name: \\images\images"

    The account im logged into has the same password as on the NAS device.  I expand the \\images\images listing and selct a folder.

    I set the "Device and Media" to my tape, everything else is left at default.  I submit the job, 20-30sec into it, I get the error message.

    e000846b - The resource could not be backed up because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent. Make sure that the correct version of the Remote Agent is installed and running on the target computer. If the server or
    For additional information regarding this error refer to link V-79-57344-33899

  • christidevos's avatar
    christidevos
    Level 3
    16 years ago
    I run 2 x Thecus NAS 8800 had the same issue and batteled for weeks now i found the issue disable your open file option on your backup and yes it works i am able to backup to or from NAS to NAS.

    Hope this helps

    Regards

    Christi
  • NCCIT's avatar
    NCCIT
    Level 3
    16 years ago

    Thanks for the reply, but that also did not work for us, that was the very first thing we checked.  We did however find a nice workaround simply create a “symbolic link” using Microsoft’s own built-in tools. 

    Here is the command:

        Mklink /d {Symbolic_Link_Location} {Actual_Location}

    For instance, if you would like to backup the \\10.10.11.162\images share, do the following:

    1.     Start an elevated command-prompt
    2.    Type the following:  mklink /d c:\Images \\10.10.11.162\images
    3.    Start Backup Exec, and create a job to backup c:\Images

    Works nicly, I had to create a account on the server and the NAS device for this, both with the same password and user name.

  • christidevos's avatar
    christidevos
    Level 3
    16 years ago

    I will keep that in mind stil don’t really understand why it is so difficult to backup to and from a NAS device will be nice to send timed snap Shots there to stop a lengthy full backup every weekend 4TB and just have changes every night. I have used BE for many years but the NAS adventure has had a lot of issues. And a lot of the NAS posts are 4 years and older asking the same questions. At least it’s working again.

  • christidevos's avatar
    christidevos
    Level 3
    16 years ago

    As is said before when i un-tick the open file option i was able to run my backup to the Nas device but it ran very slowly i tried a few different things and selected Open File option again with a few changes. Firstly under Open File options un-tick Automatically select open technology. Then move down to Microsoft Volume shadow copy and tick and pick Automatic. Work for me and the speed seem to me much faster.