Debbie -
Your posting contains no information on what analysis you've done to
gain perspective on the problem, and the dominant area in which time
is being consumed. Valuable basic information can be had by
performing repeated Query SEssion commands as the backup session
starts, and as it runs.
Yes there are trade-offs. You will use more tape space similar to what
you would with the TDP products, and you are limited to restoring to a
NetApp instead of any old Windows server. In many cases, achieving 1/4
the restore time is worth it, especially in cases where you are already
exceeding a
What about the Full-incr-incr-incr...FULL methodology of the NDMP
protocol?
Won't you find yourself backing up and keeping identical files over and
over again?
Ben
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
John Monahan
Sent: Monday, July 09
I would upgrade your TSM server to 5.4 and use NDMP to backup the NetApp.
With 5.4 you can do NDMP backups over the network much like a regular TSM
client. I just did this for a customer with a million file CIFS backup
taking 8 hours, down to 2.5 hours using NDMP over the network. No change
in ha
If you're backing up a NetApp filer via the CIFS share and are not
specifically excluding the snapshots, you ARE backing them up, as they
are simply a subdirectory under the share (~snapshot). Are you sure
you're excluding them?
As to your statement that you "did not purchase the tools required t
Thanks, I'll check into the virus scan and memory. As for the snapshots, no we
are not backing them up. I think we may look into that in the future but I was
told we did not purchase the tools required to backup the snapshots.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[E
If you server has enough resources (CPU, memory, storage...) then put the new
instance on the same server. You have to update the
clients DSM.OPT file for the ones that backup to the new "instance" anyway, but
instead of chaning TCPSERVERADDRESS you change
TCPPORT.
You currently have your TSM in
Sounds to me like the TSM Client, a Windows 2003 server needs to have more
memory.
Or it's virus scanning the file share as it's backing it up.
Also look into the 'snapshots' that NetApp may be doing on the file
shares.
Are you also backing up them in addition to the current data?
That could easi
We are in the same state, my db is 180 Gb, 87% utilized. At a high level, one
of the consultants we talked to suggested loading the database onto 2 different
servers and then deleting different storage pools and nodes from each one,
essentially putting part of the database on each server. We a
YMMV:
Enable NFS on the share, and mount it directly to your TSM server.
I realize that it is anecdotal, but I've seen NFS backups complete in
a quarter of the time compared to CIFS.
Have you considered NDMP?
[RC]
On Jul 9, 2007, at 1:14 PM, Haberstroh, Debbie (IT) wrote:
I have a netapp sh
I have a netapp share that is being backed up through a Windows 2003 server and
is taking 23-25 hours to run. It is on a gigabit network, processing
approximately 3.9 million items. Does anyone have any suggestions how to
accelerate this job? Max mount points=7, resourceutilization=7,
memory
The only way that I know to split then TSM db is to create a new TSM
server and export clients to it.
Good luck! :)
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Daad Ali
Sent: Monday, July 09, 2007 11:54 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM
Hi All,
We are discussing a way of splitting our TSM database. It is become very big
and slow.
We want to split it into 2 or 3(one will be the manager of the other two)
I don't know how to split it so I am looking for a procedure/steps on how to
do that.
Also, after splitting the data
Hello all,
I know I poised this question in the past, but I don't think their were
any responses
so I just thought I would try again. I put some windows clients on a
dedicated GigE network does anyone have any optimum values for using
GigE for Windows clients on a TSM server running on AIX 5.3.
Three TSM 5.2.7.0 Servers on AIX 5.3.
Recently moved from a shared 3494 (20 each 3592-J1A) to a shared 3584
(24 each 3592-E05).
Each of the TSM servers sees two non-shared control path drives, and
18 shared drives.
(We do plan to upgrade to TSM 5.4, and to reconfigure for a library
manager and
On Jul 9, 2007, at 10:46 AM, Michael Green wrote:
However, tar'ing the actual target directory revealed that the data is
flowing at extremely low rates - less than 100kb/sec.
In the few cases we've had to write actual tars to tape, we usually
run it through a double-buffer using dd:
tar cf
Upcoming Events & Live Technical Trainings
Tivoli's Support Technical Exchange web seminars allows you to participate in
live discussions on topics such as deployment, trouble-shooting tips, common
issues, problem solving resources and other Support and Services
recommendations.
To see the conne
We were audited. We simply trued-up, reporting the most recent client/TDP
deployments (which were quite a few). At least that was my understanding.
They did want a look at our entire environment. Anyone else want to comment?
:)
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAI
Michael,
Look at the b option to increase your blocking size. Use man tar on your host
to check for the fine print. If your tar program will let you do it, aim for
256K block sizes.
len
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Michael
G
Just out of curiosity, how many people have been audited? Did your entire
environment have to comply with the new per processor licensing or only items
purchased since the new process went into effect?
Debbie Haberstroh
TSM Administrator
-Original Message-
From: ADSM: Dist Stor Manager
On Jul 9, 2007, at 10:46 AM, Michael Green wrote:
However, tar'ing the actual target directory revealed that the data is
flowing at extremely low rates - less than 100kb/sec.
Two major factors affect this:
1. File system state, fragmentation, and disk capabilities.
2. The tar block size choi
This post is a bit offtopic, but still I decided to send ti here
because it's probably one of the very few places where large amount
backup administrators that are invested in IBM equipment come
together.
My question is related to using old school tar with IBM LTO2 drives.
I was asked to archive
This is from the README.SRV from the 5.3.2.1 patch level. If you check out the
readme for the 5.3.2.0 base level I'm sure it'll
probably be the same:
Migration and LAN-free Considerations
*
Only storage agents Versions 5.2.3, 5.2.4, and 5.3 are supported by
Ti
DP Oracle needs to match the bit architecture of the Oracle database.
Please verify that the DP Oracle package you are installing is indeed
32bit package if your Oracle is 32bit.
Regards,
Neil Rasmussen
Software Development
Data Protection for Oracle
[EMAIL PROTECTED]
Remco Post <[EMAIL PROT
Wu Tony wrote:
> Yes~
> TDP version reference target database.
> 32bit tdp for 32bit Oracle.
>
ok, customer decided that having 32 bit windows nor having 64 bits
oracle is an option, and since the tdp can only be 32 bits on 32 bit
winodws or 64 bit on 64 bit windows, he is a bit unhappy.
>
> 2007
Hi,
What is the Storage Agent level ?
Normaly, it should be at the same level as TSM server.
Thanks,
Pierre
-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De la part de zareyna
salim
Envoyé : lundi 9 juillet 2007 13:45
À : ADSM-L@VM.MARIST.EDU
Objet : [ADS
Shouldn't be. Going up is usually not a problem. The older clients won't
get any of the new server features.
I am running 5.4 servers with clients going back to V4 (VMS, old AIX,
IRIX, etc).
Zoltan Forray
Virginia Commonwealth University
Office
Hi all,
Just a quick one.. Is there going to be a problem if the TSM server will be
upgrading to 5.3.5 but the clients and Storage Agent remain to version
5.2.9?
Do I need to restart the server after installing TSM for BAC and TSM for
SAN?
Thanks,
Regards,
Zareyna Salim
No viru
Hi
We have aix 5.1 p610 ibm pseries server
Upgraded firmware.migrated to aix 5.3
After reboot keyboard is not working.
When try to login using login dialog box ,user name is not typing
Pl advice
Koti Reddy
Aix admin
29 matches
Mail list logo
