Goran,
I've first tested it a couple of months ago and it all went fine. Now I'm
setting it up for production and the tsmdev is missing from the SysBack
boot menu.
Richard.
goc <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager"
23-05-2005 18:08
Please respond to "ADSM: Dist Stor Manager
Hi,
using a NetApp-box: do you see the drives with a sysconfig -t and sysconfig
-m? You might also be stumbeling over ndmpd-authorisation on the Netapp. We
saw a default of 16 characters for the password...
On the NetApp get the WWN of the drive with a 'storage' command (not sure,
could be 'storag
How do I restore just the PDF files that were deleteD in all
directories/subdirectories below USERDATA:\SHARED\DEPT\XYZ?
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of Lawrence Clark
>Does anyone have a query that shows the mangement class for each node?
There is no one-to-one correspondence between a management class and a
client node. Clients belong to domains, and each domain has a default
Does anyone have a query that shows the mangement class for each node?
Hi TSM guru,
For tracking and tape management purpose, I am trying to come up with a
list of volumes needed for restore and/or tapes used for each storage
pool.
Now, I came up with this one after performing a search of adsm forum..
select node_name, count (distinct volume_name) as NumOfTape,stgp
Dear All,
I am running TSM 5.2.3 on Windows 2003 and here is what i want to check before
any of the disaster strike.
I am using LTO II 3582 library connected via FC SAN.
What I want:
I want to create test setup in which TSM server is on desktop and the servers
that need to be restored are on the
No, I am looking for LTO3 WORM. I know 3592 WORM is supported.
I will be using LTO3 WORM.
David Longo
>>> [EMAIL PROTECTED] 05/23/05 12:07 PM >>>
Hi,
I think you are looking for 3592.
Regards,
Karel
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf O
Additional info:
The Windows NT 4.0 operating system is no longer a supported client with
TSM version 5.3. However, NT 4.0 is a supported client in TSM 5.2 (though
with version 5.1 functionality). Since the clients shipped as part of 5.2
are supported with the 5.3 server, the NT 4.0 client is supp
hi,
i believe nothing is wrong you first choose the net interface
and then you'll automaticaly have tsm option,
at least that's what i got when testing restore from tsm
with sysback
keep up
peace
goran
- Original Message -
From: "Richard van Denzel" <[EMAIL PROTECTED]>
To:
Sent: Monday
Hi,
I think you are looking for 3592.
Regards,
Karel
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
David Longo
Sent: maandag 23 mei 2005 17:59
To: ADSM-L@VM.MARIST.EDU
Subject: LTO3 WORM Support
LTO3 WORM tapes are now available in IBM 3584 libr
LTO3 WORM tapes are now available in IBM 3584 library. From Tivoli Website, I
see LTO3 is supported,
but not clear about LTO3 WORM. (There seems to be WORM support for HP drive).
What does anybody know about support for it and when?
Thanks,
David B. Longo
System Administrator
Health First, In
Hi James,
Checkin libv XX stat=priv owner= / upd libv XX stat=priv
owner=;
Audit library XX on the library client => will tell the library manager
"its not my tape"
Q libv should show tape XX as scratch.
Regards,
Karel
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROT
I will add my voice to this issue. I have the exact same problem.
If you check the ADSM-L archives, I asked the same question, over a month
ago. Got no responses.
James R Owen <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager"
05/20/2005 05:47 PM
Please respond to
"ADSM: Dist Stor Manage
Hi All,
I've setup SysBack on three clients to use TSM as a backup device (virtual
tape device tsm0). When I make a sysback of these clients all works fine
and the image is stored in TSM.
For the ultimate test I want to restore a client (one of them can be used
for the test). When I boot the syst
Hi Fred,
Which NAS are you using? Things to double-check here are that your
datamover definitions are correct (i.e. correct HLA, LLA, username and
password). I witnessed similar errors (EMC Celerra) when I was given an
incorrect IP address for the datamover, defined my TSM datamover against
this a
16 matches
Mail list logo
