Hi Roger!
Why don't you use a MOVE DATA against r/o volumes? It has a WAIT=YES
parameter and it's better than using the AUDIT VOLUME command.
When you have a read error on a primary pool volume, the audit command
(with FIX=YES) removes the backup data from the tape. Not a problem for
backup data
Wanda,
Our situation is not exactly like you described, but we do support backups of
remote servers on eight campuses around the state. We don't have login rights
to any client servers.
We have a third-party TSM monitoring application that sends an e-mail to the
client admin and opens a
One more thought. In my experience some-to-many client admins assume that
failed file backups (file in use, file not found, file changed, etc) are the
cause of failed backups (condition code 12). If the failed files aren't
important to them they look no further for the cause of the failed
I'll second that. Our policy is that no node should generate a non-zero
exit code at the end of a backup. There's a couple things that we do:
* Exclude directories that generated errors that do not need to be
backed up (Firefox cache, all sorts of Apple stuff, etc.)
* Work with users to
Fellow TSM'ers
I'd appreciate some feedback on a question.
We are currently roling out 6.3 to a few facilities, and also need to role
out the storage agent to a number of AIX boxes.
Previosuly I'd have the 5.5 STA on an NFS export and the individual admins
just mount it and install themselves.
Questions have been raised about the efficacy of the Sophos product?
http://www.cso.com.au/article/441070/google_security_researcher_keep_sophos_away_from_high_value_systems/
[RC]
On Nov 2, 2012, at 1:16 PM, Vandeventer, Harold [BS]
harold.vandeven...@ks.gov wrote:
Is anyone using Sophos
