Problems Backing Up Snap Server

[Paul_Read]

Hi All,

Currently experiencing difficulties backing up a SNAP server. I have added it as a user defined selection. The first strange thing is that when you expand the directory structure in backup selections, all check boxes are 'greyed out'. The only way I can select any of the folders is to go to advanced file selections and check the 'include subdirectories' and 'include' options.

When the backup job runs, it fails with 'The backup of the item is bad'. Looking at the job log, the following error occurs for each folder on the SNAP drive.

'The Media Server was unable to connect to remote machine SNAP409722. The media server will fall back on the local agent to try and complete the operation. Unable to initialize Remote Agent.'

Obviously there is no way of installing a remote agent on the SNAP server so im at a bit of a loss!

Any help greatly appreciated.

Many Thanks,

Paul

[aurora]

Hi Paul,

First of all, it might be worth checking the following: http://support.veritas.com/docs/271239 as you should be able to use remote selections for a SNAP server. Also read: http://seer.support.veritas.com/docs/250083.htm

Secondly, if it's a UNIX based SNAP server, then read the following: http://seer.support.veritas.com/docs/264525.htm for some basic information regarding remote agents on UNIX SNAP servers.

[Amruta_Bhide]

Hello Paul,
Could you Please update us on the issue? Did the Articles provided by Aurora help you?

******************************************************************
*****************************************************************

Note : If we do not receive your reply within two business days, this post would be marked �assumed answered� and would be moved to �answered questions� pool.


Thanks.

[Ken_Putnam]

Do you have a remote agent serial installed on the media server?

Are you "connecting as" as and account with full acces to the Snap Server?

[Paul_Read]

Hi All, Sorry for the delay, had to wait to get access to the Server. I have ran through the 3 articles, and it all appears to be configured correctly, services log on using the local system account (Administrator), and an account with the same credentials has been set up on the Snap Server, full access to all shares granted along with being a member of the 'Admin' group. I can also confirm that we have a remote agent option installed locally on the BE Server.

Thanks for your assistance, I await your ideas.

Paul

[tejashree_Bhate]

Hello,

Refer to the following
How does backupexec understands SNAP SERVER?
(SNAP is basically an external HDD attached with power cord and network cable)
For Backupexec, NAS/SNAP SERVER is just another windows server on the network, this is because NAS units has the ability to mimic "real" Windows NT/2000, UNIX ,or Macintosh servers .This means that users don't have to do anything differently when they want to access them. As far as they are concerned,the NAS/SNAPSERVER unit is just another server out on the network on which to save or from which to retrieve their important files.
Therefore when you configure the SNAP SERVER The quick configuration series of menus takes you step-by-step through the process. First,you set up the current date and time for the server's clock,Then you select which networking environment you want the server to operate in. Snap Server is one of the more versatile NAS devices in that it supports AppleShare, UNIX NFS, and Novell Netware networks,in addition to standard Windows protocols. Once you choose windows networking environment and you select whether you want to use your existing user accounts on a Windows server or set up new accounts you are almost done with the SNAP SERVER configuration. While backing SNAP SERVER Backupexec will think it as another windows server on the network and thus demands "RAWS" but no component required.(Infact can not be installed).


To resolve this issue,purchase and register the "RAWS"/"RANT" license on the media server no component required.

Thanks.