Hello John
The REQUIRED_INTERFACE option in bp.conf/registry might be what you are
after
A route through eth2 for contacting your backup server might be an option
Regards
Michael
2011/3/18 Crowey netbackup-fo...@backupcentral.com
Gidday, I'm trying to troubleshoot some really bad performance
Both NICs are on the same IP segment.
addr:172.20.10.23 Mask:255.255.255.0
addr:172.20.10.24 Mask:255.255.255.0
As far as the OS is concerned they are on the same dedicated segments with
equal weight (Metric:1) in the routing table and probably binding to eth0
first. Run bpclntcmd -self to see
Yeah, I was in the same boat, had just upgraded to 7.0.1 and then
realized 7.1 was available. Delving into the 7.0.1 docs related
to VMware backups using the vStorage API, if you're planning on
using a VM guest as a backup host using the hotadd feature for
access to the vmdk's, I'm pretty
Dear All,
Please advise.. Our some of the big size backup's taking 18 hours to
complete and these backups spans to 4-5 Tapes.
The issue is all the Backup (4-5) Tapes have different expiration time.
Assume my backup start at 01:00 am and it takes 18 hours to complete. I
have the backup retention
You can use the bpexpdate command to expire images (you want to expire
images rather than tapes - this frees up space on the tapes and if these
are the only images will expire the tape).
However, your question implies you are rather tight on tapes in the
first place and rather than manually
If the intent is to re-use the same set of tapes, you'd could either set
the retention period to something less than 3 weeks (e.g. 19 days) or
manually expire the images on the tapes prior starting the next backup.
The later could be done using a combination of the 'bpexpdate' and
'vmquery'
Actually ignore the vmquery ... portion below. Forgot this is has been
depricated in current releases and is handled by the bpexpdate utility.
-John
On 03/18/2011 01:29 PM, John Meyers wrote:
If the intent is to re-use the same set of tapes, you'd could either set
the retention period to
Does anyone have any experience (good or bad) with upgrading from
Windows Server 2003 to 2008 and NBU 6.5 to 7.0? Currently my backup
server is running the older versions of both. I have the software to
upgrade both of them. Is there a preferred sequence: upgrade NBU then
the OS or upgrade the
Dear All,
I am on Netbackup 7.0 and OS = Redhat 5.4
Need your help to have a look on this attached script and advise.
This script will send us a consolidated backup status Report after 18
hours.
Also I am able to send the Backup Status by Backup Policy Selection. i.e.
Team A will not know the
Hello Mates,
Below is the url :
___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Hello Mates,
Below is the url that states ,how to generate Hardware,OS and NB client
version in a text file.
http://www.symantec.com/business/support/index?page=contentid=TECH128723
I have tried but every time hardware output is always empty.
Also ,while running this ,i am getting
11 matches
Mail list logo
