This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C1AB17.3C7395D0
Content-Type: text/plain;
charset="iso-8859-1"
Ken,
When we went through training (by Veritas) we were told to relocate the
master/media installs from the default "program files" to a folder called
Veritas in the root of C:(obviously we are talking MS here). No particular
explanation other than it worked better that way. Bug or not that's just the
way it is. On the other hand they stated that clients can be loaded in the
default location and work just fine. I can verify that we have had no
problems backing up a multitude of different clients from our W2K
master/media server or from the client.
David Spearman
County of Henrico, Va.
-----Original Message-----
From: Young, Ken [mailto:limelite AT ti DOT com]
Sent: 31 January, 2002 22:47
To: 'veritas-bu AT mailman.eng.auburn DOT edu'
Subject: [Veritas-bu] Windows Platform: Space in install path causes user
directed back up to fail?
Any help on this scenario will be appreciated:
My colleagues have tested User Backup to two different NetBackup Servers
with NetBackup Data Center v3.4 (applied the J0850645 patch to upgrade to
v3.4.1GA) and the client software is installed to C:\Program Files\VERITAS.
Here are the details:
Server 1: Acer Veriton 7100 NT4.0 SP6
2: P4 1.5GHz, 512MB Windows 2000 Server SP2
Client 1: Dell Latitude LS Windows 2000 Pro SP2
2: Acer TravelMate 732TL Windows 2000 Pro SP2
3: Plus a few other AcerPower standard PCs
Got the following status message on the Client
10:09:45 2002/1/31: Backup Started
10:09:49 Initiating backup
10:09:58 INF - Backup by A0123456 on client a0123456: could not set user id
for process.
Job details on the server
Job type: Backup
Backup type: User-Directed
Client: a0123456
Class: Alex
Class type: MS-Windows-NT
Schedule: Alex_User
Schedule type: User Backup
Status: could not set user id for process(31)
According to my colleagues, Veritas Support indicate this is a bug in the
software because NetBackup is installed in a folder with a space and
currently no fix is available yet.
Now, is my colleague off his rocker or is Veritas Support? I finding it a
bit difficult to believe Veritas does not have a fix, especially since the
servers and clients are all on a Windows platform. In this day and age, for
something to break when the software is installed in the path with a space
in it is a bit absurd, isn't it? Especially since the install defaults to
C:\program files\veritas in the first place.
My guess is my colleague is doing something wrong so I'm asking them to see
if they have installed the latest patches on the systems and if they created
any logs. I have no problems with this when my master server is running on
Solaris 7.
A little help, anyone?
Thanks,
Ken Young
Texas Instruments Inc.
214-567-5016
------_=_NextPart_001_01C1AB17.3C7395D0
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Windows Platform: Space in install path causes user directed backup to
fail?</TITLE>
<META content="MSHTML 6.00.2600.0" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=939534911-01022002><FONT face=Arial color=#0000ff
size=2>Ken,</FONT></SPAN></DIV>
<DIV><SPAN class=939534911-01022002><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=939534911-01022002><FONT face=Arial color=#0000ff size=2>When
we went through training (by Veritas) we were told to relocate the
master/media installs from the default "program files" to a folder called
Veritas in the root of C:(obviously we are talking MS here). No particular
explanation other than it worked better that way. Bug or not that's just the
way
it is. On the other hand they stated that clients can be loaded in the default
location and work just fine. I can verify that we have had no problems backing
up a multitude of different clients from our W2K master/media server or
from the client.</FONT></SPAN></DIV>
<DIV><SPAN class=939534911-01022002></SPAN> </DIV>
<DIV><SPAN class=939534911-01022002><FONT face=Arial color=#0000ff size=2>David
Spearman</FONT></SPAN></DIV>
<DIV><SPAN class=939534911-01022002><FONT face=Arial color=#0000ff
size=2>County
of Henrico, Va.</FONT></SPAN></DIV>
<DIV><SPAN class=939534911-01022002></SPAN> </DIV>
<DIV><SPAN class=939534911-01022002> </SPAN></DIV>
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Young, Ken
[mailto:limelite AT ti DOT com]<BR><B>Sent:</B> 31 January, 2002
22:47<BR><B>To:</B>
'veritas-bu AT mailman.eng.auburn DOT edu'<BR><B>Subject:</B> [Veritas-bu]
Windows
Platform: Space in install path causes user directed back up to
fail?<BR><BR></FONT></DIV>
<P><FONT size=2>Any help on this scenario will be appreciated:</FONT> </P>
<P><FONT size=2>My colleagues have tested User Backup to two different
NetBackup
Servers with NetBackup Data Center v3.4 (applied the J0850645 patch to upgrade
to v3.4.1GA) and the client software is installed to C:\Program Files\VERITAS.
Here are the details:</FONT></P>
<P><FONT size=2>Server 1: Acer Veriton 7100 NT4.0 SP6</FONT> <BR><FONT
size=2> 2: P4 1.5GHz, 512MB Windows 2000
Server SP2</FONT> <BR><FONT size=2>Client 1: Dell Latitude LS Windows 2000 Pro
SP2</FONT> <BR><FONT size=2> 2: Acer
TravelMate 732TL Windows 2000 Pro SP2</FONT> <BR><FONT
size=2> 3: Plus a few other AcerPower
standard PCs </FONT></P>
<P><FONT size=2>Got the following status message on the Client</FONT> <BR><FONT
size=2>10:09:45 2002/1/31: Backup Started</FONT> <BR><FONT size=2>10:09:49
Initiating backup</FONT> <BR><FONT size=2>10:09:58 INF - Backup by A0123456 on
client a0123456: could not set user id for process.</FONT> </P>
<P><FONT size=2>Job details on the server</FONT> <BR><FONT size=2>Job type:
Backup</FONT> <BR><FONT size=2>Backup type: User-Directed</FONT> <BR><FONT
size=2>Client: a0123456</FONT> <BR><FONT size=2>Class: Alex</FONT> <BR><FONT
size=2>Class type: MS-Windows-NT</FONT> <BR><FONT size=2>Schedule:
Alex_User</FONT> <BR><FONT size=2>Schedule type: User Backup</FONT> <BR><FONT
size=2>Status: could not set user id for process(31)</FONT> </P>
<P><FONT size=2>According to my colleagues, Veritas Support indicate this is a
bug in the software because NetBackup is installed in a folder with a space and
currently no fix is available yet.</FONT></P>
<P><FONT size=2>Now, is my colleague off his rocker or is Veritas Support? I
finding it a bit difficult to believe Veritas does not have a fix, especially
since the servers and clients are all on a Windows platform. In this day and
age, for something to break when the software is installed in the path with a
space in it is a bit absurd, isn't it? Especially since the install defaults to
C:\program files\veritas in the first place. </FONT></P>
<P><FONT size=2>My guess is my colleague is doing something wrong so I'm asking
them to see if they have installed the latest patches on the systems and if
they
created any logs. I have no problems with this when my master server is running
on Solaris 7.</FONT></P>
<P><FONT size=2>A little help, anyone?</FONT> </P><BR>
<P><FONT size=2>Thanks,</FONT> <BR><FONT size=2>Ken Young</FONT> <BR><FONT
size=2>Texas Instruments Inc.</FONT> <BR><FONT size=2>214-567-5016</FONT>
</P></BODY></HTML>
------_=_NextPart_001_01C1AB17.3C7395D0--
|
