From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Arni Eggertsson
> Apparently Tivoli decided to use the Microsoft API to backup the
> Exchange database, this is done to be able to do a "consistant"
> backup of the database.
It goes deeper than that.
If you stick to the APIs
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Gallerson,Charles,GLENDALE,Information Technology
> Does TSM 5.1.0.0 provide MOVE NODEDATA and multithreaded restores
Yes. Read the 5.1 Administrator's Guide. It is available on the 'Net. (See
my FAQ posted on August 24, quest
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Roger Deschner
> Note we selected SuperDLT over LTO or other tape technologies solely
> because SDLT drives could read our old DLT-IV tape cartridges. An SDLT
> drive, however, cannot write to a DLT-IV cartridge as I understand i
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Zlatko Krastev/ACIT
> Looking at the length of this thread and shaking my memory this question
> might be a good candidate for the Monthly FAQ (Mark, what do you think ?)
Great minds think alike! ;o)
--
Mark Stapleton ([EMAIL P
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Roger Deschner
> We've got half a dozen clients stuck like this right now. The first case
> I had was an important, tenured, and extremely impatient professor who
> had converted from Win 98 to Win XP, decided that XP "stinks", a
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Sam Haziprodromu
>Hi 'TSM ers, we recently upgraded our TSM server from 4.1 to 4.2 but we ran
>into a problem. AT 4.1 when we sought help it gave us a full page and
>syntax. On the newer 4.2 version help is now a single horizonta
Actually, there are more restrictions than what Mathew indicates. A copy
pool tape must be moved to the same copy pool. It cannot move the data to a
new copy pool like a primary can move to a new primary.
To move all your Copy Pool data to another copy pool, just build a new copy
pool using all
You say you put it on SAN. What kind? I am guessing a Shark or FastT
device since it is an IBM SAN. If you only got 10% with Oracle and the
issues with TSM on the database I think you have your file systems on the
AIX machine setup incorrectly or another problem. It could be the tape
drive is
>From the server, this may be useful:
select filespace_name, hl_name, ll_name from backups where
node_name='YOUR-NODE' and type=file and state=active_version and backup_date
>current_timestamp-1 day
This one actually runs pretty fast because the node_name, type, and state
columns are indexed.
P
We did a simple cpu/disk upgrade during first shift. The libary was the same,
and we moved from nt4 running on a Dell 6100 (dual 200Mhz) to a Dell 2400 also
a dual cpu running w2k.
After the last of the night's backup finished we
copyed all the primary data to the offsite pool.
Migrated all data
What SUN probably did not tell you was they were probably 32K or 64K blocks
to get that data rate. TSM Database uses 4K and most other databases are 4K
or 8K. Are you using raw volumes for the disk pools? If so, talk to SUN to
find out what the optimal block sizes are. If you are using a file
Hi there and thanks in advance for all your tips and recommendations
we have a huge distributed new TSM setup, with server spread across the
campuses. We recently moved from 3 ADSM 3.1 servers to 9 TSM 4.2.2
servers all direct attached SUN 280r(sol-2.8), SUN T3 and Spectralogic 64K
libs
I have
I recently moved the 36G TSM database and 10G log from attached SCSI disk
drives to a SAN. Backing the db now takes twice as long as it used to
(from 40 minutes to 90 minutes). The old
attached disk drives are non-RAID and TSM mirrored. The SAN drives are
RAID-5 and TSM mirrored. I know I have
13 matches
Mail list logo
