Hi List,
I have the opportunity of moving all my windows clients to an lpar on a P5.
We currently backup all windows clients to windows TSM servers. Now what I'm
after is how I go about this and move all my data. I'm guessing that I can't
just export the TSM DB from the windows server and put it o
Paul,
TSM DB backups are OS specific, you will not be able to restore a DB
backup from your Windows TSM server to a newly built AIX server. The
only way to achieve what you want is as you have said, either through
exporting the nodes over a period of time or simply backing up the nodes
afresh to t
hi all,
I am thinking of upgrading and old TDP for SAP from 3.2.0.13 to version 3.3.2
in a HP-UX machine.
Could someone explain me the procedure to install the TDP ¿? It is my first
installation of a TDP... ;-((
Could someone explain me also what is the administration assistant ¿?
Thank You !
Ibán,
First, I think you should use latest version 5.3.2, with that you have to
upgrade bu/archive client and API too.
This is how I do these upgrades:
1. Uninstall TDP for mySAP.com
2. Uninstall bu/archive client and API
3. Install bu/archive client and API newer versions
4. "Remove" java
Thanks Sami !!
I use the 3.3.2 version because the machine OS is HP-UX 11.00, so could I not
do anything more. If I remember well, is the latest version for HP-UX 11.00.
uhmm... I have some questions--- ;-)):
Why you are moving the java directory ¿? is it necessary for the TDP to run ¿?
After
Hi Ibán,
We move java directory because we had some problems installing versions
3.3.?.?. To remind: Remember move those java directories back as those were.
When you are installing TDP it will ask you is this new installation or just
upgrade. BUT you have to have those Management Classes and
My experience parallels yours although I don't know how much blame to
lay at the door of our 3rd party maintenance vendor. We have 4 lightly
used LTO1s and have drives replaced on the order of once a month.
David
>>> Zoltan Forray/AC/VCU <[EMAIL PROTECTED]> 8/8/2006 4:45:05 PM >>>
You won't get
As soon as you said 3583, I felt the pain in my backside twinge. It is of
no wonder that they discontinued the 3583 "[EMAIL PROTECTED]&* garbage" (as you
put
it). The drives we have used in it are very stable, but the loader, and
library are constantly having problems. Of course, IBM continuous
Yeh...i agree Joe. We have the same situation here. We have a 3583 with
LTO2 in a test/DR environment and it is painful to work with it, load
failures, locks up, you name it, just very inconsistent behavior. No
drive failures though and we have LTO2 in it. We also have a 3584 in our
production envi
Yes, that is correct - HP had this feature with LTO1. I did hear,
however, that this created some interoperability issues. If you
wrote a tape on an HP LTO1 drive, there was a chance you would have
trouble reading it back on other vendors drives, because the tracks
weren't written quite accordin
I'm working on a disaster recovery scenario where our TSM server (AIX) and tape
library (3584)that has 90 LTO tapes in tape pools is destroyed and several other
servers are destroyed. We have approx. 85 copy pool tapes off site.
Our thought is to recreate the TSM server via mksysb, restore the T
You can update all the primary tapes to unavailable
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Richard Hammersley
Sent: Wednesday, August 09, 2006 7:40 AM
To: ADSM-L@VM.MARIST.EDU
Subject: restore directly from copy pool tapes
I'm working on a di
Easy as pie.
When you restore the TSM data base, it wil show that your primary tape
pool tapes are still "readwrite", and your offsite tapes are "offsite".
But, your primary pool tapes are actually burned up, and your copypool
tapes have presumably been retrieved from your vault and are now at you
What we have done is -
Purchased the DR component of TSM, which a somewhat automated script
to recover your TSM server and components. It also switches your offsite
tapes to onsite, destroys the onsite versions. You can then recover your
ap servers from TSM as you would normally.
Bill
--
Wanda wrote:
Look at the parms for the "update vol" command - All you have to do is
enter "update vol * wherestgpool=primarytapepoolname
access=unavailable"
(or DESTROYED)
"update vol * wherestgpool=copypoolname access=readonly"
I find it much easier to just update the storage pool
Tsm:> u
On Aug 9, 2006, at 11:00 AM, Large, M (Matthew) wrote:
I find it much easier to just update the storage pool
Tsm:> upd stgpool acc=reado
You mean: ACCess=UNAVailable.
Just one point of note.
upd stgpool acc=unavailable
Specifies that **client nodes** cannot access files stored on
volumes
in the storage pool.
** Server processes can move files within the volumes in the
storage
pool and can also move or copy files from this storage pool t
No problem.
Rebuild (from mksysb) your TSM server.
Restore your TSM database (you'll need the current TSM device config
file and volume history file, with the device config file changed to
match the proper rmt names for the tape drives) --
OR -- we have a custo D/R device config file that define
***
This e-mail may be privileged and/or confidential, and the sender does not
waive any related rights and obligations. Any distribution, use or copying of
this e-mail or the information it contains by other than an
>> On Wed, 9 Aug 2006 10:19:08 +0100, "Pitt, Stuart" <[EMAIL PROTECTED]> said:
> I have the opportunity of moving all my windows clients to an lpar
> on a P5. [...]
> I'm guessing that I can't just export the TSM DB from the windows
> server and put it on the AIX server.
Terms of art are import
Only thing I would disagree with is the order of your checkins. Maybe for an
actual disaster, but for a D/R test where you have your
copypool tapes shipped to the recovery center, depending on the timing of the
dbbackup you'll be restoring and those tapes, there
could actually be "live" tapes tha
Yep.
In our case, the database backups go off-site with the copypool tapes
and we ship (or hand-carry) all tapes that are off-site from our storage
location (the company hangar) to the D/R hotsite at the time of the
test. So I've usually got two to six 'empty' tapes off-site per the most
recent da
Thanks to all! It was a space.g.
Laura
-Original Message-
From: Laura Lantz
Sent: Tuesday, August 08, 2006 11:43 AM
To: ADSM-L@VM.MARIST.EDU
Subject: include/exclude errors
TSM 5.2.2
AIX 5.2
Hello Everyone!
I am getting the following errors in my dsierror.log file:
08/08/0
Paul,
Assuming that "SQLDB_COPYPOOL" can be tape...
The only implication that I can think of is that if you have to resort
to using the copy storage pools, there are some DP/SQL queries
(such as querying the TSM Server for SQL database backup file information)
that will require tape mounts, possi
24 matches
Mail list logo