[Veritas-bu] Baremetal on master server
Dear All, On NBU 6 , Is it possible to use baremetal to protect master server ? Do we need key in baremetal license on master or only on media and client. Thanks HMW ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Baremetal on master server
No, Unfortunately BMR needs master server to do restores stefanos -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hermawan Sent: Wednesday, April 04, 2007 5:25 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Baremetal on master server Dear All, On NBU 6 , Is it possible to use baremetal to protect master server ? Do we need key in baremetal license on master or only on media and client. Thanks HMW ___ 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] os sees the drives; netbackup does not see the drives with sgscan
Hi All, I have two tape drives connected to HBA as direct-to-direct. OS sees the drives with cfgadm -al and tape drives are also seen under /dev/rmt. However, sgscan returns entry only internal disks and internal tape drives. What is that I am missing. Solaris version is 10. NB version is 5.1 MP5. Regards, Asiye ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Baremetal on master server
We use a solaris flash archive to protect our solaris master server.If you add in a hot catalog backup, you're pretty much set. Karl [EMAIL PROTECTED] wrote on 04/04/2007 02:37:49 AM: No, Unfortunately BMR needs master server to do restores stefanos -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hermawan Sent: Wednesday, April 04, 2007 5:25 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Baremetal on master server Dear All, On NBU 6 , Is it possible to use baremetal to protect master server ? Do we need key in baremetal license on master or only on media and client. Thanks HMW ___ 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] os sees the drives; netbackup does not see the drives with sgscan
Sounds like you might have to rebuild your sgdrivers. From /driver folder Do a ../sg.build all -mt 10 -ml Rename the sg.conf in the /kernel/drv folder Then do ./sg.install http://saifulaziz.wordpress.com/2006/12/18/how-to-configure-drive-on-solaris-for-veritas-netbackup-4/ Greg From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Asiye Yigit Sent: Wednesday, April 04, 2007 6:23 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] os sees the drives;netbackup does not see the drives with sgscan Hi All, I have two tape drives connected to HBA as direct-to-direct. OS sees the drives with cfgadm -al and tape drives are also seen under /dev/rmt. However, sgscan returns entry only internal disks and internal tape drives. What is that I am missing. Solaris version is 10. NB version is 5.1 MP5. Regards, Asiye This e-mail and any attachments are confidential, may contain legal, professional or other privileged information, and are intended solely for the addressee. If you are not the intended recipient, do not use the information in this e-mail in any way, delete this e-mail and notify the sender. CEG-IP2 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] replacing a drive
nb 5.0 mp7 Solaris 9 We have replaced 2 drives in our L700 robot and I want to correct netbackup and make it see the 2 new drives but do this without having to shutdown netbackup. I am looking at using tpautoconf with -replace_drive option. Is this what everyone else uses when they need to replace a drive and the serial number changes? is there any easier way to do this? Greg This e-mail and any attachments are confidential, may contain legal, professional or other privileged information, and are intended solely for the addressee. If you are not the intended recipient, do not use the information in this e-mail in any way, delete this e-mail and notify the sender. CEG-IP2 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Preventing Media Expiration when doing a Catalog restore
Hi, We are restoring a catalog tape to our dv environment(same server name). The catalog db seems to be expiring the images we are testing with since time has progressed past the expiry time. Is there a way to tell the catalog db to not expire any images? If i do an import, the images will expire from the time of the import. Shouldn't the same thing happen for Catalog restore? NB 6.0MP3 running on Solaris 10. Karl___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] replacing a drive
Stop ltid, remove the old drive, add the new drive? Run tpautoconf -sync after? On Wed, 4 Apr 2007, Hindle, Greg wrote: nb 5.0 mp7 Solaris 9 We have replaced 2 drives in our L700 robot and I want to correct netbackup and make it see the 2 new drives but do this without having to shutdown netbackup. I am looking at using tpautoconf with -replace_drive option. Is this what everyone else uses when they need to replace a drive and the serial number changes? is there any easier way to do this? Greg This e-mail and any attachments are confidential, may contain legal, professional or other privileged information, and are intended solely for the addressee. If you are not the intended recipient, do not use the information in this e-mail in any way, delete this e-mail and notify the sender. CEG-IP2 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Preventing Media Expiration when doing a Catalog
We are restoring a catalog tape to our dv environment(same server name). The catalog db seems to be expiring the images we are testing with since time has progressed past the expiry time. Is there a way to tell the catalog db to not expire any images? I came across this information in the past and wrote it down, but I am not sure how well it works. But reportedly touching /usr/openv/netbackup/bin/NOexpire will tell netbackup to not perform any expiration. I figure it's good for a decommissioned or DR server that is not actually performing any active backups and doesn't need the space. -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOShttp://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area This line left intentionally blank to confuse you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] 6.0 MP4 and NDMP
Folks, I upgraded my master and media server yesterday to MP4. This morning, I started looking. Nothing out of the ordinary except for NDMP. Looking at the Activity Monitor, it shows that the job failed after 4 attempts with a 41 -- Timeout. Looking at the logs on the media server with vxlogview, I see the following: 04/03/2007 01:03:30.594 [NdmpGlueLogCb] ndmp_open_and_auth_via_host: hostname=15 9.230.4.30, via_hostname=192.168.1.20 04/03/2007 01:03:30.751 [NdmpGlueLogCb] ndmp_open_and_auth_via_host: using NDMP protocol version 3 04/03/2007 01:03:30.985 [NdmpGlueLogCb] 192.168.1.20: NDMP_LOG_NORMAL 0 ndmp-ima ge: performing prolog for image backup. 04/03/2007 01:03:41.124 [NdmpGlueLogCb] 192.168.1.20: NDMP_LOG_NORMAL 0 ndmp-ima ge: continuing prolog for image backup...please wait. 04/03/2007 01:03:49.205 [NdmpGlueLogCb] 192.168.1.20: NDMP_LOG_NORMAL 0 ndmp-ima ge: backing up /usr/store. Level 3 requested by DMA. Timestamp of Apr 02 01:02:0 0 EDT 2007 based on previous level of 2. 04/03/2007 01:46:47.059 [NdmpGlueLogCb] 192.168.1.20: NDMP_LOG_NORMAL 0 ndmp-ima ge: wrote 6614742973 bytes in 2577.745990 seconds (8.60 GB/hour). 04/03/2007 01:46:47.059 [NdmpGlueLogCb] 192.168.1.20: NDMP_LOG_NORMAL 0 ndmp-ima ge: backup stream for /usr/store generated successfully, please check with your NDMP DMA for the official results. 04/03/2007 01:47:10.745 [NdmpGlueLogCb] 192.168.1.20: NDMP_LOG_NORMAL 0 FileHist ory(flushes/number/size): Dir(1565/351162/1990516) Node(426/109033/0) 04/03/2007 01:47:10.746 [Info] V-134-31 NDMP backup successfully completed, path = /usr/store The NDMP server logs show the four attempts without any indication of success. Looking at the Backup, Archive and Restore app, I see an entry for a Diff last night and it looks legit. So, we tested a restore to test NDMP server and we have success. So, is this a known issue? Or I am I looking at some level of problems? Anyone else seeing anything similar? Thanks, Jason Jason Brooks Computer Systems Engineer IITS - Longwood University voice - (434) 395-2034 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] 6.0 MP4 and NDMP
Folks, I upgraded my master and media server yesterday to MP4. This morning, I started looking. Nothing out of the ordinary except for NDMP. Did you upgrade NDMP to MP4 as well (separate patch set)? Client, server, NDMP, vault, and java are all separate sets. -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOShttp://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area This line left intentionally blank to confuse you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] 6.0 MP4 and NDMP
Yes, we did. It was from this file: NB_DMP_60_4_M_285955.linux.tar -Original Message- From: [mailto:[EMAIL PROTECTED] On Behalf Of Darren Dunham Sent: Wednesday, April 04, 2007 12:05 PM To: Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] 6.0 MP4 and NDMP Folks, I upgraded my master and media server yesterday to MP4. This morning, I started looking. Nothing out of the ordinary except for NDMP. Did you upgrade NDMP to MP4 as well (separate patch set)? Client, server, NDMP, vault, and java are all separate sets. -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOS http://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area This line left intentionally blank to confuse you. ___ 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] 6.0 MP4 and NDMP
Yes, we did. It was from this file: NB_DMP_60_4_M_285955.linux.tar Okay. You mention the NDMP server shows the attempts, but not success. Any other messages associated with the NDMP backups? Are these Netapp filers or something else? Can you post the relevant sections from the log? I haven't seen this issue before. I've done some 6.0 - 6.0MP4 upgrades and they all worked fine (as long as I actually installed NDMP portion). :-) Besides the unified log, does the Detailed Status from the job in the activity monitor have any additional information? -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOShttp://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area This line left intentionally blank to confuse you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] 6.0 MP4 and NDMP
The NDMP logs from the appliance show this: 2007 Apr 04 01:02:50 Notice: callbacks.cc:45 ndmp-image: performing prolog for image backup. 2007 Apr 04 01:03:00 Notice: callbacks.cc:45 ndmp-image: continuing prolog for image backup...please wait. 2007 Apr 04 01:03:10 Notice: callbacks.cc:45 ndmp-image: continuing prolog for image backup...please wait. 2007 Apr 04 01:03:10 Notice: callbacks.cc:45 ndmp-image: backing up /usr/store. Level 4 requested by DMA. Timestamp of Apr 03 01:03:30 EDT 2007 based on previous level of 3. 2007 Apr 04 01:12:56 Warning: callbacks.cc:54 ndmp-image: aborted. 2007 Apr 04 01:12:56 Notice: callbacks.cc:45 FileHistory(flushes/number/size): Dir(689/153867/905361) Node(220/56208/0) 2007 Apr 04 01:26:56 Notice: callbacks.cc:45 ndmp-image: performing prolog for image backup. 2007 Apr 04 01:27:07 Notice: callbacks.cc:45 ndmp-image: backing up /usr/store. Level 4 requested by DMA. Timestamp of Apr 03 01:03:30 EDT 2007 based on previous level of 3. 2007 Apr 04 01:28:52 Warning: couldn't get socket name for new connection on https listener: 443: Connection reset by peer 2007 Apr 04 01:37:00 Warning: callbacks.cc:54 ndmp-image: aborted. 2007 Apr 04 01:37:00 Notice: callbacks.cc:45 FileHistory(flushes/number/size): Dir(688/153699/904418) Node(220/56311/0) 2007 Apr 04 01:51:06 Notice: callbacks.cc:45 ndmp-image: performing prolog for image backup. 2007 Apr 04 01:51:15 Notice: callbacks.cc:45 ndmp-image: backing up /usr/store. Level 4 requested by DMA. Timestamp of Apr 03 01:03:30 EDT 2007 based on previous level of 3. 2007 Apr 04 02:00:42 Warning: callbacks.cc:54 ndmp-image: aborted. 2007 Apr 04 02:00:42 Notice: callbacks.cc:45 FileHistory(flushes/number/size): Dir(720/161145/945416) Node(230/58868/0) 2007 Apr 04 02:13:27 Notice: callbacks.cc:45 ndmp-image: performing prolog for image backup. 2007 Apr 04 02:13:35 Notice: callbacks.cc:45 ndmp-image: backing up /usr/store. Level 4 requested by DMA. Timestamp of Apr 03 01:03:30 EDT 2007 based on previous level of 3. 2007 Apr 04 02:22:39 Warning: callbacks.cc:54 ndmp-image: aborted. 2007 Apr 04 02:22:39 Notice: callbacks.cc:45 FileHistory(flushes/number/size): Dir(846/189145/1097467) Node(263/67095/0) 2007 Apr 04 09:07:20 Notice: callbacks.cc:45 ndmp-image: performing prolog for image backup. 2007 Apr 04 09:07:31 Notice: callbacks.cc:45 ndmp-image: continuing prolog for image backup...please wait. 2007 Apr 04 09:07:41 Notice: callbacks.cc:45 ndmp-image: continuing prolog for image backup...please wait. 2007 Apr 04 09:07:42 Notice: callbacks.cc:45 ndmp-image: backing up /usr/store. Level 4 requested by DMA. Timestamp of Apr 03 01:03:30 EDT 2007 based on previous level of 3. 2007 Apr 04 09:20:23 Warning: callbacks.cc:54 ndmp-image: aborted. 2007 Apr 04 09:20:23 Notice: callbacks.cc:45 FileHistory(flushes/number/size): Dir(707/156661/922632) Node(229/58506/0) The appliance is a Mirapoint mail server, which is can be and has been difficult with NDMP. The Details of the Activity Monitor show this: 4/4/2007 2:10:55 AM - requesting resource Wormwood-Tape2 4/4/2007 2:10:55 AM - requesting resource hobbes.NBU_CLIENT.MAXJOBS.159.230.4.30 4/4/2007 2:10:55 AM - requesting resource hobbes.NBU_POLICY.MAXJOBS.NDMP 4/4/2007 2:10:56 AM - granted resource hobbes.NBU_CLIENT.MAXJOBS.159.230.4.30 4/4/2007 2:10:56 AM - granted resource hobbes.NBU_POLICY.MAXJOBS.NDMP 4/4/2007 2:10:56 AM - granted resource 73 4/4/2007 2:10:56 AM - granted resource Tape3 4/4/2007 2:10:56 AM - granted resource Wormwood-Tape2 4/4/2007 2:11:12 AM - started process bpbrm (21247) 4/4/2007 2:11:12 AM - connecting 4/4/2007 2:11:12 AM - connected; connect time: 00:00:00 4/4/2007 2:11:16 AM - mounting 73 4/4/2007 2:11:49 AM - mounted; mount time: 00:00:33 4/4/2007 2:11:49 AM - positioning 73 to file 159 4/4/2007 2:13:25 AM - positioned 73; position time: 00:01:36 4/4/2007 2:13:25 AM - begin writing 4/4/2007 2:18:27 AM - Error ndmpagent(pid=21252) terminated by parent process 4/4/2007 2:21:37 AM - Error bptm(pid=21253) media manager terminated by parent process 4/4/2007 2:21:38 AM - Error ndmpagent(pid=21252) NDMP backup failed, path = /usr/store 4/4/2007 2:22:46 AM - Error ndmpagent(pid=21252) connection 0x0818c230 ndmp_message_process_one failed, status = 18 (NDMP_XDR_DECODE_ERR) 4/4/2007 2:22:45 AM - end writing; write time: 00:09:20 network connection timed out(41) It was also the 4th attempt, which I believe is the max. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darren Dunham Sent: Wednesday, April 04, 2007 12:38 PM To: Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] 6.0 MP4 and NDMP Yes, we did. It was from this file: NB_DMP_60_4_M_285955.linux.tar Okay. You mention the NDMP server shows the attempts, but not success. Any other messages associated with the NDMP backups? Are these Netapp filers or something else? Can you post the
[Veritas-bu] NOM and BLAT
Good Day NetBackup 6.0 MP4 on Win2k3 NOM 6.0 MP4 on Win2k3 (on a separate server) Can someone please confirm that BLAT is required or not, to send emails from NOM? I know it is needed for NetBackup to send emails, but I am not sure if it also needed for NOM. Thx Bored stiff? Loosen up... Download and play hundreds of games for free on Yahoo! Games. http://games.yahoo.com/games/front ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Do you know if NetBackup supports Exchange 2007
Hello, Does anyone know if NetBackup will support with Exchange 2007. We are installing a new Exchange 2007 and I want to make sure I can back it up. Thanks K ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] VxFS for /usr/openv volume
Hi All, Do you suggest to use vxfs for /usr/openv volume? Which is the best for VxFS or UFS for /usr/openv volume? Regards, ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Preventing Media Expiration when doing a Catalog restore
We are restoring a catalog tape to our dv environment(same server name). The catalog db seems to be expiring the images we are testing with since time has progressed past the expiry time. Is there a way to tell the catalog db to not expire any images? D Dunham noted the NOexpire file. There's a current technote which mentions it in the similar context of replicated catlogs, regarding not expiring images before database consistency can be established--so the file and its effects are documented. See http://support.veritas.com/docs/287636 If i do an import, the images will expire from the time of the import. Shouldn't the same thing happen for Catalog restore? Not really; these are two very different situations: 1. Catalog recovery: My master, or its datacenter, no longer exists. I have my vaulted catalog backup and data tapes and a new master server. bprecover and I'm in business. All my data expires exactly as it would have had I been running on the original master, nothing has changed, business continues. 2. Import: I have ten dust-covered tapes that may have the expired (say, three-year-retention) 1998 year-end backups that finance wants to review. Once imported, they have the same three-year lifespan as they did originally, giving appropriate time to decide what to do with the data. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] VxFS for /usr/openv volume
Hi All, Do you suggest to use vxfs for /usr/openv volume? It's fine if you have it, but it's not required. Which is the best for VxFS or UFS for /usr/openv volume? /usr/openv has no special requirement. VxFS has some general advantages over UFS in some cases, but I can't think of anything that applies specifically to /usr/openv. If you want VxFS, feel free to use VxFS. -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOShttp://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area This line left intentionally blank to confuse you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] VxFS for /usr/openv volume
I concur. We use VxFS for all filesystems other than boot/root including /usr/openv VxFS is a journaled filesystem so has a lot of benefits over ufs which isn't journaled. I'd always recommend using it where possible but as noted it isn't required. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darren Dunham Sent: Wednesday, April 04, 2007 3:22 PM To: Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VxFS for /usr/openv volume Hi All, Do you suggest to use vxfs for /usr/openv volume? It's fine if you have it, but it's not required. Which is the best for VxFS or UFS for /usr/openv volume? /usr/openv has no special requirement. VxFS has some general advantages over UFS in some cases, but I can't think of anything that applies specifically to /usr/openv. If you want VxFS, feel free to use VxFS. -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOShttp://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area This line left intentionally blank to confuse you. ___ 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] VxFS for /usr/openv volume
Ah but UFS is journaled, at least in solaris 9 len -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Lightner Sent: Wednesday, April 04, 2007 3:43 PM To: Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VxFS for /usr/openv volume I concur. We use VxFS for all filesystems other than boot/root including /usr/openv VxFS is a journaled filesystem so has a lot of benefits over ufs which isn't journaled. I'd always recommend using it where possible but as noted it isn't required. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Darren Dunham Sent: Wednesday, April 04, 2007 3:22 PM To: Veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VxFS for /usr/openv volume Hi All, Do you suggest to use vxfs for /usr/openv volume? It's fine if you have it, but it's not required. Which is the best for VxFS or UFS for /usr/openv volume? /usr/openv has no special requirement. VxFS has some general advantages over UFS in some cases, but I can't think of anything that applies specifically to /usr/openv. If you want VxFS, feel free to use VxFS. -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOShttp://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area This line left intentionally blank to confuse you. ___ 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] VxFS for /usr/openv volume
I concur. We use VxFS for all filesystems other than boot/root including /usr/openv VxFS is a journaled filesystem so has a lot of benefits over ufs which isn't journaled. I'd always recommend using it where possible but as noted it isn't required. No OS was mentioned, so the capabilities of UFS aren't defined. For instance, the Solaris version of UFS has journalling/logging capabilities since the release of Solaris 7. -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOShttp://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area This line left intentionally blank to confuse you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Status 800 problem
Hey all, Anyone ever see this before: 4/4/2007 1:50:15 PM - requesting resource BOSPTCMEDIA1-NET 4/4/2007 1:50:15 PM - requesting resource ptcmaster.bosptc.intuit.com.NBU_CLIENT.MAXJOBS.itemptcdb2.bosptc.intuit. com 4/4/2007 1:50:15 PM - requesting resource ptcmaster.bosptc.intuit.com.NBU_POLICY.MAXJOBS.Hourly_Archive_Logs 4/4/2007 1:50:16 PM - Error nbjm(pid=603) NBU status: 800, EMM status: The robotic library is not defined in EMM resource request failed(800) All backup jobs are failing with this same error, and it happens immediately once the job goes active. It appears that the library definition is absent from the EMM server but I don't know how to fix this. I'm running NBU6.0 MP4, a Solaris 9 master and a Solaris 9 media server with 1 robot and 8 drives. I can inventory the robot and see it in device monitor. My EMM server for this environment should be the master and is defined as such in the bp.conf on both the master and media server. Any help is appreciated. TIA, Dave ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Migration Help from 5.1 to 6.0 policy configuration only
Hello, I need some urgent help to do policy migration from 5.1 master server to 6.0 master server. I only need the policy information and nothing else. Additionally this is on very tight deadline and I need an answer. I would like to do my own research and I usually do, but do not have the time. So if anybody has quick and dirty way to do this please let me know as soon as you can. Thank you Denis Petrov ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Status 800 problem
Hi David, I have had this one before this was the fix from symantic: The problems when getting the status 800 is due to the EMM database believing there was no resource available (specific media, tape drives, or storage unit). The fact that you have had issues with the tape drives and I suspect that the EMM database believe there was some resource unavailable, would have caused the problem. The rebuild you did and then a restart (maybe a couple of controlled restarts), would have updated the EMM database (this can take a few minutes after a restart) and then when starting backups the status 800 should be cleared. For future reference, when getting issues that seem to be allocation related, but you know the system should have the resource the action that helps is; 1. Ensure no backups or restores are running. 2. Run the command /usr/openv/netbackup/bin/admincmd/nbrbutil -resetall to clear any allocation issues with the EMM database. 3. Controlled stop and restart of the NetBackup processes/daemons. Cheers, Edwin From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Cornely, David Sent: Wednesday, April 04, 2007 22:55 To: Veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Status 800 problem Hey all, Anyone ever see this before: 4/4/2007 1:50:15 PM - requesting resource BOSPTCMEDIA1-NET 4/4/2007 1:50:15 PM - requesting resource ptcmaster.bosptc.intuit.com.NBU_CLIENT.MAXJOBS.itemptcdb2.bosptc.intuit. com 4/4/2007 1:50:15 PM - requesting resource ptcmaster.bosptc.intuit.com.NBU_POLICY.MAXJOBS.Hourly_Archive_Logs 4/4/2007 1:50:16 PM - Error nbjm(pid=603) NBU status: 800, EMM status: The robotic library is not defined in EMM resource request failed(800) All backup jobs are failing with this same error, and it happens immediately once the job goes active. It appears that the library definition is absent from the EMM server but I don't know how to fix this. I'm running NBU6.0 MP4, a Solaris 9 master and a Solaris 9 media server with 1 robot and 8 drives. I can inventory the robot and see it in device monitor. My EMM server for this environment should be the master and is defined as such in the bp.conf on both the master and media server. Any help is appreciated. TIA, Dave ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Migration Help from 5.1 to 6.0 policy configuration
I need some urgent help to do policy migration from 5.1 master server to 6.0 master server. I only need the policy information and nothing else. Additionally this is on very tight deadline and I need an answer. I would like to do my own research and I usually do, but do not have the time. So if anybody has quick and dirty way to do this please let me know as soon as you can. I've copied /usr/openv/netbackup/db/class/* from a 5.1 machine to a new 6.0 machine. I don't know if it's supported, but it worked :-) -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOShttp://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area This line left intentionally blank to confuse you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Linux vs Solaris
Dear All, Thankx everybody for the compatibility info. We are going to use NetBackup Server for Linux x86. But Out NetBackup Clients are running on Solaris x86. (Around 40 machines) Can NetBackup Solaris client connect to NetBackup Linux server ? Pls help, Thankx Tharindu On 3/29/07, Marianne Van Den Berg [EMAIL PROTECTED] wrote: Have a look at the Compatibility Guide: http://seer.support.veritas.com/docs/278064.htm Regards Marianne -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tharindu Rukshan Bamunuarachchi Sent: 28 March 2007 16:15 To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] NetBackup Server for Solaris x86 Dear All, Can someone (from Veritas) confirm availability of following product? Veritas NetBackup Master Server for Solaris x86 (Not for SPARC; for x86) Thankx Tharindu -- Tharindu Rukshan Bamunuarachchi all fabrications are subject to decay ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu -- Tharindu Rukshan Bamunuarachchi all fabrications are subject to decay ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
