Re: SBS 2003 R2 backup: skipped (in use) files



I saw the list, but my point was that an open-file agent does *not* ensure consistency across files....which a database needs. I was illustrating this with examples such as exchange and SQL server since they have separate agents. If an open-file agent were enough, then another agent wouldn't be necessary. But again, I was using those as an *example* to illustrate my point.

So, regarding the files you specifically listed? Note the folder name: HTTPDB. The name would imply a web (HTTP) database (DB.) And given my example above, a database *usually* requires its own agent. Some file-based databases (SQLLite, MySQL) where transactions are atomic can be backed up with a snapshot based backup (Microsoft's shadow copy) but if Backup Exec doesn't do the entire snapshot at once then it could *still* break a file based database as well.

Apparently I should've been more explicit with this explanation in my previous post, but I thought I had given enough information to explain my position. Hopefully I've corrected my mistake. :) I do *not* believe an open-file agent will be enough to back up your system in this case. Maybe somebody with more experience with Trend can answer whether a backup can be successfully restored, but manufacturers generally are better able to answer that question.

As an aside, I tend to exclude application directories (applications can be reinstalled) and service accounts (network service/local service) as they'd be recreated with a new install as well. I tend to stick to backing up DATA only, for example a reporting database for the AV product is a legit backup, as you may do trend analysis on emails filtered, etc and the historical data is important. But backing up the signature database is unnecessary, as a failer event large enough to require its restore is usually large enough to require the AV's re-install.

Just my .02 cents.

-Cliff

"gb" <guido_brasletti@xxxxxxxxx> wrote in message news:17ba5ca7-597e-40f5-acd9-cef7d7948b66@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi Guys, and thank you for your replies.

Just to clarify the argument:
-we're using symantec backup exec v12 for SBS, with proper agents to
back up exchange and SQL server.
-the skipped (open) files are listed in my original post (see the
first message of this thread) an are basically part of the "documents
and settiigs folder" (NTUSER.dat) and the HTTPDB of Trend Officescan
antivirus.

Ciao
Guido

.



Relevant Pages

  • Re: Cant view merge agent properties (trying again)
    ... In the List of Actions for the Snapshot Agent History I see this repeated: ... every single database listed. ... So, just now, I went to computername\Administrator Login ID (because it's ... On the computer running SQL Server, ...
    (microsoft.public.sqlserver.replication)
  • Re: Change QueryTimeout
    ... It could be transactions queued in the distribution database. ... Looking for a SQL Server replication book? ... "Hilary Cotter" wrote: ... I cannot get to agent properties because the subscribers are ...
    (microsoft.public.sqlserver.replication)
  • Re: Steve Jobs very very interested.
    ... I just think that Agent is badly written, ... My newsreader currently has a database of over 10GB, ... A lot of developers are deathly afraid of multi-threading. ...
    (borland.public.delphi.non-technical)
  • Re: The distribution agent says "No Replicated Transactions are Available" but I dont believe it.
    ... It could be that the log reader is reading command from the log from a large ... agent is behind if at all. ... The published database is very large. ... It turned out that these were due to the distribution ...
    (microsoft.public.sqlserver.replication)
  • Re: simulate virtual directory for each user
    ... > I need different virtual directory for different customer with their names ... > of that user's web pages from database. ... > After writing the agent Id to client's cookie, ... I read cookie and get agent id and bring the agent info ...
    (microsoft.public.dotnet.framework.aspnet)

Loading