Stephen,
Have a look in ~/sqllib/userprofile where ~ is the home directory of the DB2
instance owner.
Regards,
Kurt
-Oorspronkelijk bericht-
Van: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Namens Stackwick,
Stephen
Verzonden: dinsdag 10 september 2013 23:53
Aan:
We have 2 6.3.4.0 TSM servers, one AIX and one linux. We want to move all of
the data from the AIX server to the linux server and then eventually retire the
AIX server. I understand I can also do this with replication, but because the
lijnux server will eventually be replicating to a second
Thanks, Kurt. The file exists, but is empty. I ran ps -ef | grep db2, found
the instance owner (and indeed, he's the one running the backups), and su -
to him, found the empty userprofile. TSM must be using defaults of some kind
STEPHEN STACKWICK | Senior Consultant | 301.518.6352 (m) |
Hello ,
For DB2 backups for any systems via TSM,the below mentioned environment
variables has to be define on the db2 level,then only backup to tsm will be
possible,see the below example.
host:db2sap 10 db2 get db cfg for sap|grep -i tsm
First log archive method (LOGARCHMETH1) =
I got nothing (see below). Yet, the backups are working somehow. I don't think
the DB2_VENDOR_LIB is relevant, since the end user is not using BACKOM.
db2 get db cfg for pe1 | grep -i tsm
First log archive method (LOGARCHMETH1) = TSM
Second log archive method
Didn't notice the actual EXPORT command/options you used?
On Wed, Sep 11, 2013 at 8:30 AM, Dury, John C. jd...@duqlight.com wrote:
We have 2 6.3.4.0 TSM servers, one AIX and one linux. We want to move all
of the data from the AIX server to the linux server and then eventually
retire the AIX
Hi Christian
Me again .. So if I understand correctly if my all exchange database is 1T I
will need with TDP version 6.1.3.2 a temporary space of at least 1T ?
Did with the new version of TDP 6.4.0.2 the mailbox restore will be different
meaning the space for the recovery will be much less ?
I have tried several combinations of the following and they all fail with the
output listed below.
export node toserver=LINUXSERVER filespace=* filedata=all
export node toserver=LINUXSERVER filedata=all
export node toserver=LINUXSERVER filedata=all replacedefs=yes
mergefilespaces=yes
export
Hi Robert,
The latest versions work the same way. Data Protection for Exchange
mailbox restore uses the supported interfaces of Exchange to do this.
This means that the entire mailbox database is restored into a
recovery database and the individual items are extracted using MAPI.
That means you
What happens if you specify a specific node name that hasn't been exported
yet?
On Wed, Sep 11, 2013 at 12:20 PM, Dury, John C. jd...@duqlight.com wrote:
I have tried several combinations of the following and they all fail with
the output listed below.
export node toserver=LINUXSERVER
I found the problem. There was a leftover replicated node from previous
testing, with the same name. Replicated nodes don't show up when doing a q
node so I wasn't seeing it on the new server.
Thanks for the fresh eyes.
From: Dury, John C.
Sent: Wednesday, September 11, 2013 2:02 PM
To: 'ADSM-L
Have you tried filedata=none just to see if the node definitions get
transferred? Does the exported node ever appear on the Linux server?
In the messages Processing file space \\NODENAME\, are you masking the
node name or is it actually called NODENAME?
On Wed, Sep 11, 2013 at 1:20 PM, Dury,
Our tsm server is 5.5.6, and the upgrade utilities installed is 5.5.6.
rick
From: Zoltan Forray zfor...@vcu.edu
To: ADSM-L@VM.MARIST.EDU
Date: 09/11/2013 03:09 PM
Subject:Re: help - tsm vg upgrade test
Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
Did you
Did you install the Server Upgrade utilities for the level you are
upgrading from? For instance, when I did my conversion from 5.5.7 to V6.3
Linux, I downloaded and installed:
Hi RObert,
Not correct.
A mailbox database refers to the entire Exchange database.
A user's mailbox is a subset of a mailbox databases.
Typically, a mailbox database contains hundreds
or thousands of user mailboxes.
And so, you need enough space to restore the entire database.
That is the
-Richard Rhodes wrote: -
Then . . . get this ERROR:
Beginning database preparation...
sh[129]: /usr/tivoli/tsm/upgrade/bin/dsmupgrd: not found.
Preparation completed with return code 499
It can't find /usr/tivoli/tsm/upgrade/bin/dsmupgrd, which exists:
Hi Del
So enough space for the entire mailbox database who contains the individual
items to restore , but not space for the entire database . Correct ?
Best Regards Robert
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Del
Hoobler
Sent:
That is exactly what I am trying to do.
John
- What happens if you specify a specific node name that hasn't been exported
- yet?
On Wed, Sep 11, 2013 at 12:20 PM, Dury, John C. JDury AT duqlight DOT com
wrote:
I have tried several combinations of the following and they all fail with
the
We are trying a first test of the tsm v6 upgrade procedure for a v5 tsm
server.
We are trying the network method. We restored the tsm v5 db to a test
system
and setup a tsm v6 install on a different test system.
lpar A - tsm v5 db (source)
lpar B - tsm v6 system (destination)
On lpar B we
Richard,
dsmupgrd is on the wrong LPAR.
The upgrade tools must be installed on the LPAR which has the v5 DB, not
on the LPAR hosting the v6
--
Mit freundlichen Grüßen / kind regards
Michael Prix
On 09/11/2013 08:59 PM, Richard Rhodes wrote:
We are trying a first test of the tsm v6 upgrade
20 matches
Mail list logo
