[Veritas-bu] Réf. : RE: [Veritas-bu] Files backuped twice
I would avoid this solution because for others filesystems include in this policy, using the cross mountpoint could cause the backup to be grow too much... Regards, Julien [EMAIL PROTECTED] exp.com Pour 09/05/2006 18:40 [EMAIL PROTECTED], veritas-bu@mailman.eng.auburn.edu cc Objet RE: [Veritas-bu] Files backuped twice Why not just backup /users select cross mountpoints. It'll handle both conditions. -M -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, May 09, 2006 9:49 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Files backuped twice Hi all, I use Netbackup V5,0 for a not a long time, and I have a very basic question : In an include list for Unix clients on the master server , I would like to have, for example : /users /users/login For some clients, /users/login is on the same filesystem than /users. So all the files under /users/login are backuped twice. Do you think it is possible to backup these files only once ( keyword, .. ) ? I tried using exclude/include list on the client, but no way... Thanks in advance Regards, Julien ___ 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 5.1 MP5
I second that :-) Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B32AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: Greenberg, Katherine A [mailto:[EMAIL PROTECTED] Sent: 09 May 2006 16:48 To: Conner, Mike; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] NBU 5.1 MP5 It should be installed everywhere. However, if you can only install it on the master, your environment will still function. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Conner, Mike Sent: Tuesday, May 09, 2006 11:06 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] NBU 5.1 MP5 I used NBU 5.1 and am currently at MP5. We have 1 master, 1 media and are a windows shop. I was looking at the read me and it seems the MP needs to only be installed on the master...is that correct? Just wanted to get a second opinion. Thanks Mike ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu - This e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately. Thank you. Aetna ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] NBU 5.1 MP5
Mike For consistency, I would recommend applying to all Master and Media Servers and clients where possible. It may be that MP5 adds some functionaility that a client or Media Server may lose out on. Don't believe it will NOT stop working as a result :-) for example, I use some old NBU 3.4 clients MP1 that get backed up to a 5.1 MP2 Master! Just means the client doesn't get any fancy features. Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B32AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: Conner, Mike [mailto:[EMAIL PROTECTED] Sent: 09 May 2006 16:06 To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] NBU 5.1 MP5 I used NBU 5.1 and am currently at MP5. We have 1 master, 1 media and are a windows shop. I was looking at the read me and it seems the MP needs to only be installed on the master...is that correct? Just wanted to get a second opinion. Thanks Mike ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] High throughput Redhat Media Server - real world experiences?
Hi there. Does anyone have any real worldexperience with using Redhat as a Media Server, with a quad port Gigabit NIC, using some kind of trunking on the NIC? I'm trying to design a Media Server that will be able to receive data quickly enough over IP to push a couple of fast tape drives, like LTO3. I'd like to be able to reliably get 200 MB/s or more from the network. I guess my questions are, isthis realistic? And, how is the trunking done? In the switch, or is Linux able to do it, like Solaris? Thanks in advance for any insight.
Re: [Veritas-bu] Solaris 10 client install
I've been looking at this and you have rather limited choices: 1. Install NBU while the server is still on Solaris 9; you can then upgrade to Solaris 10 and push updates in the normal way. 2. Push the install from the Master Server using either the 'trusted hosts' (r commands allowed) or FTP. If you are lucky enough to have a secured environment where neither FTP (due to clear text passwords) nor r commands are allowed, you have a problem. What I am having to do in this latter case is modify one of the Symantec supplied scripts to support SFTP. You cannot run the CD install script, it exits without doing anything. There are lots of caveats about what is supported on Solaris 10 about Zones, but I've not really fathomed out what it means, and we don't seem to be using zones yet. As you are running Windows I'm not sure if even the FTP option is open to you. Last option would be to install the client on a Solaris 9 server, make a tarball, copy it to your Solaris 10 system and unpack it. You will however have to make the changes to the inet configuration by hand. I checked with Symantec and unlike 4.5, where FP6 was a full install, there is no plan to do anything similar with 5.1. Rather unsatisfactory! William D L Brown Chris Freemantle [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 09-May-2006 17:18 To veritas-bu@mailman.eng.auburn.edu cc [EMAIL PROTECTED] Subject [Veritas-bu] Solaris 10 client install Can anyone point me to docs detailing how to install a Netbackup 5.1 solaris 10 client? I'm running Netbackup 5.1 mp3 under Windows. I've got the original install media for 5.1 Do I just install from the media then patch? thanks in advance -- --- REMEMBER - the safety of your data is your responsibility If it's important to you - ** MAKE A COPY ** or 2 or 3 or 4 or There is only one certainty about storage systems - they *will* fail ! Chris Freemantle Data Manager Wellcome Department of Imaging Neuroscience Tel. +44 (0)20 7833 7472 reception Tel. +44 (0)20 7833 7496 direct Fax +44 (0)20 7813 1420 Home Page: http://www.fil.ion.ucl.ac.uk ___ 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] Export and Import NetBackup configuration
Dave What do you do?? Recover to an alternative Server or recover to a different name? Is there a documented process? Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B32AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: Dave Markham [mailto:[EMAIL PROTECTED] Sent: 09 May 2006 11:00 To: WEAVER, Simon Cc: 'Kathy Falakfarsa'; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Export and Import NetBackup configuration It is exactly what i do for a DR process. Only caveat is need to have the hostname of the backup server to be the same as its embedded into the catalogue and with different host names i couldnt get the robot and certain things to work correctly. Cheers WEAVER, Simon wrote: */Hi/* */what I understand is, if you use have a Catalog Backup Tape, you can use BPRECOVER onto the new Server, providing the Server name is correct./* *//* */There is an unofficial method to recovering the data to a different server, but not sure if you want to go down this route, and I do not know if Symantec would like it!/* *//* */but I hear it is possible from their consultants/* /Regards/ /Simon Weaver *3rd Line Technical Support Windows Domain Administrator*/ /EADS Astrium Limited, B32AA IM (DCS)/ /Anchorage Road, Portsmouth, PO3 5PU/ /Email: //[EMAIL PROTECTED]/ mailto:[EMAIL PROTECTED] -Original Message- *From:* Kathy Falakfarsa [mailto:[EMAIL PROTECTED] *Sent:* 05 May 2006 19:49 *To:* veritas-bu@mailman.eng.auburn.edu *Subject:* [Veritas-bu] Export and Import NetBackup configuration Hello, Does anyone know, if I can Export the NetBackup configuration from an existing NetBackup server and Import it to a new server on another site? NetBackup: 5.0 with MP2 OS: Windows 2003 Ent. SP1 Thanks This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] NB 6 and VSP on Windows
Title: Message Well that wont help young Tim :-( And a bit bad that NBU wont do it even with open transaction agent enabled! Regards Simon Weaver3rd Line Technical SupportWindows Domain Administrator EADS Astrium Limited, B32AA IM (DCS)Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message-From: Steve Cashman [mailto:[EMAIL PROTECTED] Sent: 09 May 2006 21:14To: DeanCc: WEAVER, Simon; Wilkinson, Tim; veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] NB 6 and VSP on Windows In my exp neither VSP or VSS will allow you to backup open .pst files Steve On 5/9/06, Dean [EMAIL PROTECTED] wrote: VSS is using the Windows VSS service, which in turn can access other technology such as Veritas Volume Manager, or snapshot/mirror capabilities of your disk hardware, which would be the way to go if you're licensed for those goodies. I am about to implement FlashBackup to backup some huge Windows file servers using the NBU 6 advanced client. Currently the backups of those file servers are very slow (the old traversing the filesystem issue). We will use Flashbackup to do block level backups. Flashbackup uses Windows VSS to ensure a consistent disk image during the backup, which in turn will utilise either VxVM or storage array snapshot capabilities to achieve this. VSP is, by comparison, fairly dumb :PAlthough I'm talking purely from theory - haven't tested it yet.I can't talk about .pst files. You should probably investigate using the NBU agent for Exchange. Tim Wilkinson I.T. Support Officer Science Corporate Information Systems Defence Science Technology Organisation Department of Defence Tel: (02) 96921484 Fax: (02) 96921562 Email: [EMAIL PROTECTED] This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
[Veritas-bu] Slightly off subject
All Slightly off subject Generallywe are looking for a vendor toolkit that can. a) monitor a given server task I/O workload on a given 'real' storage subsystem environment/configuration. b) allow logical modelling changes within the tool to create an alternative (theoretical) storage subsystem environment. c) accurately predict/model the effect to the monitored task of a variety of assumed changes to the physical/logical storage subsystem environment. d) this 'effect' will ideally demonstrate any changes to individual Write-I/O's (in milliseconds) and any changes to the tasks overall elapsed time. Specifically... Tool must provide for monitoring/calibration of tasks on Solaris and Windows servers. Tool will understand (and be able to model) the runtime environments for all major storage subsystem suppliers (minimally EMC and HDS). Tool will understand (and be able to model) the runtime environments for all major SAN switch suppliers (minimally Cisco and Mcdata). Tool must be able to model the effect of.. - changing the tasks logical I/O blksize - activating EMC or HDS synchronous replication over any required distance up to 200 km (based upon DWDM fibre connectivity) - different simulated loads (simulated I/O path loading, simulated storage cache loading, etc) laid over the monitored workload. - all the major switch/storage configuration settings (logical and physical). - combinations of all the above. Any help would be appreciated Regards Mark Goodchild Branches Remediation J.P.Morgan Chase Phone: 01202347149 Mail: Mark A Goodchild/[EMAIL PROTECTED] E-Mail: [EMAIL PROTECTED]
Re: [Veritas-bu] High throughput Redhat Media Server - real world experiences?
Trunking as you refer to it is bonding and typical network speed is increased not 2x but 1.5x real world performance. Also, an LTO3 drive supposedly can do around 80MB/s, so unless you get one of the fastest PCI-X cards or PCI-E 8X/16X then you may max out the I/O of the board's interface. A better idea is more media servers with one or two drives on each one. On 5/10/06, Dean [EMAIL PROTECTED] wrote: Hi there. Does anyone have any real world experience with using Redhat as a Media Server, with a quad port Gigabit NIC, using some kind of trunking on the NIC? I'm trying to design a Media Server that will be able to receive data quickly enough over IP to push a couple of fast tape drives, like LTO3. I'd like to be able to reliably get 200 MB/s or more from the network. I guess my questions are, is this realistic? And, how is the trunking done? In the switch, or is Linux able to do it, like Solaris? Thanks in advance for any insight. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NetBackup Server
As long as you have the same hostname at the DR site and same equipment setup, you should just be able to do a bprecover and be on your way.On 5/9/06, Kathy Falakfarsa [EMAIL PROTECTED] wrote: I am trying to setup a NetBackup server in a new site, I was planning to create a standby server with a same name so I can use BPRecover to get the database in to this new server, but my manager doesn't like the idea of not using all the hardware on new site and leave it only for disaster recovery. His idea is to use that server as a second master server (on production) and if something goes wrong with one of the sites, use the other one as a disaster recovery server (i.e. restore tapes from one site to other). I don't know if this is possible or how complicated it is. I am looking for best practices for this situation. P.S. we will be using Mirror View to replicate the information to the new site. Thanks From: WEAVER, Simon [mailto:[EMAIL PROTECTED]] Sent: May 8, 2006 1:54 AM To: Kathy Falakfarsa; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] NetBackup Server Kathy Is this standby Server going to be implemented if your current one goes down or dies? Will you be using BPRecover to get the Database onto this server? Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B32AA IM (DCS) Anchorage Road , Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: Kathy Falakfarsa [mailto:[EMAIL PROTECTED]] Sent: 06 May 2006 00:06 To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] NetBackup Server I am trying to install a standby NetBackup server on a different site but on a same domain. I am looking for any documentation that suggests how to set this server up? Do I create a second master server? Your help is appreciated. This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
Re: [Veritas-bu] Export and Import NetBackup configuration
Use same name, install SW on secondary box with same setup, run bprecover, be on your way. On 5/10/06, WEAVER, Simon [EMAIL PROTECTED] wrote: Dave What do you do?? Recover to an alternative Server or recover to a different name? Is there a documented process? Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B32AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: Dave Markham [mailto:[EMAIL PROTECTED] Sent: 09 May 2006 11:00 To: WEAVER, Simon Cc: 'Kathy Falakfarsa'; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Export and Import NetBackup configuration It is exactly what i do for a DR process. Only caveat is need to have the hostname of the backup server to be the same as its embedded into the catalogue and with different host names i couldnt get the robot and certain things to work correctly. Cheers WEAVER, Simon wrote: */Hi/* */what I understand is, if you use have a Catalog Backup Tape, you can use BPRECOVER onto the new Server, providing the Server name is correct./* *//* */There is an unofficial method to recovering the data to a different server, but not sure if you want to go down this route, and I do not know if Symantec would like it!/* *//* */but I hear it is possible from their consultants/* /Regards/ /Simon Weaver *3rd Line Technical Support Windows Domain Administrator*/ /EADS Astrium Limited, B32AA IM (DCS)/ /Anchorage Road, Portsmouth, PO3 5PU/ /Email: //[EMAIL PROTECTED]/ mailto:[EMAIL PROTECTED] -Original Message- *From:* Kathy Falakfarsa [mailto:[EMAIL PROTECTED] *Sent:* 05 May 2006 19:49 *To:* veritas-bu@mailman.eng.auburn.edu *Subject:* [Veritas-bu] Export and Import NetBackup configuration Hello, Does anyone know, if I can Export the NetBackup configuration from an existing NetBackup server and Import it to a new server on another site? NetBackup: 5.0 with MP2 OS: Windows 2003 Ent. SP1 Thanks This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ 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] Solaris 10 client install
I did not have any issues installing the client from the CD and then patching to MP3 under Solaris 10, although it has been a while since I did that. On 5/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I've been looking at this and you have rather limited choices: 1. Install NBU while the server is still on Solaris 9; you can then upgrade to Solaris 10 and push updates in the normal way. 2. Push the install from the Master Server using either the 'trusted hosts' (r commands allowed) or FTP. If you are lucky enough to have a secured environment where neither FTP (due to clear text passwords) nor r commands are allowed, you have a problem. What I am having to do in this latter case is modify one of the Symantec supplied scripts to support SFTP. You cannot run the CD install script, it exits without doing anything. There are lots of caveats about what is supported on Solaris 10 about Zones, but I've not really fathomed out what it means, and we don't seem to be using zones yet. As you are running Windows I'm not sure if even the FTP option is open to you. Last option would be to install the client on a Solaris 9 server, make a tarball, copy it to your Solaris 10 system and unpack it. You will however have to make the changes to the inet configuration by hand. I checked with Symantec and unlike 4.5, where FP6 was a full install, there is no plan to do anything similar with 5.1. Rather unsatisfactory! William D L Brown Chris Freemantle [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 09-May-2006 17:18 To veritas-bu@mailman.eng.auburn.edu cc [EMAIL PROTECTED] Subject [Veritas-bu] Solaris 10 client install Can anyone point me to docs detailing how to install a Netbackup 5.1 solaris 10 client? I'm running Netbackup 5.1 mp3 under Windows. I've got the original install media for 5.1 Do I just install from the media then patch? thanks in advance -- --- REMEMBER - the safety of your data is your responsibility If it's important to you - ** MAKE A COPY ** or 2 or 3 or 4 or There is only one certainty about storage systems - they *will* fail ! Chris Freemantle Data Manager Wellcome Department of Imaging Neuroscience Tel. +44 (0)20 7833 7472 reception Tel. +44 (0)20 7833 7496 direct Fax +44 (0)20 7813 1420 Home Page: http://www.fil.ion.ucl.ac.uk ___ 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 maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Renaming NB 6.0MP2 servers
Not supported under 5.1x and when I opened a ticket concerning this they said there is no supported method, only if it is REALLY necessary you can call Veritas' consulting services and have them fix it. On 5/9/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'd like to rename a NB 6.0MP2 master server. In fact, i want to clone my master production server and rename it at our DR site. As far as i know this isn't really supported yet. Karl-Frédéric Rossing, Technical Services phone: 204-786-6431 fax: 204-784-6755 toll free: 1-800-665-1934 www.federated.ca CONFIDENTIALITY NOTICE The information in this email may be confidential and/or legally privileged. This email is intended to be reviewed by only the individual(s) or organization(s) named above. If you are not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any review, dissemination or copying of this email and its attachments, if any, or the information contained herein is prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email and its attachments from your system. Thank you.
[Veritas-bu] bpstart_notify
All I have inherited a windows 2003 netbackup 5.1 mp4 master server. I want to automate the robot inventory. I have a bpstart_notify.Windows2003_Backup.bat file in the netbackup bin folder. It runs quite happily, unfortunately it does not wait for the inventory to finish. Therefore all my backups fail error 96, but rerun quite happily. How do I make the .bat file wait for the inventory to complete. I have tried sleep n and start /wait but they both do nothing. Regards Mark Goodchild Branches Remediation J.P.Morgan Chase Phone: 01202347149 Mail: Mark A Goodchild/[EMAIL PROTECTED] E-Mail: [EMAIL PROTECTED]
RE: [Veritas-bu] bpstart_notify
I think you need to put it in
session_start_notify.bat instead.
Patrick Whelan
NetBackup Specialist
Architect Engineering
+44 20 7863 5243
Of all the things I've lost, I miss my mind the most! - Unknown
-Original
Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED]
Sent: 10 May 2006 13:30
To:
veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu]
bpstart_notify
All
I
have inherited a windows 2003 netbackup 5.1 mp4 master server.
I
want to automate the robot inventory.
I
have a bpstart_notify.Windows2003_Backup.bat file in the netbackup bin folder.
It
runs quite happily, unfortunately it does not wait for the inventory to finish.
Therefore
all my backups fail error 96, but rerun quite happily.
How
do I make the .bat file wait for the inventory to complete.
I
have tried sleep n and start /wait but they both do nothing.
Regards
Mark Goodchild
Branches Remediation J.P.Morgan Chase
Phone: 01202347149
Mail: Mark A Goodchild/[EMAIL PROTECTED]
E-Mail: [EMAIL PROTECTED]
*
The message is intended for the named addressee only and may not be disclosed to or used by anyone else, nor may it be copied in any way.
The contents of this message and its attachments are confidential and may also be subject to legal privilege. If you are not the named addressee and/or have received this message in error, please advise us by e-mailing [EMAIL PROTECTED] and delete the message and any attachments without retaining any copies.
Internet communications are not secure and COLT does not accept responsibility for this message, its contents nor responsibility for any viruses.
No contracts can be created or varied on behalf of COLT Telecommunications, its subsidiaries or affiliates ("COLT") and any other party by email Communications unless expressly agreed in writing with such other party.
Please note that incoming emails will be automatically scanned to eliminate potential viruses and unsolicited promotional emails. For more information refer to www.colt.net or contact us on +44(0)20 7390 3900.
RE: [Veritas-bu] Renaming NB 6.0MP2 servers
Title: Message It can be done - I just spoke to someone but told me its a drawn out process (not supported by Symantec) but it could work. Not too sure how much of a risk it is Regards Simon Weaver3rd Line Technical SupportWindows Domain Administrator EADS Astrium Limited, B32AA IM (DCS)Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message-From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: 10 May 2006 11:49To: [EMAIL PROTECTED]Cc: veritas-buSubject: Re: [Veritas-bu] Renaming NB 6.0MP2 serversNot supported under 5.1x and when I opened a ticket concerning this they said there is no supported method, only if it is REALLY necessary you can call Veritas' consulting services and have them fix it. On 5/9/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'd like to rename a NB 6.0MP2 master server. In fact, i want to clone my master production server and rename it at our DR site. As far as i know this isn't really supported yet. Karl-Frédéric Rossing, Technical Services phone: 204-786-6431 fax: 204-784-6755 toll free: 1-800-665-1934 www.federated.ca CONFIDENTIALITY NOTICE The information in this email may be confidential and/or legally privileged. This email is intended to be reviewed by only the individual(s) or organization(s) named above. If you are not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any review, dissemination or copying of this email and its attachments, if any, or the information contained herein is prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email and its attachments from your system. Thank you. This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
[Veritas-bu] NOM on Windows 2003 SP1
Title: NOM on Windows 2003 SP1 Hi All I am attempting to install NOM into a Windows environment with no success, I have managed to get it working on Solaris. Master Server = Windows 2003 SP1, NBU 6.0GA NOM Server = Windows 2003 SP1, NBU Client 6.0GA On the NOM server we installed Java 1.5.x that we downloaded from the internet, PBX and VxSS as per the installation guide. We then installed NOM, checked that all services are started, including the Veritas Web service. We start NOM and obtained a login screen choose English (or Default) for the Language, admin for the user, Vxadmin for the password and the Domain we left as the default which was [EMAIL PROTECTED] This is the error message: User authenticationfailed. The user name/password are invalid for the selected domain If we keep trying we eventually get a java dump: Exception Report The server excountered an internal error () that prevented it from fulfilling this request Further down: Root cause Failed to get credentials. hostname.domain. [vx. NOM_TRUSTED_CLIENTS hostname.domain] Any help or direction would be much appreciated. Regards Fiona Greenhough LECHABILE Storage Solutions (PTY) Ltd Unit 1, Cambridge Commercial Park Regent Street, Paulshof P O Box 784013, Sandton, 2146 Switchboard: +27 11 519 8100 Phone: +27 11 519 8124 Fax: +27 11 519 8147 Cell: +27 082 338 4754 Email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] This e-mail and attachments relating thereto, is intended for the above-mentioned recipient. If you have received this e-mail in error, kindly notify the sender and delete it immediately as it contains information relating to the official business of LECHABILE Storage Solutions (PTY) Ltd, which is confidential, legally privileged and proprietary to LECHABILE Storage Solutions (PTY) Ltd. LECHABILE Storage Solutions (PTY) Ltd does not own and endorse any other content. The views and opinions expressed in this e-mail are those of the sender unless clearly stated as being those of LECHABILE Storage Solutions (PTY) Ltd.
RE: [Veritas-bu] NetBackup Server
Title: Message Kathy I dont mind answering this. If the other server is the same name as your CURRENT MASTER Server, and you can configure a tape robotic library and use BPRECOVER then it will work. BPRecover does not rely on any hardware. from a DR point, I would say have a box on standby ready to talk to the Robot and use bprecover! Regards Simon Weaver3rd Line Technical SupportWindows Domain Administrator EADS Astrium Limited, B32AA IM (DCS)Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message-From: Kathy Falakfarsa [mailto:[EMAIL PROTECTED] Sent: 09 May 2006 23:07To: WEAVER, Simon; veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] NetBackup Server I am trying to setup a NetBackup server in a new site, I was planning to create a standby server with a same name so I can use BPRecover to get the database in to this new server, but my manager doesn't like the idea of not using all the hardware on new site and leave it only for disaster recovery. His idea is to use that server as a second master server (on production) and if something goes wrong with one of the sites, use the other one as a disaster recovery server (i.e. restore tapes from one site to other). I don't know if this is possible or how complicated it is. I am looking for best practices for this situation. P.S. we will be using Mirror View to replicate the information to the new site. Thanks From: WEAVER, Simon [mailto:[EMAIL PROTECTED] Sent: May 8, 2006 1:54 AMTo: Kathy Falakfarsa; veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] NetBackup Server KathyIs this standby Server going to be implemented if your current one goes down or dies? Will you be using BPRecover to get the Database onto this server? Regards Simon Weaver3rd Line Technical SupportWindows Domain Administrator EADS Astrium Limited, B32AA IM (DCS)Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message-From: Kathy Falakfarsa [mailto:[EMAIL PROTECTED] Sent: 06 May 2006 00:06To: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] NetBackup Server I am trying to install a standby NetBackup server on a different site but on a same domain. I am looking for any documentation that suggests how to set this server up? Do I create a second master server? Your help is appreciated. This email is for the intended addressee only.If you have received it in error then you must not use, retain, disseminate or otherwise deal with it.Please notify the sender by return email.The views of the author may not necessarily constitute the views of EADS Astrium Limited.Nothing in this email shall bind EADS Astrium Limited in any contract or obligation.EADS Astrium Limited, Registered in England and Wales No. 2449259Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
RE: [Veritas-bu] Export and Import NetBackup configuration
I know that!! But in response to another thread, is there a document that allows you to recover to an alternative name! I know its an unsupported method, but I belive there is a way around it But im not paying a consultant to do it :-) Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B32AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: 10 May 2006 11:56 To: WEAVER, Simon Cc: veritas-bu Subject: Re: [Veritas-bu] Export and Import NetBackup configuration Use same name, install SW on secondary box with same setup, run bprecover, be on your way. On 5/10/06, WEAVER, Simon [EMAIL PROTECTED] wrote: Dave What do you do?? Recover to an alternative Server or recover to a different name? Is there a documented process? Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B32AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: Dave Markham [mailto:[EMAIL PROTECTED] Sent: 09 May 2006 11:00 To: WEAVER, Simon Cc: 'Kathy Falakfarsa'; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Export and Import NetBackup configuration It is exactly what i do for a DR process. Only caveat is need to have the hostname of the backup server to be the same as its embedded into the catalogue and with different host names i couldnt get the robot and certain things to work correctly. Cheers WEAVER, Simon wrote: */Hi/* */what I understand is, if you use have a Catalog Backup Tape, you can use BPRECOVER onto the new Server, providing the Server name is correct./* *//* */There is an unofficial method to recovering the data to a different server, but not sure if you want to go down this route, and I do not know if Symantec would like it!/* *//* */but I hear it is possible from their consultants/* /Regards/ /Simon Weaver *3rd Line Technical Support Windows Domain Administrator*/ /EADS Astrium Limited, B32AA IM (DCS)/ /Anchorage Road, Portsmouth, PO3 5PU/ /Email: //[EMAIL PROTECTED]/ mailto:[EMAIL PROTECTED] -Original Message- *From:* Kathy Falakfarsa [mailto:[EMAIL PROTECTED] *Sent:* 05 May 2006 19:49 *To:* veritas-bu@mailman.eng.auburn.edu *Subject:* [Veritas-bu] Export and Import NetBackup configuration Hello, Does anyone know, if I can Export the NetBackup configuration from an existing NetBackup server and Import it to a new server on another site? NetBackup: 5.0 with MP2 OS: Windows 2003 Ent. SP1 Thanks This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] Export and Import NetBackup configuration
Will do Justin Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B32AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: 10 May 2006 15:00 To: WEAVER, Simon Cc: veritas-bu Subject: Re: [Veritas-bu] Export and Import NetBackup configuration Good luck, if you find one, let me know. On 5/10/06, WEAVER, Simon [EMAIL PROTECTED] wrote: I know that!! But in response to another thread, is there a document that allows you to recover to an alternative name! I know its an unsupported method, but I belive there is a way around it But im not paying a consultant to do it :-) Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B32AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: Justin Piszcz [mailto:[EMAIL PROTECTED] Sent: 10 May 2006 11:56 To: WEAVER, Simon Cc: veritas-bu Subject: Re: [Veritas-bu] Export and Import NetBackup configuration Use same name, install SW on secondary box with same setup, run bprecover, be on your way. On 5/10/06, WEAVER, Simon [EMAIL PROTECTED] wrote: Dave What do you do?? Recover to an alternative Server or recover to a different name? Is there a documented process? Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B32AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: Dave Markham [mailto:[EMAIL PROTECTED] Sent: 09 May 2006 11:00 To: WEAVER, Simon Cc: 'Kathy Falakfarsa'; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Export and Import NetBackup configuration It is exactly what i do for a DR process. Only caveat is need to have the hostname of the backup server to be the same as its embedded into the catalogue and with different host names i couldnt get the robot and certain things to work correctly. Cheers WEAVER, Simon wrote: */Hi/* */what I understand is, if you use have a Catalog Backup Tape, you can use BPRECOVER onto the new Server, providing the Server name is correct./* *//* */There is an unofficial method to recovering the data to a different server, but not sure if you want to go down this route, and I do not know if Symantec would like it!/* *//* */but I hear it is possible from their consultants/* /Regards/ /Simon Weaver *3rd Line Technical Support Windows Domain Administrator*/ /EADS Astrium Limited, B32AA IM (DCS)/ /Anchorage Road, Portsmouth, PO3 5PU/ /Email: //[EMAIL PROTECTED]/ mailto:[EMAIL PROTECTED] -Original Message- *From:* Kathy Falakfarsa [mailto:[EMAIL PROTECTED] *Sent:* 05 May 2006 19:49 *To:* veritas-bu@mailman.eng.auburn.edu *Subject:* [Veritas-bu] Export and Import NetBackup configuration Hello, Does anyone know, if I can Export the NetBackup configuration from an existing NetBackup server and Import it to a new server on another site? NetBackup: 5.0 with MP2 OS: Windows 2003 Ent. SP1 Thanks This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind
RE: [Veritas-bu] NOM on Windows 2003 SP1
I had initial problems installing NOM to my test NBU 6.0GA setup (before rolling to production). I had to open a case - best I recall is that the Windows installer didn't actually install all it was supposed to. I found my error the same way - couldn't authenticate. How many domains do you have listed when you look at Veritas Security Services? There should be 5, IIRC. Mine had 2 or 3 from the initial install. I had to talk with the Veritas Rep to manually create the remainder. Jason -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fiona Greenhough Sent: Wednesday, May 10, 2006 9:49 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] NOM on Windows 2003 SP1 Hi All I am attempting to install NOM into a Windows environment with no success, I have managed to get it working on Solaris. Master Server = Windows 2003 SP1, NBU 6.0GA NOM Server = Windows 2003 SP1, NBU Client 6.0GA On the NOM server we installed Java 1.5.x that we downloaded from the internet, PBX and VxSS as per the installation guide. We then installed NOM, checked that all services are started, including the Veritas Web service. We start NOM and obtained a login screen choose English (or Default) for the Language, admin for the user, Vxadmin for the password and the Domain we left as the default which was [EMAIL PROTECTED] This is the error message: User authenticationfailed. The user name/password are invalid for the selected domain If we keep trying we eventually get a java dump: Exception Report The server excountered an internal error () that prevented it from fulfilling this request Further down: Root cause Failed to get credentials. hostname.domain. [vx. NOM_TRUSTED_CLIENTS hostname.domain] Any help or direction would be much appreciated. Regards Fiona Greenhough LECHABILE Storage Solutions (PTY) Ltd Unit 1, Cambridge Commercial Park Regent Street, Paulshof P O Box 784013, Sandton, 2146 Switchboard: +27 11 519 8100 Phone: +27 11 519 8124 Fax: +27 11 519 8147 Cell: +27 082 338 4754 Email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] This e-mail and attachments relating thereto, is intended for the above-mentioned recipient. If you have received this e-mail in error, kindly notify the sender and delete it immediately as it contains information relating to the official business of LECHABILE Storage Solutions (PTY) Ltd, which is confidential, legally privileged and proprietary to LECHABILE Storage Solutions (PTY) Ltd. LECHABILE Storage Solutions (PTY) Ltd does not own and endorse any other content. The views and opinions expressed in this e-mail are those of the sender unless clearly stated as being those of LECHABILE Storage Solutions (PTY) Ltd. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] Export and Import NetBackup configuration
Am I misinterpreting the original post? According to the manual, using bprecover with the -dhost option is supposed to allow recovery of the database to an alternate host. This is a snippet from the command manual. bprecover -dhost destination_host Specifies the host to which the selected catalog is restored. Normally, catalogs are restored to the host where the data originated (as displayed with the -l option). The -d option makes it possible to restore the catalog to another host. Caution Use the dhost option with EXTREME caution, since it can overwrite existing catalogs on the destination host. To permit recovery in case you unintentionally overwrite the wrong catalogs, you can move existing catalogs to a temporary directory on the destination host. The following NetBackup client software must be installed on the destination host: /usr/openv/netbackup/bin/bpcd and /usr/openv/netbackup/bin/tar Note Do not specify -r all (or ALL) with -dhost when using this command. Either explicitly specify an image (for example, -r 2) or use the interactive mode (-r). Patrick Whelan NetBackup Specialist Architect Engineering +44 20 7863 5243 Of all the things I've lost, I miss my mind the most! - Unknown * The message is intended for the named addressee only and may not be disclosed to or used by anyone else, nor may it be copied in any way. The contents of this message and its attachments are confidential and may also be subject to legal privilege. If you are not the named addressee and/or have received this message in error, please advise us by e-mailing [EMAIL PROTECTED] and delete the message and any attachments without retaining any copies. Internet communications are not secure and COLT does not accept responsibility for this message, its contents nor responsibility for any viruses. No contracts can be created or varied on behalf of COLT Telecommunications, its subsidiaries or affiliates (COLT) and any other party by email Communications unless expressly agreed in writing with such other party. Please note that incoming emails will be automatically scanned to eliminate potential viruses and unsolicited promotional emails. For more information refer to www.colt.net or contact us on +44(0)20 7390 3900. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Symantec and Linux support
I regularly see postings from people looking to enhance their use of Linux as NetBackup servers. Although I am a *strong* Linux advocate and a Red Hat Certified Engineer, I would advise that you think long and hard about this decision. Symantec has not yet been able to demonstrate any willingness to support Red Hat Enterprise Linux as an enterprise platform. Fact: NetBackup 6.5, targeted for release in February, 2007, will drop support for RHEL 3. RHEL 3 started shipping in October, 2003 and will be supported by Red Hat through October, 2010. Symantec will cut you off with its current release nearly 4 years before Red Hat stops supporting the OS. On the other hand, Windows 2000, which was released 2 1/2 years earlier than RHEL 3, will still be supported by NetBackup 6.5. Additionally, mainstream support for Win2K server has already ended and full support will end from Microsoft *before* RHEL 3 support ends. This should show you where Symantec's priorities lie. Fact: Symantec Brightmail is not available for RHEL 4 so if you're deploying today, you have to deploy on RHEL 3. One Symantec enterprise product will soon be unable to back up another Symantec enterprise product. RHEL 4 has been out for over a year and still Symantec hasn't started supporting it. I just searched the support site for the system requirements in case my local office was wrong, and RHEL 4 still does not seem to be supported. Fact: NOM on Linux. Nope, it doesn't exist. Windows or Solaris only. Symantec doesn't seem to get it. I'm turning blue in the face trying to explain this to my local office. I know that there are Symantec folks on this list - feel free to pass this on. Symantec's actions do not go without notice. I've been asked by my management why we're not using Linux for NetBackup and I bluntly told them that Symantec can't be trusted to support the platform as it should be trusted. We recently replaced our master and one of our media servers and stuck with Solaris. We spent a lot more money but at least I know it will work. Enough rambling. If you have concerns about NetBackup and Linux support, contact your Symantec reps. .../Ed -- Ed Wilts, RHCE Mounds View, MN, USA mailto:[EMAIL PROTECTED] Member #1, Red Hat Community Ambassador Program ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] Export and Import NetBackup configuration
Thanks for the information. Could you please let me know what document you got that information from, so I can downloaded and review it. Thanks Kathy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Whelan, Patrick Sent: May 10, 2006 11:48 AM To: Ed Wilts; WEAVER, Simon Cc: Justin Piszcz; veritas-bu Subject: RE: [Veritas-bu] Export and Import NetBackup configuration Am I misinterpreting the original post? According to the manual, using bprecover with the -dhost option is supposed to allow recovery of the database to an alternate host. This is a snippet from the command manual. bprecover -dhost destination_host Specifies the host to which the selected catalog is restored. Normally, catalogs are restored to the host where the data originated (as displayed with the -l option). The -d option makes it possible to restore the catalog to another host. Caution Use the dhost option with EXTREME caution, since it can overwrite existing catalogs on the destination host. To permit recovery in case you unintentionally overwrite the wrong catalogs, you can move existing catalogs to a temporary directory on the destination host. The following NetBackup client software must be installed on the destination host: /usr/openv/netbackup/bin/bpcd and /usr/openv/netbackup/bin/tar Note Do not specify -r all (or ALL) with -dhost when using this command. Either explicitly specify an image (for example, -r 2) or use the interactive mode (-r). Patrick Whelan NetBackup Specialist Architect Engineering +44 20 7863 5243 Of all the things I've lost, I miss my mind the most! - Unknown * The message is intended for the named addressee only and may not be disclosed to or used by anyone else, nor may it be copied in any way. The contents of this message and its attachments are confidential and may also be subject to legal privilege. If you are not the named addressee and/or have received this message in error, please advise us by e-mailing [EMAIL PROTECTED] and delete the message and any attachments without retaining any copies. Internet communications are not secure and COLT does not accept responsibility for this message, its contents nor responsibility for any viruses. No contracts can be created or varied on behalf of COLT Telecommunications, its subsidiaries or affiliates (COLT) and any other party by email Communications unless expressly agreed in writing with such other party. Please note that incoming emails will be automatically scanned to eliminate potential viruses and unsolicited promotional emails. For more information refer to www.colt.net or contact us on +44(0)20 7390 3900. ___ 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] hanging bpbkar process
Just because they are the same box does not exclude the Network issues, if you are using an NFS mount it is probably over the network. It could be a problem with the NFS mount / share going away momentarily but its hard to tell from this. Can you post more of the Bpbrm log? o Does this only happen on the NFS backup? o Is this client able to perform other types of backups (Local drives, System_state)? o Is it possible to backup the slice on the local computer vs NFS mounting it to the NBU server? Steve From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Aaron MillsSent: Tuesday, May 09, 2006 4:59 PMTo: Steve Cashman; Justin PiszczCc: veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] hanging bpbkar process Well the server/client are the same box so network issues are out. I'm NFS mounting a slice to the NBU server and then backing up it up. After about 3 hours, the client process just stops logging. I've checked bpbrm, bptm, and bpbkar logs to no avail. Could an NFS hicup cause this to happen? bpbrm.log shows: 06:57:36.696 [13465] 2 bpbrm sighandler: signal 14 caught by bpbrm06:57:36.696 [13465] 2 bpbrm sighandler: bpbrm timeout after 10800 seconds06:57:36.696 [13465] 2 clear_held_signals: clearing signal mask stack, mask_stack_depth = 006:57:36.696 [13465] 2 bpbrm kill_child_process: start06:57:36.697 [13465] 2 bpbrm wait_for_child: start06:59:10.955 [13465] 2 bpbrm wait_for_child: child exit_status = 82 signal_status = 006:59:10.955 [13465] 2 inform_client_of_status: INF - Server status = 41 some three hours earlier, the last log from bpbkar looks like: ...snip... 03:58:24.319 [13472] 2 bpbkar process_file: INF - /path/to/some/file is sparse: stat.st_size = 12, stat.st_blocks * 512 = 003:58:24.320 [13472] 2 bpbkar process_file: INF - /path/to/some/file is now size 1203:58:24.320 [13472] 4 bpbkar PrintFile: /path/to/some/file 03:58:24.320 [13472] 2 bpbkar process_file: INF - /path/to/some/file is sparse: stat.st_size = 12, stat.st_blocks * 512 = 003:58:24.321 [13472] 2 bpbkar process_file: INF - /path/to/some/file is now size 1203:58:24.322 [13472] 4 bpbkar PrintFile: /path/to/some/file03:58:24.322 [13472] 2 bpbkar process_file: INF - /path/to/some/file is sparse: stat.st_size = 12, stat.st_blocks * 512 = 003:58:24.323 [13472] 2 bpbkar process_file: INF - /path/to/some/file is now size 12 (Is this "is sparse" message what I should be worried about?) then nothing 'till I killed the process some 27 hours later: 11:33:35.407 [13472] 16 bpbkar sighandler: ERR - bpbkar killed by signal 15 From: Steve Cashman [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 09, 2006 2:11 PMTo: Justin PiszczCc: Aaron Mills; veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] hanging bpbkar process Often times the Media / Master server encounters and error and exits but cant notify the Client (they don't even attempt to) It sounds like you have at least some logs enabled on the Media server since you mention that you reviewed the Bpbrm log. So review the Media Server logs to see if you can get more information. What I often have seen is a network disconnect between the Client and the Media Server. This stops the backup as far as Bpbrm is concerned but Bpbkar does not know about it, he just keeps churning through data until he is done. If this only happens on single client then it maybe something like a bad port, Nic, Driver ect. If it only happens on one Policy but other policies for that same client fail then you have a mystery on your hands. If you can post the relevant logs so we can browse them a bit (Bpbrm, Bpbkar, Bptm to start I would think) Steve Hope that helps On 5/9/06, Justin Piszcz [EMAIL PROTECTED] wrote: mkdir /usr/openv/netbackup/logs/bpbkar on the client, add VERBOSE = 5to the bp.conf and watch the logs, also you can make a lot of logging directories on the server as well and tail them when the problematicclient is backing up/etc.On 5/9/06, Aaron Mills [EMAIL PROTECTED] wrote: I had a backup timeout yesterday. bpbrm timed out after the configured interval (3 hours), but when I check to see what happened to the client process, bpbkar is still running (client/server on the same box) - it just hasn't done anything since three hours before the job timed out. The bpbkar log doesn't show anything useful. The process hums along and then just stops logging all of the sudden. This always seems to happen on the same job, though - never any others. Any ideas on where else I should look here? -Aaron Aaron Mills System Administrator Return Path, Inc. 303.642.4111 [EMAIL PROTECTED] http://www.returnpath.biz___Veritas-bu maillist-Veritas-bu@mailman.eng.auburn.eduhttp://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Symantec and Linux support
Ed, What about the other white meat. We have SLES 8 and 9 Linux boxes running as both Master and Media Servers. ;-) -sj Ed Wilts [EMAIL PROTECTED] 5/10/2006 10:17 AM I regularly see postings from people looking to enhance their use of Linux as NetBackup servers. Although I am a *strong* Linux advocate and a Red Hat Certified Engineer, I would advise that you think long and hard about this decision. Symantec has not yet been able to demonstrate any willingness to support Red Hat Enterprise Linux as an enterprise platform. Fact: NetBackup 6.5, targeted for release in February, 2007, will drop support for RHEL 3. RHEL 3 started shipping in October, 2003 and will be supported by Red Hat through October, 2010. Symantec will cut you off with its current release nearly 4 years before Red Hat stops supporting the OS. On the other hand, Windows 2000, which was released 2 1/2 years earlier than RHEL 3, will still be supported by NetBackup 6.5. Additionally, mainstream support for Win2K server has already ended and full support will end from Microsoft *before* RHEL 3 support ends. This should show you where Symantec's priorities lie. Fact: Symantec Brightmail is not available for RHEL 4 so if you're deploying today, you have to deploy on RHEL 3. One Symantec enterprise product will soon be unable to back up another Symantec enterprise product. RHEL 4 has been out for over a year and still Symantec hasn't started supporting it. I just searched the support site for the system requirements in case my local office was wrong, and RHEL 4 still does not seem to be supported. Fact: NOM on Linux. Nope, it doesn't exist. Windows or Solaris only. Symantec doesn't seem to get it. I'm turning blue in the face trying to explain this to my local office. I know that there are Symantec folks on this list - feel free to pass this on. Symantec's actions do not go without notice. I've been asked by my management why we're not using Linux for NetBackup and I bluntly told them that Symantec can't be trusted to support the platform as it should be trusted. We recently replaced our master and one of our media servers and stuck with Solaris. We spent a lot more money but at least I know it will work. Enough rambling. If you have concerns about NetBackup and Linux support, contact your Symantec reps. .../Ed -- Ed Wilts, RHCE Mounds View, MN, USA mailto:[EMAIL PROTECTED] Member #1, Red Hat Community Ambassador Program ___ 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] Symantec and Linux support
Oh wait, Scott? Who do you work for? :-P We are also going to be deploying NetBackup w/ SLES. Had a hiccup with the NBU 5 release we were running and wanting to use 64-bit architecture. Working back towards this as an option. RedHat got greedy and has a crappy licensing model and I think a lot of people are moving away from them as *the choice* for Enterprise Linux deployment (just what I've heard in mumbles and gripes). And if you look at the fact that SLES is supported on everything from 32-bit to 64-bit to Z-series mainframes (as a client, at least), I think they're being smart and spotting the direction of the industry away from RedHat. My gripe with Symantec as a WHOLE is a complete lack of interest/support/caring/notice for the fact that there are freaks out here deploying SLES on IBM Power platform. Symantec won't even consider this a *direction* of the industry, however, aside from Microsoft (**chuckle**) they are the ONLY Tier 1/Top 10 software manufacturer who isn't at least looking at this as viable... let alone that IBM and Oracle have most of their product stack ported to this platform... :-D Enjoy your day! Kate -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Jacobson Sent: Wednesday, May 10, 2006 12:44 PM To: Ed Wilts; List Veritas List Subject: Re: [Veritas-bu] Symantec and Linux support Ed, What about the other white meat. We have SLES 8 and 9 Linux boxes running as both Master and Media Servers. ;-) -sj Ed Wilts [EMAIL PROTECTED] 5/10/2006 10:17 AM I regularly see postings from people looking to enhance their use of Linux as NetBackup servers. Although I am a *strong* Linux advocate and a Red Hat Certified Engineer, I would advise that you think long and hard about this decision. Symantec has not yet been able to demonstrate any willingness to support Red Hat Enterprise Linux as an enterprise platform. Fact: NetBackup 6.5, targeted for release in February, 2007, will drop support for RHEL 3. RHEL 3 started shipping in October, 2003 and will be supported by Red Hat through October, 2010. Symantec will cut you off with its current release nearly 4 years before Red Hat stops supporting the OS. On the other hand, Windows 2000, which was released 2 1/2 years earlier than RHEL 3, will still be supported by NetBackup 6.5. Additionally, mainstream support for Win2K server has already ended and full support will end from Microsoft *before* RHEL 3 support ends. This should show you where Symantec's priorities lie. Fact: Symantec Brightmail is not available for RHEL 4 so if you're deploying today, you have to deploy on RHEL 3. One Symantec enterprise product will soon be unable to back up another Symantec enterprise product. RHEL 4 has been out for over a year and still Symantec hasn't started supporting it. I just searched the support site for the system requirements in case my local office was wrong, and RHEL 4 still does not seem to be supported. Fact: NOM on Linux. Nope, it doesn't exist. Windows or Solaris only. Symantec doesn't seem to get it. I'm turning blue in the face trying to explain this to my local office. I know that there are Symantec folks on this list - feel free to pass this on. Symantec's actions do not go without notice. I've been asked by my management why we're not using Linux for NetBackup and I bluntly told them that Symantec can't be trusted to support the platform as it should be trusted. We recently replaced our master and one of our media servers and stuck with Solaris. We spent a lot more money but at least I know it will work. Enough rambling. If you have concerns about NetBackup and Linux support, contact your Symantec reps. .../Ed -- Ed Wilts, RHCE Mounds View, MN, USA mailto:[EMAIL PROTECTED] Member #1, Red Hat Community Ambassador Program ___ 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 e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately. Thank you. Aetna ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] Symantec and Linux support
We are also interested in long term support for SLES on Zseries. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Jacobson Sent: Wednesday, May 10, 2006 11:44 AM To: Ed Wilts; List Veritas List Subject: Re: [Veritas-bu] Symantec and Linux support Ed, What about the other white meat. We have SLES 8 and 9 Linux boxes running as both Master and Media Servers. ;-) -sj Ed Wilts [EMAIL PROTECTED] 5/10/2006 10:17 AM I regularly see postings from people looking to enhance their use of Linux as NetBackup servers. Although I am a *strong* Linux advocate and a Red Hat Certified Engineer, I would advise that you think long and hard about this decision. Symantec has not yet been able to demonstrate any willingness to support Red Hat Enterprise Linux as an enterprise platform. Fact: NetBackup 6.5, targeted for release in February, 2007, will drop support for RHEL 3. RHEL 3 started shipping in October, 2003 and will be supported by Red Hat through October, 2010. Symantec will cut you off with its current release nearly 4 years before Red Hat stops supporting the OS. On the other hand, Windows 2000, which was released 2 1/2 years earlier than RHEL 3, will still be supported by NetBackup 6.5. Additionally, mainstream support for Win2K server has already ended and full support will end from Microsoft *before* RHEL 3 support ends. This should show you where Symantec's priorities lie. Fact: Symantec Brightmail is not available for RHEL 4 so if you're deploying today, you have to deploy on RHEL 3. One Symantec enterprise product will soon be unable to back up another Symantec enterprise product. RHEL 4 has been out for over a year and still Symantec hasn't started supporting it. I just searched the support site for the system requirements in case my local office was wrong, and RHEL 4 still does not seem to be supported. Fact: NOM on Linux. Nope, it doesn't exist. Windows or Solaris only. Symantec doesn't seem to get it. I'm turning blue in the face trying to explain this to my local office. I know that there are Symantec folks on this list - feel free to pass this on. Symantec's actions do not go without notice. I've been asked by my management why we're not using Linux for NetBackup and I bluntly told them that Symantec can't be trusted to support the platform as it should be trusted. We recently replaced our master and one of our media servers and stuck with Solaris. We spent a lot more money but at least I know it will work. Enough rambling. If you have concerns about NetBackup and Linux support, contact your Symantec reps. .../Ed -- Ed Wilts, RHCE Mounds View, MN, USA mailto:[EMAIL PROTECTED] Member #1, Red Hat Community Ambassador Program ___ 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 e-mail and any attachments may contain confidential information of Northwestern Mutual. If you are not the intended recipient of this message, be aware that any disclosure, copying, distribution or use of this e-mail and any attachments is prohibited. If you have received this e-mail in error, please notify Northwestern Mutual immediately by returning it to the sender and delete all copies from your system. Please be advised that communications received via the Northwestern Mutual Secure Message Center are secure. Communications that are not received via the Northwestern Mutual Secure Message Center may not be secure and could be observed by a third party. Thank you for your cooperation. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] Symantec and Linux support
Thanks for the info Ed. I will definitely be contacting my rep and engineer regarding this. I don't want to be stuck back too far in order to support RHEL3. We have more and more Linux server here, running various editions of RedHat, from RedHat 9, to RHEL2-4. RHEL4 currently has no BMR support- slated for 6.0MP4. We'll see. One of the reasons we went with NBU was cross-platform compatibility and functionality. It will be pathetic if we would have to abandon NBU because of support. Jason -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts Sent: Wednesday, May 10, 2006 12:18 PM To: List Veritas List Subject: [Veritas-bu] Symantec and Linux support I regularly see postings from people looking to enhance their use of Linux as NetBackup servers. Although I am a *strong* Linux advocate and a Red Hat Certified Engineer, I would advise that you think long and hard about this decision. Symantec has not yet been able to demonstrate any willingness to support Red Hat Enterprise Linux as an enterprise platform. Fact: NetBackup 6.5, targeted for release in February, 2007, will drop support for RHEL 3. RHEL 3 started shipping in October, 2003 and will be supported by Red Hat through October, 2010. Symantec will cut you off with its current release nearly 4 years before Red Hat stops supporting the OS. On the other hand, Windows 2000, which was released 2 1/2 years earlier than RHEL 3, will still be supported by NetBackup 6.5. Additionally, mainstream support for Win2K server has already ended and full support will end from Microsoft *before* RHEL 3 support ends. This should show you where Symantec's priorities lie. Fact: Symantec Brightmail is not available for RHEL 4 so if you're deploying today, you have to deploy on RHEL 3. One Symantec enterprise product will soon be unable to back up another Symantec enterprise product. RHEL 4 has been out for over a year and still Symantec hasn't started supporting it. I just searched the support site for the system requirements in case my local office was wrong, and RHEL 4 still does not seem to be supported. Fact: NOM on Linux. Nope, it doesn't exist. Windows or Solaris only. Symantec doesn't seem to get it. I'm turning blue in the face trying to explain this to my local office. I know that there are Symantec folks on this list - feel free to pass this on. Symantec's actions do not go without notice. I've been asked by my management why we're not using Linux for NetBackup and I bluntly told them that Symantec can't be trusted to support the platform as it should be trusted. We recently replaced our master and one of our media servers and stuck with Solaris. We spent a lot more money but at least I know it will work. Enough rambling. If you have concerns about NetBackup and Linux support, contact your Symantec reps. .../Ed -- Ed Wilts, RHCE Mounds View, MN, USA mailto:[EMAIL PROTECTED] Member #1, Red Hat Community Ambassador Program ___ 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] Symantec and Linux support
I don't honestly know of a single company these days that isn't looking at Linux for one reason or another... Unless you aren't. And then I'll know of one :) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dhotre, Shekhar Sent: Wednesday, May 10, 2006 1:23 PM To: Scott Jacobson; Ed Wilts; List Veritas List Subject: RE: [Veritas-bu] Symantec and Linux support I've been asked by my management why we're not using Linux for NetBackup Any particular reason -your management is interested in Linux ? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Jacobson Sent: Wednesday, May 10, 2006 12:44 PM To: Ed Wilts; List Veritas List Subject: Re: [Veritas-bu] Symantec and Linux support Ed, What about the other white meat. We have SLES 8 and 9 Linux boxes running as both Master and Media Servers. ;-) -sj Ed Wilts [EMAIL PROTECTED] 5/10/2006 10:17 AM I regularly see postings from people looking to enhance their use of Linux as NetBackup servers. Although I am a *strong* Linux advocate and a Red Hat Certified Engineer, I would advise that you think long and hard about this decision. Symantec has not yet been able to demonstrate any willingness to support Red Hat Enterprise Linux as an enterprise platform. Fact: NetBackup 6.5, targeted for release in February, 2007, will drop support for RHEL 3. RHEL 3 started shipping in October, 2003 and will be supported by Red Hat through October, 2010. Symantec will cut you off with its current release nearly 4 years before Red Hat stops supporting the OS. On the other hand, Windows 2000, which was released 2 1/2 years earlier than RHEL 3, will still be supported by NetBackup 6.5. Additionally, mainstream support for Win2K server has already ended and full support will end from Microsoft *before* RHEL 3 support ends. This should show you where Symantec's priorities lie. Fact: Symantec Brightmail is not available for RHEL 4 so if you're deploying today, you have to deploy on RHEL 3. One Symantec enterprise product will soon be unable to back up another Symantec enterprise product. RHEL 4 has been out for over a year and still Symantec hasn't started supporting it. I just searched the support site for the system requirements in case my local office was wrong, and RHEL 4 still does not seem to be supported. Fact: NOM on Linux. Nope, it doesn't exist. Windows or Solaris only. Symantec doesn't seem to get it. I'm turning blue in the face trying to explain this to my local office. I know that there are Symantec folks on this list - feel free to pass this on. Symantec's actions do not go without notice. I've been asked by my management why we're not using Linux for NetBackup and I bluntly told them that Symantec can't be trusted to support the platform as it should be trusted. We recently replaced our master and one of our media servers and stuck with Solaris. We spent a lot more money but at least I know it will work. Enough rambling. If you have concerns about NetBackup and Linux support, contact your Symantec reps. .../Ed -- Ed Wilts, RHCE Mounds View, MN, USA mailto:[EMAIL PROTECTED] Member #1, Red Hat Community Ambassador Program ___ 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 email (including any attachments) is confidential. If you are not the intended recipient you must not copy, use, disclose, distribute or rely on the information contained in it. If you have received this email in error, please notify the sender immediately by reply email and delete the email from your system. Confidentiality and legal privilege attached to this communication are not waived or lost by reason of mistaken delivery to you. Lend Lease does not guarantee that this email or the attachment(s) are unaffected by computer virus, corruption or other defects. Lend Lease may monitor incoming and outgoing emails for compliance with its Email Policy. Please note that our servers may not be located in your country. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu - This e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately. Thank you. Aetna ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Symantec and Linux support
Perceived lower TCO, percieved increased stability compared to Windows, less prone to viral infections as opposed to Windows, perceived increased ability to harden Linux versus, Windows, to name a few reasons why we've chosen to look at Linux. In some technology spaces it makes sense, in others, it doesn't. The key operative above is, "perceived". Dhotre, Shekhar wrote: I've been asked by my management why we're not using Linux for NetBackup Any particular reason -your management is interested in Linux ? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Scott Jacobson Sent: Wednesday, May 10, 2006 12:44 PM To: Ed Wilts; List Veritas List Subject: Re: [Veritas-bu] Symantec and Linux support Ed, What about the other "white meat". We have SLES 8 and 9 Linux boxes running as both Master and Media Servers. ;-) -sj Ed Wilts [EMAIL PROTECTED] 5/10/2006 10:17 AM I regularly see postings from people looking to enhance their use of Linux as NetBackup servers. Although I am a *strong* Linux advocate and a Red Hat Certified Engineer, I would advise that you think long and hard about this decision. Symantec has not yet been able to demonstrate any willingness to support Red Hat Enterprise Linux as an enterprise platform. Fact: NetBackup 6.5, targeted for release in February, 2007, will drop support for RHEL 3. RHEL 3 started shipping in October, 2003 and will be supported by Red Hat through October, 2010. Symantec will cut you off with its current release nearly 4 years before Red Hat stops supporting the OS. On the other hand, Windows 2000, which was released 2 1/2 years earlier than RHEL 3, will still be supported by NetBackup 6.5. Additionally, mainstream support for Win2K server has already ended and full support will end from Microsoft *before* RHEL 3 support ends. This should show you where Symantec's priorities lie. Fact: Symantec Brightmail is not available for RHEL 4 so if you're deploying today, you have to deploy on RHEL 3. One Symantec enterprise product will soon be unable to back up another Symantec enterprise product. RHEL 4 has been out for over a year and still Symantec hasn't started supporting it. I just searched the support site for the system requirements in case my local office was wrong, and RHEL 4 still does not seem to be supported. Fact: NOM on Linux. Nope, it doesn't exist. Windows or Solaris only. Symantec doesn't seem to get it. I'm turning blue in the face trying to explain this to my local office. I know that there are Symantec folks on this list - feel free to pass this on. Symantec's actions do not go without notice. I've been asked by my management why we're not using Linux for NetBackup and I bluntly told them that Symantec can't be trusted to support the platform as it should be trusted. We recently replaced our master and one of our media servers and stuck with Solaris. We spent a lot more money but at least I know it will work. Enough rambling. If you have concerns about NetBackup and Linux support, contact your Symantec reps. .../Ed -- Ed Wilts, RHCE Mounds View, MN, USA mailto:[EMAIL PROTECTED] Member #1, Red Hat Community Ambassador Program ___ 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 email (including any attachments) is confidential. If you are not the intended recipient you must not copy, use, disclose, distribute or rely on the information contained in it. If you have received this email in error, please notify the sender immediately by reply email and delete the email from your system. Confidentiality and legal privilege attached to this communication are not waived or lost by reason of mistaken delivery to you. Lend Lease does not guarantee that this email or the attachment(s) are unaffected by computer virus, corruption or other defects. Lend Lease may monitor incoming and outgoing emails for compliance with its Email Policy. Please note that our servers may not be located in your country." ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu -- === Steven L. Sesar Senior Operating Systems Programmer/Analyst UNIX Application Services R101 The MITRE Corporation 202 Burlington Road - KS101 Bedford, MA 01730 tel: (781) 271-7702 fax: (781) 271-2600 mobile: (617) 893-9635 email: [EMAIL PROTECTED] ===
[Veritas-bu] cannot read media header
Title: cannot read media header I have a SDLT tape that according to the netbackup catalog contains netbackup images, When ever I try to read the media's content I receive the error Error from master server. Cannot read media header , may not be Netbackup media or corrupt. I have worked with Veritas tech support, but they have offered no solution to recoverying the data on this tape. I suspect the media header is corrupt but the images are still on the tape. Any recommendation or soultions to recoverying the data off this tape will be appreciated. Vertias 5.1MP5 Tim Duncan
RE: [Veritas-bu] Symantec and Linux support
I'm with you. Linux for enterprise is a reality. RedHat and Suse are the two main commercial variants. We use RHEL here and they used it at Cisco when I worked there as well. Not supporting the two main commercial distros is showing a lack of recognizing reality. My company has no plans to move to SLES from RHEL anytime soon. If forced into choosing between changing our Linux distro or our backup solution I'm not sure which would win and would think Symantec wouldn't want to be tied to one or the other. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Greenberg, Katherine A Sent: Wednesday, May 10, 2006 1:28 PM To: Dhotre, Shekhar; List Veritas List Subject: RE: [Veritas-bu] Symantec and Linux support I don't honestly know of a single company these days that isn't looking at Linux for one reason or another... Unless you aren't. And then I'll know of one :) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dhotre, Shekhar Sent: Wednesday, May 10, 2006 1:23 PM To: Scott Jacobson; Ed Wilts; List Veritas List Subject: RE: [Veritas-bu] Symantec and Linux support I've been asked by my management why we're not using Linux for NetBackup Any particular reason -your management is interested in Linux ? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Jacobson Sent: Wednesday, May 10, 2006 12:44 PM To: Ed Wilts; List Veritas List Subject: Re: [Veritas-bu] Symantec and Linux support Ed, What about the other white meat. We have SLES 8 and 9 Linux boxes running as both Master and Media Servers. ;-) -sj Ed Wilts [EMAIL PROTECTED] 5/10/2006 10:17 AM I regularly see postings from people looking to enhance their use of Linux as NetBackup servers. Although I am a *strong* Linux advocate and a Red Hat Certified Engineer, I would advise that you think long and hard about this decision. Symantec has not yet been able to demonstrate any willingness to support Red Hat Enterprise Linux as an enterprise platform. Fact: NetBackup 6.5, targeted for release in February, 2007, will drop support for RHEL 3. RHEL 3 started shipping in October, 2003 and will be supported by Red Hat through October, 2010. Symantec will cut you off with its current release nearly 4 years before Red Hat stops supporting the OS. On the other hand, Windows 2000, which was released 2 1/2 years earlier than RHEL 3, will still be supported by NetBackup 6.5. Additionally, mainstream support for Win2K server has already ended and full support will end from Microsoft *before* RHEL 3 support ends. This should show you where Symantec's priorities lie. Fact: Symantec Brightmail is not available for RHEL 4 so if you're deploying today, you have to deploy on RHEL 3. One Symantec enterprise product will soon be unable to back up another Symantec enterprise product. RHEL 4 has been out for over a year and still Symantec hasn't started supporting it. I just searched the support site for the system requirements in case my local office was wrong, and RHEL 4 still does not seem to be supported. Fact: NOM on Linux. Nope, it doesn't exist. Windows or Solaris only. Symantec doesn't seem to get it. I'm turning blue in the face trying to explain this to my local office. I know that there are Symantec folks on this list - feel free to pass this on. Symantec's actions do not go without notice. I've been asked by my management why we're not using Linux for NetBackup and I bluntly told them that Symantec can't be trusted to support the platform as it should be trusted. We recently replaced our master and one of our media servers and stuck with Solaris. We spent a lot more money but at least I know it will work. Enough rambling. If you have concerns about NetBackup and Linux support, contact your Symantec reps. .../Ed -- Ed Wilts, RHCE Mounds View, MN, USA mailto:[EMAIL PROTECTED] Member #1, Red Hat Community Ambassador Program ___ 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 email (including any attachments) is confidential. If you are not the intended recipient you must not copy, use, disclose, distribute or rely on the information contained in it. If you have received this email in error, please notify the sender immediately by reply email and delete the email from your system. Confidentiality and legal privilege attached to this communication are not waived or lost by reason of mistaken delivery to you. Lend Lease does not guarantee that this email or the attachment(s) are unaffected by computer virus, corruption or other defects. Lend Lease may monitor incoming and
[Veritas-bu] Sg / sgen driver issue
I'm trying to set up Sun Fire-480R as a new backup server to replace an old one and in a situation where I'm stuck and thus want to ask here. I'm running Solaris 8 with all the latest Solaris patches including st driver patch, etc. latest SAN Foundation Kit 4.4.9. And I have a FC-attached HP MSL 5060 library with 2 LTO-1 drives via Brocade Silkworm switches. After installing NetBackup v5.1, I tried following the steps in MediaMgr_DeviceConfig_Guide.txt but no matter what I tried, I couldn't have it see both tape drives properly and I believe it's something to do with sg.conf, sg.links, devlink.tab files. However, I may be wrong. I tried all I could try with cfgadm, devfsadm, luxadm, zoning, etc. and know that I have all the proper connections and the box can see the library itself but not all the drives. Anyone experienced similar things and have any advice? Thank you in advance!!! - Young ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
FW: [Veritas-bu] File listing for Fragment
Andrew, Were these tapes made using ndmp or were they made using a mapped drive from a NetBackup enabled client? ndmp uses a dump file format like Solaris ufsdump. If your restoring from ndmp, once you put the NetBackup fragments back together, you will then have an Ontap compatible dump file, which you can use an Ontap restore command or Solaris ufsdump. I dont see getting around having to restore the entire dumpfile, which is a PITA for those of us use to the ease of single file restore with NetBackup, but is a reality when dealing with ndmp in combination with any 3rd party software. Why go to all this bother? Import all the tapes into NetBackup, then restore the entire qtree to an alternate location using NetBackup. Pick out the files you need and move them back where you need them. Thats really the best way to do it. You can create an alternate location to restore with inexpensive storage for less money than you can write the code to do it and youre still going to need to restore the entire dump file somewhere or write code to dynamically keep track of both the fragment structure and the dump file structure as you parse them in memory somewhere. It sounds like that should be a piece of software worth some $$$. If Im wrong here, someone please correct me. Mickey Baker Safe Data Services, LLC Independent Storage Consultant From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Andrew Wilkin Sent: Wednesday, May 10, 2006 1:12 AM To: [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] File listing for Fragment Ok then, I can identify that the file I'm looking for is 'x' blocks from the start of the backup image!, this is the 5th field in the *.f file. My value is 105001394 for the 5th field. How do I then go 'x' blocks from the start of the backup image on the tape? I've been using 'mt' and it uses 'files' to count, not 'blocks' as specified within the *.f file. Should I be using another utility? Thanks Regards Andrew Wilkin Computer Systems Analyst Department of Lands Panorama Ave BATHURST, NSW, 2795, AUSTRALIA Ph: 61 2 6332 8397 Fx: 61 2 6332 8457 E-mail: [EMAIL PROTECTED] WEB: www.lands.nsw.gov.au http://www.lands.nsw.gov.au From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, 10 May 2006 8:26 AM To: Andrew Wilkin Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] File listing for Fragment No offense, but seeking to a single fragment reading files is netbackup's job. The TOC you describe (associating fragment to file) is the quick definition of Netbackup's image catalog. You're starting to write the application you've already bought. To answer your question, I think you're going to have to mine the catalog directly for the info you're looking for. Look under the /usr/openv/netbackup/db/images/client/timestamp/imagename.f files for the file to frag info. If you're using the binary catalog, you'll have to convert them. -M From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Cashman Sent: Tuesday, May 09, 2006 2:53 PM To: Andrew Wilkin Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] File listing for Fragment Try bpimagelist -backupid (backup_id) Steve On 5/5/06, Andrew Wilkin [EMAIL PROTECTED] wrote: Hi All, I'm after a away to extract the files that are contained within an individual BackupId that has multiple Fragments (File number on a Tape). If I have a single backup image and it spans many Fragments / File Numbers, on the media, is there a way to extract a listing's of those files from a single Fragment/File Number using a single backup id, though the are multiple Fragments for that single backup? (sorry but I've repeated myself here!) I know I can get a complete listing of a specific backup using bpmedialist and give the backup id etc. But using the Images on Media control( from the GUI), I can see the multiple Fragments on the Tape with the File Numbers, so there must be a way somehow to relate this back into the NetBackup DataBase to use it! This has come about from an historic NDMP system I've had to recover from and for the particular directory, they are 27 Fragments, and I know how to extract the NDMP backup using a SUN system, but I didn't know which file on the tape to skip to. I have managed to extract the data. But I'm hoping I can get a better solution to what I've done, by creating a TOC for each of the Fragments and grep-ping for my data to extract! Thanks Regards Andrew Wilkin Computer Systems Analyst Department of Lands Panorama Ave BATHURST, NSW, 2795, AUSTRALIA Ph: 61 2 6332 8397 Fx: 61 2 6332 8457 E-mail: [EMAIL PROTECTED] WEB: www.lands.nsw.gov.au http://www.lands.nsw.gov.au *** This message is intended for the addressee named
Re: [Veritas-bu] Sg / sgen driver issue
Song, Young wrote: I'm trying to set up Sun Fire-480R as a new backup server to replace an old one and in a situation where I'm stuck and thus want to ask here. I'm running Solaris 8 with all the latest Solaris patches including st driver patch, etc. latest SAN Foundation Kit 4.4.9. And I have a FC-attached HP MSL 5060 library with 2 LTO-1 drives via Brocade Silkworm switches. After installing NetBackup v5.1, I tried following the steps in MediaMgr_DeviceConfig_Guide.txt but no matter what I tried, I couldn't have it see both tape drives properly and I believe it's something to do with sg.conf, sg.links, devlink.tab files. However, I may be wrong. I tried all I could try with cfgadm, devfsadm, luxadm, zoning, etc. and know that I have all the proper connections and the box can see the library itself but not all the drives. Anyone experienced similar things and have any advice? Thank you in advance!!! - Young ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu Young, If your /kernel/drv/st.conf and sg.conf aren't correct all the commands *adm commands won't do a thing. I'd start with the st.conf. And there is probably a .conf file for whatever kind of hba you're using on the 480. Gregg ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] BMR Boot Error
I'm still working at testing BMR. Having loads of fun ;-) Today's task: take a BMR image of a Win2K server and restore it to new hardware, all Dell boxes. Original is not RAID, BMR restore to RAID. Build a generic boot floppy with appropriate drivers, recent downloads from Dell's site. Booted the client and received an error something like this: This program cannot be run in DOS mode. Neither google nor veritas/symantec seem to know about this any later than NBU 4.5. Anyone else seen this? Suggestions for a fix? Or, just punt and open another case? Thanks, Jason Jason Brooks Computer Systems Engineer IITS - Longwood University voice - (434) 395-2916 fax - (434) 395-2035 mailto:[EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Symantec and Linux support
On Wed, May 10, 2006 at 10:44:19AM -0600, Scott Jacobson wrote: Ed, What about the other white meat. We have SLES 8 and 9 Linux boxes running as both Master and Media Servers. Symantec doesn't support Brightmail on any Linux distribution other than RHEL 3 AS and RHEL 3 ES. That should tell you something about their Linux commitment too - after all, I'd put SLES in the same category as RHEL for enterprise-quality (even though I've never worked with SLES). I've not looked at NetBackup support on SLES at all. .../Ed ;-) -sj Ed Wilts [EMAIL PROTECTED] 5/10/2006 10:17 AM I regularly see postings from people looking to enhance their use of Linux as NetBackup servers. Although I am a *strong* Linux advocate and a Red Hat Certified Engineer, I would advise that you think long and hard about this decision. Symantec has not yet been able to demonstrate any willingness to support Red Hat Enterprise Linux as an enterprise platform. Fact: NetBackup 6.5, targeted for release in February, 2007, will drop support for RHEL 3. RHEL 3 started shipping in October, 2003 and will be supported by Red Hat through October, 2010. Symantec will cut you off with its current release nearly 4 years before Red Hat stops supporting the OS. On the other hand, Windows 2000, which was released 2 1/2 years earlier than RHEL 3, will still be supported by NetBackup 6.5. Additionally, mainstream support for Win2K server has already ended and full support will end from Microsoft *before* RHEL 3 support ends. This should show you where Symantec's priorities lie. Fact: Symantec Brightmail is not available for RHEL 4 so if you're deploying today, you have to deploy on RHEL 3. One Symantec enterprise product will soon be unable to back up another Symantec enterprise product. RHEL 4 has been out for over a year and still Symantec hasn't started supporting it. I just searched the support site for the system requirements in case my local office was wrong, and RHEL 4 still does not seem to be supported. Fact: NOM on Linux. Nope, it doesn't exist. Windows or Solaris only. Symantec doesn't seem to get it. I'm turning blue in the face trying to explain this to my local office. I know that there are Symantec folks on this list - feel free to pass this on. Symantec's actions do not go without notice. I've been asked by my management why we're not using Linux for NetBackup and I bluntly told them that Symantec can't be trusted to support the platform as it should be trusted. We recently replaced our master and one of our media servers and stuck with Solaris. We spent a lot more money but at least I know it will work. Enough rambling. If you have concerns about NetBackup and Linux support, contact your Symantec reps. .../Ed -- Ed Wilts, RHCE Mounds View, MN, USA mailto:[EMAIL PROTECTED] Member #1, Red Hat Community Ambassador Program ___ 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 -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] Symantec and Linux support
Looks like they're about as supported as each other... under 6.0. http://ftp.support.veritas.com/pub/support/products/NetBackup_Enterprise _Server/278064.pdf Things that crack me up though, are things like... ITANIUM SUPPORT being the cats meow! I mean, come on, did everyone out there seriously pick Intel over AMD in the 64-bit platform arena?? (if you did, sorry) ~Kate -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts Sent: Wednesday, May 10, 2006 3:48 PM To: Scott Jacobson Cc: List Veritas List Subject: Re: [Veritas-bu] Symantec and Linux support On Wed, May 10, 2006 at 10:44:19AM -0600, Scott Jacobson wrote: Ed, What about the other white meat. We have SLES 8 and 9 Linux boxes running as both Master and Media Servers. Symantec doesn't support Brightmail on any Linux distribution other than RHEL 3 AS and RHEL 3 ES. That should tell you something about their Linux commitment too - after all, I'd put SLES in the same category as RHEL for enterprise-quality (even though I've never worked with SLES). I've not looked at NetBackup support on SLES at all. .../Ed ;-) -sj Ed Wilts [EMAIL PROTECTED] 5/10/2006 10:17 AM I regularly see postings from people looking to enhance their use of Linux as NetBackup servers. Although I am a *strong* Linux advocate and a Red Hat Certified Engineer, I would advise that you think long and hard about this decision. Symantec has not yet been able to demonstrate any willingness to support Red Hat Enterprise Linux as an enterprise platform. Fact: NetBackup 6.5, targeted for release in February, 2007, will drop support for RHEL 3. RHEL 3 started shipping in October, 2003 and will be supported by Red Hat through October, 2010. Symantec will cut you off with its current release nearly 4 years before Red Hat stops supporting the OS. On the other hand, Windows 2000, which was released 2 1/2 years earlier than RHEL 3, will still be supported by NetBackup 6.5. Additionally, mainstream support for Win2K server has already ended and full support will end from Microsoft *before* RHEL 3 support ends. This should show you where Symantec's priorities lie. Fact: Symantec Brightmail is not available for RHEL 4 so if you're deploying today, you have to deploy on RHEL 3. One Symantec enterprise product will soon be unable to back up another Symantec enterprise product. RHEL 4 has been out for over a year and still Symantec hasn't started supporting it. I just searched the support site for the system requirements in case my local office was wrong, and RHEL 4 still does not seem to be supported. Fact: NOM on Linux. Nope, it doesn't exist. Windows or Solaris only. Symantec doesn't seem to get it. I'm turning blue in the face trying to explain this to my local office. I know that there are Symantec folks on this list - feel free to pass this on. Symantec's actions do not go without notice. I've been asked by my management why we're not using Linux for NetBackup and I bluntly told them that Symantec can't be trusted to support the platform as it should be trusted. We recently replaced our master and one of our media servers and stuck with Solaris. We spent a lot more money but at least I know it will work. Enough rambling. If you have concerns about NetBackup and Linux support, contact your Symantec reps. .../Ed -- Ed Wilts, RHCE Mounds View, MN, USA mailto:[EMAIL PROTECTED] Member #1, Red Hat Community Ambassador Program ___ 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 -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu - This e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately. Thank you. Aetna ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Alfred MAK is on leave
I will be out of the office starting 05/11/2006 and will not return until 05/15/2006. I will respond to your message when I return. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Symantec and Linux support
Or for that matter, OES/Linux. It'd be really nice to *at least* run media servers w/ OES, so cluster nodes could back themselves up. I was told it's not on the roadmap as of Feb/06 ~ Robin Scott Jacobson [EMAIL PROTECTED] 05/10/06 9:44 AM Ed, What about the other white meat. We have SLES 8 and 9 Linux boxes running as both Master and Media Servers. ;- ) - sj ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] Symantec and Linux support
All doom and gloom in the Linux camp today! Take heart my fellow hoohum'in Penguins! http://ftp.support.veritas.com/pub/support/products/NetBackup_Enterprise _Server/278064.pdf Comment #98- Next major release following NetBackup 6.0 will not support this OS version. This status could change if market and/or vendor support positions change. Talk about CYA! That's only next to the 64Bit and Older versions of RedHat and SLES. The newer versions (Redhat 4 / SLES9) have no such comment for 32bit, although the 64bit is a bit disconcerting. =/ I personally am hoping to upgrade to Redhat Media Servers when we upgrade to 6! Keep the faith! (Whatever small amount there may be left!) -J -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts Sent: Wednesday, May 10, 2006 3:48 PM To: Scott Jacobson Cc: List Veritas List Subject: Re: [Veritas-bu] Symantec and Linux support On Wed, May 10, 2006 at 10:44:19AM -0600, Scott Jacobson wrote: Ed, What about the other white meat. We have SLES 8 and 9 Linux boxes running as both Master and Media Servers. Symantec doesn't support Brightmail on any Linux distribution other than RHEL 3 AS and RHEL 3 ES. That should tell you something about their Linux commitment too - after all, I'd put SLES in the same category as RHEL for enterprise-quality (even though I've never worked with SLES). I've not looked at NetBackup support on SLES at all. .../Ed ;-) -sj Ed Wilts [EMAIL PROTECTED] 5/10/2006 10:17 AM I regularly see postings from people looking to enhance their use of Linux as NetBackup servers. Although I am a *strong* Linux advocate and a Red Hat Certified Engineer, I would advise that you think long and hard about this decision. Symantec has not yet been able to demonstrate any willingness to support Red Hat Enterprise Linux as an enterprise platform. Fact: NetBackup 6.5, targeted for release in February, 2007, will drop support for RHEL 3. RHEL 3 started shipping in October, 2003 and will be supported by Red Hat through October, 2010. Symantec will cut you off with its current release nearly 4 years before Red Hat stops supporting the OS. On the other hand, Windows 2000, which was released 2 1/2 years earlier than RHEL 3, will still be supported by NetBackup 6.5. Additionally, mainstream support for Win2K server has already ended and full support will end from Microsoft *before* RHEL 3 support ends. This should show you where Symantec's priorities lie. Fact: Symantec Brightmail is not available for RHEL 4 so if you're deploying today, you have to deploy on RHEL 3. One Symantec enterprise product will soon be unable to back up another Symantec enterprise product. RHEL 4 has been out for over a year and still Symantec hasn't started supporting it. I just searched the support site for the system requirements in case my local office was wrong, and RHEL 4 still does not seem to be supported. Fact: NOM on Linux. Nope, it doesn't exist. Windows or Solaris only. Symantec doesn't seem to get it. I'm turning blue in the face trying to explain this to my local office. I know that there are Symantec folks on this list - feel free to pass this on. Symantec's actions do not go without notice. I've been asked by my management why we're not using Linux for NetBackup and I bluntly told them that Symantec can't be trusted to support the platform as it should be trusted. We recently replaced our master and one of our media servers and stuck with Solaris. We spent a lot more money but at least I know it will work. Enough rambling. If you have concerns about NetBackup and Linux support, contact your Symantec reps. .../Ed -- Ed Wilts, RHCE Mounds View, MN, USA mailto:[EMAIL PROTECTED] Member #1, Red Hat Community Ambassador Program ___ 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 -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] ___ 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] NOM on Windows 2003 SP1
Title: NOM on Windows 2003 SP1 Hi Fiona We run NOM on Win 2003 as well but we use the [EMAIL PROTECTED] as that is the only one that seems to work with the admin account. That does appear to be backed up by the Release Notes:- "The initial domain name is NOM_BuiltIn@FQHN. FQHN is the fully qualified host name on which the NOM server and NOM web client are running." Regards Richard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fiona GreenhoughSent: Thursday, 11 May 2006 1:49 amTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] NOM on Windows 2003 SP1 Hi All I am attempting to install NOM into a Windows environment with no success, I have managed to get it working on Solaris. Master Server = Windows 2003 SP1, NBU 6.0GA NOM Server = Windows 2003 SP1, NBU Client 6.0GA On the NOM server we installed Java 1.5.x that we downloaded from the internet, PBX and VxSS as per the installation guide. We then installed NOM, checked that all services are started, including the Veritas Web service. We start NOM and obtained a login screen choose English (or Default) for the Language, admin for the user, Vxadmin for the password and the Domain we left as the default which was [EMAIL PROTECTED] This is the error message: "User authenticationfailed. The user name/password are invalid for the selected domain" If we keep trying we eventually get a java dump: "Exception Report The server excountered an internal error () that prevented it from fulfilling this request" Further down: "Root cause Failed to get credentials. hostname.domain. [vx. NOM_TRUSTED_CLIENTS hostname.domain]" Any help or direction would be much appreciated. RegardsFiona GreenhoughLECHABILE Storage Solutions (PTY) LtdUnit 1, Cambridge Commercial ParkRegent Street, PaulshofP O Box 784013, Sandton, 2146Switchboard: +27 11 519 8100Phone: +27 11 519 8124Fax: +27 11 519 8147Cell: +27 082 338 4754Email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]This e-mail and attachments relating thereto, is intended for the above-mentioned recipient. If you have received this e-mail in error, kindly notify the sender and delete it immediately as it contains information relating to the official business of LECHABILE Storage Solutions (PTY) Ltd, which is confidential, legally privileged and proprietary to LECHABILE Storage Solutions (PTY) Ltd. LECHABILE Storage Solutions (PTY) Ltd does not own and endorse any other content. The views and opinions expressed in this e-mail are those of the sender unless clearly stated as being those of LECHABILE Storage Solutions (PTY) Ltd. ** This electronic email and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed. The views expressed in this message are those of the individual sender and may not necessarily reflect the views of the Christchurch City Council. If you are not the correct recipient of this email please advise the sender and delete. Christchurch City Council http://www.ccc.govt.nz **
Re: [Veritas-bu] Symantec and Linux support
On Wed, May 10, 2006 at 04:27:41PM -0400, Martin, Jonathan (Contractor) wrote: Comment #98- Next major release following NetBackup 6.0 will not support this OS version. This status could change if market and/or vendor support positions change. Talk about CYA! That's only next to the 64Bit and Older versions of RedHat and SLES. The newer versions (Redhat 4 / SLES9) have no such comment for 32bit, although the 64bit is a bit disconcerting. =/ Yeah, my sales rep is saying no decision has been made yet Symantec has officially documented no support. Which vendor support positions are they talking about? The one by Red Hat that says RHEL 3 is supported through October, 2010? Or the one that by Microsoft by says that Win2K is no longer supported but Symantec is chosing to support it anyway? RHEL 3 is not an older version - it's not the current version, but it's the one that even Symantec forces us to deploy today for some of their enterprise products. The only thing that I believe will get Symantec to change their minds is the market support position. We, as the customer community, have to tell Symantec that their support commitment sucks and is not acceptable. Red Hat is commited to RHEL 3 - why won't Symantec commit to it? .../Ed -- Ed Wilts, RHCE Mounds View, MN, USA mailto:[EMAIL PROTECTED] Member #1, Red Hat Community Ambassador Program ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] Renaming NB 6.0MP2 servers
I'd be fascinated to know how? I had a try but ended up with a nbemm server that simply crashed as soon as it started. I've still got an open case with support on how it can be done - their answer so far is that it can be done, but they have to figure it out first! Regards, Tristan From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steven L. SesarSent: Thursday, 11 May 2006 12:39 AMTo: WEAVER, SimonCc: 'Justin Piszcz'; [EMAIL PROTECTED]; veritas-buSubject: Re: [Veritas-bu] Renaming NB 6.0MP2 servers I've done it - it was actually a more complex problem in my case: I cooked 4 master servers (1 Windows, 3 Solaris) down into one Solaris master. It was a very time-consuming and involved process. It worked just fine, however there are a ton of "gotchas" along the way. I did a lot of scripting, both beforehand and on the fly, in order to get this to work. I also had a very good working knowledge of NBU and its internals. please be sure that you really need to do this before attempting it.--SteveWEAVER, Simon wrote: It can be done - I just spoke to someone but told me its a drawn out process (not supported by Symantec) but it could work. Not too sure how much of a risk it is Regards Simon Weaver3rd Line Technical SupportWindows Domain Administrator EADS Astrium Limited, B32AA IM (DCS)Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message-From: Justin Piszcz [mailto:[EMAIL PROTECTED]] Sent: 10 May 2006 11:49To: [EMAIL PROTECTED]Cc: veritas-buSubject: Re: [Veritas-bu] Renaming NB 6.0MP2 serversNot supported under 5.1x and when I opened a ticket concerning this they said there is no supported method, only if it is REALLY necessary you can call Veritas' consulting services and have them fix it. On 5/9/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I'd like to rename a NB 6.0MP2 master server. In fact, i want to clone my master production server and rename it at our DR site. As far as i know this isn't really supported yet. Karl-Frédéric Rossing, Technical Services phone: 204-786-6431 fax: 204-784-6755 toll free: 1-800-665-1934 www.federated.ca CONFIDENTIALITY NOTICE The information in this email may be confidential and/or legally privileged. This email is intended to be reviewed by only the individual(s) or organization(s) named above. If you are not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any review, dissemination or copying of this email and its attachments, if any, or the information contained herein is prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email and its attachments from your system. Thank you. This email is for the intended addressee only.If you have received it in error then you must not use, retain, disseminate or otherwise deal with it.Please notify the sender by return email.The views of the author may not necessarily constitute the views of EADS Astrium Limited.Nothing in this email shall bind EADS Astrium Limited in any contract or obligation.EADS Astrium Limited, Registered in England and Wales No. 2449259Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
RE: [Veritas-bu] Symantec and Linux support
To all the folks who have active Veritas support contracts, and who are struggling with Veritas's patchy linux support - can I suggest we all add our thoughts to: http://enhancement.veritas.com/ At least that way there's some chance that someone further up from your local account rep will see it. :-) Regards, Tristan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts Sent: Thursday, 11 May 2006 2:18 AM To: List Veritas List Subject: [Veritas-bu] Symantec and Linux support I regularly see postings from people looking to enhance their use of Linux as NetBackup servers. Although I am a *strong* Linux advocate and a Red Hat Certified Engineer, I would advise that you think long and hard about this decision. Symantec has not yet been able to demonstrate any willingness to support Red Hat Enterprise Linux as an enterprise platform. Fact: NetBackup 6.5, targeted for release in February, 2007, will drop support for RHEL 3. RHEL 3 started shipping in October, 2003 and will be supported by Red Hat through October, 2010. Symantec will cut you off with its current release nearly 4 years before Red Hat stops supporting the OS. On the other hand, Windows 2000, which was released 2 1/2 years earlier than RHEL 3, will still be supported by NetBackup 6.5. Additionally, mainstream support for Win2K server has already ended and full support will end from Microsoft *before* RHEL 3 support ends. This should show you where Symantec's priorities lie. Fact: Symantec Brightmail is not available for RHEL 4 so if you're deploying today, you have to deploy on RHEL 3. One Symantec enterprise product will soon be unable to back up another Symantec enterprise product. RHEL 4 has been out for over a year and still Symantec hasn't started supporting it. I just searched the support site for the system requirements in case my local office was wrong, and RHEL 4 still does not seem to be supported. Fact: NOM on Linux. Nope, it doesn't exist. Windows or Solaris only. Symantec doesn't seem to get it. I'm turning blue in the face trying to explain this to my local office. I know that there are Symantec folks on this list - feel free to pass this on. Symantec's actions do not go without notice. I've been asked by my management why we're not using Linux for NetBackup and I bluntly told them that Symantec can't be trusted to support the platform as it should be trusted. We recently replaced our master and one of our media servers and stuck with Solaris. We spent a lot more money but at least I know it will work. Enough rambling. If you have concerns about NetBackup and Linux support, contact your Symantec reps. .../Ed -- Ed Wilts, RHCE Mounds View, MN, USA mailto:[EMAIL PROTECTED] Member #1, Red Hat Community Ambassador Program ___ 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] Sg / sgen driver issue
Have a look at your st.conf. I have a MSL 6030, and it attaches to the FC via a built in SCSI/FC router. That router presents the tape drives as LUN's 1 2, with the controller as LUN 0. By default, the solaris st only scans LUN 0, but that can be changed in ST conf. Regards, Tristan. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Song, Young Sent: Thursday, 11 May 2006 4:33 AM To: 'veritas-bu@mailman.eng.auburn.edu' Subject: [Veritas-bu] Sg / sgen driver issue I'm trying to set up Sun Fire-480R as a new backup server to replace an old one and in a situation where I'm stuck and thus want to ask here. I'm running Solaris 8 with all the latest Solaris patches including st driver patch, etc. latest SAN Foundation Kit 4.4.9. And I have a FC-attached HP MSL 5060 library with 2 LTO-1 drives via Brocade Silkworm switches. After installing NetBackup v5.1, I tried following the steps in MediaMgr_DeviceConfig_Guide.txt but no matter what I tried, I couldn't have it see both tape drives properly and I believe it's something to do with sg.conf, sg.links, devlink.tab files. However, I may be wrong. I tried all I could try with cfgadm, devfsadm, luxadm, zoning, etc. and know that I have all the proper connections and the box can see the library itself but not all the drives. Anyone experienced similar things and have any advice? Thank you in advance!!! - Young ___ 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] Sg / sgen driver issue
Hi Tristan, That sounds to be my case as well. From the info for the one drive and router that are visible, how can I identify and add the correct entry for the other tape drive into st.conf file? Thanks! - Young -Original Message- From: Tristan Ball [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 10, 2006 3:15 PM To: Song, Young; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Sg / sgen driver issue Have a look at your st.conf. I have a MSL 6030, and it attaches to the FC via a built in SCSI/FC router. That router presents the tape drives as LUN's 1 2, with the controller as LUN 0. By default, the solaris st only scans LUN 0, but that can be changed in ST conf. Regards, Tristan. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Song, Young Sent: Thursday, 11 May 2006 4:33 AM To: 'veritas-bu@mailman.eng.auburn.edu' Subject: [Veritas-bu] Sg / sgen driver issue I'm trying to set up Sun Fire-480R as a new backup server to replace an old one and in a situation where I'm stuck and thus want to ask here. I'm running Solaris 8 with all the latest Solaris patches including st driver patch, etc. latest SAN Foundation Kit 4.4.9. And I have a FC-attached HP MSL 5060 library with 2 LTO-1 drives via Brocade Silkworm switches. After installing NetBackup v5.1, I tried following the steps in MediaMgr_DeviceConfig_Guide.txt but no matter what I tried, I couldn't have it see both tape drives properly and I believe it's something to do with sg.conf, sg.links, devlink.tab files. However, I may be wrong. I tried all I could try with cfgadm, devfsadm, luxadm, zoning, etc. and know that I have all the proper connections and the box can see the library itself but not all the drives. Anyone experienced similar things and have any advice? Thank you in advance!!! - Young ___ 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] Symantec and Linux support
On Thu, May 11, 2006 at 08:08:48AM +1000, Tristan Ball wrote: To all the folks who have active Veritas support contracts, and who are struggling with Veritas's patchy linux support - can I suggest we all add our thoughts to: http://enhancement.veritas.com/ We're not asking for enhancements. We're asking that they support the operating systems that are still on active support by their manufacturers. If Red Hat has dropped support, I'd agree with Symantec's position. Right now, Symantec's position sucks. I have completed the form though and I'll see if I even get a response. .../Ed -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] Symantec and Linux support
Can someone please send me the link to the client compatibility matrix for Netbackup 4.5? I can never seem to find what I'm looking for on the support web site... TIA, Neil -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tristan Ball Sent: Wednesday, May 10, 2006 3:09 PM To: Ed Wilts; List Veritas List Subject: RE: [Veritas-bu] Symantec and Linux support To all the folks who have active Veritas support contracts, and who are struggling with Veritas's patchy linux support - can I suggest we all add our thoughts to: http://enhancement.veritas.com/ At least that way there's some chance that someone further up from your local account rep will see it. :-) Regards, Tristan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts Sent: Thursday, 11 May 2006 2:18 AM To: List Veritas List Subject: [Veritas-bu] Symantec and Linux support I regularly see postings from people looking to enhance their use of Linux as NetBackup servers. Although I am a *strong* Linux advocate and a Red Hat Certified Engineer, I would advise that you think long and hard about this decision. Symantec has not yet been able to demonstrate any willingness to support Red Hat Enterprise Linux as an enterprise platform. Fact: NetBackup 6.5, targeted for release in February, 2007, will drop support for RHEL 3. RHEL 3 started shipping in October, 2003 and will be supported by Red Hat through October, 2010. Symantec will cut you off with its current release nearly 4 years before Red Hat stops supporting the OS. On the other hand, Windows 2000, which was released 2 1/2 years earlier than RHEL 3, will still be supported by NetBackup 6.5. Additionally, mainstream support for Win2K server has already ended and full support will end from Microsoft *before* RHEL 3 support ends. This should show you where Symantec's priorities lie. Fact: Symantec Brightmail is not available for RHEL 4 so if you're deploying today, you have to deploy on RHEL 3. One Symantec enterprise product will soon be unable to back up another Symantec enterprise product. RHEL 4 has been out for over a year and still Symantec hasn't started supporting it. I just searched the support site for the system requirements in case my local office was wrong, and RHEL 4 still does not seem to be supported. Fact: NOM on Linux. Nope, it doesn't exist. Windows or Solaris only. Symantec doesn't seem to get it. I'm turning blue in the face trying to explain this to my local office. I know that there are Symantec folks on this list - feel free to pass this on. Symantec's actions do not go without notice. I've been asked by my management why we're not using Linux for NetBackup and I bluntly told them that Symantec can't be trusted to support the platform as it should be trusted. We recently replaced our master and one of our media servers and stuck with Solaris. We spent a lot more money but at least I know it will work. Enough rambling. If you have concerns about NetBackup and Linux support, contact your Symantec reps. .../Ed -- Ed Wilts, RHCE Mounds View, MN, USA mailto:[EMAIL PROTECTED] Member #1, Red Hat Community Ambassador Program ___ 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 maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] Sg / sgen driver issue
Your st.conf probably has something like: name=st class=scsi target=0 lun=0; name=st class=scsi target=1 lun=0; You need to add lines like: name=st class=scsi target=0 lun=1; name=st class=scsi target=0 lun=2; I personally added Luns 1-7 on targets 0-7. That possibly makes boot up a little slower, but it also means the drives will be picked up almost regardless of whatever silliness I might pull on the SAN. :-) Regards, T. -Original Message- From: Song, Young [mailto:[EMAIL PROTECTED] Sent: Thursday, 11 May 2006 8:25 AM To: Tristan Ball; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Sg / sgen driver issue Hi Tristan, That sounds to be my case as well. From the info for the one drive and router that are visible, how can I identify and add the correct entry for the other tape drive into st.conf file? Thanks! - Young -Original Message- From: Tristan Ball [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 10, 2006 3:15 PM To: Song, Young; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Sg / sgen driver issue Have a look at your st.conf. I have a MSL 6030, and it attaches to the FC via a built in SCSI/FC router. That router presents the tape drives as LUN's 1 2, with the controller as LUN 0. By default, the solaris st only scans LUN 0, but that can be changed in ST conf. Regards, Tristan. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Song, Young Sent: Thursday, 11 May 2006 4:33 AM To: 'veritas-bu@mailman.eng.auburn.edu' Subject: [Veritas-bu] Sg / sgen driver issue I'm trying to set up Sun Fire-480R as a new backup server to replace an old one and in a situation where I'm stuck and thus want to ask here. I'm running Solaris 8 with all the latest Solaris patches including st driver patch, etc. latest SAN Foundation Kit 4.4.9. And I have a FC-attached HP MSL 5060 library with 2 LTO-1 drives via Brocade Silkworm switches. After installing NetBackup v5.1, I tried following the steps in MediaMgr_DeviceConfig_Guide.txt but no matter what I tried, I couldn't have it see both tape drives properly and I believe it's something to do with sg.conf, sg.links, devlink.tab files. However, I may be wrong. I tried all I could try with cfgadm, devfsadm, luxadm, zoning, etc. and know that I have all the proper connections and the box can see the library itself but not all the drives. Anyone experienced similar things and have any advice? Thank you in advance!!! - Young ___ 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] cannot read media header
Title: cannot read media header Take a look at this doc: http://seer.support.veritas.com/docs/205940.htm If the media header is corrupt, but the integrity of the tape is OK, then you should be able to skip past the media header (the first 'file' on the tape) and extract the rest of the data with NetBackup's version of tar. matt From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tim DuncanSent: Wednesday, May 10, 2006 11:03 AMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] cannot read media header I have a SDLT tape that according to the netbackup catalog contains netbackup images, When ever I try to read the media's content I receive the error "Error from master server. Cannot read media header , may not be Netbackup media or corrupt. I have worked with Veritas tech support, but they have offered no solution to recoverying the data on this tape. I suspect the media header is corrupt but the images are still on the tape. Any recommendation or soultions to recoverying the data off this tape will be appreciated. Vertias 5.1MP5 Tim Duncan
RE: [Veritas-bu] cannot read media header
From: Tim Duncan [EMAIL PROTECTED]
To: veritas-bu@mailman.eng.auburn.edu
Subject: [Veritas-bu] cannot read media header
This is a multi-part message in MIME format.
--_=_NextPart_001_01C6745B.F06FD668
Content-Type: text/plain;
charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
I have a SDLT tape that according to the netbackup catalog contains
netbackup images,=20
When ever I try to read the media's content I receive the
error Error
from master server. Cannot read media header , may not be Netbackup
media or corrupt.=20
I have worked with Veritas tech support, but they have offered no
solution to recoverying the data on this tape. I suspect the media
header is corrupt but the images are still on the tape. Any
recommendation or soultions to recoverying the data off this tape will
be appreciated. =20
Tim - you can get creative with tools to try to figure out what, if
anything, is on this tape.
vmphyinv to see if it's a catalog or data tape or unknown. bprecover -l
to see if it's a catalog tape. Assuming no joy with those, you can use
mt and {dd|cp|copy|whatever} to copy the first (or more) file off the
tape (just to make them easier to work with) and see what it looks like
(send it to GNU tar, or cpio, or od, or ...). File sizes are a good
clue--and matchable against frag sizes recorded in the catalog metadata.
A NetBackup label's content is very obvious (1HDR, tape number,
NetBackup magic text string) but you already know the first file isn't
that or you wouldn't be asking the question.
If there is at least the start of a NetBackup image on the tape, it's
readable with tar.
If this really was a NetBackup tape (not doubting you, but consider that
the barcode could be physically swapped, for instance), and something
wrote to the tape at BOT, the chances are slim that you can recover data
from whatever used to be at the front of the tape.
___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Export and Import NetBackup configuration
The dhost parameterjust restores the files from the catalog backup to a host other than the one you're running bprecover on. So you might have files other than the master catalog one the catalog backup tape, such as a media server's voldb, or even some non-NetBackup files. I used to backup several SQL-Backtrack catalogs with bpbackupdb, along with the master's catalog and several media server's voldbs. The -dhost let me recover all of these different hosts' by just mounting the tape once on the master (but running bprecover several times). You can physically restore the master catalog to whatever server name you like, but NetBackup (probably!) won't work... On 5/10/06, Whelan, Patrick [EMAIL PROTECTED] wrote: Am I misinterpreting the original post?According to the manual, using bprecover with the -dhost option is supposed to allow recovery of the database to an alternate host. This isa snippet from the command manual.bprecover-dhost destination_hostSpecifies the host to which the selected catalog is restored. Normally, catalogs are restored to the host where the data originated (asdisplayedwith the -l option). The -d option makes it possible to restore thecatalog to another host.Caution Use the dhost option with EXTREME caution, since it can overwrite existingcatalogs on the destination host. To permit recovery in case youunintentionallyoverwrite the wrong catalogs, you can move existing catalogs to atemporarydirectory on the destination host. The following NetBackup client software must be installed on thedestination host:/usr/openv/netbackup/bin/bpcdand/usr/openv/netbackup/bin/tarNote Do not specify -r all (or ALL) with -dhost when using this command. Eitherexplicitly specify an image (for example, -r 2) or use the interactivemode (-r).Patrick WhelanNetBackup SpecialistArchitect Engineering+44 20 7863 5243Of all the things I've lost, I miss my mind the most! - Unknown *The message is intended for the named addressee only and may not be disclosed to or used by anyone else, nor may it be copied in any way. The contents of this message and its attachments are confidential and may also be subject to legal privilege.If you are not the named addressee and/or have received this message in error, please advise us by e-mailing [EMAIL PROTECTED] and delete the message and any attachments without retaining any copies.Internet communications are not secure and COLT does not accept responsibility for this message, its contents nor responsibility for any viruses. No contracts can be created or varied on behalf of COLT Telecommunications, its subsidiaries or affiliates (COLT) and any other party by email Communications unless expressly agreed in writing with such other party. Please note that incoming emails will be automatically scanned to eliminate potential viruses and unsolicited promotional emails. For more information refer to www.colt.net or contact us on +44(0)20 7390 3900. ___Veritas-bu maillist-Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] Export and Import NetBackup configuration
Kathy Most likely from the Netbackup SysAdmin guide or Media Manager guide perhaps? Wasn't the original question about using bprecover on the same server which would be in standby? Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B32AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: Kathy Falakfarsa [mailto:[EMAIL PROTECTED] Sent: 10 May 2006 17:24 To: Whelan, Patrick; Ed Wilts; WEAVER, Simon Cc: Justin Piszcz; veritas-bu Subject: RE: [Veritas-bu] Export and Import NetBackup configuration Thanks for the information. Could you please let me know what document you got that information from, so I can downloaded and review it. Thanks Kathy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Whelan, Patrick Sent: May 10, 2006 11:48 AM To: Ed Wilts; WEAVER, Simon Cc: Justin Piszcz; veritas-bu Subject: RE: [Veritas-bu] Export and Import NetBackup configuration Am I misinterpreting the original post? According to the manual, using bprecover with the -dhost option is supposed to allow recovery of the database to an alternate host. This is a snippet from the command manual. bprecover -dhost destination_host Specifies the host to which the selected catalog is restored. Normally, catalogs are restored to the host where the data originated (as displayed with the -l option). The -d option makes it possible to restore the catalog to another host. Caution Use the dhost option with EXTREME caution, since it can overwrite existing catalogs on the destination host. To permit recovery in case you unintentionally overwrite the wrong catalogs, you can move existing catalogs to a temporary directory on the destination host. The following NetBackup client software must be installed on the destination host: /usr/openv/netbackup/bin/bpcd and /usr/openv/netbackup/bin/tar Note Do not specify -r all (or ALL) with -dhost when using this command. Either explicitly specify an image (for example, -r 2) or use the interactive mode (-r). Patrick Whelan NetBackup Specialist Architect Engineering +44 20 7863 5243 Of all the things I've lost, I miss my mind the most! - Unknown * The message is intended for the named addressee only and may not be disclosed to or used by anyone else, nor may it be copied in any way. The contents of this message and its attachments are confidential and may also be subject to legal privilege. If you are not the named addressee and/or have received this message in error, please advise us by e-mailing [EMAIL PROTECTED] and delete the message and any attachments without retaining any copies. Internet communications are not secure and COLT does not accept responsibility for this message, its contents nor responsibility for any viruses. No contracts can be created or varied on behalf of COLT Telecommunications, its subsidiaries or affiliates (COLT) and any other party by email Communications unless expressly agreed in writing with such other party. Please note that incoming emails will be automatically scanned to eliminate potential viruses and unsolicited promotional emails. For more information refer to www.colt.net or contact us on +44(0)20 7390 3900. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] BMR Boot Error
Hi Jason I am VERY interested in this product, as its something I am really looking for. Do you have any more details, pdf white papers, costs or links atall. Happy to discuss off list if this goes off topic Thanks Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B32AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: Brooks, Jason [mailto:[EMAIL PROTECTED] Sent: 10 May 2006 19:59 To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] BMR Boot Error I'm still working at testing BMR. Having loads of fun ;-) Today's task: take a BMR image of a Win2K server and restore it to new hardware, all Dell boxes. Original is not RAID, BMR restore to RAID. Build a generic boot floppy with appropriate drivers, recent downloads from Dell's site. Booted the client and received an error something like this: This program cannot be run in DOS mode. Neither google nor veritas/symantec seem to know about this any later than NBU 4.5. Anyone else seen this? Suggestions for a fix? Or, just punt and open another case? Thanks, Jason Jason Brooks Computer Systems Engineer IITS - Longwood University voice - (434) 395-2916 fax - (434) 395-2035 mailto:[EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] cannot read media header
Title: Message Tim Was it used as a Catalog backup! Seen this error when using a tape that contains Netbackup Catalog information. It will not use the tape. Regards Simon Weaver3rd Line Technical SupportWindows Domain Administrator EADS Astrium Limited, B32AA IM (DCS)Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message-From: Tim Duncan [mailto:[EMAIL PROTECTED] Sent: 10 May 2006 19:03To: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] cannot read media header I have a SDLT tape that according to the netbackup catalog contains netbackup images, When ever I try to read the media's content I receive the error "Error from master server. Cannot read media header , may not be Netbackup media or corrupt. I have worked with Veritas tech support, but they have offered no solution to recoverying the data on this tape. I suspect the media header is corrupt but the images are still on the tape. Any recommendation or soultions to recoverying the data off this tape will be appreciated. Vertias 5.1MP5 Tim Duncan This email is for the intended addressee only. If you have received it in error then you must not use, retain, disseminate or otherwise deal with it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of EADS Astrium Limited. Nothing in this email shall bind EADS Astrium Limited in any contract or obligation. EADS Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
