Have you tried recycling the netbackup services.
In command prompt go to c:\program files\veritas\netbackup\bin\
bpdown -f -v
bpup -f -v
On Wed, Feb 23, 2011 at 8:28 AM, McDonald, James F. II <
james.f.mcdonald...@saic.com> wrote:
> We are running NBU 6.5 for Windows on Server 2003.
>
>
>
> Re
What Update pack is running?
What's changed in the environment? Anything recently updated like AV?
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Saran
Brar
Sent: Thursday, February 24, 2011 8:25 AM
We are looking at new disk storage from HP that are iSCSI. I have heard that
iSCSI is not a supported by NBU (current version 7.0)
The compatibility list does not directly say (Hard to understand), only NDMP
Direct copy "Not Implemented". Any insight from the
Collective would be helpful and yes r
I have restarted the services; I even rebooted the server just to be
safe. Our program SA said he hasn't pushed an update on the system for
a while now, so nothing has changed on the system that I know of. I
tried rebuilding one of the policies (suggested by Scott Jacobson) but I
still had the sa
One of our SA's was unable to log onto the server, so went back and saw
that the logs for the server had filled up a large chunk of HDD space.
I cleared them out and he was able to login. Does NBU have its own
location for log storage, or does something need to be done to NBU after
I cleared out t
Looks like EMM server down issue. did you check for free space on the
master/emm server and any logging enabled which is creating heavy logs and
eating up the space.
Subject: RE: [Veritas-bu] NBU 6.5 acting buggy
Date: Thu, 24 Feb 2011 08:27:49 -0500
From: james.f.mcdonald...@saic.com
To: sa
Hi,
Database error?
Is your NB_EMMSRV running?
Did you check the DB EMM logs?
=> /usr/openv/db/log
Justin.
On Thu, 24 Feb 2011, McDonald, James F. II wrote:
> I have restarted the services; I even rebooted the server just to be
> safe. Our program SA said he hasn't pushed an update on the sys
NDMP is typically (exclusively?) used for file systems. iSCSI is block.
You should back up the data via host agents.
On Feb 24, 2011 6:45 AM, "Jim Caldwell"
wrote:
> We are looking at new disk storage from HP that are iSCSI. I have heard
that iSCSI is not a supported by NBU (current version 7.0)
I would recommend opening a support case, especially when jobs are not starting
when they are suppose to.
Kevin
On Feb 24, 2011, at 2:25 AM, Saran Brar wrote:
> Have you tried recycling the netbackup services.
>
> In command prompt go to c:\program files\veritas\netbackup\bin\
>
> bpdown -
is it an D2D series array?
what's the use case? target for backup to disk (basic/advanceddisk), dedupe?
On Thu, Feb 24, 2011 at 2:44 PM, Jim Caldwell <
caldwe...@nccommunitycolleges.edu> wrote:
> We are looking at new disk storage from HP that are iSCSI. I have heard
> that iSCSI is not a suppor
Hi,
If you ran out of space it could of screwed up the EMM DB.
Check the logs for the EMM DB.
Justin.
On Thu, 24 Feb 2011, McDonald, James F. II wrote:
> One of our SA's was unable to log onto the server, so went back and saw
> that the logs for the server had filled up a large chunk of HDD spa
I have a customer using FT Media Server over 2Gbit HBA and we can see
125MB/sec per target port.
Check if SAN Client is able to read the data from fs.
On Wed, Feb 23, 2011 at 5:38 PM, Heathe Yeakley wrote:
> I picked up some Enterprise Client licenses to speed up the backups on
> some of my larg
Its in regards of Re: [Veritas-bu] NBU 6.5 acting buggy
I would check the nbpemreq -subsystem 23 screen
to see if scheduling was not disabled
I would double check the switches, cant remeber it by hard.
___
Veritas-bu maillist - Veritas-bu@mailman.
If you get low on space, EMM will shut down to save the database from
corruption. I believe the default is 1% free, but can't remember. There
will be a log entry in the emm log stating this was the case. This sounds
like what could have been happening here because you could access at least
the
Hello,
check this buffer parameters NUMBER_DATA_BUFFERS_FT and SIZE_DATA_BUFFERS
http://www.symantec.com/business/support/index?page=content&id=TECH1724
Hope it helps.
Boris
On Thu, Feb 24, 2011 at 9:40 AM, Bahadir Kiziltan <
bahadir.kizil...@gmail.com> wrote:
> I have a customer using FT Med
This is indeed a valid issue and one that we were unaware was affecting us
until this morning. The bpbkar logs on our clients are showing many many files
being incorrectly excluded from our OS backups because of the use of wild cards
in our exclude lists. Luckily, we have not run into any issu
NetBackup logs are in C:\Program Files\Veritas\NetBackup\Logs Directory.
Is your hard drive full where NetBackup is installed?
NOTE: I stated C: Drive, but it could depend where you installed
NetBackup
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:verita
Starting to wonder what is in the Windows Event Logs, and if the disk
space is a problem
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Kevin
Holtz
Sent: Thursday, February 24, 2011 2:09 PM
To: S
Well Geoff. What I do is run a SQL query on the DB everyday. This gets
me the list of all files used for DB/LOG/Archivelogs/TEMP tablespace
etc. Strip off the filenames, then sort/unique and update the
exclude_list with the results.
This way, I never have to worry about new FS, new DB datafiles
Hi,
We are using Netbackup since the version 3.1 -3.2 times.
We came from TSM which we used for several years.
I have had no real pain with NBU, perhaps because we have a relatively
standard environment.
Now because we were a Sun/Oracle customer or support was going to move
directly to Syman
20 matches
Mail list logo
