We have regular 1gb connections. They only get about 40MB/s with one channel
and are able max it out with 4-6 channels. We have maybe 20-30 dbs in the 1-3TB
range so basically just the right numbers to want to avoid storage agents.
On Nov 11, 2016, 9:49 AM -0500, Rhodes, Richard L.
, wrote:
> W
What's the connection between the Oracle server and the TSM server? Whether
multiple channels not multiplexed, or, one channel with multiplexing (or some
other combination) may not speed up the backup/restore depending on the weakest
link (source disks, lan, disk pool target disks, tape). Our
Hello Shawn,
if you have tsm for san this would be good option for multi TB env. For TB
DBs we use from 4-8 session backing up to tape direcly
HTH
Chavdar
On Friday, November 11, 2016, Shawn Drew wrote:
> I’m looking for best practice advice for TDP for Oracle with regards to #
> of channe
I’m looking for best practice advice for TDP for Oracle with regards to # of
channels.
If you have a classic TSM environment with a disk pool that migrates to tape,
it would seem that using one-channel for TDPO backups makes the most sense to
prevent the case where multi-channel files get migra
We have two TSM v7.1.7.0 server running on different RHEL 7.x servers. The
primary storage pool is BACKUPPOOL which has it's volumes in the local OS
mounted as NFS volumes across a 10g network connection. The volumes live on the
Data domain which does it's own deduplication in the background. We
My experience (which confounded IBM) is the expires would never end (let it
run for over 9-days) even when picking a single node to expire. I was
restarting the TSM server on a daily basis, it not multiple times a day -
especially when I was going the expires 1-by-1 to determine which nodes
were c
Hi Steve,
Yes, the older backups matching the specification should get rebound.
Del
"ADSM: Dist Stor Manager" wrote on 11/11/2016
12:26:28 AM:
> From: Steven Harris
> To: ADSM-L@VM.MARIST.EDU
> Date: 11/11/2016 12:27 AM
> Subject: Rebind
Thanks. I think the reason why EXPIRE INVENTORY without NODES only seems
to expire a small amount of nodes is that it tries to continue where it
left the last time it stopped – if you happen to normally run expire
with DURATION= limitation. If TSM cancels the expire process
after duration is exceed