Log shipping monitor

Hello,
I am just setting up log shipping on our new web servers. I have S1
primary, S2 secondary and S3 monitoring. The log shipping is working OK.
Logs are being backed up on S1, being copied to S2 and then loaded
successfully.
In my Log Shipping Monitor, on the Log Shipping Pair Properties Status tab,
the last backup file is still showing first_file_00000000000.trn. The last
file copied and Last file loaded on the are correct. When I am viewing the
monitor thru' EM on S3, and on the Source tab try to view the Backup
Schedule, the button is not disabled but does not display anything. If I
view the monitor thru' EM on S1 and view the Backup Schedule it displays the
schedule.
The only thing I have noticed is that the graphic at the top of the monitor
is showing (LOCAL).dbname --> S2.dbname. I would have expected it to show
S1.dbname --> S2.dbname. Is it trying to look at the backup on (LOCAL) so
looking on S3 which is just the monitoring server.
Anyone else seen this? Thanks for any help you can give me.
ClaireB
Sorry - meant to add I am looking at the graphic on S3.
"ClaireB" wrote:

> Hello,
> I am just setting up log shipping on our new web servers. I have S1
> primary, S2 secondary and S3 monitoring. The log shipping is working OK.
> Logs are being backed up on S1, being copied to S2 and then loaded
> successfully.
> In my Log Shipping Monitor, on the Log Shipping Pair Properties Status tab,
> the last backup file is still showing first_file_00000000000.trn. The last
> file copied and Last file loaded on the are correct. When I am viewing the
> monitor thru' EM on S3, and on the Source tab try to view the Backup
> Schedule, the button is not disabled but does not display anything. If I
> view the monitor thru' EM on S1 and view the Backup Schedule it displays the
> schedule.
> The only thing I have noticed is that the graphic at the top of the monitor
> is showing (LOCAL).dbname --> S2.dbname. I would have expected it to show
> S1.dbname --> S2.dbname. Is it trying to look at the backup on (LOCAL) so
> looking on S3 which is just the monitoring server.
> Anyone else seen this? Thanks for any help you can give me.
> ClaireB