Re: [Veritas-bu] LTO-2 LTO-3 mix

2007-04-26 Thread Bobby Williams
But if the bar code rule changes, how does NetBackup know that it is not a
new tape?
 
If you have 25 tapes sitting in offsite storage that NB read as ABC001-025,
you pull them back for a restore, NetBackup will not know anything about
them, assign them to scratch and you sit there wondering why the tapes don't
load.
 
Another scenario is that Quantum comes in and has to update the firmware on
a library and in the process has to remove all of the tapes to perform the
library calibration/verification (I have been through several of these).
All the tapes are put back into the robot (we know not all in the same
place).  How will NetBackup determine what is old, what is new, what is
borrowed, which admin is blue.
 
I have worked on this for over 6 months and have had a case opened/closed
with Veritas.  They concur with my dooms day scenario.
 
I have already had a similar thing happen on the install of a new library on
the same master that read 8 characters instead of 6 on the bar code label.
I caught it before tapes got overwritten.
 



Bobby Williams 
2205 Peterson Drive 
Chattanooga, Tennessee  37421 
423-296-8200 

 

  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of McCammont,
Anderson (IT)
Sent: Wednesday, April 25, 2007 11:30 PM
To: [EMAIL PROTECTED]; Martin, Jonathan (Contractor); Spearman, David;
veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] LTO-2 LTO-3 mix


No - changing the media id generation rule (MEDIA_ID_BARCODE_CHARS in
vm.conf) affects the media id.  Changing the barcode rules (potentially)
changes the media type and volume pool.  Existing tapes won't be reallocated
to a new pool on a barcode change - if they did then every inventory of the
library would break netbackup.  vmupdate(1M) only assigns attributes to new
media.
 
If we could put regexps into vmrule e.g.
 
(made up vmrule -listall -b)
barcode  mediavolume max mounts/
tag  type pool cleanings description

--
*CU$ HC2_CLN  None50 LTO Cleaning Tapes
CLN  DLT2_CLN None20 DLT Cleaning Tapes

*L4$ HCART4   Scratch  0 LTO4 media
*L3$ HCART3   Scratch  0 LTO3 media
*L2$ HCART2   Scratch  0 LTO2 media
NONE   DEFAULT  None 0 
DEFAULTDEFAULT  Scratch  0 --


then the world would be a better place.  A trivial code change I'd bet and a
feature request that's been outstanding for several years.

 
  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bobby
Williams
Sent: 25 April 2007 18:21
To: McCammont, Anderson (IT); 'Martin, Jonathan (Contractor)'; 'Spearman,
David'; veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] LTO-2 LTO-3 mix


You can't change the bar code rules like that in mid stream.  It would
change the media id of every tape already in the library and put every
existing tape in scratch.
 
You are going to either have to partition the drives in separate partitions
(Yuk), or just pick your default tape type and add all of the other types
manually (not a big deal).  Existing tapes don't use the bar code rules
anyway, they are already known.  It is only NEW to the robot tapes that need
to have a bar code rule.
 
I have 2 i2K's with both LTO-3 and LTO-2.  No big deal.  I have them in the
same partition.  I use the LTO-3's mostly for tape to tape duplication for
offsite (LTO-2 duplicated to LTO-3 works great).  Most of the clients can't
push data fast enough to feed the LTO-3 tapes.  (Yes, I do multiplex some
mid range x3 to feed tapes data).  I use Staging disks to catch the really
slow ones and do disk to tape staging to the LTO-3 tapes.  If you put the
LTO-3's in their own partition, you could not use any tape duplication
between partitions.
 
Another major headache that I have at a site with 2 separate libraries (both
ADIC 1k's) is when one runs out of media, everything fails with 96 errors
and then moves to the other physical library.  Not a big issue until failure
stats are looked at.
 




Bobby Williams 
2205 Peterson Drive 
Chattanooga, Tennessee  37421 
423-296-8200 

 


  _  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of McCammont,
Anderson (IT)
Sent: Tuesday, April 24, 2007 10:24 PM
To: Martin, Jonathan (Contractor); Spearman, David;
veritas-bu@mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] LTO-2 LTO-3 mix


If you do this you need to take part of your six digit barcode range and
dedicate it to the particular media type.  
 
