I would also delete the veritas registry key to ensure a fresh install.
Simon
P.S. hkey_local_machine\software\ VERITAS
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Martin,
Jonathan
Sent: Tuesday, August 26, 2008 1:38 PM
To:
Hi,
I've run the .msi installer and it gives me the below error message
Error 1723, There is a problem with this window installer package. A DLL
required for this install to complete could not be run.
Is there something wrong with the OS?
Regards
Use setup, not the msi installer
David Spearman
County of Hnerico
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of dy018
Sent: Wednesday, August 27, 2008 9:09 AM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] NBU6.5 Win Client Installation
The Short Version:
1) Upgrade to 6.5.2(a?)
2) Download VCB software from VMWare and install on Media Server.
3) Create a folder called VMWmnt on the Media Server (D:\VMWmnt etc..)
4) Configure VC or Hosts in Master under Media and Device Management /
Credentials / Virtual Machine Servers
5)
On Tue, Aug 26, 2008 at 7:41 AM, Martin, Jonathan [EMAIL PROTECTED]wrote:
I run several scripts that manually prune my DSSUs and DSUs of unwanted
images. Forget the catalog, just run bpexpdate with the image switch
and use the server_image num directly on any file you find on the
drive.
Good catch Ed! My script runs BPIMAGELIST to verify that there are two
copies before expiring. Definitely something that needs to be taken
into consideration!
-Jonathan
From: Ed Wilts [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 27, 2008 9:38 AM
To:
Open a support ticket - there are undocumented features with NBPEM in 6.5.2.
Support will verify a few things and give you an EEB to put on your system.
-- Original message --
From: Jorge Fábregas [EMAIL PROTECTED]
Hello everyone,
After I installed 6.5.2 I
Hi Thanks for your reply,
Using the exe was what we did in the first place, i'm jus trying out installing
using the .msi as suggested by Martins to see if there's any difference but
apparently still the same problem but different error messages.
Regards
On Wed, Aug 27, 2008 at 8:38 AM, Ed Wilts [EMAIL PROTECTED] wrote:
With older versions of NBU,
I pressed send before the fingers finished typing. More coffee required :-)
What I started to say was that with older versions of NBU, the DSSUs had a
tendency to leave cruft behind. The more
Unix Agents and Options cd.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of bubbwe
Sent: 26 August 2008 14:37
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] Anyone using BMR
I am trying to run some BMR tests in our lab and am having
Hi, I'm setting up a new system for the first time and am getting a few
problems. I've created a catalog backup , an this starts fine, runs
child jobs to run the backups ok, but then the parent job just sits
there even if I leave it for hours! I then have to cancel the job .
08/27/2008
Look for errors in the install log.
Extract from TechNote http://seer.support.veritas.com/docs/270110.htm:
Review the install log file for errors. The install log file is found
in the C:\Documents and Settings\administrator_userid\Local
Settings\Temp directory.
Also have a look at these
The jobs failling with 196 at midnight is a bug, and I was told that the fix
for this is going to be in 6.5.3.
+--
|This was sent by [EMAIL PROTECTED] via Backup Central.
|Forward SPAM to [EMAIL PROTECTED]
My catalog backups take approx 3 hours. You may need to let it run longer than
35 minutes.
Doug Preston
Systems Engineer
LandAmerica Financial Group, Inc. - A Fortune 2008 Most Admired Company
#1 in Mortgage Services Two Years in a Row
1123 South Park View DR, Covina CA 91724
Phone 626-339-5221
Hi Doug, should this be the same even if a new build, with very little in the
catalog? I have also let it run for 5 hours and its still hung at the same
place
-Original Message-
From: Preston, Doug [mailto:[EMAIL PROTECTED]
Sent: 27 August 2008 16:42
To: Matthews, Gary (GSD UK
I am configuring a new backup server running Netbackup Pro 3.51.30 running on
Windows 2003 Server R2.
The Netbackup software is setup and the client install package has been created.
I have installed the Netbackup client onto the client machine running Windows
2000.
I can run an initial
Hello,
Try renaming Netbackup.dll then re-run the installation.
Regards.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of dy018
Sent: Wednesday, August 27, 2008 6:09 AM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] NBU6.5 Win Client
Hi, do you mean renaming netbackup.dll to any other name before running the
install?
+--
|This was sent by [EMAIL PROTECTED] via Backup Central.
|Forward SPAM to [EMAIL PROTECTED]
Yes, such as Netbackup.org or Netbackuporg.dll. This if your error
message also contains text stating to close Netbackup processes and try
again.
I have also discovered it best to use the local admin account as my
personal account gives an error since my home folder mapped drive
changed to a
The netbackup.dll i think only existing after installation (correct me if i'm
wrong), i do not find any netbackup.dll file in the installation CD. Right now
i'm not able to install the netbackup client. After looking thru the
installation log, below are the last 2 line where it stop during
Hello everyone,
After I installed 6.5.2 I noticed all jobs 196'ing at midnight (even when
the next day was a runday). This is a known issue for people running
6.5.2 and 6.5.2a
My question is: is this a bug ? Or is this simply how it's going to be
from now on? (and thus you'll have to check
Thanks everybody for helping out here - I've managed to clear up enough space.
And Ed, that script is awesome - a special thank you for that!
A related question though - here's an edited dump showing the three types of
responses I got from running your script:
gandalf-backup_1219582879
On Wed, Aug 27, 2008 at 5:34 PM, Crowey
[EMAIL PROTECTED]wrote:
Thanks everybody for helping out here - I've managed to clear up enough
space.
And Ed, that script is awesome - a special thank you for that!
A related question though - here's an edited dump showing the three types
of
I am trying to perform a VCB backup using the vcbMounter command and the -m
nbd option as I do not have SAN (or iSCSI) connectivity between my proxy
server and my ESX host.
When I run the following command vcbMounter -h ip_addr_of_esx_host -u root-p
-a ippaddr:vcb-clt-1 -r
Hopefully we have to run NBCC in upgardation process from 6.0 to 6.5
Do you got any solution for it... if so please let me know
and the process of upgrade which you have fallowed, as we are also planning for
an upgrade and stuck in the middle.
Any reply is appriciated.
Thanks,
Harish Joseph.
25 matches
Mail list logo