e this:
domain somewhere.com
nameserver 192.168.1.1
nameserver 192.168.1.2
with your domain and nameservers, of course.
Matt Zufelt
Southern Utah University
>>> [EMAIL PROTECTED] 02/26/03 12:28PM >>>
Environment:
TSM server 5.1.1.6 on AIX 4.3.3
Netware 5 (latest TSA nlm's) TS
I second Jim's advice. Especially on our servers with large number of files, using
the managedservices option saves TONS of memory. We had one server that after a few
weeks, DSMC.NLM was using nearly 3/4 of a gig of RAM. Using managedservices and
dsmcad.nlm solved the problem.
Matt Z
one I actually
perform NDS backups from) to the following.
DOMAIN ALL-LOCAL -NDS:
That still does an all local backup, but excludes NDS.
Matt Zufelt
Southern Utah University
>>> [EMAIL PROTECTED] wrote on 3/2/2005 9:15 AM:
> We have this Netware system that has be
ng on site to perform the
upgrade. Perhaps that's why it is so pricey? Although I never confirmed it,
I'm guessing the requirement to have a field engineer come on-site was to
protect the integrity of the code.
Matt Zufelt
>>> [EMAIL PROTECTED] wrote on 4/11/2005 12:26 P
>>> On 5/9/2006 at 12:57 AM, [EMAIL PROTECTED] wrote:
> Hello TSM+NetWare Experts,
>
> is there a way to put the output of, for example,
> "dsmc q backup" on the NetWare 6 console into a file?
>
> Or, if not, can I use another OS's TSM client?
> I didn't succeed with Linux and MS Windows TSM clie
I believe the problem was fixed in later versions of the TSM for NetWare client.
Until you are able to upgrade, you can work around it by loading netdb.nlm before
loading dsmc.
Matt
>>> [EMAIL PROTECTED] 9/23/2003 9:21:47 AM >>>
Is anyone familiar with the following problem:
SERVER-5.60-918:
.
It names the TSM filespaces something like ClusterName/Volume instead of
ServerName/Volume.
Matt Zufelt
Southern Utah University
>>> [EMAIL PROTECTED] 9/26/2003 2:26:44 AM >>>
Jim,
first of all thanks for the reply.
One question though, these will be shared cluster volumes s
o perform the
backups, dsmcad loads dsmc, does the backup, and then unloads dsmc thereby freeing the
memory. This method has worked wonders for memory utilization on our servers here.
Matt Zufelt
Southern Utah University
>>> [EMAIL PROTECTED] 9/26/2003 4:53:51 PM >>>
All,
Enviro
lient
to the DSM.OPT file. Then, just load dsmcad (without loading dsmc sched). If you
receive public symbol errors when loading dsmcad, load netdb first then dsmcad.
Matt Zufelt
Southern Utah University
>>> [EMAIL PROTECTED] 10/31/2003 8:22:48 AM >>>
NWWAIT NO
in dsm.opt
ne in your dsm.opt file.
For example:
DOMAIN ALL-LOCAL NDS:
When you query the filespaces on the TSM server, you'll see a filespace called
NODE\NDS: which is listed separate from other filespaces for the node.
Matt Zufelt
Southern Utah University
>>> [EMAIL PROTECTED] 1/14/20
last night's backup follows my sig.
Thanks in advance for any help!
Matt Zufelt
Southern Utah University
-->last night's dsmerror.log output->
03/08/2004 00:00:01 ANS1228E Sending of object '\\xpsp1pc\c$\Documents and
Settings\All Users\Application Data\Microsoft\Network\D
really want to do that for all the obvious
reasons, but it wouldn't be the end of the world if that was the only solution. If
this client were to ever die, I would probably prefer to do a ground-up rebuild
anyway, rather than an ASR restore.
Thanks again for the help!
Matt Zufelt
Southern U
urce. The unique dsm.opt file contains the
TSM node name, the domain line that points specifically to the clustered volume, and a
specific httpport for that resource.
I've got a longer doc that goes into more detail that I will send you off-list.
Matt Zufelt
Southern Utah University
>&g
ength (000123L1).
I am familiar with the procedure for changing the 3583 library to use the extended
length labels, but what do I need to do to get TSM to recognize them (without causing
data loss)?
Thanks in advance,
Matt Zufelt
Southern Utah University
In your dsm.opt file you need this line:
NWEXITNLMPrompt NO
--Matt
>>> On 5/21/2007 at 7:52 AM, William Kyndt <[EMAIL PROTECTED]> wrote:
> Hi,
>
> We have recently upgraded our Tivoli Netware Clients to version 5.3.2 to
> match our backend version. We run a 4 node cluster and it has
VOLNAME:
and only backup the volume that is explicitly stated in the domain line. There
shouldn't be a need to negate volumes using DOMAIN. Just explicitly define the
volume you want to backup.
Matt Zufelt
Southern Utah University
>>> On 6/6/2007 at 10:40 AM, Zoltan
It is possible to load it multiple times with the same name. However, I prefer
to rename it for unload purposes. If you load with the same name, when you
type 'unload dsmc', all instances will unload. If you've renamed them, you can
'unload dsmcvol1' or 'unload dsmcvol2' to unload the specifi
17 matches
Mail list logo