Symantec-Be
- Category: 電腦相關
- Last Updated: Monday, 08 October 2012 13:42
- Published: Monday, 08 October 2012 12:21
- Written by sam
公司的幾臺主機買了BESR作備份
也訂了REPORT…
但明明就有八臺…每次出來的報告都是七臺
剩下的那一臺
怎麼每次都沒有…
趁著星期假日…反正沒事…就當作自修…
先找到該目標機…
先檢查它的SERVICE…
Symantec Management Agent
嗯…
主要的AGENT都還在…重啟過後也正常
再到REPORT SERVER這邊作點檢查
撈一下它失常了多久了…
原來四月多就失常了…
還停真夠久了!
再從REPORT SERVER中 撈一下
是不是它沒有序號或是不在管理的名單中
再檢查一下…是不是平常撈取的sql語法有誤
SELECT
[vri1_Computer].[Name],
[dca2_BESR_Image].[Size],
[dca2_BESR_Image].[Timestamp]
FROM
[vRM_Computer_Item] AS [vri1_Computer]
LEFT OUTER JOIN [Inv_BESR_Image] AS [dca2_BESR_Image]
ON ([vri1_Computer].[Guid] = [dca2_BESR_Image].[_ResourceGuid])
GROUP BY
[vri1_Computer].[Name],
[dca2_BESR_Image].[Size],
[dca2_BESR_Image].[Timestamp]
ORDER BY
[dca2_BESR_Image].[Timestamp] DESC
看來也是沒有…
正常點選policy會出現狀態

再檢查一下 agent的派送情況
但還是一樣

也都正常…
臨時想到…可能缺少另一個元件…

果然就是它了… Symantec system recovery plug-in .......
手動來給它派送一下

再查一下狀態

快正常了…
再來就是隔天再檢查了(等半夜作完排程)

回到正常了…
Daily report 也有它了…