It's sad that Netbackup doesn't support proper regexps in the barcode rules
so that the 'L2', 'L3' (presumably) 'L4' last two digits of the barcode can
be used to select the media type.  We've had a feature request in for years
for this and it's gone nowhere (unless 6.x does it and our rep 

Re: [Veritas-bu] LTO-2 LTO-3 mix [NC]

2007-04-26 Thread misha . pavlov
Bobby, but from what I understand:

 But if the bar code rule changes, how does NetBackup know that it is not 
a new tape?

By checking the media catalogs.

 If you have 25 tapes sitting in offsite storage that NB read as 
ABC001-025
 you pull them back for a restore, NetBackup will not know anything about 
them,
 assign them to scratch and you sit there wondering why the tapes don't 
load.

If you put them back in the robot for the restore, you have to make sure 
NBU knows about them.
If it does not - then you'd have to import them.
Also, NBU has rules on which tapes it can and which tapes it cannot 
overwrite ( ALLOW_MEDIA_OVERWRITE )


 Another scenario is that Quantum comes in and has to update the 
 firmware on a library and in the process has to remove all of the 
 tapes to perform the library calibration/verification (I have been 
 through several of these).  All the tapes are put back into the 
 robot (we know not all in the same place).
And it does not matter for NBU which slot has which tape - that's 
libraries business.

 How will NetBackup determine what is old, what is new, what is borrowed, 
which admin is blue.
Catalogs.

 I have worked on this for over 6 months and have had a case 
opened/closed with Veritas.
 They concur with my dooms day scenario.

They are there to solve the immediate issues mostly.
Scenarios are not welcome :-)


 I have already had a similar thing happen on the install of a new 
 library on the same master that read 8 characters instead of 6 on 
 the bar code label.  I caught it before tapes got overwritten.

