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.
Showing posts with label agent. Show all posts
Showing posts with label agent. Show all posts
Tuesday, March 27, 2012
Monday, March 26, 2012
Getting Step history info into job notification emails
In SQL Agent, under the properties of a job, there is a notification tab
where you can direct it to send you an email if a job fails. However, that
email appears to contain the history for the overall job, but not the
history detail for the particular step that failed.
For example, the email text I get from my failed job (which has only 1 step)
is:
JOB RUN: 'svCON Check WS02' was run on 10/27/2003 at 10:21:31 AM
DURATION: 0 hours, 0 minutes, 1 seconds
STATUS: Failed
MESSAGES: The job failed. The Job was invoked by User sa. The last step to
run was step 1 (check WS02).
Not very useful. If I right click on the job, choose "View Job History..."
and then check the box for "Show Step Details", then I can click on the row
for Step 1 and see a more precise message:
Executed as user: sa. WS02 workstation did not check in. Last check in was:
Sep 11 2000 7:05AM [SQLSTATE 42000] (Error 50000). The step failed.
Does anyone know how I can add this step history info to the job's email
notification?You can't do it unless you write your own code.
Besides, the purpose of email notification is to let you
know what has failed and then manual intervention by an
operator or dba will be required to fix it.
>--Original Message--
>In SQL Agent, under the properties of a job, there is a
notification tab
>where you can direct it to send you an email if a job
fails. However, that
>email appears to contain the history for the overall job,
but not the
>history detail for the particular step that failed.
>For example, the email text I get from my failed job
(which has only 1 step)
>is:
>JOB RUN: 'svCON Check WS02' was run on 10/27/2003 at
10:21:31 AM
>DURATION: 0 hours, 0 minutes, 1 seconds
>STATUS: Failed
>MESSAGES: The job failed. The Job was invoked by User
sa. The last step to
>run was step 1 (check WS02).
>Not very useful. If I right click on the job,
choose "View Job History..."
>and then check the box for "Show Step Details", then I
can click on the row
>for Step 1 and see a more precise message:
>Executed as user: sa. WS02 workstation did not check in.
Last check in was:
>Sep 11 2000 7:05AM [SQLSTATE 42000] (Error 50000). The
step failed.
>Does anyone know how I can add this step history info to
the job's email
>notification?
>
>.
>
where you can direct it to send you an email if a job fails. However, that
email appears to contain the history for the overall job, but not the
history detail for the particular step that failed.
For example, the email text I get from my failed job (which has only 1 step)
is:
JOB RUN: 'svCON Check WS02' was run on 10/27/2003 at 10:21:31 AM
DURATION: 0 hours, 0 minutes, 1 seconds
STATUS: Failed
MESSAGES: The job failed. The Job was invoked by User sa. The last step to
run was step 1 (check WS02).
Not very useful. If I right click on the job, choose "View Job History..."
and then check the box for "Show Step Details", then I can click on the row
for Step 1 and see a more precise message:
Executed as user: sa. WS02 workstation did not check in. Last check in was:
Sep 11 2000 7:05AM [SQLSTATE 42000] (Error 50000). The step failed.
Does anyone know how I can add this step history info to the job's email
notification?You can't do it unless you write your own code.
Besides, the purpose of email notification is to let you
know what has failed and then manual intervention by an
operator or dba will be required to fix it.
>--Original Message--
>In SQL Agent, under the properties of a job, there is a
notification tab
>where you can direct it to send you an email if a job
fails. However, that
>email appears to contain the history for the overall job,
but not the
>history detail for the particular step that failed.
>For example, the email text I get from my failed job
(which has only 1 step)
>is:
>JOB RUN: 'svCON Check WS02' was run on 10/27/2003 at
10:21:31 AM
>DURATION: 0 hours, 0 minutes, 1 seconds
>STATUS: Failed
>MESSAGES: The job failed. The Job was invoked by User
sa. The last step to
>run was step 1 (check WS02).
>Not very useful. If I right click on the job,
choose "View Job History..."
>and then check the box for "Show Step Details", then I
can click on the row
>for Step 1 and see a more precise message:
>Executed as user: sa. WS02 workstation did not check in.
Last check in was:
>Sep 11 2000 7:05AM [SQLSTATE 42000] (Error 50000). The
step failed.
>Does anyone know how I can add this step history info to
the job's email
>notification?
>
>.
>
Sunday, February 26, 2012
Getting Info from Merge Agent Programmatically
Hi - I was wondering how one goes about getting infomation on agent
activity (merge and snapshot agent in my case). I would like to know when
the last synchronization took place, if it failed or not, any error
messages, etc.
How can I get this information without EM?
Thank you,
Maer
Thank you, Paul. This is exactly what I was looking for.
Do we have any control over what the name of the agent is?
Thank you - Maer
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:0ed301c4b1c8$0f7b9770$a601280a@.phx.gbl...
> Maer,
> this script will get you details of the last history for
> the merge agent called 'DH1791628-Northwind-
> NorthwindStaff-DH1791628-3'.
> It will have basic error info if an error occurs.
> If you want the detailed error info, you'll need to join
> to the MSrepl_errors table: MSmerge_history.error_id =
> MSrepl_errors.id. This table typically has several rows
> so you might want to use a cursor to add the text
> together.
> HTH,
> Paul Ibison (SQL Server MVP)
>
> declare @.agent_id int
> select @.agent_id = id from msmerge_agents where name
> = 'DH1791628-Northwind-NorthwindStaff-DH1791628-3'
> select top 1 case
> when rh.runstatus = 1 then 'Start'
> when rh.runstatus = 2 then 'Succeed'
> when rh.runstatus = 3 then 'In progress'
> when rh.runstatus = 4 then 'Idle'
> when rh.runstatus = 5 then 'Retry'
> when rh.runstatus = 6 then 'Fail'
> end as RunStatus,
> 'start_time' = convert(nvarchar(12), start_time, 112) +
> substring(convert(nvarchar(24), start_time, 121), 11, 13),
> comments
> from MSmerge_history rh
> order by timestamp desc
activity (merge and snapshot agent in my case). I would like to know when
the last synchronization took place, if it failed or not, any error
messages, etc.
How can I get this information without EM?
Thank you,
Maer
Thank you, Paul. This is exactly what I was looking for.
Do we have any control over what the name of the agent is?
Thank you - Maer
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:0ed301c4b1c8$0f7b9770$a601280a@.phx.gbl...
> Maer,
> this script will get you details of the last history for
> the merge agent called 'DH1791628-Northwind-
> NorthwindStaff-DH1791628-3'.
> It will have basic error info if an error occurs.
> If you want the detailed error info, you'll need to join
> to the MSrepl_errors table: MSmerge_history.error_id =
> MSrepl_errors.id. This table typically has several rows
> so you might want to use a cursor to add the text
> together.
> HTH,
> Paul Ibison (SQL Server MVP)
>
> declare @.agent_id int
> select @.agent_id = id from msmerge_agents where name
> = 'DH1791628-Northwind-NorthwindStaff-DH1791628-3'
> select top 1 case
> when rh.runstatus = 1 then 'Start'
> when rh.runstatus = 2 then 'Succeed'
> when rh.runstatus = 3 then 'In progress'
> when rh.runstatus = 4 then 'Idle'
> when rh.runstatus = 5 then 'Retry'
> when rh.runstatus = 6 then 'Fail'
> end as RunStatus,
> 'start_time' = convert(nvarchar(12), start_time, 112) +
> substring(convert(nvarchar(24), start_time, 121), 11, 13),
> comments
> from MSmerge_history rh
> order by timestamp desc
Labels:
agent,
agentactivity,
case,
database,
infomation,
merge,
microsoft,
mysql,
oracle,
programmatically,
server,
snapshot,
sql,
whenthe
Subscribe to:
Posts (Atom)