Hi, I've seen this problem before.
I have a customer that newly installed a new SL3000 and Acsls 7.3
Not sure if it's a bug, but problem did resolve itself by restarting acsls
server.
I did check the
Q acs 0 online
Q lsm 0,0 offline
Q cap 0,0 online
Doing the var lsm 0,0 online did give me the
Hello All,
I've been backing up several SQL servers for quite some time now and
through re-creating a disaster recovery situation and reading through
SAP section of the NetBackup SQL Admin guide I notice the section for
backing up transaction logs.
After going through the SQL transaction log
Hi All
Currently looking into the SAN Client / Fibre Transport clients.
Wondered if anyone else has implemented this on 6.5 and any pros cons?
While readin the SS Guide - it seems to imply you need a Media Server,
but does not really explain if you can use a Master Server for this
(even though a
Title: NetBackup Fibre Transport Client Backups
Simon,
afaik, a SAN Client is a Media Server that can only backup its own data.
It needs the same infrastructure as a Media Server (hba, san, zonings
and etc ...)
The difference is the license price
If it works fine or not, I still dont
SAN Client means the client is the Media Server, but can only back itself up.
You need to have the SAN client be zoned to the tape library or disk location
you want to back up to. At the same time, if you are doing this to a tape
library, you need to have the shared storage option licensed for
On Mon, Oct 12, 2009 at 09:21:38AM +0100, Clooney, David wrote:
Darren
Have written the code already in perl if you want a copy? Runs daily, figures
out what vtl volumes have been returned to scratch in the last 24 hours and
labels accordingly.
Ah, interesting. Are you just parsing one
Anybody pulling, or have pulled, their hair out on this one?
Synthetic Backup Fails Code 671
*error=the database contains conflicting or erroneous entries(238)*
I found the following, but even though it seemed to match my issue, it was
of no use.
Hi Simon,
I have it configured and it works quite well, especially on the really big
clients. It works just with Sun Solaris or Linux NetBackup Media Servers,
you need to have a separate Qlogic card better with more then one port, and
to have zoning done properly on your fiber switches, on the
Simon, I think that some of the replies on the list are not quite correct.
We are implementing the SAN Client/FT Media Server for a production data
centre, and I've spent several months working on it in our test labs.
It's true that the documentation is slightly confusing, especially if you
Page 14 of the NB High Availability guide:
=
NetBackup does not support the conversion of an existing non-failover
NetBackup server to a failover NetBackup server. Contact Symantec
Enterprise Technical Support.
=
Huh?
Should be easy, I'd think. Why would I need Tech Support?
On Tue, Oct 13, 2009 at 2:32 PM, Donaldson, Mark mark.donald...@staples.com
wrote:
Page 14 of the NB High Availability guide:
=
NetBackup does not support the conversion of an existing non-failover
NetBackup server to a failover NetBackup server. Contact Symantec
Enterprise
Simon,
Here's a link to an archive of a post that Tanuja K. (most awesome SAN
client engineer ever!) gave about 4 months ago. I would also recommend
checking the 6.5.4 updates as well.
http://www.mail-archive.com/veritas-bu@mailman.eng.auburn.edu/msg22839.html
Rusty Major, MCSE, BCFP, VCS ▪
Mark's post about converting a standalone master to clustered prompted me to
post this.
Our current master server is standalone, physical, RHEL4, NBU 6.5.3.
Since Symantec will now support virtual master servers, we're planning to
convert it to a virtualised host running under VMware. The main
Hi,
Just want to know your if any one out there who are successfully running
netbackup clients in 5.1 version (including the Oracle, SAp SQL) agent
backups.
in 653 master/media environemnt
Because we tried to upgrade our environment
one Master server (solaris 9)
Two media server (solaris
The goal is to get off of the aging V880 and onto a cheaper Linux
platform. At the same time, we've had a couple high-profile hardware
failures in the past couple months and, since the hardware is cheap (and
the VCS license is free thanks to our site license), putting in a
cluster seems a way to
Massive data transfer through virtual HBA is reportedly difficult. Bare
metal might be better.
If this is a true Master Server, not a Media Server, I'm going to guess
there's no issues. If this, however, needs to access tape drives, you
might want to investigate the limitations of virtual
I would not advise using an agent to backup to a different version Media
server, especially one so far downrev as you have described.
Your problem sounds like you have something else going on in your
environment. A 54 means it cannot reach the client at all and it seems
strange that it worked
On Tue, Oct 13, 2009 at 4:03 PM, Dean dean.de...@gmail.com wrote:
Mark's post about converting a standalone master to clustered prompted me
to post this.
Our current master server is standalone, physical, RHEL4, NBU 6.5.3.
Since Symantec will now support virtual master servers, we're
Thanks guys.
Just to clarify, we have no intention of doing any backups to the master
server, either to disk or tape. All of the backups will be performed by
physical media servers.
Having said that, I haven't really thought about catalog backups yet.
Luckily I will have a chance to test this to
19 matches
Mail list logo
