Video Screencast Help

Trying to backup ReadyNAS 2100 using Backup Exec 2012

Created: 28 Mar 2013 | 8 comments

Greetings

We have purchased a NetGear ReadyNas 2100 and now need to add the contents to our night LTO5 backup using BE2012.

On the ReadyNAS forums, they mention that you need to install a RALUS add-on onto the ReadyNAS box itself which I have now done. I did originally try BETA version 13.0.5204 but that did not install properly so I eventually successfully installed version 12.5.3. According to the notes, once you add the IP address of the BE server into that add-on, it should broadcast itself to the BE server.

In BE2012, I am trying to add the ReadyNas 2100 as a Linux server but am having no joy. I have purchased the remote agent for Linux servers from Symantec. I was originally getting timeout errors when trying to add the ReadyNAS 2100 as a server in BE2012. Now when I try to add the server, I get the message "Inserting Resource Container" for a long time but eventually the ReadyNAS adds as a server (or at least no error appears), but you cannot browse the contents to add any folders. When you try to create a backup job, you get a "Browse Failure" error. When I do a "Test Credentials" using both the "admin" account that was created on the ReadyNas 2100, or using the "System Logon Account", both fail. The Credential status just says "Test Failed. Test Recommended".

Any idea of what I am doing wrong?

Scully

Operating Systems:

Comments 8 CommentsJump to latest comment

VJware's picture

I dont think you would need to install any add-on.

Regarding the container issue - Have a look @ this KB - http://www.symantec.com/business/support/index?pag...

Is the "admin" account which is created in  the NAS also present in Backup Exec with same user name/password ? If yes, run an actual backup job and not perform a credentials test.

CraigV's picture

VJware: To backup a NAS you need an agent...so you need to buy the license. The licensing guide is clear on this in order to be compliant, even if you can't install the agent on the NAS.

If the NAS can be AD-integrated, why not consider doing this. You'd be able to use the BESA to connect to the NAS and it should take care of your authentication issues.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

VJware's picture

@CraigV: I am perfectly clear on that part, however i have mentioned about an "addon" and not the agent. Thanks !

CraigV's picture

RALUS add-on = RALUS agent, just to be clear.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Scully's picture

VJWare - The admin account was added in BE. The username and password match the admin username/password used on the ReadyNAS 2100. I have tried prefixing and not prefixing the name of the ReadyNAS account with the name of the NAS box, but neither works.

I have removed the add-on from the ReadyNAS box in the hope that BE would push one down but still am not getting any further.

I checked the TCP 135 issue with our network team but they have confirmed that as both devices are on our local LAN (same IP range), that port is not being blocked.

I definitely have the RALUS license added into BE.

The ReadyNAS is added onto our domain (I can see the computer account for it and access the shares on it using \\NAS_BOX_NAME), but I have tried adding it as a Windows server, file server and Linux server in BE but none work.

Any other ideas?

Scully

VJware's picture

With what error, does the backup job fail ?

And try configuring the backups using this KB -

http://www.symantec.com/business/support/index?page=content&id=TECH189560

Scully's picture

When I choose "Backup to Tape", the window pops up to allow you to choose files but I get this error straight away:

I will shortly try the other steps you gave me the link for(http://www.symantec.com/business/support/index?page=content&id=TECH189560)

screenshot1.png

VJware's picture

Just one other thing. If the above KB doesn't help, try changing the NDMP port. Use this KB - http://www.symantec.com/business/support/index?pag...

(Ignore the title though)