Hi Lars-Erik
I had this problem with a Windows2000 box. The intel admins had installed
the 5.4.0.0 client, which the installer allowed even though not supported,
When I realized that I asked them to downgrade it to 5.3.6.0.
Some time after that they tried to restore a number of files, and the on
So I assume you have multiple primary pools, including that dead Netware
pool, that back up into one copy pool? And you want to delete just SOME of
the nodes out of the Copy Pool?
Only good way I can think of, is to run MOVE NODEDATA on those Netware
servers.
Start with empty scratch volumes; ru
Original Message
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf
Of Mark Stapleton Sent: Monday, January 12, 2009 11:20 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: I'm missing something somewhere -- part 2
> What's the collocation on that pool set for? If it's collocated
Is the destination pool collocated?
--
Mark Stapleton (mark.staple...@cdw.com)
CDW
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Kauffman, Tom
Sent: Tuesday, January 13, 2009 9:15 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] I'm missing
Original Message
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf
Of Kelly Lipp Sent: Monday, January 12, 2009 4:51 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: I'm missing something somewhere -- part 2
> Is cache=yes on that pool? Are you talking about percent utilized o
Hello everyone,
TSM server 5.4.3 on Windows 2003 server.
I have decommissioned all client Netware servers ; since their data were
on a specific storage pool, only for netware files, I was able to move the
related tapes out of the library ('move media ...' commands), because I'm
running out of ava
The client level is the same as from the beginning, but I have upgraded the
server and did it the 1st of December to 5.5.1.1.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Timothy Hughes
Sent: den 13 januari 2009 14:37
To: ADSM-L@VM.MARIST.ED
On Jan 13, 2009, at 8:36 AM, Timothy Hughes wrote:
Yeah, I was thinking about this also, I'm curious if it makes a
difference how far down a level the restore is from the backup
level? ...
Chapter 1 of the client manual starts with a definition of levels
compatibilities, per IBM development a
Yeah, I was thinking about this also, I'm curious if it makes a
difference how far down a level the restore is from the backup level?
for example
backup client level TSM 5.5.1
restore client level TSM 5.5.0 or a 5.4 level
compared to
backup client level TSM 5.5.1
restore client level 5.3.
Encryption is not involved and the client is the one first installed a long
time ago. Why does the restore works for 50 of the files and not 8 of them?
There are files created in between that are no problem to restore!?
The dsmerror.log doesn´t show more than this:
2009.01.13 12:16:20 ANS4014E
Yeah, using down level clients to restore data can be interesting :)
K
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Richard Sims
Sent: dinsdag 13 januari 2009 13:29
To: ADSM-L@VM.MARIST.EDU
Subject: Re: ANS4014E
If encryption is involved
If encryption is involved, this may be the situation described in
Technote 1281972.
More likely, I would suspect that the client attempting the restoral
is not the one which performed the backup, and that the backup client
was at a higher level, as summarized in APAR IC53549. The
dsmerror.log ma
TSM Server 5.5.1.1 Windows 2003
TSM Client 5.3.4.6 Windows 2003
I´m trying to restore deleted files to a mapped share on a client and I do get
this error in the dsmerror.log. I can restore 50 out of 58 backed up files.
2009.01.13 12:16:19 ANS4014E Error processing
'\\192.168.101.160\c$\Temp\Res
13 matches
Mail list logo
