Greetings Paul,
OK, I guess I mis-interpreted your question, apoligies.
My initial thoughts are that you could set up a different DNS name for
each interface on the media server.
Then create a different storage unit that refers to each Media server
name, and have that storage unit
refer to
On Thu, Feb 28, 2008 at 8:37 AM, Elena Khan [EMAIL PROTECTED] wrote:
I took Veritas NetBackup 6.5 for Solaris Administration in November.
Facility is in New York City on Madison Avenue (midtown)
I was very pleased with the training, esp. the instructor who was open to
lots of technical
Dear NetBackup community,
i have a question about the Fragment Size option in NetBackup 6.5
Windows Server 2003 environment.
Are there any good known values for? Actually I set for all storage
units (diskstaging and mediamanagers) a value of 2048 MB - is this a
good option or is this
Do you have file called /usr/opv/volmgr/misc/EJECT.txt ?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Monday, March 03, 2008 12:19 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] ACSLS and Netbackup Enterprise
We just incorporated a new STK 8500 in our Netbackup environment. We have
an AIX 5.3 master running Netbackup 6.0 MP4. After completing the nights
backups we use Vault Management with Netbackup to duplicate our data and
send tapes off-site. As part of the 8500 we just implemented an 7.2 ACSLS
We are planning the above mentioned upgrade. The catch is that we are
switching hardware and OS as well.
Currently running 3.4.1 on WinNT
New Backup server (which will have the same name) is Windows 2003 and will
have 6.5 loaded on it.
These are my proposed steps:
1 – Create a VM of WIN NT and
Hi List,
We are considering using the working.Dir parameter to have VMWare
place snapshots on a different LUN (on the SAN). We do not have space
available on our guests' LUNs for snapshots. We will also use the
sched.swap.dir parameter to keep the vswp files on the same LUN that
guests' vmdk
WOW
Now that's a big upgrade, hope you aren't planning to do this all in one
day. Plus what would worry me is that you are doing all those upgrades on
a VM without actually being able to verify if anything even works
Why not just upgrade current system to 4.5, setup the new hardware with
On Thu, Feb 28, 2008 at 10:27 AM, Sean Mohr [EMAIL PROTECTED] wrote:
It made for support to look at it and you really have to let them check it
out.
We went through the process and it took multiple passes and fixes of
problems in our catalog before we are ok to do the upgrade and the
On Mon, 3 Mar 2008, Mohre, Oliver wrote:
Dear NetBackup community,
i have a question about the Fragment Size option in NetBackup 6.5
Windows Server 2003 environment.
Are there any good known values for? Actually I set for all storage
units (diskstaging and mediamanagers) a value of
If you are using NTFS then you size must be less than about 50GB. NTFS
files larger than that would error in Netbackup on my original testing.
I'm currently using 10GB for my fragment sizes but I haven't done any
performance testing related to other fragment sizes.
-Jonathan
-Original
Must be less than 50 GiB for NTFS? Hm.. I came into an environment that
had no fragment size set and it (worked) albeit-- it took 2+ hours to
restore a single file at the end of the tape (using Linux/ext3) however.
Justin.
On Mon, 3 Mar 2008, Martin, Jonathan wrote:
If you are using NTFS
Be afraid. Be very afraid.
First, don't violate one of the sacred laws of upgrading: don't upgrade
more than one thing at a time. You can upgrade your hardware, your OS
your backup software. But for goodness sake, don't do them at the same
time
I agree with Jared. I really don't
The Default Fragment size was orginally 2048 Megabytes.
This was raised to 524,288 megabytes in 5.x or 6.x?? At least for disk. If
I remember right, it was raised to reduce disk fragmentation with Disk
Units.
jim
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
I no longer use a fragment size...it is set to 0. This was recommended
by veritas since all new tape drives can position to location within a
fragment (can't remember what that is called...). The fragment size is
a throw back to when tape drives could only position to a file marker.
I had to
Paul,
Each NIC on the media server should have a separate IP.
Assign each IP a name in dns
Ensure that the static routes are set up correctly between the media
server and the clients. This part is critical.
This means if you run a traceroute from teh media server to the client
it is sending the
Hello all,
Anyone is already using 6.0mp6, that was released last Feb, 27 ?
[]'s
Pedro Moranga
AVISO: A informação contida neste e-mail, bem como em qualquer de seus anexos,
é CONFIDENCIAL e destinada ao uso exclusivo do(s) destinatário(s) acima
referido(s), podendo conter informações
17 matches
Mail list logo
