I missed that part...
-Mensaje original-
De: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] En nombre de
Allen S. Rout
Enviado el: Martes, 21 de Agosto de 2007 13:32
Para: ADSM-L@VM.MARIST.EDU
Asunto: Re: [ADSM-L] Servermigration and IP-Replacement
>> On Tue, 21 Aug 2007 16:01:04 +
I have restore backups from WIN in AIX...
Adrian Carlos Pardo
IBM Certified Deployment Professional
IBM Tivoli Storage Manager 5.2 & 5.3,
Tecsystem S.R.L.
Buenos Aires, Argentina.
+54 (11) 4704-6667 ext 121
[EMAIL PROTECTED]
-Mensaje original-
De: ADSM: Dist Stor Manager [mailt
>> On Tue, 21 Aug 2007 16:01:04 +0200, "Bos, Karel" <[EMAIL PROTECTED]> said:
> Why don't you simple restore your DB this new server?
You can't restore DB backups across architectures. :)
- Allen S. Rout
On Aug 21, 2007, at 9:50 AM, Wanda Prather wrote:
The client's IP address is saved as part of the node definition (do
a q
node f=d and you'll see it.), so that isn't a problem.
However, test the move on ONE client before you flop the IP addresses.
All the client data will move fine with an EXPO
Hi,
In windows the ITSM node password is saved in a registry key containing both
ITSM servername and ITSM nodename. So your ITSM server name should be the same.
Also setting your clients to polling could help.
Why don't you simple restore your DB this new server?
Regards,
Karel
-Origina
The client's IP address is saved as part of the node definition (do a q
node f=d and you'll see it.), so that isn't a problem.
However, test the move on ONE client before you flop the IP addresses.
All the client data will move fine with an EXPORT, but it used to be that
if your server platform c
Zoltan -
Your postings don't relate any analysis performed at the Linux level...
Have your Linux people take a good look at that system, to get a profile
of its behavior under load, as to memory, paging, disk, network, and
processor utilization, to help narrow the problem. One sometimes
discover
Hi Folks,
we're in the process of replacing one of our TSM servers.
Old machine is TSM 5.2.2.3 on Solaris,
New machine is TSM 5.4.0.3 on Win2k3.
To minimize impact on the clients I thought of this:
1. ex/import all nodes/schedules/domains... to new server (some with
data, some without)
2. swap
