Hi Kurt,
How about a export server filedata=allactive ?? Than you have alle active
data in 1 set without increasing the DB.
If nessesary, you can import the node with merge=no, so the imported fs's
will get a different name, what you can savely delete after use. And
becaurce the DB data you need
Stapleton, Mark wrote:
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of Jon Evans
Following on from this... If you had a failure of one of the libraries
(say it burnt!) and the primary storage pool is lost, would it be
possible to have a second TSM server (other than the
If you want to maintain all the schedules that go with the correct node with
the correct drive letters for his 75 nodes And when
an admin adds a drive to a node without letting you know? Or removes one and
now your schedules fail because D:\*.* doesn't exist?
Whose fault does that end up
Hi,
I got something like this some time ago. When I installed 5.2 (don't
remember the exact level) 64bit on a 64bit AIX 5.1 kernel, things were going
slow and CPU use was very high. Just for curiosity I uninstalled the server and
installed the 32bit version, without changing anything on
Hello.
In the TSM administrator guide (5.3) I have found that:
Attention: If the original database or recovery log volumes are
available, you issue only the DSMSERV RESTORE DB utility. However, if
those volumes have been lost, you must first issue the DSMSERV FORMAT
command to initialize the
You could write a script that runs as part of a preschedule command which gets
a list local drives and then compares that to the list of drives that is in the
command file. It could then send you an e-mail if any are missing.
We have to do this for our cluster servers. Because there currently
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
Behalf Of Alexander Lazarevich
Now I'm confused. We bought 5.1.0 from a reseller, and we do
have passport
advantage. But I can't find 5.3.0 anywhere on the ftp site at
all. Are you
saying it's on there somewhere? Or are you saying that
I have to archive 4 servers that have data on same directory but different disk
letter.I would like to do only one schedule.
I tried this object on a schedule define on TSM server. TSM has an error with
this wildcard, somebody did something like that ???
Client schedules : ARCHIVE_EDD_WIN
No guarantees, but you might try an asterisk * instead of a question
mark ?.
--
Mark Stapleton ([EMAIL PROTECTED])
IBM Certified Advanced Deployment Professional
Tivoli Storage Management Solutions 2005
IBM Certified Advanced Technical Expert (CATE) AIX
Office 262.521.5627
-Original
I tried an asterisk * and this .. to.
-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De la part de Stapleton,
Mark
Envoyé : 14 septembre, 2005 09:09
À : ADSM-L@VM.MARIST.EDU
Objet : Re: [ADSM-L] TSM client wildcard
No guarantees, but you might try an
Windows 2K server.
I did I migrate install from 5.1.9 to 5.3.0. Worked fine. Then I did an
upgrade from 5.3.0 to 5.3.1. During the install, while the installer was
upgrading the server intance, I got this error message:
adsmsvc.exe - unable to locate dll
The dynamic link library pai_module.dll
You can only wildcard file names in the archive, incremental, or selective
command file specifications:
Invalid: dsmc archive *:\abc\*
Invalid: dsmc archive c:\abc*\*
Valid: dsmc archive c:\abc1\* c:\abc2\* d:\abc\*
Thus you will need to spell out the drive letters in your file specs,
i.e.,
I want to be able to access the Domino backups via the web-gui. However, I
can't seem to figure out how to configure it, considering the
multi-partition server configuration we are using.
Here is the config:
SUN Solaris system
6-Domino instances
TSM 5.3.x client
TDP 5.3.x client
13-Node
Thanks for the feedback so far.
An archive is out of question due to the 'schedule maintenance' that would be
required as William pointed out and due to the bandwith anyway.
But the 'export node' mentioned by Maurice is a possibility that I will try out
further. A good suggestion tht I
Thanks :-)
The exports don't expire :-) That's the fun It's the backup that does
the expiration
So if you import a node, you will get all the data you import, after a
backup the active data could go to inactive and/or expire.
But i guess you only want to import the data to restore it and
Andy you confirm that I need different schedule.
Thanks
-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] De la part de Andrew
Raibeck
Envoyé : 14 septembre, 2005 10:08
À : ADSM-L@VM.MARIST.EDU
Objet : Re: [ADSM-L] TSM client wildcard
You can only wildcard
The TSM client dsm.opt file must define a DOMNODE option for each TDP
node, for example
SERVERNAME baserver
COMMMETHOD TCPip
TCPPORT1500
TCPSERVERADDRESS node
NODENAMEBANODE
PASSWORDACCESS generate
PASSWORDDIR
Hye
We have a windows 2003 SP1 files server that contain 7 000 000 files of a
capacity of 300 GB. Every day we add 15 000 files for around 1GB. We made
incremental for ever to backup this.
The backup is now very long 20 hours. TSM client is 5.3.0.3. And now we thinks
it's affect the
It's a little messy, perhaps the same result could be achieved, using the
*same* single schedule which runs a script on each host - this .bat or .pl
file might have the dsmc archive invocation specific to that host,
containing the appropriate drive letter (hey, if you're good with perl,
you could
Chantal,
Sounds like TSM journaling would fit your needs.
We have several 2003 fileservers with 10mil+ files and 3TB+ (but a lot
of this are huge .pst files).
Journaling will at least eliminate the filesystem trawling that
normally happens for incrementals.
Be aware that you may need to tune the
Are you able to zip up the files perhaps? I suspect the problem is
reading the huge number of small files in order to decide whether they
require a backup. Perhaps Journaling may help here .. although I have no
personal experience of this..
Also.. check network performance (switch and card set to
Hi,
If possible split the back-up over multiple nodes and/or start using
journaling.
I would try the first part (splitting) over journaling because of the
instability issues with journaling.
Regards,
Karel
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On
That is correct.
The log is cleared/reset each time you do a TSM DB backup; ALL the
current information is on the DB backup tape.
-If you lose your TSM DB, but your log is still intact AND you are
running with the log in ROLLFORWARD mode, you can restore your DB from
the last DB backup and roll
TSM 5.3.1 on win 2000 server.
This is a brand new upgrade (migrate) install. Server is happy. However, I
can't install the new web interface for TSM (called Administration Center)
because it requires that Integrated Solutions Console (ISC) be installed
first.
- I've downloaded the AC installer
I got the same error; somebody else posted the same thing here last
week.
pai_module.dll for some reason doesn't get copied from the TSM_IMAGES
directory to the correct directory.
I just copied mine over, everything works fine. (So did the other
person who posted.)
I've been running at 5.3.1.3
ISC is on passport advantage as part of the 5.3 package.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Alexander Lazarevich
Sent: Wednesday, September 14, 2005 11:06 AM
To: ADSM-L@VM.MARIST.EDU
Subject: integrated solutions console 5.1?
TSM 5.3.1
Thank you.
The DOMNODE option was what I was missing.
Eduardo Esteban [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
09/14/2005 10:56 AM
Please respond to
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
To
ADSM-L@VM.MARIST.EDU
cc
Subject
Re: [ADSM-L] Domino TDP on
RTFM for IMPORT - there is an option DATES=RELATIVE.
You can use that to control whether files roll off based on their
original backup dates, or relative to the date you do the import.
However, I think a better solution is usually to isolate the imported
node entirely.
I'm assuming that you
TOR is 5.3.1.0, running on W2K3. The hardware also runs ISC/AC, but we
don't use that much.
TOR is set to monitor two TSM servers, one at 5.3, and one at 5.2, both
running AIX, if it matters.
For each TSM server, I have the standard hourly report, and two daily
reports; the standard daily
Afternoon all,
Our TSM Server is AIX 5.2.02 at TSM 5.2.6. This morning we noticed a
strange problem with 2 of our windows clients that do archiving. When
one attempts to retrieve from the archive using the Backup-Archive GUI
nothing displays in the window. In this case nothing means you only
Break up the backups into part, say certain file criteria or directory
criteria
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Boileau, Chantal
Sent: Wednesday, September 14, 2005 11:23 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Backup windows File
Good Afternoon.
We are running TSM 5.2.2 server/client with an IBM LTO tape
library(LTO2).
We currently have around 130 clients, 9.2TB of data.
I was watching reclamation yesterday by accident since it's not
something I regularly check and noticed it seemed to take a long time to
run so I ran a
Does Move data also run slow?
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
Jones, Eric J
Sent: Wednesday, September 14, 2005 12:38 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Reclamation/Audits running slow
Good Afternoon.
We are running TSM 5.2.2
TSM Version 5.2.3.5
AIX O/S 5.3
Library - ADIC I2000 Scalar, partitioned library,10 drive 2 drive
IBM drives -LTO 2
We had to move slots over from one partition to the other(due to high
utilization), pending slot/drive order.
What is the correct procedure?
Steps:
Killed all processes/sessions
Speaking of which similar work was performed today.
Here's the steps I used. The setup is little different from yours because
I have one TSM instance with two partitioned libraries defined.
AIX, TSM 5.2.4.5, 3584 Library with LTO1 and LTO2 drives.
1.Migrate all the data off from disk to tapes
Not sure if this relates, but I had a similar problem at one point, and
it ended up being a conflict between the TOR and the actual BA client on
the TOR machine. The BA client had issues with prompted mode, so the
backup wouldn't start until TOR tried to run it's reports - something
about TOR
I am trying to create a file device class of 250GB (I have more than
enough free disk space to do this) and I am getting the following error:
ANR8366E DEFINE DEVCLASS: Invalid value for MAXCAPACITY parameter.
(SESSION: 104127)
Any ideas?
what is the system OS?
I am thinking there is some sort of file size limitation placed by the OS,
Checkout the wiki link.
http://en.wikipedia.org/wiki/Comparison_of_file_systems
Thanks,
Sung Y. Lee
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 09/14/2005
05:09:17 PM:
I am trying to
Well, of course it would be much more helpful to know the exact command
you were issuing (copy pasted from what you typed), but at a guess, you
probably used MAXCAP=250GB instead of just MAXCAP=250G.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Ah, my previous post can be ignored. .., just found something interesting.
Looks like when defining devclass for file type, maxcap value is not
limited by filesize nor space limitation.
wiki link is still cool however..
Sung Y. Lee
- Forwarded by Sung Y Lee/Austin/IBM on 09/14/2005 05:34 PM
== On Wed, 14 Sep 2005 10:08:21 +0200, Rainer Wolf [EMAIL PROTECTED] said:
Stapleton, Mark wrote:
Virtual volume usage requires not only the server where the data physically
resides, but also the server that created the virtual volumes in the first
place. Otherwise there will be no access to
Config
Tsm server version 5.3
Windows 2003 server
3583 IBM library using tsm driver connected via SCSI
Does anyone have a similar config? And if so do you have issues with label
scratch search=bulk. I am currently having to connect to the library web page
and import the tapes, and do a label
As a side note all firmware has been upgraded regularly in the past 2 years. No
help from firmware change..
-Original Message-
From: Meadows, Andrew [EMAIL PROTECTED]
To: 'ADSM-L@VM.MARIST.EDU' ADSM-L@VM.MARIST.EDU
Sent: Wed Sep 14 21:31:21 2005
Subject: 3583 library
Config
Tsm server
Hi Andrew
We have just upgraded our 3583 to a 3584 and the following is
the syntax we would run for checking in new tapes to be labelled
LABEL LIBVOLUME 3583LIB CHECKIN=SCRATCH SEARCH=BULK LABELSOURCE=BARCODE
Then obviously or maybe not q req and then reply to that number.
Hope
Hi Todd, Steve, All,
Two likely causes are documented in APARs IC43649, and IC44976. You can
go to ibm.com and search for those for more information. In a nut shell,
IC43649 documents a restriction for TOR where it doesn't surface an
expired admin password for the account it uses to
45 matches
Mail list logo