I have no problems having 3 different media types in the 618 slots L700. 
All is peachy.


 Bobby Williams 
 2205 Peterson Drive 
 Chattanooga, Tennessee  37421 
 423-296-8200 
 
 
 From: [EMAIL PROTECTED] [mailto:veritas-bu-
 [EMAIL PROTECTED] On Behalf Of McCammont, Anderson (IT)
 Sent: Wednesday, April 25, 2007 11:30 PM
 To: [EMAIL PROTECTED]; Martin, Jonathan (Contractor); Spearman, 
 David; veritas-bu@mailman.eng.auburn.edu
 Subject: Re: [Veritas-bu] LTO-2 LTO-3 mix

 No - changing the media id generation rule (MEDIA_ID_BARCODE_CHARS 
 in vm.conf) affects the media id.  Changing the barcode rules 
 (potentially) changes the media type and volume pool.  Existing 
 tapes won't be reallocated to a new pool on a barcode change - if 
 they did then every inventory of the library would break netbackup. 
 vmupdate(1M) only assigns attributes to new media.
 
 If we could put regexps into vmrule e.g.
 
 (made up vmrule -listall -b)
 barcode  mediavolume max mounts/
 tag  type pool cleanings description
 
--
 *CU$ HC2_CLN  None50 LTO Cleaning Tapes
 CLN  DLT2_CLN None20 DLT Cleaning 
 Tapes 
 *L4$ HCART4   Scratch  0 LTO4 media
 *L3$ HCART3   Scratch  0 LTO3 media
 *L2$ HCART2   Scratch  0 LTO2 media
 NONE   DEFAULT  None 0 
 DEFAULTDEFAULT  Scratch  0 --  
 then the world would be a better place.  A trivial code change I'd 
 bet and a feature request that's been outstanding for several years.
 
 
 From: [EMAIL PROTECTED] [mailto:veritas-bu-
 [EMAIL PROTECTED] On Behalf Of Bobby Williams
 Sent: 25 April 2007 18:21
 To: McCammont, Anderson (IT); 'Martin, Jonathan (Contractor)'; 
 'Spearman, David'; veritas-bu@mailman.eng.auburn.edu
 Subject: Re: [Veritas-bu] LTO-2 LTO-3 mix

 You can't change the bar code rules like that in mid stream.  It 
 would change the media id of every tape already in the library and 
 put every existing tape in scratch.
 
 You are going to either have to partition the drives in separate 
 partitions (Yuk), or just pick your default tape type and add all of
 the other types manually (not a big deal).  Existing tapes don't use
 the bar code rules anyway, they are already known.  It is only NEW 
 to the robot tapes that need to have a bar code rule.
 
 I have 2 i2K's with both LTO-3 and LTO-2.  No big deal.  I have them
 in the same partition.  I use the LTO-3's mostly for tape to tape 
 duplication for offsite (LTO-2 duplicated to LTO-3 works great). 
 Most of the clients can't push data fast enough to feed the LTO-3 
 tapes.  (Yes, I do multiplex some mid range x3 to feed tapes data). 
 I use Staging disks to catch the really slow ones and do disk to 
 tape staging to the LTO-3 tapes.  If you put the LTO-3's in their 
 own partition, you could not use any tape duplication between 
partitions.
 
 Another major headache that I have at a site with 2 separate 
 libraries (both ADIC 1k's) is when one runs out of media, everything
 fails with 96 errors and then moves to the other physical library. 
 Not a big issue until failure stats are looked at.
 
 

 Bobby Williams 
 2205 Peterson Drive 
 Chattanooga, Tennessee  37421 
 

[Veritas-bu] Netbackup Catalog Checker

2007-04-26 Thread Barstow, Allan \(SN\)
 
I am trying to determine the current level of NBCC and how to
download it. There was a document 285909 at one time, but it appears to
have been removed. The current 6.0 upgrade manual still lists the use of
this program as a requirement.

Any help would be appreciated.

Allan Barstow
Spirit AeroSystems
[EMAIL PROTECTED]


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


Re: [Veritas-bu] Netbackup Catalog Checker [NC]

2007-04-26 Thread misha . pavlov
From my past experience it is better to open a call and works with 
Symantec on this.
I've done it already few times in he past.
Last time, back in Spetembet, it took me 1 month ( ! ) to clean catalogs.
In the NBCC output there may be many discrepancies listed and those guys 
have a trained eye and ( i think ) a parser to seed trhought it.

I am at 5.1 yet, so can't help you with the version. IN any case, the 
document for 5.1 is http://support.veritas.com/docs/267965
I am sure you are aware of the search on the support site - 
http://www.symantec.com/enterprise/support/search.jsp?
It sucks big time and almost impossible to find anything on it, but  ... 
as a last resort 





Barstow, Allan \(SN\) [EMAIL PROTECTED] 
Sent by: [EMAIL PROTECTED]
04/26/2007 09:36 AM


To
veritas-bu@mailman.eng.auburn.edu
cc

Subject
[Veritas-bu] Netbackup Catalog Checker






 
 I am trying to determine the current level of NBCC and 
how to
download it. There was a document 285909 at one time, but it appears to
have been removed. The current 6.0 upgrade manual still lists the use of
this program as a requirement.

 Any help would be appreciated.

Allan Barstow
Spirit AeroSystems
[EMAIL PROTECTED]


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


*
This message and any attachments (the message) are confidential and
intended solely for the addressees.
Any unauthorised use or dissemination is prohibited. 
E-mails are susceptible to alteration.   
Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates 
shall be liable for the message if altered, changed or falsified. 

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


[Veritas-bu] NDMP and SSO in NetBackup 6.0

2007-04-26 Thread Rongsheng Fang
Hi,

We have some Celerra NAS devices on the network (and SAN) and would like 
to  use NDMP to back up those devices. We have a tape library with six 
tape drives in the SAN. Is it possible to configure the Celerra NAS 
devices to mount the tape drives from the SAN with NetBackup SSO option? 
Or we have to mount the tape drive on one of the NetBackup media servers 
and do three-way or remote NDMP backup? I read through the NetBackup for 
NDMP SA's guide but still not clear on how SSO works with NDMP. Can 
somebody kindly explain to me how SSO works with NDMP?

Thanks much,

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


[Veritas-bu] Exchange 2003 Cluster - Backup Area Network

2007-04-26 Thread DLew97

Hi -

I am trying to backup my exchange 2003 cluster through my backup area
network.  I had created a ip address resource with a Backup Area Address for
the cluster.  The backup area network card has been configured as well.  I
have configured the Netbackup agent to reflect the changes and i am able to
ping from the master/media servers.  Am I missing something else? My backups
are failing with a status 69.

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


Re: [Veritas-bu] NDMP and SSO in NetBackup 6.0 [NC]

2007-04-26 Thread misha . pavlov
Rongsheng,


I can't give yo much details on NDMP SSO configuration option as this is 
new in 6.0 and I am still on 5.1
I do not think there is much difference though - when doing tpconfig to 
create a device on media server, you'd just add -share yes option.

For what it's worth, here are some generic NDMP ramblings I can share with 
you.

You'll need the NetBackup for NDMP option installed with the license and 
mostlikely the same on EMC sides.
If drives already zoned and Celera can see them - you practically all set 
 jsut few configuration commands to run :-)

Celera see the drive and start dumping to it when it's told to.
Media and master servers get the devices ( tpconfig ) and  STU configured 
( bpstu[list|add|rep|del] ) with drives connected to NDMP host ( 
ndmphost:nrst#a in my NetApp case ).

Master, media , robot control  ( could be all on the same machine ) 
servers will do the scheduling and the media management ( pick, mount, 
unmount, etc. ) NBU will give a goahead to Celera to do the SCSI 
Reserve/Release and to start dumping to the specified NDMP drive[s].


Would be nice if you could post the summary if you'll decide to go with 
this.


Regards




Rongsheng Fang [EMAIL PROTECTED] 
Sent by: [EMAIL PROTECTED]
04/26/2007 10:41 AM


To
veritas-bu@mailman.eng.auburn.edu
cc

Subject
[Veritas-bu] NDMP and SSO in NetBackup 6.0






Hi,

We have some Celerra NAS devices on the network (and SAN) and would like 
to  use NDMP to back up those devices. We have a tape library with six 
tape drives in the SAN. Is it possible to configure the Celerra NAS 
devices to mount the tape drives from the SAN with NetBackup SSO option? 
Or we have to mount the tape drive on one of the NetBackup media servers 
and do three-way or remote NDMP backup? I read through the NetBackup for 
NDMP SA's guide but still not clear on how SSO works with NDMP. Can 
somebody kindly explain to me how SSO works with NDMP?

Thanks much,

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


*
This message and any attachments (the message) are confidential and
intended solely for the addressees.
Any unauthorised use or dissemination is prohibited. 
E-mails are susceptible to alteration.   
Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates 
shall be liable for the message if altered, changed or falsified. 

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


Re: [Veritas-bu] NDMP and SSO in NetBackup 6.0

2007-04-26 Thread Spearman, David
Rongsheng,

We use nbu6mp4/sso/ndmp to back up celerra cifs servers. It is easier than with 
5.1 but works fine with one word of caution down below.

You need to zone the fibre so the celerra sees the drives. Setting up the 
library is specific to that box. Once all the fibre stuff is done you will need 
an sso licemse and a ndmp license. Once loaded you will go to media and device 
mgt/devices/ndmp hosts (this is the gui of course, (sorry all you died in the 
wool cmd line junkies) and add the name of the CIFS server you want to back up. 
After that use the Configure storage devices wizard to discover the paths via 
the ndmp option. This is way simplistic. It is well detailed in the 6.0 admin 
guides and those should be used. I followed them step by step and had no 
problems.

CAUTION: I have mentioned this about the Celerra before but will do so again. 
If you are running the 5.5 code on the Celerra when you do an interogation of 
the unit whether by gui or command line the process can get hung up. The 
Celerra instead of timing out will fail the datamover. If you don't pick up on 
the fact that the DM has failed and you run another interogation you might fail 
the 2nd datamover which makes for a lot of unhappy users. So when you do this 
have nasadmin up and stop what your doing if you get the first failure. EMC 
knows about this, we actually had their people on site, who promptly blew away 
our celerra database. They have not been back.

David Spearman
County of Henrico

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Rongsheng
Fang
Sent: Thursday, April 26, 2007 10:42 AM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] NDMP and SSO in NetBackup 6.0


Hi,

We have some Celerra NAS devices on the network (and SAN) and would like 
to  use NDMP to back up those devices. We have a tape library with six 
tape drives in the SAN. Is it possible to configure the Celerra NAS 
devices to mount the tape drives from the SAN with NetBackup SSO option? 
Or we have to mount the tape drive on one of the NetBackup media servers 
and do three-way or remote NDMP backup? I read through the NetBackup for 
NDMP SA's guide but still not clear on how SSO works with NDMP. Can 
somebody kindly explain to me how SSO works with NDMP?

Thanks much,

Rongsheng
___
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


[Veritas-bu] NDMP and SSO in NetBackup 6.0

2007-04-26 Thread Mike Heck
Rongsheng,

NDPM and SSO works very similar to normal SSO with NetBackup. 

What I would do is configure the Windows and UNIX hosts to share the
drives first, then configure access to the NDMP Host (Celerra NAS), then
finally modify the drives to include the NDMP path to the drives. 

You can then set up an NDMP storage Unit, and start backing up.

However I feel the need to advise you that not all versions of all
filers are compatible with SSO, this is mainly due the way reserve and
release are handled in some versions of some manufacturers Filer OS.
Please check the support.veritas.com web site, compatibility list for
NDMP to verify that your Filers OS is compatible.

Thank you,
Mike Heck

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


Re: [Veritas-bu] Exchange 2003 Cluster - Backup Area Network

2007-04-26 Thread Tom Burrell
Per Symantec's website:

http://support.veritas.com/docs/276349

Status 69 or Status 71:

* Confirm the directives are correct for the
version of Exchange. For Exchange 5.5, the directives
are Microsoft Exchange Server:\Information Store and
Microsoft Exchange Server:\Directory. For Exchange
2000/2003 server is Microsoft Information Store:\* or
Microsoft Information Store:\storage_group_name. 
Please note that for the files list Microsoft
Information Store:\* to work correctly, Allow multiple
data streams must be enabled.
* Confirm that the servers list correctly lists
the Exchange server name.  Do not use a NetBackup
name, the name of a backup interface, or a fully
qualified domain name.  If the server is listed in the
Exchange administrative console as Exchange_server_1,
confirm that is how it is listed in the policy.  If
the policy shows Exchange_server_1_backup or
Exchange_server_1.domain.com, the backups will fail.
* If the backup makes use of the directive
NEW_STREAM, be sure the Allow multiple data streams
option is selected.  


Tom


--- DLew97 [EMAIL PROTECTED] wrote:

 Hi -
 
 I am trying to backup my exchange 2003 cluster
 through my backup area
 network.  I had created a ip address resource with a
 Backup Area Address for
 the cluster.  The backup area network card has been
 configured as well.  I
 have configured the Netbackup agent to reflect the
 changes and i am able to
 ping from the master/media servers.  Am I missing
 something else? My backups
 are failing with a status 69.
 
 -- 
 DLew97
  ___
 Veritas-bu maillist  - 
 Veritas-bu@mailman.eng.auburn.edu

http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
 


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


Re: [Veritas-bu] NDMP and SSO in NetBackup 6.0

2007-04-26 Thread Mike Heck
If I understand you correctly, you want to share all 4 drives between
the Media servers and the NAS device. Allowing the NAS device to do
local backup and not use the network. If that is correct I am afraid it
is not possible with the Sun NAS device.

See the support.veritas.com web site for the current Veritas
NetBackup(tm)Network Data Management Protocol (NDMP) Compatibility List
(updated January 29, 2007) document number 251713. The Sun NAS device
is only supported for Direct attached, remote, and 3-way NDMP, not SSO. 

So with the Sun NAS device the only possible solution to use direct
attached tape drive would be to zone the SAN to have at least one tape
drive dedicated to the Sun NAS device. This would however limit you to 3
or less drives for the 2 media servers to use for non-NDMP backups.
Otherwise you could use remote NDMP, but that would require pulling all
the data over the network. 

To clarify the reason that some vendors are not supported, there are two
different ways of doing scsi reserve and release. If the vendor does not
support the hard reserve / release that NetBackup uses we cannot assure
the integrity of the data and thus cannot support SSO on that platform.

So far Only these vendors have been certified to support SSO:
EMC Celera in most of the 5.1 and higher DART OS Revisions
ONStore in EverON 1.2.3 and higher
IBM running Data ONTap 7.1.1 and higher 
DinoStor running OS 3.6.5
NetApp running 7.1.1 or higher 

Thank you,
Mike Heck
CFT


-Original Message-
From: Martin, Jonathan (Contractor) [mailto:[EMAIL PROTECTED] 
Sent: Thursday, April 26, 2007 2:08 PM
To: Mike Heck; veritas-bu@mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] NDMP and SSO in NetBackup 6.0

Ok... Just a point of clarification here...

I was under the assumption that if I had 4 fiber drives in library
shared with 2 media servers via SSO that I could also share one of those
drives with an NDMP NAS, namely a Sun StorEdge 5320.  Is this not the
case?

Just to clarify, when it comes NDMP backup time I want the Sun StorEdge
to allocate one of the SSO drives and write its data to it while sending
metadata to one of the media servers.  Is that not gonna happen?

-Jonathan



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mike
Heck
Sent: Thursday, April 26, 2007 1:56 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] NDMP and SSO in NetBackup 6.0

Rongsheng,

NDPM and SSO works very similar to normal SSO with NetBackup. 

What I would do is configure the Windows and UNIX hosts to share the
drives first, then configure access to the NDMP Host (Celerra NAS), then
finally modify the drives to include the NDMP path to the drives. 

You can then set up an NDMP storage Unit, and start backing up.

However I feel the need to advise you that not all versions of all
filers are compatible with SSO, this is mainly due the way reserve and
release are handled in some versions of some manufacturers Filer OS.
Please check the support.veritas.com web site, compatibility list for
NDMP to verify that your Filers OS is compatible.

Thank you,
Mike Heck

___
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 and SSO in NetBackup 6.0 [NC]

2007-04-26 Thread misha . pavlov
Why not ? 
STK loves NT ... I'm sure it is a Dell box with Enginio controllers ...
If you want to use shared ( SSO ) drives - confirm with STK/SUN if the 
NDMP version it runs supports SCSI Reserve/Release  and of course as was 
mentioned yearlier today, NetBackup have to be version 6.


Regards.

--
Misha Pavlov
Société Générale
desk: (212) 278-6096
cell: (646) 346-9341

This message uses only 100% recycled electrons.



Martin, Jonathan \(Contractor\) [EMAIL PROTECTED] 
Sent by: [EMAIL PROTECTED]
04/26/2007 03:07 PM


To
Mike Heck [EMAIL PROTECTED], veritas-bu@mailman.eng.auburn.edu
cc

Subject
Re: [Veritas-bu] NDMP and SSO in NetBackup 6.0






Ok... Just a point of clarification here...

I was under the assumption that if I had 4 fiber drives in library
shared with 2 media servers via SSO that I could also share one of those
drives with an NDMP NAS, namely a Sun StorEdge 5320.  Is this not the
case?

Just to clarify, when it comes NDMP backup time I want the Sun StorEdge
to allocate one of the SSO drives and write its data to it while sending
metadata to one of the media servers.  Is that not gonna happen?

-Jonathan



-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Mike
Heck
Sent: Thursday, April 26, 2007 1:56 PM
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] NDMP and SSO in NetBackup 6.0

Rongsheng,

NDPM and SSO works very similar to normal SSO with NetBackup. 

What I would do is configure the Windows and UNIX hosts to share the
drives first, then configure access to the NDMP Host (Celerra NAS), then
finally modify the drives to include the NDMP path to the drives. 

You can then set up an NDMP storage Unit, and start backing up.

However I feel the need to advise you that not all versions of all
filers are compatible with SSO, this is mainly due the way reserve and
release are handled in some versions of some manufacturers Filer OS.
Please check the support.veritas.com web site, compatibility list for
NDMP to verify that your Filers OS is compatible.

Thank you,
Mike Heck

___
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


*
This message and any attachments (the message) are confidential and
intended solely for the addressees.
Any unauthorised use or dissemination is prohibited. 
E-mails are susceptible to alteration.   
Neither SOCIETE GENERALE nor any of its subsidiaries or affiliates 
shall be liable for the message if altered, changed or falsified. 

*

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


[Veritas-bu] changing hostname of master server on 6.0

2007-04-26 Thread Jerry Rioux
I know on the support site it says not to do this without Symantec Support, but 
has anyone ever done it. If so, what are the steps involved, any documentation?
 
Thanks,
Jerry
___
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu