Doesn't TSM 4.1 allow the sharing of a 3494 between multiple TSM servers
without partitioning it?
At 08:40 PM 11/15/00 -0800, T.Y. Wu wrote:
>I need to add a 2nd RS/6000 TSM server to an existing 3494. The book
>says that IBM ATL must be partitioned for multiple TSM servers to use
>the same libr
Mr. W.
Contrary to George, I'll share my opinions or suggestions here or anywhere
(including your site). I'm not so high minded that I 'feel the need' to
only share my 'oh so valuable' opinion on here or at Tivoli.(smile) I will
go to any site where I can ask the proper question and receive a p
Mr. W:
I choose to share my opinions and suggestions with this TSM list group and
Tivoli direct. I believe my questions and issues have the highest
probability of being addressed by following these channels. I'm not sure I
see the value in the site you are peddling.
I do not need annonymity to
I need to add a 2nd RS/6000 TSM server to an existing 3494. The book
says that IBM ATL must be partitioned for multiple TSM servers to use
the same library. Exactly how is a 3494 partitioned? What needs to be
done on the 3494 side? I know I need to use different set of category
numbers for the
Hi folks, it's the webmaster of Backup Central here. Please take a look at
this ONE TIME plug for another FREE resource that I've put together
there. I apologize for this unsolicited message, but I'm not selling
anything, and I think it will benefit both current and future ADSM/TSM
customers.
H
It works, thanks James
Raymond Chao
> Kill the dsmserv process as gracefully as possible (kill -11). Then
change
> to the
> /usr/tivoli/tsm/server/bin directory and bring dsmserv up in the
foreground.
> You will be at the TSM server console with system authority.
> Register or update the admin
F Y I ... there is a SHOW INCLEXCL command you can issue from dsmc client
that will resolve the list - makes it easy to see what kinds of changes work
vs. don't work when trying to solve these kinds of puzzles. It is the
client code that controls this, but it also must resolve inclexcl entries
as
I believe there was a pretty good description of how to do this in the TSM
Installation Guide for Solaris. You should be able to find it online of it
may have come with your software. My recollection was that you actually
deleted the device files, edited the .conf files and then reconfigured th
Thanks - that seems to agree with what the book tells me too, although I
have to say it's not entirely clear about it. There ought to be a big
warning "Don't do a boot -r when you plug in the library".
Does anyone know how to remove library and drive devices from Solaris? Is
there a way that do
Hi gurus.
We have ADSM 3.1 in AIX 4.3.2
What is the best way to control sessions of a node? I want that a node
only have one session active, no more.
Any suggestions?
Thanks for your help.
Raul Giraldo Suarez
TSM Bancolombia
Thanks for the information
> -Original Message-
> From: Lawrence Clark [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, November 15, 2000 12:54 PM
> To: [EMAIL PROTECTED]
> Subject: Re: TSM 4.1 Server and SQL Backtrack
>
> When we were deciding to go to either 3.7 or 4.1, SQL-BACKTRACK
Has anyone seen this?
11/15/2000 15:37:39 TcpRead: Zero byte buffer read.
11/15/2000 15:37:39 sessRecvVerb: Error -50 from call to 'readRtn'.
11/15/2000 15:37:41 ANS1017E Session rejected: TCP/IP connection failure
11/15/2000 15:37:41 ANS1017E Session rejected: TCP/IP connection failure
Thanks,
We now have a few users who are asking about a FreeBSD client.
At 02:50 AM 6/1/2000 +, Carl Makin wrote:
>On Wed, 31 May 2000, Joshua S. Bassi wrote:
>
> > Start a discussion on the ADSM-R list. Marketing is supposedly
> > monitoring this requirements list and will listen to it a whole
> > l
When we were deciding to go to either 3.7 or 4.1, SQL-BACKTRACK was testing the 4.1
release. I believe they added 4.1 as a supported release.
>>> [EMAIL PROTECTED] 11/15/00 03:49PM >>>
> Hi Everyone,
>
> We have our server on AIX 4.3.3 and planning to be migrating to TSM 4.1
> from ADSM 3.1.7 th
the exclude.fs should be just the name of the mount point, i.e.
EXCLUDE.FS /ofa1/* < this is wrong
EXCLUDE.FS /ofa1< I think this will work
On Wed, 15 Nov 2000, Jeannine Walter wrote:
> All,
> I am having problems with the inclexcl list on this machine. I hav
> Hi Everyone,
>
> We have our server on AIX 4.3.3 and planning to be migrating to TSM 4.1
> from ADSM 3.1.7 this weekend. We have AIX clients and NT Clients. Some
> are on TSM v 3.1 and other ADSM 3.7.
Did anyone have any trouble with SQL Backtrack with TSM 4.1
> Any help will be greatly appre
Take the default node registration which is compression=client. Then in the
dsm.opt file on Windows and the dsm.sys file on Unix, set compression yes
for those clients desiring compression. The default value is compression
no.
Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Color
We would like to set the compression on some of our nodes to on but still
keep it client's choice. What would the flag be and would it belong in the
dms.opt or the dsm.sys.
ThanX,
Greg
Hello,
Except for the adsm schedule log I cannot find a way to save output
from the command line interface. I need the results of big restores
or big manual backups saved.
--
Mark Brown
Operations Supervisor
=
Tel ---> 514-398-2321
Fax ---> 514-398-6876
E-mail --
I went round and round on this with the IBMer who helped me install years
ago. It seemed that everything we tried didn't work. Until the day we
went back to the original list and did a "q occ". It seems that "q fi"
shows known file spaces. Try your list or Tivoli's and look to see what's
actua
All,
I am having problems with the inclexcl list on this machine. I have tried
several different variations on it and it still seems to ignore the exclude
statements. On this box, it's a major problem since the excludes total
almost 4TB of data. The weird thing is that it seems to recognize and
Gerhard,
I think this is a bug. The problem I believe is that the Win9x client is
trying to access NTFS security information and those APIs are not supported
on Win9x. The work-around would be to specify SKIPNTPermissions YES in the
dsm.opt file.
Regards,
Mike Dile
Tivoli Storage Manager Clie
I just installed ADSM on my NT server and, after a restart, when I go
through the GUI wizard I get the following error:
ANS0113E NLInt: Message repository
"C:\Progra~1IBM\ADSM\baclient\dscameng.txt" has an invalid control record"
It's a fresh install. How can I get past this??
Andre' Jennings
There is one thing to keep in mind when you change the dsm.opt on an NT
system to make TSM think you are a different node.
The driver letters c:,d:, etc.. get substituted to their UNC names
based on the machinename of the machine that is doing the backups and
restores.
Say I have a machinename '
Hi,
we have a Windows95 client (3.7.2.0.1) with NT network drives.
When we are backing up the network drives, we get the following entries
in the TSM Error Log:
2000-11-15 13:38:39 TransWin32RC(): Win32 RC 5 from fioScanDirEntry():
FindFirstFile
2000-11-15 13:38:56 GetBackupStreamSize(): FindFir
Use the command "set accounting on" to start recording the smf
information. The smf record type is 42 with a subtype of 14. Check the
ADSM or TSM Administrator's Guide for the content and format of the records.
Jim Sporer
At 11:32 AM 11/15/2000 -0500, you wrote:
>Can you give me more specifics
What I do is basically follow the methods outlined in this MS article:
http://support.microsoft.com/support/kb/articles/Q125/9/96.asp
In order to get to the original registry key that contains the shares, you
can use the load hive function in regedt32 to load the old system registry
hive from th
Hi All!
We have a TDP for R/3 Ver 3.1.0.1 on AIX 4.3.3. When we are running
BRBACKUP utility then it generates an error message "BKI2006E General
exception in dispatcher. Exiting ..." ,but BRARCHIVE utility runs
correctly.
SAP version is 4.6B.
Do you have any experience about?
Sandor Maklari
Can you give me more specifics ?
Is this an options ?What SMF type records ? Are these records mapped
somewhere ?
For OS390 the same information in dsmaccnt.log, is written in smf records.
Jim Sporer
Thomas,
Cannot speak about NT restores specifically, but have had some experience of
Novell restores and do not see why from a TSM view they should be different.
Say you want to restore client A's filespaces to client B
With Netware you just specify the nodename of client A in the dsm.opt of clie
For OS390 the same information in dsmaccnt.log, is written in smf records.
Jim Sporer
At 09:20 AM 11/15/2000 -0500, you wrote:
>I guess I should have clarified my environment.
>
>This is OS/390 2.5. There is no dsmaccnt.log.
>
>And as I mentioned to Maria, I am not going through a proxy. I go di
On Wed, 15 Nov 2000, Steven P Roder wrote:
> > Hi *SM-ers!
> > Today I will be a proud owner of two new libraries. I will have to move the
> > data (both tapepool and copypool) from the old libraries (3575) to the new
> > ones (3494).
> > I can think of 3 different methods to do this:
> > 1) Using
Has anybody been successful restoring "shares"?
-Original Message-
From: Joshua S. Bassi [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, November 15, 2000 10:05 AM
To: [EMAIL PROTECTED]
Subject: Re: Windows NT Shares are not restored!?
The share information is not kept in the directories th
Hi Stephanie,
Yes, if you do not run the archivelogs command often enough and the Domino
Log
space fills up, it will stop (crash) the Domino server. I do believe you
get a warning
to the Domino console, but it does continue and eventually crashes.
Check out the /THRESHOLD= option on the archiv
I used khexedit (for KDE) and did a text search for ext2.I then added reiserfs
just before it. This actually worked for dsmc but I think I ran into problems
with dsm not seing the filesystem. That is why I used a virtualmountpoint
directive in TSM instead. In other words I wouldn\'t recomend modif
Could you clarify how you would add reiserfs to the list of valid
filesystems? Also - is that a plausible solution, i.e. would it actually
work?
Also, has anyone had any experience w/ ext3 and TSM? I would imagint that
due to its similarity to ext2, that it probably works - can anyone confirm
>We have seen this problem a couple of times now and were wondering if =
>anyone has any suggestions for an easy way to deal with it. We have seen =
>someone who is not a registered node on our OS/390 TSM 3.7.3 server =
>attempt to access the server with a client. Of course, they get rejected =
> Here is a "Disaster-Recovery" testing question: we are attempting to
> practice restoring the server then restoring a client from the restored ADSM
> server. My current quandry lies in server-clinet names; the LAN techs say
> we cannot define a test client with the same name as the test box li
> Hi *SM-ers!
> Today I will be a proud owner of two new libraries. I will have to move the
> data (both tapepool and copypool) from the old libraries (3575) to the new
> ones (3494).
> I can think of 3 different methods to do this:
> 1) Using the MOVE DATA command to move the data on a volume lev
I talked to Tivoli support about this a couple of weeks ago and they have no
plans to support this filesystem type. We got around this problem by NFS
mounting the system to it's self over the loopback address.
Chris Anderson
WIC Systems Administrator
> -Original Message-
> From: Patrick
Hi Nick!
I was thinking the same way, but a few weeks ago I was reading a discussion
on this list about the difference in performance between a move data and a
reclaim. That's why I hoping to find someone who has done such an exercise.
Thanks for your answer!
Kindest regards,
Eric van Loon
-O
We have seen this problem a couple of times now and were wondering if anyone has any
suggestions for an easy way to deal with it. We have seen someone who is not a
registered node on our OS/390 TSM 3.7.3 server attempt to access the server with a
client. Of course, they get rejected as an inv
The share information is not kept in the directories themselves.
Instead Microsoft stores this info in the registry. To restore
all share info requires restoring the registry key in addition
to the directories.
--
Joshua S. Bassi
IBM Certified- AIX Support, HACMP, SAN
Enterprise Disk(Shark)& Ta
Does anyone a way around this ?
ADSM 3.1.3 and TSM 3.7.3 clients on NT. When the application is running, it all
goes fine. Then someone logs in and logs out of the server and the client
connection to the server drops. This also happens on scheduled jobs. I read
somewhere once (forgotten where) t
I guess I should have clarified my environment.
This is OS/390 2.5. There is no dsmaccnt.log.
And as I mentioned to Maria, I am not going through a proxy. I go directly
to the OS/390 box.
"France, Don G
(Pace)" To: [EMAIL PROTECTED]
I'd say #1 is the best way, since you stay in full control. #2 will tie up
the "MIGPROC" number of drives in the old library, making control harder.
If you can keep both type of libraries for a while, you can just point the
new data to the 3494's, wait for expiration to clean up most of what is
Paul,
This may be too obvious, but make sure they have the following nlms loaded:
tsands, tsa500, and tsadosp
sometimes you need to unload and reload these guys to get things synched up.
Paul Zarnowski wrote:
> We have a Novell IntranetWare 4.11 user who is attempting to install TSM
> v4.1. A
Hello,
I would migrate all new data to the 3494,
move data (3575 -> 3494) from all volumes in FILLING status
and let expire volumes in FULL status, helping with appropriate reclamation
processes
Regards,
René Lambelet
Nestec S.A. / Informatique du Centre
55, av. Nestlé CH-1800 Vevey (Switzerl
Larry, we have the same sort of config but on an aix node...before we can
define the library and drives we had to delete
them from the aix OS (rmt devices) and redefine them as tivoli storage
management devices (lib - lb0 drives- mt0)
Robert Burton
Open System Storage Analyst
Royal Bank of Canad
Hi *SM-ers!
Today I will be a proud owner of two new libraries. I will have to move the
data (both tapepool and copypool) from the old libraries (3575) to the new
ones (3494).
I can think of 3 different methods to do this:
1) Using the MOVE DATA command to move the data on a volume level to the ne
Hi,
We are about to use TDP for Domino to backup our servers in production.
We activated the transaction logging, in archive mode on the Domino server.
We set the log archive backup three times during the day + an incremental
backup of the databases every night + a full backup and inactivation of
Have you tried loading clibaux?
load clibaux
If it gives errors about \"public symbols\" then you probably have the wrong
versions of some NLMs. Are you running the latest SP?
Quoting Paul Zarnowski <[EMAIL PROTECTED]>:
> We have a Novell IntranetWare 4.11 user who is attempting to install
>
Not sure about TSM support but there are a couple of ways around the problem.
Either use hexedit on dsmc and add reseirfs to the list of valid filesystems or
use virtual mount points.
Quoting \"GWDVMS::MOELLER\" <[EMAIL PROTECTED]>:
> Some of our clients have deployed LINUX (SuSE 7.0) systems
Good morning!
This error generally points to a corrupt file. Here is a procedure for it:
ANS1028S - Corrupted file
1. Review dsmerror.log file to determine where the corrupted files is
located.
/var/adm/dsmerror.log
11/08/00 00:43:57 TransErrno: Unexpected error from lstat, errno = 89
11/08
Is there a plan on Tivoli Data Protection for Oracle (AIX, HP-UX, Sun
Solaris & NT) to support Oracle8.1.7.
If so what is the requirement and planned available date. Thanks.
Regards,
Eric Tang
Please help!
Running a backup on an aix box with an adsm 3.1 client we keep getting the
following error and the backup of the filesystem stops/failes
11/15/00 09:58:21 TransErrno: Unexpected error from lstat, errno = 4
11/15/00 09:58:25 PrivIncrFileSpace: Received rc=131 from
fioGetDirEntrie
Hi Paul,
we have NW 4.11 with patchlevel 8a and TSM v4.1 and we get no error messages.
regards
Reiner
>>> [EMAIL PROTECTED] 15.11.2000 02:32:44 >>>
We have a Novell IntranetWare 4.11 user who is attempting to install TSM
v4.1. After they install the software, when they try to:
load sys:t
Some of our clients have deployed LINUX (SuSE 7.0) systems
that make use of the (rather new) "reiserfs" file system.
It pretty much seems that the 4.1 TSM client can't handle this type
of file system - it acts like the affected file systems didn't exist.
Is TSM support for "reiserfs" planned in
Hello. I'm running ADSM Server on Unix Server and backing up NT with ADSM Client
3.1.0.8. One of our NT servers is a cluster. For retrieving files via WEB in a
node it can be necessary to create a service called "ADSM Client Acceptor" that
hears by a port. We want to fix that port. By default the
59 matches
Mail list logo
