On 08/06/2012 04:12 PM, Arbogast, Warren K wrote:
There is a Linux fileserver here that serves web content. It has 21 million
files in one filesystem named /ip. There are over 4,500 directories at the
second level of the filesystem. The server is running the 6.3.0.0 client, and
has 2 virtual
Keith - Just a few thoughts you may have entertained…
In that it's a network file system, network throughput may be a factor, where
gigabit ethernet and jumbo frames may help. Network statistics may reveal
periodic packet losses and retransmissions which slow things down: the
'nfsstat' command
Allen,
Thank you for the suggestions.
By 'proxy agent' I mean they are authorized to do backups on behalf of the
target server.
We are doing possibility one, in your set of cases, with four agents. I kept
the example simple for readability, but perhaps some clarity was lost.
It seems we may
On 08/07/2012 11:10 AM, Arbogast, Warren K wrote:
By 'proxy agent' I mean they are authorized to do backups on behalf
of the target server.
We are doing possibility one, in your set of cases, with four
agents. I kept the example simple for readability, but perhaps some
clarity was lost.
We've got a similar beast. The problem is the sheer number of files,
which the client must keep a list of, in order to decide which files
need to be backed up. This is the whole idea behind TSM's Progressive
Incremental backup model. We have found that as file counts reach the
many millions,
On 08/07/2012 12:46 PM, Roger Deschner wrote:
There is no restore equivalent to MEMORYEFFICIENTBACKUP YES or
MEMORYEFFICIENT DISKCACHEMETHOD for restore. The ability to restore is
the whole point of backup, so take restore issues seriously.
Doesn't no query restore help some with that? It's
NetApp / nSeries backup question (non-NDMP backup):
Has anyone else wanted to use the snapshotroot option for scheduled backups run
from a NAS client? We run scheduled backups from NAS clients for shares on a
vFiler. snapdiff backups are not supported on vFilers, so we would like to do
the
Allen,
I see your point, finally, that BIGFS_AF will copy files, but BIGFS_GL will
remove them. Clearly, splitting the backup of one filesystem among multiple
proxy nodes via include/exclude statements is futile. There are 4500+
directories under /ip, so virtualmountpoints aren't workable
Well, I'm stumped.
My customer has a 2-node Exchange 2003 active/passive cluster on Win2K3 R2 SP2.
TDP for Exchange is 6.1.3.3, Legacy backups.
Node 1 is usually the active node, and TSM works fine.
The TDPEX GUI on Node 1 works as expected. The client scheduler service for
Exchange is
Wanda,
Have you tried tracing the activity of the process with Sysinternals'
Process Monitor? It might help in pinpointing at what stage exactly the
client exits. Maybe it is trying to read a registry key and crashes on that
or something. I've found Process Monitor very helpful in a number of
10 matches
Mail list logo
