A rather archaic method. if you know the path of the report file
make a batch file
something like:
find "Error flag string" ReportPath > c:\Failed.txt
notepad c:\Failed.txt
Use >> for appending > will overwrite.
FIND [/V] [/C] [/N] [/I] "string" [[drive:][path]filename[ ...]]
/V Displays all lines NOT containing the specified string.
/C Displays only the count of lines containing the string.
/N Displays line numbers with the displayed lines.
/I Ignores the case of characters when searching for the string.
"string" Specifies the text string to find.
[drive:][path]filename
Specifies a file or files to search.
Then your error report is but a click away.
hth
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: "NT 2000 Discussions" <[EMAIL PROTECTED]>
Sent: Friday, January 17, 2003 2:25 AM
Subject: Backup Exec
| When a backup fails is there an easy way to look through the error report
| for what has failed, i have looked through the whole long document and i
| can't see where it failed but i have to believe that there is an easier
way
| to do this?
|
| tia
| Vee
|
|
| ------
| You are subscribed as [EMAIL PROTECTED]
| Archives: http://www.swynk.com/sitesearch/search.asp
| To unsubscribe send a blank email to %%email.unsub%%
|
------
You are subscribed as [email protected]
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe send a blank email to [EMAIL PROTECTED]
