"ADSM: Dist Stor Manager" wrote on 12/11/2006
06:11:52 PM:
> Hi all,
>
> I am wondering if there are any issues folks can inform me as it relates
> to a migration of TSM to a new server. The one main question I have is
> this. If I attach the 3584 and LTO2 drives to a new server, install TSM
> at
Hi all,
I am wondering if there are any issues folks can inform me as it relates
to a migration of TSM to a new server. The one main question I have is
this. If I attach the 3584 and LTO2 drives to a new server, install TSM
at the same level currently and define the library and one drive, will
TSM
OK, if this is a DR scenario, it's a little more complicated. In fact, a
lot more complicated. Are both TSM servers at the same location? I
wouldn't expect they are if this is for DR. In a disaster, you need to
plan for TSM A being unavailable, so you need a way to get your nodes' data
to TSM B
Here's a question. I just started thinking about what I've been doing and
have a concern.
We've been going through a lot of server migrations and things lately, as
well as refreshing older machines and rebuilding them. Just for safety I've
been moving nodes from one domain to a domain I created c
Compression is nice, but many VTLs take a large performance hit doing
compression.
The killer feature of VTLs is data de-duplication, which is beginning to
be available.
Orville L. Lantto
Storage Consultant
GlassHouse Technologies, Inc.
200 Crossing Boulevard
Framingham, MA 01702
[EMAIL PRO
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Greg Yuzik
>I am in the process of updating my WIN2K3 clients to 5.3.4.8 (in
>accordance to the recent critical alert TSM announced a couple days ago
>APAR IC50347), and I am receiving an error message that I cannot seem
to
>find
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Roger Deschner
>I keep hearing it said, that if you're going to buy a great big disk
>array for TSM, that it works better if you let TSM know it has disks
>(DEVCLASS=FILE), than if you lie and try to tell it they are virtual
>tape
Greetings,
I am updating the list about this problem in case anyone else gets
bit by it.
Richard was right in a measure; we had a tape drive that was failing
to eject tapes properly. The side effect, though, with TSM's library
inventory becoming corrupt, is a bug addressed by APAR
First of all, I have successfully built a BartPE CD including decent TSM
client version which is deployed on our servers. That's actually easy. You can
decide which scsi controller and network controller drivers you need.
If you compare TSM+BartPE restores to e.g. Acronis TrueImage I would say
Hi Richard
Thanks, No we have not tried that yet I will try and find the correct
syntax for that combination.
Thanks again!
Tim
Richard Sims wrote:
Tim -
Have you tried a combination of -TCPServeraddress and -
VIRTUALNodename and -PASsword?
Richard Sims
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Christian Svensson
>Don't forget that you also need to have a unique FLOPPY involved for
each
>server. How many wants to manage x hundreds of floppies?
This is incorrect. No floppies are involved in my BMR processes for
Windows.
Tim -
Have you tried a combination of -TCPServeraddress and -
VIRTUALNodename and -PASsword?
Richard Sims
Robin here's a further explanation.
Is there a way to access the TSM backup server for the node (s) that I
want the
data restored to? There are six 6 nodes the production set on TSM
server A
and the DR set on TSM server B. The client would like to be able to restore
data from one node to it
Go to the site in my sig, and search on ANS1009W.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED]
Internet e-mail: [EMAIL PROTECTED]
IBM Tivoli Storage Manager support web page:
http://www.ibm
Robin thanks,
This would not be a one time restore, How could this be done on a continuous
basis for DR purposes?
.
Robin Sharpe wrote:
If all you need to do is a one time restore, I would just register the
target client node (DOCDRB) on TSM server A, perform the restore, them
remove the def
Good morning,
I am in the process of updating my WIN2K3 clients to 5.3.4.8 (in
accordance to the recent critical alert TSM announced a couple days ago
APAR IC50347), and I am receiving an error message that I cannot seem to
find any answers to.
After updating my client node, I start the TSM
Hi Leigh,
The TSM server is NOT large-address aware. (Current client levels, 5.3.3.0
and higher, are linked with /LARGEADDRESSAWARE.)
You're almost certainly know this already, but I'll mention it anyway for
the benefit of others following this thread: The boot.ini parms affect not
just TSM, but
Does anybody have any experience of configuring the following windows
boot.ini parameters in conjunction with TSM server;
/PAE /3GB
With regards to being able to allocate >2GB to the TSM database
bufferpool with Windows 2003 Enterprise Edition (32 bit)
I have a Windows 2003 EE (32-bit) server wi
Hi *,
We are trying to increase the recover times of our servers ( a mix of AIX,
Linux and Windows boxes ) during our yearly DR tests. Is anyone using the
Backup Image to do, from what I've read , snapshots of the filesystems and then
do a restore image plus incrementals to bring the servers up
If all you need to do is a one time restore, I would just register the
target client node (DOCDRB) on TSM server A, perform the restore, them
remove the definition of DOCDRB.
Regards,
Robin Sharpe
Berlex Labs
Timothy Hughes
<[EMAIL PROTECTED]
IT.STATE.NJ.U
For those of you using DIRMC with a device class of FILE to
store directories, with TSM V5.3 the minimum write to this
device class is 256K Bytes. So directories that where once
800 bytes are written to a 256K byte file.
Your storage pool for the directories will increase dramatically.
Any
Because it's a Windows app, it's on the TSM FTP site in the directory
for Windows patches; it's the file named TSMWINCONxxx.
Just download that 1 file and click, run setup.exe and take the
defaults:
ftp://service.boulder.ibm.com/storage/tivoli-storage-management/maintena
nce/server/v5r3/WIN/5.3.4
Recently started the migration process for our ZOS TSM to AIX and I'm
currently running both these servers. In the process of our Desktop Group
changing our PC's from ZEN To LanDesk I lost the TSMOR that was running
for our ZOS server. Since I also need to add the AIX server I went to
download t
A client tried to restore a volume's data ( NVOL1:) from DOCUSRA
to a volume on DOCDRB but can't. DOCUSRA is a node registered
on TSM server A and DOCDRSB is registered on TSM server B does something
needs to be configured for this restore to work? I understand I can restore
data from one node to
24 matches
Mail list logo
