Has anyone seen the following errors ?
01/29/05 11:29:32 ANS9178E dsmscoutd: cannot open file /dev/fsm: The
requested resource is busy..
01/29/05 11:29:32 ANS9178E dsmscoutd: cannot open file /dev/fsm: The
requested resource is busy..
01/29/05 11:29:32 ANS9178E dsmscoutd: cannot open file
We have had two occurrences in the last two weeks of 1,500+ dsmscoutd
processes initiating and effectively crashing our system. The parent
dmcscoutd process, seems to start 2 new son (dmcscoutd) processes every
10 seconds, and continues to do this until the system hangs.
Has anyone experienced
Does anyone have any suggestions that would reduce the time it takes the scout daemon
to produce a candidates list on a HSM file system that contains a large number of
files ?
We currently have the candidatesinterval option at 12, however it takes approximately
8 to 10 hours for the scout
We are currently having problems performing incremental backups on a file system that
has a large amount of files. The daily changes to this file system are small so we are
only sending approximately 5 - 10 gig per backup however, since there are around
3,000,000 files to examine, the backup
We are running the TSM client and server on AIX. I thought journaled bakups were only
supported on Win 2000 and NT ?
Thanks,
Mark.
[EMAIL PROTECTED] 10/01/03 09:51AM
You can use journal backup.
- Michael
-Oprindelig meddelelse-
Fra: Mark Trancygier [mailto:[EMAIL PROTECTED]
Sendt
] 10/01/03 10:57AM
= On Wed, 1 Oct 2003 09:27:41 -0400, Mark Trancygier [EMAIL PROTECTED] said:
We are currently having problems performing incremental backups on a file
system that has a large amount of files. The daily changes to this file
system are small so we are only sending approximately 5
