In general computing you will want to have your production data center with
all your production servers and your remote site data center functioning as
your production fix / test / development / disaster recovery data center.
Wise processing practice is to perform monthly production fix refreshes f
Be aware that there are many reasons why you won't be able to restore, even
if the backup DID work successfully. For example:
**
**
- *Tapes are damaged or unavailable*
- It's easy to damage tapes when you transport them to your off-site DR
tests.
**
- Critical files are exclude
>From the few responses I got about 6.1.4.x vs 6.2.1.1 for a new server,
the responses leaned to 6.2.x.
With that decision made, the next is laying out the structure of storage
pools and such.
Most discussions/directions from here/IBM say that DEVCLASS FILE is the
way to go vs defining fixed sto
- *"Rogue" servers never got registered to TSM*
- Gartner says this problem has escalated lately with VMware machines
popping up everywhere.
I'm convinced they breed, at night, when no one's minding themzillions
and zillions
Fertilized by Microsoft...
Kelly J. Lipp
Cuerno Verde Consulting, Inc.
O: 719-531-5574 C: 719-238-5239
kellyjl...@yahoo.com
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Prather, Wanda
Sent: Friday, September 17, 2010 8:53 AM
To: ADSM-L@VM.MA
EWWW!
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kelly
J. Lipp
Sent: Friday, September 17, 2010 11:38 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Validate backup and archives.
Fertilized by Microsoft...
Kelly J.
I am configuring the automatic archive log in DB2 using vendoropt tsm
>
> First log archive method (LOGARCHMETH1) =
> VENDOR:/usr/tivoli/tsm/tdp_r3/db264/libtdpdb264.a
> Options for logarchmeth1 (LOGARCHOPT1) = /db2/PIP/tdp_r3/vendor.env
> Second log archive method (LOGARCHMETH2) =
> VENDOR:/usr
Hello all
I'm trying to unzip a solaris 6.1.0.0 client and I keep getting the
error below has anyone had this issue before?
# ls
6.1.0.0-TIV-TSMBAC-SolarisSparc.tar.Z
# gunzip 6.1.0.0-TIV-TSMBAC-SolarisSparc.tar.Z
# ls
6.1.0.0-TIV-TSMBAC-SolarisSparc.tar
# tar -xvf 6.1.0.0-TIV-TSMBAC-SolarisSpa
>So, have you migrated to devclass FILE?
I have migrated most of primary pools to devc/stgpool FILE and found
them perfect (it was done as a preparation to use de-duplication in 6.x, by the
way am still 5.5.4). It is good from any point of view(backup, restore, making
tape copies, etc).
Sounds like a bad/corrupt package. The size should be 98.7MB or
103,537,561 bytes (from the FTP site)
Why would you want 6.1.0.0 when 6.2.x is available? Or as a minimum 6.1.3.
Suggest downloading a higher/newer version or at least re-downloading this
one.
From:
Timothy Hughes
To:
ADSM-L@VM.MA
My thanks to all who replied to my requests for help last Friday.
I thought I would reply and let everybody know how this played out.
In our situation, we had 128 virtual tape drives, and for two nights in
a row, the TSM Library Master instance was getting into a state where
there would be 80 o
11 matches
Mail list logo
