Could you be a little more specific?
I tried using the explorer search engine for the word size and for
sz in all of the files in that folder and did not get a hit.
Bob Stump
Fidelity Information Services
ENT STORAGE MANAGEMENT - TAPE
Mobile (269)832-0293
I had a similar problem few years ago and it was driving me nuts.
It turned out one of our drives (16 total) was bad and damaged tapes.
Not all but some. Then these tapes would get mounted in other drives
which would go down. Absolutely random drives and random times.
I resolved it by
Guys i have just updated our Netbackup 5.0 environment to MP7. Master
server is Solaris9. All stuff was fine with upgrade but now some of the
windows clients dont seem to backup correctly.
They get a portion of the way through and then this message appears and
they grind to a halt until i cancel
I second that inquiry...it was my understanding there wasn't much you
could do to tune NDMP backups.
---Rich Dellaripa
-Original Message-
From: Rajmund Siwik [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 03, 2007 4:35 PM
To: Nick Majeran; veritas-bu@mailman.eng.auburn.edu
Subject: Re:
I guess that this is my 3rd post to this list in the same light, but I figure
maybe the 3rd times a charm, as I have not seen any responses to my previous
posts. I guess it is possible that no one is messing with this level of
authorization. From what I read, these methods are going away in
On Thu, 5 Jul 2007, Dave Markham wrote:
Guys i have just updated our Netbackup 5.0 environment to MP7. Master
server is Solaris9. All stuff was fine with upgrade but now some of the
windows clients dont seem to backup correctly.
They get a portion of the way through and then this message
Again, let me reiterate: I have not attempted to tune NDMP backups
from a NetApp filer to LTO-3 tape. All of my tests were conducted
from EMC Celerra NSX NAS devices.
However, one thing you should be able to tune, and which is quite
easy, is SIZE_DATA_BUFFERS_NDMP. By default, Netbackup uses a
EMC actually has a whole written guide to tuning the Celerra.
You can get it off of powerlink.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Nick
Majeran
Sent: Thursday, July 05, 2007 2:10 PM
To: Dellaripa, Rich
Cc: Rajmund Siwik;
I _BELIEVE_ that SIZE_DATA_BUFFERS_NDMP applies only to 3rd party NDMP
backups that are sent to a NetBackup server. If you're doing filer to
self or filer to filer backups (3rd party backups to another filer),
then I don't think that SIZE_DATA_BUFFERS_NDMP applies. When NetBackup
is telling a
I did some testing with SIZE_DATA_BUFFERS_NDMP using direct attached and
I think the setting is not used by my filer, but the buffers size you
set must match the buffer size in the filer configuration. So there is
a connection between this setting and the local filer buffer size. If
they don't
Yes, I've found the same; with direct NDMP, the SIZE_DATA_BUFFERS_NDMP
must match, however, three-way NDMP is less picky.
On 7/5/07, Adams, Dwayne [EMAIL PROTECTED] wrote:
I did some testing with SIZE_DATA_BUFFERS_NDMP using direct attached and
I think the setting is not used by my filer, but
Hi all,
Anyone knows Vaulting very well?
Currently, we are planning to do the following
LAN clients backup via VTL. One full backup every end of each week.
After all successful full backup, i'll be using vaulting to do duplication
without eject to keep in the tape library as to cover
First recommendation is to read the Vault Guides.
Second is to dig into the logfiles created by vault in that sid. You can
find some useful information there.
Lastly, make sure your max number of copies is set to the appropriate
number. Sounds to me like you need to have it set to at least 3.
I worked with Symantec some time ago with this very issue.
And the short answer is no, there is no other way other than manually
restoring the data than backing up up with netbackup.
--
Mike Sponsler
[EMAIL PROTECTED]
Northrop Grumman Information Technology
Netbackup 6.0 MP4, solaris 10 master server; Netbackup 6.0 MP4, solaris
8 san media servers
Roughly 55 media servers.
After I rebooted the netbackup daemons, I had the following issue:
Master server can ping and ssh to all media servers, but Master server
cannot communicate to media servers via
I think this also applies to other backup software (other than BEWS). Had
one client asking for the same thing, migrate their EDM (an old emc
backup) tapes to NetBackup. But if would be the case - restore then backup
again to NBU - it would really eat up a lot of resources.
They decided not
- Did all of your media server registerd on your /etc/hosts file at the
master server?
- did the master server name and ip address listed on /etc/hosts at all the
media server?
- on /usr/openv/netbackup/bp.conf, did all the media server registered
there, with the SERVER = media_server_name
- Did all of your media server registerd on your /etc/hosts file at the
master server?
yes. The environment had been working for several months. No recent
patch updates or changes (that I'm aware of). The master server lost
netbackup communication with the media servers upon restarting the
Yeap..
it's odd.. :)
well.. as far as I know, it's too risky if you have that much of media
server.
Because they alway communicate each other, and when even one media server
couldn't talk, the process will be hung.
Are you already check this:
- on /usr/openv/netbackup/bp.conf, did all the media
19 matches
Mail list logo
