Re: [Veritas-bu] Changing backup retention periods

[Spencer O'Donnell]

You will need to use bpexpdate with the recalculate switch to change
existing backups. You can do it by client name.

 

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Mark
Glazerman
Sent: Tuesday, April 27, 2010 11:18 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Changing backup retention periods

 

We've had a request to extend the retention period on backups from one
of our hosts so that data needed for some troubleshooting won't expire
before it can be used.

 

Currently the retention period for this data is 1 week.  If I change the
retention period in the policy that backed up this data to 2 weeks, will
this change be applied to both future and past backups handled by this
policy ?

 

Essentially I'm trying to work out if this change will be applied
retro-actively to existing backup images ?

 

Thanks,

 

Mark Glazerman

Enterprise Storage Administrator

Spartech Corporation

Desk: 314-889-8282

Fax: 314-854-8282

Cell: 618-520-3401

mark.glazer...@spartech.com  

http://www.spartech.com  

P please don't print this e-mail unless you really need to

This e-mail and any files transmitted with it are confidential, are
intended solely for the use of the addressee, and may be legally
privileged. If you have received this email in error please notify the
sender immediately, and do not copy or forward it.

 

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Netbackup Migration.

[Spencer O'Donnell]

One issue you will have is the image files are not compatible from
Windows to unix and vice versa. So you would have to do a cat_convert on
them all. At least that was a 5.1 issue and still lives today I believe.


 

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Ulises
Rodriguez
Sent: Wednesday, April 28, 2010 1:07 PM
To: 'veritas-bu@mailman.eng.auburn.edu'
Subject: [Veritas-bu] Netbackup Migration.

 

Hello All, 

 

I am looking to migrate my windows 2003 32 bit  netbackup master/media
server to Redhat  64 bit enterprise edition. 

 

What I am looking for is for advice what I need to watch out for as far
as the config/migration etc..etc.. 

 

My support contract with a local company suggested to use their
professional services for this migration.

 

Any advice will be appreciated. 

 

Thank you,

 

Ulises Rodriguez.

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Netbackup and robot change.

[Spencer O'Donnell]

You just needed to go to the existing VG and do a mass move to
standalone. Then inventory the new robot.

 

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Johan
Redelinghuys
Sent: Wednesday, May 12, 2010 8:37 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Netbackup and robot change.

 

Netbackup 6.5.4 on master server. Server connected to an I2K robot.
Robot went down and was replaced with a new one. All the tapes were
transferred over to the new robot. Drive and robot configuration deleted
on Netbackup master server and rescan was done. Robot and drives were
picked up. All in TLD control and all looked OK.

 

Ran robot inventory and "volume not unique in database" error was
encountered. Even pulling in the tapes via the cap still produces the
same error. Had to manually add each tape (128 tapes) one by one.
Selected move and changed standalone to robot. Selected the correct slot
and added the tape. Then right click tape and do a rescan and add .

 

What is the quickest way to get tapes back without going this manually?
The tapes were still protected so deleting them and then doing inventory
was not an option. What is the CLI options?

 

The issue seems to be that the volume group changed. 

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] LTO3 to LTO4 conversion

[Spencer O'Donnell]

You don't really need new pools just a lto4 scratch pool. NBU takes care
to match the correct tape media type with the right drive type i.e.
hcart1 for lto3 and dhcart2 for lto4

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate
Sanders
Sent: Wednesday, May 26, 2010 2:24 PM
To: Martin, Jonathan
Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU
Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion

Or create new LTO4 Pools that contain only LTO4 media, then when the
LTO3 expires back to their pools, these will no longer be used by the
Policies. Thus enforcing only LTO4 media is used. Yeah? All the
information I've been getting is making sense now.

Thanks everyone.


On 05/26/2010 01:07 PM, Martin, Jonathan wrote:
> Barcode rules are only used when injecting new media.  Your existing
> media will return to whatever pool they came from when they expire. If
> you don't want your old LTO3 media to be used anymore then change your
> media type for LTO4 to something different than what your LTO3 media
> use, and reconfigure your drives only to use that media type.
>
> I.e. - LTO3 media type hcart, LTO4 media type hcart1, drive type
hcart1.
>
> NetBackup won't put an "hcart" media an "hcart1" drive.
>
> -Jonathan
>
> -Original Message-
> From: veritas-bu-boun...@mailman.eng.auburn.edu
> [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate
> Sanders
> Sent: Wednesday, May 26, 2010 1:59 PM
> To: judy_hinchcli...@administaff.com
> Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU
> Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion
>
> That tiny bit of information just answered tons of questions. Thank
you!
>
> So now I know how to properly handle all new incoming LTO4 tapes. And
> ensure they wind up in the LTO4 scratch pool. In order to ensure LTO3s
> wind up in a "dead pool" for old tapes, do I simply enter "L3" as the
> barcode rule? And when are these rules actually processed? I know it's
> used when injecting new tapes, but what other situations does it apply
> these rules?
>
>
> On 05/26/2010 12:16 PM, judy_hinchcli...@administaff.com wrote:
>   
>> Bar code rules can be viewed
>> Go to the gui and act like you are going to inject tapes into your
>> 
> library
>   
>> Choose the radio button for update volume configuration
>> This will then un-gray the advanced options
>> Click that button and you will see a screen where you configure the
>> 
> barcode rules ( you should be able to find this in the volume manger
> manual)
>   
>>
>> Now the barcode rules are based on what it finds when it scans the
>> 
> barcodes on the tapes.
>   
>> If you lto3 tapes have a L3 in the barcode then you can make a rule
>> 
> telling it 
>   
>> L3's go to  
>>
>>
>>
>> Make your rules and put 1 l3 and 1 l4 in the map and inject the
tapes,
>> 
> then see if the tapes end up in the pools you want them to.
>   
>>
>>
>> -Original Message-
>> From: veritas-bu-boun...@mailman.eng.auburn.edu
>> 
> [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate
> Sanders
>   
>> Sent: Wednesday, May 26, 2010 11:12 AM
>> To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU
>> Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion
>>
>> Getting ready to load in the new LTO4 tapes, but I'm still having a
>> 
> hard
>   
>> time planning the right way to do it. I assume I can make a new LTO4
>> scratch pool that will store all my initial blank media. I disable
the
>> existing scratch pool and this will ensure that only new LTO4 tapes
>> 
> are
>   
>> rotated into my other pools. But how do I make sure the existing LTO3
>> tapes that expire are not put back into this new LTO4 scratch pool?
>> People keep mention barcode rules/labels but I've been unable to find
>> what this means or where to view/manage these. If I were to make new
>> duplicate LTO4 pools for my other volumes (production4, ndmp4,
>> 
> offsite4,
>   
>> etc) would this ensure none of the existing LTO3 tapes are reused?
>>
>> I've been digging through the Media Manager (5.1) Admin manual for a
>> better understanding of how NBU uses scratch/pools and expires tapes,
>> but nothing really seems to explain how it works, just how to manage
>> general tasks. If anyone can help answer my questions and also
provide
>> 
> a
>   
>> better place for me to focus studying on I'd appreciate it.
>>
>> Thanks.
>>
>>
>> On 05/03/2010 10:23 AM, Nate Sanders wrote:
>>   
>> 
>>> Forgive me for what may be a straight forward question, but our last
>>> backup admin has left and I'm doing my best to step up and keep our
>>> systems moving along. I'm looking for a general outline of an LTO3
to
>>> LTO4 conversion with Netbackup 5.1 (upgrading is on the list, but we
>>> can't wait to complete it). Right now we still have some LTO2 tapes,
>>>   
> and
>   
>>> I believe I must migrate and/or eject and store these in order to
>>> complete the conversion. Are there

Re: [Veritas-bu] Error bptm(pid=5620) write error on media

[Spencer O'Donnell]

Try turning on the /usr/openv/netbackup/logs/bptm log on the media
server that should give you some more detail

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of shetty
Sent: Monday, May 31, 2010 2:35 AM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] Error bptm(pid=5620) write error on media


Hi,

we have only one drive configured. and tapes are not getting freezed it
just gets failed directly 

Please find the error below.

5/31/2010 7:18:21 AM - connecting
5/31/2010 7:18:21 AM - connected; connect time: 00:00:00
5/31/2010 7:18:30 AM - mounted
5/31/2010 7:18:30 AM - positioning NE3026 to file 4
5/31/2010 7:18:32 AM - positioned NE3026; position time: 00:00:02
5/31/2010 7:18:32 AM - begin writing
5/31/2010 7:18:33 AM - Error bptm(pid=1564) write error on media id
NE3099, drive index 0, writing header block, 55
5/31/2010 7:18:41 AM - end writing; write time: 00:00:09
media write error(84)

Regards,
Suhas


-
Hi, 

It may have used a different drive, show tpclean -L output and check the

job details, did it use the same job? Are other tapes being frozen on 
that drive or just that one? 

Justin. 

On Thu, 6 May 2010, shetty wrote: 

Quote: 

Hi all, 

I'm Suhas, 

I'm getting the following error when my disk to tape backup is in
progress only for 1 storage 

Error bptm(pid=5620) write error on media id NE3026, drive index 0,
writing header block, 55 

But when i re- initiate the backup the same media will be picked on
which it had failed to start, and also gets completed successfully. 

Media: HP LTO3tape 
Veritas netbackup 6.5.5 

Can i get a help on this

+--
|This was sent by suha...@microland.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] VSP versus VSS

[Spencer O'Donnell]

May as well convert to VSS now. It is no longer there in 7.0. I swapped
all my 2003 and 2008 clients and things have never work3ed better, no
more status code 156 errors. There is a good vss enabler script on the
Symantec Forums. 

 

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Ed Wilts
Sent: Tuesday, June 01, 2010 11:49 AM
To: pranav batra
Cc: Veritas
Subject: Re: [Veritas-bu] VSP versus VSS

 

On Tue, Jun 1, 2010 at 10:12 AM, pranav batra
 wrote:

 

I have a small question on VSP/VSS.

 

As symantec recommends VSS for 2003 clients over VSP then why  it is the
defauly snap-shot provider option ?


It's historical and is no longer the default in NetBackup 7.0. 
 

Any specific reason for this recommendation as i can't find any
tech note specifying why VSS:

 

They all just explain that VSS is for 2003 and VSP for 2000.

I agree but why?


Windows 2000 did not have a snapshot service provided by the operating
system so Veritas had to write their own.  Microsoft added it in Windows
2003. 

VSS has a HUGE advantage for the backup administrator because snapshots
are now the responsibility of the server administrator, not the backup
administrator.  If snapshots fail, it's usually because the server
administrator doesn't have something configured correctly or the admins
have neglected to install patches to VSS (there are some but some
Windows admins seem to install ONLY security patches and ignore all
reliability/functionality fixes).
 

What happened two weeks ago:-There are our two cluster server
and both got hung while getting backed up.

We are still looking for the root cause but couldn't find
yet...The thing we suspect is that they were using VSP and when we
changed snapshot provider to VSS( As they are 2003) ,backups and server
both running fine from 2 weeks and didn't hung once.

 

Does VSP plays some part in making the server hung?

What could be the possible reasons?

Does VSP plays some part in making the CPU utilisation high?


VSP is evil.  Don't try and debug it - just quit using it. 


   .../Ed



Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE 
ewi...@ewilts.org

Linkedin  

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] VSP versus VSS

[Spencer O'Donnell]

This is the tool from the Symantec forums and I used it on my Solaris master 
and it worked fine.

 

http://www.symantec.com/connect/downloads/interactive-checkenable-vss-windows-hosts

 

 

 

From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Herbert.George
Sent: Thursday, June 03, 2010 1:22 PM
To: William Brown; Veritas
Subject: Re: [Veritas-bu] VSP versus VSS

 

If you have a windows machine handy, you could install the media server 
software on it to get the VSP disable tool.  You don't actually have to do 
backups with it.  Of course there are licensing considerations, but that should 
work.

 

Since I don't yet have a 6.5.6 installation, I can only guess that your silent 
install will still work as it has in the past.  But only actually trying it 
will tell.  Maybe someone with 6.5.6 can provide some experience

 

I agree with the previously expressed "VSP is evil!"

 

George Herbert

Basline Storage Engineer - Backup

 

SunTrust Banks, Inc.

From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of William Brown
Sent: Thursday, June 03, 2010 5:59 AM
To: Veritas
Subject: Re: [Veritas-bu] VSP versus VSS

 

I was reading that section of the 6.5.6 release notes and I just couldn't quite 
understand it.  It seems to say that as of 6.5.6 Symantec have caused VSP to be 
automatically installed.  Previously we have always disabled it - we do Windows 
installs using silentclient.cmd, and that has an entry you can edit to stop it 
installing VSP.  So it seems to read that as a new feature in 6.5.6 you cannot 
stop it installing VSP?

 

It then goes on to say that at NetBackup 7.0 VSP is not supported

 

Am I reading this right...6.5.6 will install VSP whether you like it or not, 
and so if you want to get back to the 'status quo' at e.g. 6.5.4 of not 
installing it, you must use this new VSP disable tool, or suddenly VSP is going 
to start running on all the 6.5.6 clients, in place of VSS?  There is a table 
on page 50/51 of the 6.5.6 document updates that shows the behaviour of Windows 
- it says "The following table describes the backup behavior based on the 
Windows Open

File Backup setting for the client and whether or not VSS is available on the 
client." - and in none of the cases is VSP run.  I'm guessing that they meant 
to say that the table applies *after the VSP disable tool is run* and that 
makes it really confusing.

 

Does anyone know what actually needs to be done after upgrading to 6.5.6 on 
Windows 2003, to make sure VSP is not going to run?

 

Also...the VSP Disable tool can be run "from a Windows master server or media 
server" - we don't use those, all our Master & Media are UNIX.  So what do we 
do?

 

William D L Brown

 

From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Herbert.George
Sent: 01 June 2010 21:18
To: Spencer O'Donnell; Ed Wilts; pranav batra
Cc: Veritas
Subject: Re: [Veritas-bu] VSP versus VSS

 

>From a recent case with Symantec support:

 

... in the NB_6.5.6 readme, might be something to consider.

===

NetBackup 6.5.6 automatically installs the Veritas volume snapshot Provider

(VSP) method for Open File Backups. VSP is the default Open File Backup method 
in this release.

NetBackup 6.5.6 includes the VSP disable tool (bpvspdisable.exe) for

administrators to use to disable VSP on clients if it is not needed. The tool 
deletes the VSP cache files from the disk of the client system. All future VSP 
requests on those clients are redirected to use Microsoft native Volume Shadow 
Copy Service (VSS).

The VSP method for Open File Backups is not supported in NetBackup 7.0. Having 
run the VSP disable tool does not affect upgrading to NetBackup 7.0.

The VSP disable tool can be used on the following operating systems:

■ Windows Server 2000

■ Windows Server 2003 with Service Pack 2 (x86 and IA64)

■ Windows XP 32-bit and 64-bit (x86 and IA64)



 

 

George Herbert

Basline Storage Engineer - Backup

 

SunTrust Banks, Inc.

From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Spencer 
O'Donnell
Sent: Tuesday, June 01, 2010 1:14 PM
To: Ed Wilts; pranav batra
Cc: Veritas
Subject: Re: [Veritas-bu] VSP versus VSS

 

May as well convert to VSS now. It is no longer there in 7.0. I swapped all my 
2003 and 2008 clients and things have never work3ed better, no more status code 
156 errors. There is a good vss enabler script on the Symantec Forums. 

 

From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Ed Wilts
Sent: Tuesday, June 01, 2010 11:49 AM
To: pranav batra
Cc: Veritas
Subject: Re: [Veritas-bu] VSP versus VSS

 

On Tue, Jun

Re: [Veritas-bu] FalconStor/NetApp w/OST

[Spencer O'Donnell]

What issues are you seeing with the Quantum in regards to restore?

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of mitch808
Sent: Monday, June 07, 2010 2:51 AM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] FalconStor/NetApp w/OST


There is no OST functionality with NetApp.  NetApp wants you to buy more
storage, and snap everything, to their storage.  There is no need for
backup to them.

As for Falconstor, I've yet to see any customer with it.  And I see a
lot of customers a week across many states.  

The customers that have Datadomain, love it.  Almost as fanatical as
NetApp users.  DataDomain's new DD Bost software is intriguing, but why?
were they suffering against other players, that they had to offload
processing?  

Quantum has one of the best implementations of OST, with their direct to
tape feature.  But I'm not sure if their restore issues have been solved
yet?

Exagrid as well has some positive remarks.  

I'm pretty sure, that you'll pay more by a lot for DataDomain, but will
it be worth it?

+--
|This was sent by mnab...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] NDMP Celera Backup Question

[Spencer O'Donnell]

Unfortunately you can exclude data but you cannot use wildcards. You can
exclude specific files or folders but that is the extent. For backup you
cannot use wildcards or specific file names just directories.

 

http://seer.entsupport.symantec.com/docs/235246.htm

 

From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Jimenez,
Daniel
Sent: Monday, June 21, 2010 2:11 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] NDMP Celera Backup Question

 

Hey guys

 

I have a tough question, I am attempting to create two NDMP policies
that will backup data from a Celera running 5.6. The first policy will
backup all data except for PST files. The second policy would only
backup PST files and exclude all other data but according to EMC, there
are no includes we can add to our backup policies. So we can create the
second policy that will exclude all data but there are no includes to
add PST files as the only files to backup. Any ideas? 

 

Daniel Jimenez

Data Protection Team

 

___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] Experience with Sun Fire x4540 as Media Server

[Spencer O'Donnell]

What you need to watch out for is what Symantec supports on the x86 Solaris. 
For instance no dedup support yet for 7.0. Data domain doesn't support OST on 
x86 for Solaris. They didn't support for a BMR master until 6.5.3 I believe. So 
just figure out what you need to run on the media server and double check the 
compatibility matrixes

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of WALLEBROEK Bart
Sent: Tuesday, July 06, 2010 3:32 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] Experience with Sun Fire x4540 as Media Server

Does anyone of you have any experience with a Sun Fire x4540 as a NetBackup 
Media Server ?

As we recently discovered that destaging on Windows Media Servers is somehow 
limited (speed) we tested this on a Solaris box and saw a huge difference.  
Therefore we want to try out this SUN Fire server as a Media Server.

Best Regards,
Bart WALLEBROEK
Backup Admin & Systems & Applications Management & Support Specialist 
Enterprise Applications Delivery - Infrastructure Management
S.W.I.F.T. SCRL
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] NBU 7 Opscenter

[Spencer O'Donnell]

You need to install an agent in order to get the collections working.
The agent can be installed on the master or on the Opscenter server. We
couldn't install on the master because the agent wasn't supported on our
master platform x86 Solaris. 

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of ansa
Sent: Thursday, July 08, 2010 5:23 AM
To: VERITAS-BU@mailman.eng.auburn.edu
Subject: [Veritas-bu] NBU 7 Opscenter


Hi

We trying to use Opscenter for reports, but its seams as if its a little
buggy.the polling agents stops working sometimes and we have never
had an "last successfull data load" anybody got some ideas ?.

+--
|This was sent by a...@sdu.dk via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--


___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Re: [Veritas-bu] OpsCenter

[Spencer O'Donnell]

The other problem I ran into was my master Solaris X86 doesn't have an
Opscenter agent so I needed to install the agent on the Opscenter bbox.

-Original Message-
From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate
Sanders
Sent: Wednesday, September 01, 2010 9:44 AM
To: judy_hinchcli...@administaff.com
Cc: Sanders, Nate; VERITAS-BU@MAILMAN.ENG.AUBURN.EDU
Subject: Re: [Veritas-bu] OpsCenter

A 6.5 Master works with 7.0 OpsCenter using an Agent. That's what I am
trying to find, along with information on how to change the default port
for the OpsCenter app.


On 08/31/2010 05:12 PM, judy_hinchcli...@administaff.com wrote:
> 6.5 is NOM  7.0 is Opscenter
>
> -Original Message-
> From: veritas-bu-boun...@mailman.eng.auburn.edu
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate
Sanders
> Sent: Tuesday, August 31, 2010 5:05 PM
> To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU
> Subject: Re: [Veritas-bu] OpsCenter
>
> Also does anyone know where to get the 6.5 Agent? Documentation says
> it's in OpsCenter/Agent but all I see is OpsCenter/Server from the
NB7.0
> install file (NB_7.0_LinuxR_x86_64_GA).
>
> On 08/31/2010 04:59 PM, Nate Sanders wrote:
>   
>> So OpsCenter defaults to port 80 assuming nobody in their right mind
>> would be running a webserer. How in the world do you change it to
some
>> other port without having access to the UI? I've been through the
Admin
>> guide and Google with no such luck. I'm all ready frustrated with the
>> fact it ignored my install path and decided to throw everything where
it
>> wanted to despite what I told it.
>>
>>   
>> 
>   

-- 
Nate SandersDigital Motorworks
System Administrator  (512) 692 - 1038




This message and any attachments are intended only for the use of the
addressee and may contain information that is privileged and
confidential. If the reader of the message is not the intended recipient
or an authorized representative of the intended recipient, you are
hereby notified that any dissemination of this communication is strictly
prohibited. If you have received this communication in error, please
notify us immediately by e-mail and delete the message and any
attachments from your system.
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu