Hello Ricky,
You can do an export node with a mergefilespace=yes option, but I've found
that to be problematic when replicating application data. You could
rename the node on the source server first, before exporting, then the
node will import with a different name and will not hav
Good Morning All,
We have exchange data on an old TSM server that we are trying to decommission.
What I need to do is, export the exchange data that still exists on the old
TSM server to our new TSM server that was just built approximately 6 months
ago. So my question is, can I export the node
ce Access Strategy: Sequential
...
Mount Limit: DRIVES
De :Jason Barkes
A : ADSM-L@VM.MARIST.EDU,
Date : 2014-07-23 06:33
Objet : Re: [ADSM-L] Number of Mount Points for Export Node
Envoyé par :"ADSM: Dist Stor Manager"
Thankyou André, I had al;ready
15:23
Subject:Re: [ADSM-L] Number of Mount Points for Export Node
Sent by:"ADSM: Dist Stor Manager"
Hi,
try this option upd node MAXNUMMP=<>
ref:
3.63.16 UPDATE NODE (Update node attributes)
(1)
>>-UPDat
Québec a besoin de tous ses travailleurs
www.csst.qc.ca
De :Jason Barkes
A : ADSM-L@VM.MARIST.EDU,
Date : 2014-07-17 08:33
Objet : [ADSM-L] Number of Mount Points for Export Node
Envoyé par :"ADSM: Dist Stor Manager"
Hi,
I am currently exporting nodes from
Hi,
I am currently exporting nodes from one server to another. My
data is not collocated so there are many tape mounts to be completed. It
only sets off one process. Is there anyway to up the number of tape
mounts the export is doing?
Many Thanks,
Jason
Enterprise Support Group
Hi everybody,
Just a little up.
Regards, Mickael.
+--
|This was sent by bobpatrick808...@yahoo.fr via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+---
export node failed. (normal...)
If i delete vol vol_name discarddata=yes in the 9 tape when i do the export the
data can't be read on that tape and the export was successfull ? (i know all
the data on this tape was lost)
Regards, Mi
Hi Roger Deschner, thanks for reply
That exactly what we try to do export node server1 to server2 but during the
export we have an read error on tape and the export node failed.
The LTO3 tape driver associated to the tsm server1 5.5 have one drive HS and
the new tsm server 6.3 have a tape
Try exporting the node directly from one server to the other via the
network. Getting the two servers to talk to each other over the net is
not difficult. V5 talks to V6 OK.
BTW just finished an upgrade of our largest TSM server (300GB database)
from V5 to V6, and it went very well. I have conclud
Hi and thanks for reply Rick,
The audit volume was in progress, i hope the audit was good.
Happy new year to you and your family.
Regars, Mickael.
+--
|This was sent by bobpatrick808...@yahoo.fr via Backup Central.
|Forward SPA
Subject: [ADSM-L] Export node bad tape
Hi everybody,
I try to export node from old server (5.5 lto3) to new serveur (6.3 lto6) but i
have an error with a tape and the export node failed because of that, i have no
copypool (because the 5.5 lto3 have one drive since 1month and the second
server was new
Hi everybody,
I try to export node from old server (5.5 lto3) to new serveur (6.3 lto6) but i
have an error with a tape and the export node failed because of that, i have no
copypool (because the 5.5 lto3 have one drive since 1month and the second
server was new (interest of the export node
en 18 juli 2013 08:11
Till: ADSM-L@VM.MARIST.EDU
Ämne: Export node question
Hello
I have an information question about the process export node (server to server)
.
When I run the command: export node X filedata=alltoserver=Y
exportidentifier=X
How the process export
Hello
I have an information question about the process export node (server to server)
.
When I run the command: export node X filedata=alltoserver=Y
exportidentifier=X
How the process export the files ? Active data first and then the inactive
data ? or how ?
I know
: Export node to another server is slow for Windows
2008 R2 64 bit node
Hello Wanda,
Thank you very much for detailed and helpful answers.
Fortunately, I have new TSM Server 6.3.3.100 and TSM Client 6.4.0. In addition,
I have used recommended way of upgrade for all Windows 2008 servers - perform
: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] FW: Export node to another server is slow for Windows
2008 R2 64 bit node
Hi Grigori,
This is a known performance problem with 5.5 servers and 6.2+ Windows clients
on Win2K8 (and Win2K12).
I've run into it at 3 customers, and it's very pain
d allow the old systemstate backups to sit on the old server until
they naturally expire.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Grigori Solonovitch
Sent: Monday, April 01, 2013 7:00 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] FW: Ex
some bug in 5.5.6 with client 6.2.4?
Grigori G. Solonovitch
Senior Systems Architect Ahli United Bank Kuwait www.ahliunited.com.kw
Please consider the environment before printing this E-mail
From: Grigori Solonovitch
Sent: 27 03 2013 11:57 AM
To: ADSM: Dist Stor Manager (ADSM-L@VM.MARIST.EDU)
S
Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Erwann
Simon
Sent: 27 03 2013 10:27 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Export node to another server is slow for Windows 2008 R2
64 bit node
Hi Grigori,
Know that system state contains many more
,
Erwann
Grigori Solonovitch a écrit :
>Source: TSM 5.5.6 for AIX 5.3-12-06
>Target: TSM 6.3.3.100 for AIX 7.1-01-06
>It looks "export node" is very slow when I am trying to move all data
>for Windows 2008 R2 64 bit (speed is less than 1MB/s).
>It is almost unbelievable, but I
Source: TSM 5.5.6 for AIX 5.3-12-06
Target: TSM 6.3.3.100 for AIX 7.1-01-06
It looks "export node" is very slow when I am trying to move all data for
Windows 2008 R2 64 bit (speed is less than 1MB/s).
It is almost unbelievable, but I have moved a few Windows 2003 servers with
speed
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Wednesday, August 29, 2012 3:51 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Export node to new server
Since you said these are not trivial-size nodes, here are some tricks I've used:
a) Don&
ze of each export
by using fromdate/todate on the export, like fromdate = 01/01/2010
todate=12/31/2010. When that's finished, do it again, pick up another later
date range, then another and another until you get current.
c) Then every morning do: export node filedata=all fromtime=no
) 296-0631
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Monday, August 27, 2012 3:58 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Export node to new server
>>Do I follow the "virtual volumes" setup
the target server.
Woe be unto you if you have domains/mgmt. classes with the same names, but
different retention rules, when you start the export/import.
>>Then, define the node manually on the target;
Not necessary, it will get created with the import.
Then:
>>1: Lock the no
>
> Then, define the node manually on the target; some changes in contact, Policy
> Domain names and other items easy to define manually, but don't need to
> be exported/imported.
>
> Then:
> 1: Lock the node.
> 2: EXPORT NODE TOSERVER= FILEDATA=BACKUP
> EXPORTID
s and other items easy to define manually, but don't need to be
exported/imported.
Then:
1: Lock the node.
2: EXPORT NODE TOSERVER= FILEDATA=BACKUP EXPORTIDENTIFIER=.
3: monitor that, but have the node manager edit the DSM.OPT.
4: unlock node when done.
5: delete filespaces/node on
7;s just one step.
Wanda
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Vandeventer, Harold [BS]
Sent: Thursday, August 23, 2012 4:19 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Export node to new server
My goal is to relocate all backup data
sday, August 23, 2012 4:19 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Export node to new server
My goal is to relocate all backup data for a node currently on a TSM 5.5.2
server to a TSM 6.2.4 server.
There are no archive or space managed data in the system.
First time I've had to try thi
n the target server with appropriate schedules, policy, etc.
Have the node manager modify the DSM.OPT file to specify the new server.
Let scheduled backups run.
On source TSM: EXPORT NODE FILEDATA=BACKUP DEVCLASS=
On target TSM: IMPORT NODE FILEDATA=BACKUP DEVCLASS=
DATES=ABSOLUTE MERGEFILES
}.
thanks
From: Hughes, Timothy
Sent: Thursday, March 29, 2012 9:05 AM
To: ADSM-L@VM.MARIST.EDU
Subject: TSM Export Node not exporting certain files
Has anyone ever had a issue where TSM export suspend itself when trying to
export certain files to another TSM Server? I have noticed the exports seems
=\ADSM.SYS\ASR\ ASR.SIF.
(SESSION:
199762, PROCESS: 20831)
03/29/12 08:38:37 ANR0637I EXPORT NODE: Processing file space
\\logicianq1\o$ for node LOGICIANQ1 fsId 7 . (SESSION:
199762, PROCESS: 20834)
03/29/12 08:38:37
Yes.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Steven
Langdale
Sent: Wednesday, February 15, 2012 6:24 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Export node and management classes
Hi All
I can't seem to find a definitive answ
Hi All
I can't seem to find a definitive answer on this one, so thought I'd ask
the wider group.
I have some nodes i'd like to export from one instance to another. The
nodes use 3-4 different managemant classes and also some archive data with
7 year retention.
If I have a target domain with all
Hi Krishbababu
The export/import is of primary data, which gets placed into a primary
storage pool on the receiving server. Should you choose to run a backup
stg on that, the new server TSM database will not yet have a copy and
create one.
So import your data and run a backup stg on it to get y
Hi,
When exporting client node to another server, do the destination server
import copy pool also???
Regards
Krishnababu
Disclaimer:
This email message (including attachments if any) may contain privileged,
proprietary, confidential information, which may be exempt from any kind of
disc
On Jun 3, 2010, at 10:59 PM, M KIRAN KUMAR wrote:
> Can u tell me if we export a node directly to a server will that exported
> node be visible in the client node list with file spaces on the target
> server for data retrivals?
Providing that the export-import was successful, the target server sh
Yes I performed test archival and executed export node.
Can u tell me if we export a node directly to a server will that exported
node be visible in the client node list with file spaces on the target
server for data retrivals?
Regards,
Kiran.
-Original Message-
From: ADSM: Dist Stor
On Jun 3, 2010, at 4:43 AM, M KIRAN KUMAR wrote:
> Export node node1 filedata=all toserver=2(server2 name)
>
> I am testing in a test environment before actually implementing in
> production servers.
>
> NR0986I Process 12 for EXPORT NODE running in the
> AM
Export node node1 filedata=all toserver=2(server2 name)
I am testing in a test environment before actually implementing in
production servers.
NR0986I Process 12 for EXPORT NODE running in the
AMBACKGROUND processed 5 items for a total of 1,914,957
What exactly was the 'export node' command you issued to export the
definitions and data between servers? And what exactly did the TSM
Server activity log report regarding the completion status and
statistics of that export process?
//David Mc
London, UK
On 3 Jun 2010, at 08:47, M K
e the export node data in the second
server.
Regards,
Kiran.
Disclaimer:
This email message (including attachments if any) may contain privileged,
proprietary, confidential information, which may be exempt from any kind of
disclosure whatsoever and is intended solely for the use of address
Wanda,
Thank you for your reply. It got me on the right track to find the
problem.
Best wishes,
Keith
tting)
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Keith Arbogast
Sent: Monday, April 12, 2010 11:40 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] export node writing to spacemgpool
I am seeing surprising behavior from a process exporting a node
direct
I am seeing surprising behavior from a process exporting a node
directly to another server. Most of the exported files are being
written to an HSM disk pool and HSM tape pool, but some to the primary
disk and tape poosl. All the filespaces being exported are dong this.
I see this by running 'q oc
To
ADSM-L
cc
Subject
Re: [ADSM-L] More than 1 EXPORT NODE per tape
Stacked.
Kelly Lipp
Chief Technology Officer
www.storserver.com
719-266-8777 x7105
STORServer solves your data backup challenges.
Once and for all.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads
12:34 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] More than 1 EXPORT NODE per tape
Are they stacked on the same tape? I thought they were put on separate
tapes?
Regards,
Shawn
Shawn Drew
Internet
boatr...@memorialhealth.com
Sent by
-L
cc
Subject
Re: [ADSM-L] More than 1 EXPORT NODE per tape
Export node node1,node2,node3
_
From: Mario Behring [mailto:mariobehr...@yahoo.com]
Sent: Thursday, January 07, 2010 2:13 PM
To:
Subject: [ADSM-L] More than 1 EXPORT NODE per tape
Hi
It is not possible...yet
Nodegroups were created a while ago to allow multiple backsets to be
stacked, but this functionality hasn't been added to export-node.
I hope IBM adds this because exports are my last-resort archive, when
backupsets aren't supported (API backups, etc)
Regar
Export node node1,node2,node3
_
From: Mario Behring [mailto:mariobehr...@yahoo.com]
Sent: Thursday, January 07, 2010 2:13 PM
To:
Subject: [ADSM-L] More than 1 EXPORT NODE per tape
Hi list,
Is it possible to use put more than 1 export on the same
Hi list,
Is it possible to use put more than 1 export on the same tape? I executed one
export but there is room for much more data on the tape.I think it is not
possible.didn´t see anything that made me believe otherwise.so I´m
asking...
Mario
TSM server,
transporting tapes and then reading back in on the other. Plus, with some of
the extras in the EXPORT NODE command in recent versions, as the node was
still 'live' it enabled us to perform some very simple delta 'top-up'
EXPORTS to ensure that, at the point the client was cu
>
> - Original Message - From: "David McClelland" <
> david.mcclell...@networkc.co.uk>
> To:
> Sent: Tuesday, August 11, 2009 3:31 PM
> Subject: Re: [ADSM-L] Export NODE from Windows TSm Server to AIX TSM Server
>
>
>
> Hi Sandeep, yes this is pe
- Original Message -
From: "David McClelland"
To:
Sent: Tuesday, August 11, 2009 3:31 PM
Subject: Re: [ADSM-L] Export NODE from Windows TSm Server to AIX TSM Server
Hi Sandeep, yes this is perfectly possible.
/David Mc
London, UK
Sent from my iPhone
On 11 Aug 2009, at 10:5
Possible except for NDMP backups. :(
Regards,
Shawn
Shawn Drew
Internet
sandeep.j...@dcmds.com
Sent by: ADSM-L@VM.MARIST.EDU
08/11/2009 05:55 AM
Please respond to
ADSM-L@VM.MARIST.EDU
To
ADSM-L
cc
Subject
[ADSM-L] Export NODE from Windows
You can export directly to the other TSM server.
Look at EXPORT NODE with options like MERGE and TOSERVER.
Andy Huebner
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of ashish
sharma
Sent: Tuesday, August 11, 2009 7:21 AM
To: ADSM-L
Hello Sandeep,
This is possible provided the library manager is same.You need to
crossdefine both servers to each other and then use command
export node filedata=all
On Tue, Aug 11, 2009 at 3:25 PM, Sandeep jain wrote:
> Hello friends
>
> Is it possible to export node from windows T
Hi Sandeep, yes this is perfectly possible.
/David Mc
London, UK
Sent from my iPhone
On 11 Aug 2009, at 10:55, Sandeep jain wrote:
Hello friends
Is it possible to export node from windows TSM Server to AIX TSM
server.
I have got one situation where we have to merge one TSM server on
Hello friends
Is it possible to export node from windows TSM Server to AIX TSM server.
I have got one situation where we have to merge one TSM server on Windows into
another live TSM server on AIXas the client wants a single TSM server.
With best regards
sandeep jain
This email has been
we are trying to move data from the CX to the Centera via TSM import/export
node utility. The performance so far has been only 1GB/hr.
What are other ways that we can utilize TSM to migrate data instead of
import/export node?
We are thinking of setting the current storage pools to read only
I'm having some surprising things happen when doing an EXPORT NODE
directly to another server, on a node that has a CLOPTSET defined.
Both servers are TSM 5.5 on AIX.
I exported a node from one server to another, which has a cloptset
defined, and the cloptset exists on both source and t
: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Richard Sims
Sent: 21 April 2009 13:45
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Verifying EXPORT NODE is successful with Q OCC -
LOGICAL SPACE OCCUPIED (MB) differences?
David -
The Admin Ref manual description of the Physical and
David -
The Admin Ref manual description of the Physical and Logical Space
report element from Query OCCupancy is superficial, leading the
customer to believe that the Logical value is just the amount of space
occupied by client files. According to info I've seen, logical space
also includes hea
Hi Team,
I’ve performed an EXPORT NODE operation from a source TSM server (Windows
5.4.3.2) to a target server (AIX 5.5.1.1) over TCP/IP with the TOSERVER
option. All appears to have completed successfully, the processes on both
TSM Servers report SUCCESS with no errors. However, being of a
TSM has made a major change for the exporting the node between servers in
version 5.5, where you restart the export node process that was suspended
because or error. I think in your case mergefilespace=yes option will work so,
the data doesn't get duplicated, but the entire process will
I'm using TSM 5.4.3 .
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Abid Ilias
Sent: Thursday, July 03, 2008 10:25 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: EXPORT node toserver
If you are using TSM Server version 5.5 export node will start
If you are using TSM Server version 5.5 export node will start from where it
left off. You can use mergefilespace option also so it will not duplicate.
Also issue following command on the source server ' q export ' to see the
status of the export.
-Original Message-
From:
I ran an export node toserver and it errored 1/3 of the way into 200gb
of data.
Are there any steps that need to be taken in order to restart this other
than mergefilespace ?
Will any of my archive data be duplicated on the target server ?
>> On Thu, 29 May 2008 15:37:58 -0400, Kevin Boatright <[EMAIL PROTECTED]> said:
> Anyone run into issues exporting nodes from one TSM server to a
> second instance of TSM running on the same physical server?
It's been a while, but I've done a bunch of that once upon a time.
> Will this data pas
On May 29, 2008, at 3:37 PM, Kevin Boatright wrote:
...
Will this data pass though the network?
Not if you use the communication method called Shared Memory.
Richard Sims
Anyone run into issues exporting nodes from one TSM server to a second instance
of TSM running on the same physical server?
Will this data pass though the network?
Thanks
Kevin
Amos
-Original Message-
From: Bradshaw, Cecil C Mr DATACEN/IBM [mailto:[EMAIL PROTECTED]
Sent: Friday, March 21, 2008 22:45
To: Amos Hagay ADSM
Subject: RE: Export Node with 24TB to other TSM on other Site
Amos,
If your node has more than one filespace I suggest you seriously
consider expor
tions, admin definitions, node definitions, and later the node data. It
was slick.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Evans, Bill
Sent: Friday, March 21, 2008 3:15 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Export Node with 24TB to
I use the following:
EXPORT NODE filedata=all merge=yes toserver=
replacedefs=yes
DEL fi * /to delete on the current server
REM NODE /to remove the node
You will need to register the node on the other server
Works and all the history goes with the export, but, it is not fast.
I see from
You can use the parameters "filedata=all" and toserver=otherTSMserverName" on
the export node command. But that would only go smoothly and quickly as
possible if you have a reasonably fast link between the two servers, tape
won't be too much of a bottleneck, and the expo
Hi To All,
I got 2 TSM Servers, and I need to Export Node from one server to another,
I have a connection between the 2 Sites, and everything is working great, my
problem is that I need to Export 24TB of data,
In the beginning I thought that I can export the Node to the other server
without
Yes...Well the copygroups in the target server for both backups and archives
would both have a destination of ALLDISKPOOL.
- Original Message -
From: "Christian Svensson" <[EMAIL PROTECTED]>
To:
Sent: Thursday, September 27, 2007 10:39 AM
Subject: [ADSM-L] SV: Expor
sprungligt meddelande-
Från: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] För Larry Clark
Skickat: den 27 september 2007 16:32
Till: ADSM-L@VM.MARIST.EDU
Ämne: Export node (Directly)
ServerA has a combination of primary storage pools, disk & tape library
managed using migration, etc. It also h
rA I entered:
Export Node aixnode1 File=* Filedata=all Toserver=ServerB
Would it place all the backup and archive data for aixnode1 in ALLDISKPOOL
on ServerB?
ould just leave them that way until you are ready to completely destroy the
NOVELL data.
From: ADSM: Dist Stor Manager on behalf of Richard Mochnaczewski
Sent: Tue 6/19/2007 3:03 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Export Node and OS Migrations
Hi *,
We a
Hi *,
We are currently in the middle of migrating our Novell file servers to Windows
2003. We will be doing a copy of all our Novell file server data to our Windows
2003 machines and then eventually deleting the Novell machine in the future. In
the meantime, we will be running low on slots in o
Yes
- Original Message -
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
To: ADSM-L@VM.MARIST.EDU
Sent: Thu Apr 05 12:17:32 2007
Subject: export node
Hello,
I am trying to export the obsolete nodes(filespace and all) so that
I can free up some space on tsm server. The problem i
Hello,
I am trying to export the obsolete nodes(filespace and all) so that
I can free up some space on tsm server. The problem is I am low on scratch
volumes where these nodes reside. Am I correct to think that I better have
sufficient scratch volumes available before exporting the obsolete
k fine on our old S7A, the numbers where usually
100MB/s
>and up.
>
>Has anyone running TSM on AIX seen similar behavior?
This is not an AIX issue. TSM's export node command, when you use it to
move actual client data, has been glacially slow since day one on all OS
platforms and a
Hi!
This is probaly not an itsm-issue, but anyway..:
both tsm-servers, 5.3.4, running on the same P650, AIX5.3-box.
Shared memory is used (lo0), but performance is useless. (about 140KB/sek on
average, 70KB in, 70KB out)
This used to work fine on our old S7A, the numbers where usually 100MB/s
a
-L@VM.MARIST.EDU
Subject: TSM DB Increased - Export Node To Tape (Archive Data)
Hi All
I am running out of space for my TSM DB ( 98% ); What I'[m doing now is to
export some archive data to tape and delete it from archivepool/copypool. My
problem is while trying to export 80 version of ar
ith some hidden, secret option !
"Rofie, Abu Bakar" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager"
10/31/2006 08:54 AM
Please respond to
"ADSM: Dist Stor Manager"
To
ADSM-L@VM.MARIST.EDU
cc
Subject
[ADSM-L] TSM DB Increased - Export Node To Ta
Hi All
I am running out of space for my TSM DB ( 98% ); What I'[m doing now is to
export some archive data to tape and delete it from archivepool/copypool. My
problem is while trying to export 80 version of archive data (which was
taken on monthly basis) I only can supply 'fromdate' option where b
Tom -
To factors which come to mind are:
- Lack of collocation can make for a lot of tape repositioning,
which, depending upon your tape technology, can be painful.
- I know from experience, watching reclamations, that tapes which
have been sitting unused for long periods of time (years)
Hi!
Both source ant target-servers are 5.3.2.0, running on the same P650 machine,
AIX 5.3.0.0
I only get around 35-50 KB/s, and that is useless...
When exporting to tape from the target-server, the export runs at 20-30 MB/s,
and about the same when importing from the tape to the source-server.
Hello,
We want to transfer large Filespaces (> 10 TB) from server to server.
Source and target are both AIX TSM servers, source TSM 5220, target TSM
5320.
These long jobs (more than 30 days) are typical candidates to get
interrupted (Media error, network, disks, other,...) and we had already
thes
hanks and Warmest Regards,
Justin Case <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager"
05/12/2006 04:27 AM
Please respond to
"ADSM: Dist Stor Manager"
To
ADSM-L@VM.MARIST.EDU
cc
Subject
Re: [ADSM-L] Export Node
tape drives our available for the extra work.
Justin
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Andy
Huebner
Sent: Thursday, May 11, 2006 3:41 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Export Node
I need to export some nodes from one TSM server to
I need to export some nodes from one TSM server to another to balance
the load.
I tested the command 'export node1 filedata=all toserver=serverb
mergfilespaces=yes' and got a data rate of about 16GB an hour. The 2nd
run of the exact same command finished in 1/4 of the first run time and
moved no d
"ADSM: Dist Stor Manager" wrote on 03/21/2006
02:00:35 PM:
> I'm migrating a TSM instance from AIX to Linux. I have a node that
> has a single filespace with about 5TB of data in it. Looking at the
> performance I'm getting I'd guess that the export node i
Hi,
I'm migrating a TSM instance from AIX to Linux. I have a node that
has a single filespace with about 5TB of data in it. Looking at the
performance I'm getting I'd guess that the export node is going to
take a week or two to complete - not good. And most likely I'll ne
I was exporting a large node ( 290 GB, 2.3 million objects ) with
all files ( active & inactive ) from one TSM server to another
over the weekend. Inadvertently, a scheduled backup took place
to the destination TSM server for that node in the middle of this
process.
The manual warns about performi
Pretorius,
> 1. Does anyone know if export node works with the Exchange TDP? (Win2k3
> with Exchange2k3)
This should work, make sure you export all filespaces for the node.
Each TSM filespace contains data for one and only one Exchange storage
group.
> 2. Instead of running multiple
x27;re the bug, some days you're the windshield" - ??
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Stapleton,
Mark
Sent: Wednesday, June 29, 2005 8:16 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Export node with TDP's ?
Archive the d
1 - 100 of 173 matches
Mail list logo
