We have spent the better part of this week trying to export a node from one
server to another. It is constantly failing with server lock issues,
requiring us to restart it. Then when it finishes, there are lots of
"objects that are part of incomplete groups" being deleted when it
finishes?
Also
4:09 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] Directory-Container Storage Pools - Export/Import
>
> Thanks David. I think the steps you mention follow what is in the
> directory-container storage pool FAQ:
>
>
> Q6. How can I store existing data to a directory-con
Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Maness, Eric
Sent: Wednesday, March 23, 2016 4:09 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Directory-Container Storage Pools - Export/Import
Thanks David. I think the steps you mention follow what is in the
directory-container
again on new 7.1.5.0 server and age node out on 6.3.5.100 server. I hope they
fix the export/import in the near future.
Eric Maness
OA | ITSD | SDC
Work: (573) 526-0578
eric.man...@oa.mo.gov
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On
s we serve.
From: ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] on behalf of Maness, Eric
[eric.man...@oa.mo.gov]
Sent: Wednesday, March 23, 2016 3:44 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Directory-Container Storage Pools - Export/Import
Is the following stil
for the future roadmap. Traditional move and copy
features are not supported for directory-container storage pools. You cannot
use the following commands with directory-container storage pools:
* BACKUP STGPOOL
* EXPORT/IMPORT
* GENERATE BACKUPSET
* MOVE DATA
Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Alford, Ben
Sent: Monday, August 25, 2014 7:47 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TSM Export / Import to FC SAN Disk?
We need to copy backup data for two nodes from our old TSM server to our
We need to copy backup data for two nodes from our old TSM server to our new
one. These nodes have retention policies of seven years, so we think
export/import is the way to go.
The old and new TSM servers are on the same FC network and we have defined a
large 2 TB file on the FC SAN. The
Can EXPORT/IMPORT preempt if NOPREEMPT is set? I see two "opinions":
http://www-01.ibm.com/support/knowledgecenter/SSGSG7_6.3.4/com.ibm.itsm.srv.doc/r_srv_mng_process_preempt_opts_mount_point.html?lang=en
claims that:
To disable preemption, specify NOPREEMPT in the server options fi
archived filed from the
imported node (as long as the nodes versions are not older than 5.4.0.0)
Regards,
Jean Yu
(512) 286-9376 (T/L 363-9376)
From: Bill Boyer
To: ADSM-L@vm.marist.edu,
Date: 03/28/2014 10:36 AM
Subject:[ADSM-L] Export/Import compatibility between server
What is the compatibility for being able to EXPORT from one TSM server and
IMPORT on another? I have a customer with (2) TSM servers on the other side
of the world from each other. They plan on wanting to EXPORT from one and
IMPORT and restore on the other. How far apart can the 2 TSM server be and
That's a clever little trick Wanda, i'm going to remember this one, thanks.
:-)
On Tue, Apr 23, 2013 at 4:23 AM, Prather, Wanda wrote:
>
> When there is no archiving activity on the client machine, on the TSM
> server do:
> rename the ...abcd filespaces to ...abcnew
> rename the ...abc1 filespace
:23 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Export/import from TSM 5.5.6 to TSM 6.3.3.100
>> by mistake MERGEFILESPACES=YES was not specified during
>> export/import of archive data;
>> as a result without giving any warnings or errors archive data w
>> by mistake MERGEFILESPACES=YES was not specified during
>> export/import of archive data;
>> as a result without giving any warnings or errors archive data was
>> imported to separate set of file spaces slightly changed in comparison with
>> b
;
- upgrade has been completed successfully without any problems and new
TSM Server is in production mode now;
- export/import for big nodes was done in two steps: first with
FILEDATA=BACKUP, then with FILEDATA=ARCHIVE (just to reduce export/import time
and avoid skipping backups
ARIST.EDU
01/26/2012 02:10 AM
Please respond to
ADSM-L@VM.MARIST.EDU
To
ADSM-L
cc
Subject
[ADSM-L] Export / Import of NDMP Data
Hi,
I got a situations where a customer wants to export NDMP data out from TSM
and maybe later import it to the same or another TSM Server.
They are running today
ristian Svensson"
À: ADSM-L@VM.MARIST.EDU
Envoyé: Jeudi 26 Janvier 2012 08:10:34
Objet: [ADSM-L] Export / Import of NDMP Data
Hi,
I got a situations where a customer wants to export NDMP data out from TSM and
maybe later import it to the same or another TSM Server.
They are running today TSM 6
Hi,
I got a situations where a customer wants to export NDMP data out from TSM and
maybe later import it to the same or another TSM Server.
They are running today TSM 6.2.3.0 on Windows and the NDMP data are NetApp
Dumps based on 8.0.1 and 7.3.5.1
My question is, has anyone successfully been ex
hello,
problem solved, something with the storage system was wrong.
with best regards
stefan savoric
hello,
every day i send data (export) from my source server to a target tsm
server. (both 5.5.4.2)
the command is:
export node * domain=tag filedata=allmergefilespaces=yes
toserver=xxx_server1 fromdate=today-1 fromtime=10:00:00
an every day i get a message on target system like
ANR0656W I
>> On Tue, 5 May 2009 15:43:13 -0400, "Huebschman, George J."
>> said:
> Hello everyone.
> I remember reading a discussion of the many different ways of exporting
> and importing. I believe that there was a link to someone's personal
> site, but I don't recall who it was...
That's-a me. :)
N
Hello everyone.
I remember reading a discussion of the many different ways of exporting
and importing. I believe that there was a link to someone's personal
site, but I don't recall who it was...
I want to try to solve an export question as simply as possible. I can
think of ways to do it ineffic
e
> import bombs when creating the node and subsequently does not import any
> data. Has anyone had real success with the export/import, or is its use hit
> and miss ? I have a ticket open with IBM and have double checked my
> privilege when doing a toserver import and also and have ch
data to be
>> exported ). We want to move the node from one instance ot another. I also
>> tried doing an export from tape to import on the second instance, but the
>> import bombs when creating the node and subsequently does not import any
>> data. Has anyone had real suc
ernet
richard.mochnaczew...@standardlife.ca
Sent by: ADSM-L@VM.MARIST.EDU
02/19/2009 02:42 PM
Please respond to
ADSM-L@VM.MARIST.EDU
To
ADSM-L
cc
Subject
[ADSM-L] Export/Import node from one instance to another
Hi *,
I'm experiencing some trouble trying to export all of one node's fil
import any data. Has anyone had real success with the
export/import, or is its use hit and miss ? I have a ticket open with IBM and
have double checked my privilege when doing a toserver import and also and have
checked my export and import when using tape and it all looks good.
TSM Server 5.4.3.0
> Yeah, but wouldn't that lead to an empty node in the target server? Of
> course I want to migrate the data, I just don't like the idea of
> copying ten tapes worth of data to a set of temporary tapes and then
> again to new storage pool tapes (I have not tried it yet, but I assume
> TSM doesn't j
es).
See Ya'
Howard
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf
> Of Henrik Ahlgren
> Sent: Friday, November 21, 2008 4:01 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] export/import nodes
>
> thanks for comm
I never used, but I think that might work for you...
If you use the command UPDATE LIBV, then you can change the owner of the
volumes...
>>-UPDate LIBVolume--library_name--volume_name-->
>--++--+---+---><
'-STATus--=--+-PRIvate-+
thanks for comments so far.
Yeah, but wouldn't that lead to an empty node in the target server? Of
course I want to migrate the data, I just don't like the idea of
copying ten tapes worth of data to a set of temporary tapes and then
again to new storage pool tapes (I have not tried it yet, but I a
I think you can use the command export node with the parameter
filedata=none. Example:
export node test filed=none tos=server1
Please, correct me if I'm wrong.
On Thu, Nov 20, 2008 at 9:13 PM, Wanda Prather <[EMAIL PROTECTED]> wrote:
> You can't copy just some DB entries.
> Other people have re
You can't copy just some DB entries.
Other people have reported success with restoring the TSM DB to the new
server, then deleting the unwanted filespaces/nodes on the new server.
But you need to review your tape inventory carefully. The fact that your
storage pool is collocated doesn't mean that
I've heard that this might be on the roadmap for tsm 6.X for X >= 2
On 20 nov 2008, at 15:32, Henrik Ahlgren wrote:
Hi,
I have a simple question.
Let's say that I'm splitting a large TSM server instances into few
smaller servers, using a shared library with library manager/client
architec
: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Henrik
Ahlgren
Sent: Thursday, November 20, 2008 8:32 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] export/import nodes
Hi,
I have a simple question.
Let's say that I'm splitting a large TSM server instances into few
small
Hi,
I have a simple question.
Let's say that I'm splitting a large TSM server instances into few
smaller servers, using a shared library with library manager/client
architecture.
Now, if there are pretty big client nodes whose data is on collocated
tapes, can I move a node between server
2008 4:57 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] AW: [ADSM-L] Export / import nodes with shared library
Hi again,
Thank you Neil !
- Sorry, but 'UPD LIBV ... OWN=' do not solve the problem ...
---> ANR8969E The owner of volume XX can not be updated to owner TSM1.
VATE forever)
Any other idea(s) ?
Thank you !
Otto
-Ursprüngliche Nachricht-
Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von
Strand, Neil B.
Gesendet: Freitag, 27. Juni 2008 16:39
An: ADSM-L@VM.MARIST.EDU
Betreff: Re: [ADSM-L] Export / import nodes with shared library
Otto,
- Y
Otto,
- You should be able to just update the libvol owner on the library
manager to the new server.
- You may also consider using server-server export which transfers data
through the ethernet from the source to target server. This process
allows for concurrent export/import and reduces the
Hi TSM'ers,
We splitted our TSM Server up to five instances (four library clients, one
library manager, 3494)
To move the nodes to new instances we export/import them on tape
(TSM0 is library manager, TSM1-TSM4 are library clients)
(1) on instance TSM1: Export node to vol
Unfortunately, EXP POL really means export domain.]
Original message
>Date: Tue, 3 Apr 2007 14:07:17 -0500
>From: Michael Read <[EMAIL PROTECTED]>
>Subject: [ADSM-L] export - import policy question
>To: ADSM-L@VM.MARIST.EDU
>
>I ran an export policy on a TS
g for what someone else deems
as best practice for the media which is consumed during my export
import. Do you hang on to this for any period of time, or do you just
make it scratch again?
04/03/07 11:00:23 ANR0640I IMPORT POLICY: Processing policy set
ACTIVE in
pol
On Jul 28, 2006, at 2:20 AM, Andreas Priebe wrote:
...
Note the difference in FILE_SIZE: 56210 vs. 11195180! This seems
strange!
And what does the difference in the field AGGREGATED mean (No vs.
124/256)?
...
Another thing is puzzeling me: the blank in the filename in the
"select", which is
Hi,
we are just testing the migration of a TSM 5.1.9.5 (AIX 4.3)
to a TSM 5.2.7.2 (AIX 5.2).
So far everything seems OK, policies and data were exported and
imported just fine, but I noticed a discrepancy in the file sizes
shown in a select from contents for ALL files (data are from a ContenManag
Hi all,
Windows 5.3.3 server
I have an export/ import question. Has anyone successfully exported and
imported a client that was using journaling? Then after importing the
client, during the next backup, did journaling work correctly?
Brett Whitlock
Storage Management Group
Did anyone have a performance result for an export/import process of a node
using:
1- sequential media
2- server to server comm.
Any recommendations ¿?
TSM 5.2.2.0 running on solaris 8 to TSM 5.2.6.3 running on solaris 9
Regards,
Ibán Bernaldo de Quirós Márquez
Technical Specialist
cell
Hi all,
following scenario.
Server one have a disk only backup. Server two have a tapelibrary.
We do a export data over StS connection from one server to another.
On server one we run everyday the "del volh type=all" command
My question : After this "del volh" expires the exported data on server
he procedure is rather to occur for a Notes database (lost mail) then for
an Oracle database.
best regards,
Kurt
From: ADSM: Dist Stor Manager on behalf of Del Hoobler
Sent: Fri 18/11/2005 0:01
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] export / import T
Kurt,
How about just renaming the imported filespaces to something like this:
RENAME FILESPACE SERVER.DOMDBS1SERVERIMP.DOMDBS
RENAME FILESPACE SERVER.DOMLOGS1 SERVERIMP.DOMLOGS
Give this a try.
For SQL Server... it is slightly more complicated, because there could
be more filesp
best regards,
Kurt
Van: ADSM: Dist Stor Manager namens Del Hoobler
Verzonden: do 17/11/2005 16:21
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: Re: [ADSM-L] export / import TDP Notes backup
Kurt,
You cannot do this. The filespace names MUST end in ".DOMDBS" and
".DOMLOGS" in orde
"ADSM: Dist Stor Manager" wrote on 11/17/2005
03:40:07 AM:
> Good morning everybody,
>
> At least in Belgium it is morning.
>
> I'm testing the export / import procedures of a node that contains
> the online backup of a Notes server.
>
> The ba
Good morning everybody,
At least in Belgium it is morning.
I'm testing the export / import procedures of a node that contains the online
backup of a Notes server.
The backup of the server_notes with the TDP (Win2000, TSM BA client 5.3.2, TDP
Notes 5.1.5.1, TSM server 5.3.2.1 on Window
I'm running TSM 5.2.6.1 on AIX 5.2. I've run exports and imports before but
not on a regular basis so I've got a question. How does an Import work as it
relates to replacing files when an import was done previously? Shouldn't the
files show the new import as active files?
A few weeks ago we did an
o 15/09/2005 22:02
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: Re: [ADSM-L] export import node metadata TSM database
Look at the server VOLHISTORY; export tapes are recorded there.
I believe you will find that if an EXPORT spills to a second tape, the
second tape is recorded as "vol seq #2" o
e-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Kurt Beyers
Sent: Thursday, September 15, 2005 3:12 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: export import node metadata TSM database
Thanks for the answers Wanda.
Exporting all of the active backup data of all the serve
is not in the TSM dictionary, but I'm just trying to be creative to
answer the customer wish list.
thanks,
Kurt
Van: ADSM: Dist Stor Manager namens Prather, Wanda
Verzonden: do 15/09/2005 17:42
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: Re: [ADSM-L] export impor
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Kurt Beyers
Sent: Thursday, September 15, 2005 9:54 AM
To: ADSM-L@VM.MARIST.EDU
Subject: export import node metadata TSM database
Hi,
Is there any metadata of the exports stored in the TSM database
Hi,
Is there any metadata of the exports stored in the TSM database?
If I want to export eg two clients A and B to the same volume (eg a tape vol001
that has enough space of course), can I specify twice the command:
export node A filedata=backupactive devclass= VOL=vol001
export node B filed
Hi all!
I will realice the import/export operations to move a TSM Server from AIX to
SUN, but I doubt about the storage pools. Well, I have more than 30 Storage Pools.
Do I need to have those all storage pools name defined on new server (target server)
that was defined on the sourc
. 06082-1900
E-MAIL: [EMAIL PROTECTED]
PHONE: (860)403-2281
"Prather, Wanda"
<[EMAIL PROTECTED]To: [EMAIL PROTECTED]
UAPL.EDU>cc:
Sent by: "ADS
ECTED]
PHONE: (860)403-2281
"Rainer Holzinger"
<[EMAIL PROTECTED]To:
[EMAIL PROTECTED]
YMMENE.COM>cc:
Sent by: "ADSM: Dist Subject: An
Brian,
what exactly was the export command you entered?
Could it be that only active files have been exported/imported?
I don't know how inactive files are handled at export/import which have
been deleted from client. Are they exported?
regards, Rainer
Alex
When I have done server-to-server EXPORT/IMPORT to servers with incompatible
media types, there were some differences in the logical/physical space
occupied on the target server. I assume that was due to differences in how
blocks are formatted with the different media, because testing restores
gt; -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]
> On Behalf Of Brian L. Nick
> Sent: maandag 12 januari 2004 16:35
> To: [EMAIL PROTECTED]
> Subject: Re: Export / Import
>
>
> That was my original assumption but if you look at the &#
[EMAIL PROTECTED]
<[EMAIL PROTECTED]cc:
L> Subject: Re: Export / Import
Sent by: "ADSM:
Dist Stor
Manager"
<[EMAI
I'm not sure but since the physical space occupied decreases
could it be that the export/import process reconstruct the
aggregates and thus removes any 'holes' you may have had
in your aggregates on the OS/390 server?
Rega
An: [EMAIL PROTECTED]
NIXWM.COM> Kopie:
Gesendet von:Thema: Export / Import
"ADSM: Dist Stor
Manager"
<[EMAIL PROTECTED]
Good morning everyone,
We are in the process of migrating from TSM 4.2.1.9 running on OS/390 2.10
to TSM 5.2 on AIX 5.1. Due to incompatible media we are using the server to
server export import process to move node data, however I am seeing
discrepancies in the amounts of data to move. Here is
Hi To all
I am about to run an Export /Import for a node. My primary server is on a
Aix and got there a nodename called RAYA and want to export it to a Windows
server.
The configuration in my secondary server (Windows) is different , not the
same Domain or MamagmentClass or Devclass.
Primary
I just want to thank everyone in the group for your help! I was very
nervous about trying out this export import, but now that I have a better
idea of how it works I think I'm ready to give it a try. Thanks again!
***
Joni
Joni,
No you don't lose the original when you export
John
**
The information in this E-Mail is confidential and may be legally
privileged. It may not represent the views of Scottish and Southern
Energy plc.
It is intended solely
L PROTECTED]>
Sent by:"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject:Re: export/import
I can write to tape, but since this concerns tsm on the mainframe and the
stk silos are run with tms, I don't think that I can remove one tap
It's a copy.
-Original Message-
From: Joni Moyer [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 12, 2003 2:01 PM
To: [EMAIL PROTECTED]
Subject: Re: export/import
I can write to tape, but since this concerns tsm on the mainframe and the
stk silos are run with tms, I don't
y: "ADSM: [EMAIL PROTECTED]
Dist Stor cc
Manager"
<[EMAIL PROTECTED] Subject
.EDU> Re: export/import
11/12/2003 01
o it!
It's much faster than using server-to-server communication, because with
server-to-server, you have to transmit the data via TCP-IP.
The only reason you MUST use server-to-server for export/import, is if you
have no compatible media that both servers can read/write.
-Original Me
Hello all!
I am just trying to get a better idea of how export/import data between 2
tsm os/390 servers works. I know that in order to do this I will have to
create server to server communication. I will then export the data for
certain nodes onto virtual memory. What virtual memory is used
Any reason not to used these commands to basically reassign a large
number of nodes to a new domain on the same server?
Manually reassigning doesn't seem like that big of a deal, but dealing
with all the schedules looks like no fun, and I don't see where any of
the server copy commands do what I w
ogrammer
[EMAIL PROTECTED]
(717)975-8338
Zoltan
Forray/AC/VCUTo: [EMAIL PROTECTED]
<[EMAIL PROTECTED]>cc:
Sent by: "ADSM: Subject: Re: export/import client data
>>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
ARK.COM> cc:
Sent by: "ADSM: Subject: export/import client data
Dist Stor
Manager"
<[EMAIL PROTECTED]
.EDU>
08/07/2003 02:0
server we were trying to import to, in the first place.
"Rushforth, Tim" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
08/07/2003 04:16 PM
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
DSM: Subject: Re: export/import client data
Dist Stor
Manager"
<[EMAIL PROTECTED]
.EDU>
08/07/2003 03:16
PM
Please respond to
. I have been
researching export/import of node data and I am not quite sure if this is
the method that would work What I want to do is register the servers
on the production tsm and let them do backups/archives to this server and
let all of the other backup information expire after their 95
Hello guys!!!
I'm in a export/import process from TSM AIX to TSM W2K plataform. The old TSM Server
(AIX) have about 30GB and the new one
started with 50GB of db size. The export/import occurs by node.
I've started the export/import for the biggest node on the TSM environment (Netwa
little success in the past using export/import where the
target server was at a lower version than the source server (kinda makes
sense, since the data base can change from one version to the next), so I
don't think this is guaranteed to work.
That being said, if you did the setup using the
Hi list-
Due to some restructuring, I need to export node 'x' from TSM server 'k'
and then import it to TSM server 'c'.
I want to use virtual vols.
I set up the server-server comm stuff, devc, and client nodes as needed.
I ran the export node 'x' on server 'k' specifying a devc that points to
se
Hi,
I just got done doing an export/import of a windows 2000 node. Before
starting the export/import, I first did a "move nodedata" command to get all
the files onto just a few tapes so that the export/import would run faster.
I then did an "export node filedata=all tos=server02
Paul,
I did a LOT of export/import when I reorganized the data in my TSM system
after adding our LTO library. This is what I saw.
Yes, you can export selected filespaces. You're right, the data in TSM is
not affected automatically.\
Then delete the filespace you want gone.
When you IMPOR
Paul,
I don't know about reimporting to the same system, but when I exported
nodes to a new server, I found the same situation. I had to define the
old, invalid stgpools referenced by the invalid mgmtc on the new
machine. Diskpools were easy enough to jigger, but tapepools only got easy
with th
I have some filespaces that have part of their files that got stored in the
wrong storage pools, apparently because of a copy group definition error.
The question I have now is, will the following fix/do what I want. We do
not have V5 installed, we are at 4.2.2.12.
Export the Node (This
On TEST2 issue the command DELETE FILESPACE TEST1 * TYPE=SERVER
Jim Sporer
At 02:51 PM 9/27/2002 -0400, you wrote:
>I've been playing around with export/import using server-2-server virtual
>volumes with some success. We have be migrating one of our clients off OS390
>to AIX TS
- Original Message -
From: "Bill Boyer" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 27, 2002 8:51 PM
Subject: Export/Import with virtual volumes
> I've been playing around with export/import using server-2-server virtual
> volu
I've been playing around with export/import using server-2-server virtual
volumes with some success. We have be migrating one of our clients off OS390
to AIX TSM server..so I wanted to be prepared.
I was able to export from TEST1 to TEST2, and then import into TEST2 with no
problems. But
Here is the scenario :
Client : AIX 4.3.3 TSM 4.2.1.21
Server : Z/OS TSM 4.2.1.15
- An archive is created on client1 to server1 with user1
- A set access command is done to give access to user2 to the files
- server1 exports the archive
- server2 imports the archive
- user2 on client2 tries to r
ROTECTED]>
2002-04-29 14:38
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject:please advise best procedure..export/import
Hi
Could you tell me if there is a better way to achieve the following.
Basically we had a p
Hi
Could you tell me if there is a better way to achieve the following.
Basically we had a period where archive data was going to the wrong storage
pools. The archive copygroup setting has now been fixed but I have archive
data that I want to move to the archive storage pools. To get the archive
: [EMAIL PROTECTED]
Subject: Re: Export/Import process
It's OS/390 V2R9. The LPAR has GIGABIT Ethernet, so throughput should be
good. I'll check with our network folks.
Thank you VERY much.
-Original Message-
From: Cook, Dwight E (SAIC) [mailto:[EMAIL PROTECTED]]
Sent
unley, Ike" <[EMAIL PROTECTED]> on 02/14/2002 04:57:23 PM
Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:(bcc: John Naylor/HAV/SSE)
Subject: Re: Export/Import process
Great,
Thanks a lot. I'm reading TSM doc as I
ubject: RE: Export/Import process
Is that an OS/390 running MVS/ESA ?
probably your network interface... or TCP/IP configuration on MVS
lots of tuning is required under MVS to get TSM to run well...
and it still won't run as good as on a healthy IBM S70 AIX machine...
we got rid of our two MVS
1,162 BPX-- IdleW 2.0 H 76.2 M 4.4 K Node WinNT
What causes idle wait?
-Original Message-
From: Prather, Wanda [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 14, 2002 11:32 AM
To: [EMAIL PROTECTED]
Subject: Re: Export/Import process
Neither.
Look at the help for IMPORT NOD
Scott Adams/Dilbert
-Original Message-
From: Hunley, Ike [mailto:[EMAIL PROTECTED]]
Sent: Thursday, February 14, 2002 11:00 AM
To: [EMAIL PROTECTED]
Subject: Export/Import process
We had a TSM region setup for testing and we are moving servers from
1 - 100 of 119 matches
Mail list logo
