Oh yeah, I found the site already. Made an account for myself on adsm.org
too. Would have posted the link for the next victim but didn't want to be
a pest. Plus I should have just searched my archive for 'ftp' and I would
have found it.
I will download the 5.2... client, thanks for the tip
Hi all,
Who knows which is the highest version level of 32bit TSM Client API?
Please tell me, thanks!
Best Regards!
Zenghui Zhai
Senior Engineer
Technology Service Specialist
Beijing Office
EDIns Computer Technology (Shanghai) Co., Ltd.
A702 IBM Tower, Pacific Century Place, 2A Gong Ti
with import you can't merge client data...
You can merge client data, at least on an export directly to another server
(toserver=) with the mergefilespaces option
From: Hooft, Jeroen [mailto:[EMAIL PROTECTED]
Have a look at these answers of Del Hoobler:
http://msgs2.adsm.org/cgi-bin/get/adsm0304/818.html
http://msgs2.adsm.org/cgi-bin/get/adsm0201/9.html
When will the returncodes of tdpsql be documented?
They are...by Microsoft. They are generated at
Hello,
i have a temporary solution. This problem is describe in the APAR PQ18821.
In the command line with command del archd (nodename) erase the wrong
entries.
A fix for this problem is available.
Mit freundlichen Grüßen
Steffen Bloß
Kreissparkasse Saalfeld-Rudolstadt
IT - Management
Tel :
Cache Migrated Files is set to NO on the DISKDIRS pool. Is that the parm
you are speaking of?
Thanks,
Debi Randolph
Stapleton, Mark
[EMAIL PROTECTED]To: [EMAIL PROTECTED]
COM cc:
Well, the short answer is that IBM doesn't support moving a TSM data base to
a different platform.
My guess is that it has to do with the differences in the filesystems, don't
know.
What you are describing will work fine if you are going from AIX to AIX, or
Solaris to Solaris.
And regarding DR,
We are looking at the same issue. In our case, we need to perform IMAGE
backups of 2-4 Terabytes of data, weekly.
We are looking at LTO2 (200GB native per cartridge).
Saw this blurb:
The Ultrium LTO2 is the ideal choice for modern data centers where the backup window
is shrinking, backing up
We've got TSM 5.1.6.5 server on Windows 2K server. It's been running
great, most clients are backing up just fine, except for a Mac OSX client
- the only OSX client in our environment at the moment.
The Mac is: G4 v3.3 1.4GHz, 2GB RAM, OSX 10.2.6(6L60), darwin kernel
version 6.6.
I've installed
Hello.
We have strange problem with one of our client nodes.
It runs 5.1.6.6 client on .NET
The server is 5.1.7 on AIX 4.3.3
Running incremental or archive produces error:
Normal File-- 104,858,112 \\sab11\m$\REDO02.LOG [Sent]
Normal File-- 104,858,112 \\sab11\m$\REDO03.LOG **
I am using DRM to restore a 4.2.3.1 NT server, from DRM (yep, can't upgrade
until we get rid
of our Novell 4.11 servers, ... that should be done by this time next year
;)
Anyway, when doing the drm restore, the command in the script that was
exploded from the DRM plan file is
While the thread is getting longer and longer, I still see some more to
comment.
Richard already gave the answer - TSM will split the file into pieces and
put each chunk on a tape. So the size of file compared to cartridge
capacity is not an argument. The number of tapes depends on tape
12 matches
Mail list logo