i know this topic has been covered and i've searched but i can't find the answer.
-SQL server is a diffrent server than my backup server
-i've installed the sql agent option on the backup exec server
-i've installed the client network utility on the remote server
the backup server doesn't see the SQL server databases. any thoughts
could it be a security issue?
thanks!If your production server and the backup servers are different, then you can not schedule the backup of the production server DB on the backup server.
What you need to do is :
1. Verify if the SQLServerAgent service is running with the domain account, not with localsystem account.
2. Map a drive of the backup server to the production server.Give all the rights to the user account, with which the SQLServerAgent service is running.
3. On a production server , schedule a job for backup of the Prod DB to the backup server. and in the backup folder name specify the complete UNC. e.g \\servername\sharename\file.bak.
May be this will help you out.
Thanks|||And also ensure simlar netlib protocol used to connect from remote (backup) server to sQL Server.
The best method is to perform local backup on SQL server and then copy the file across the network, this way you can reduce overhead of stressing SQL during backup process.|||Originally posted by Satya
And also ensure simlar netlib protocol used to connect from remote (backup) server to sQL Server.
The best method is to perform local backup on SQL server and then copy the file across the network, this way you can reduce overhead of stressing SQL during backup process.
ok, one problem though... the sql agent isn't running. the option has been installed, but i can't deploy the agent to the sql server, assuming it's the same method as deploying the windows 2000 remote agent.|||Tried restarting the SQLAgent?|||Originally posted by Satya
Tried restarting the SQLAgent?
unfortunately there is no sql agent "service" on either the sql server or the backup server. when i say that the option has been installed, i mean that the serial number has been added, but i feel that the agent isn't in fact installed.|||SQLAgent will be installed by default alongwith SQL Server installation.
Check whether any issues in starting the service on SQL Server via Enterprise Manager.|||Originally posted by Satya
SQLAgent will be installed by default alongwith SQL Server installation.
Check whether any issues in starting the service on SQL Server via Enterprise Manager.
ok thanks, i've actually schedule a reboot on both server's. i'll post any issues tomorrow. thanks again.|||ok, sql agent service, sql server service are both running fine on the sql server. i think my issue is installing the backup exec sql agent, how do i install this on a remote server?|||Refer to the vendor's documentation about installation.|||Dude, I've got the same problem with my Backup Exec Agent for SQL and Exchange. Neither are listed on the install options remotely window. I've found an easy way around this is to install the full backup exec on you SQL server, that is if it can handle it. In that installation, install the SQL agent. Then you get the little SQL server icon on the thing.
MOD: Edited to remove unnecessary comments.|||Little piece of advice, if you are using Backup Exec, don't use the open files option. It doesn't get along with SQL Server 2000 too well. Also, just backup the backup file directory. Make sure you tell it to skip the program directory with SQL Server in it and the directories with your data and log files. Otherwise you could have several long nights in front of you.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment