Re: [Veritas-bu] Saving restore requests
Have you checked for any entries in the admin log after firing off the command? -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of pwhelan0610 Sent: 08 April 2010 17:05 To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] Saving restore requests Does anyone know of a way to save the items clicked in the restore GUI to a file for rerunning from the command line in the future? Patrick +-- |This was sent by netbac...@whelan-consulting.co.uk via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Nic Utilization
Hi Heather If you have Cisco switches you can use EtherChannel (PAgP) which is very similar to LACP for port aggregation - you would want to load balance by source MAC. This should benefit your media servers depending on what backup devices they are writing to. You will also the need some kind of multipathing/load balancing software running on your backup servers. If your master server is a dedicated master you should simply configure it for failover as a 1Gb nic should be more than enough. What backup devices do you have on your media servers? If you have anything which can write faster than about 60 Mb p/s you should definitely get some load balancing setup The bp.conf setting will push data out of a specific interface on the client itself where possible so you would really be able to control which interface it goes to on the media server. You could add entries into the clients hosts file so different client send data to different interfaces on the server but that creates single points of failures and is a little messy Cheers Tal -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Heathe Kyle Yeakley Sent: 08 April 2010 21:34 To: Veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Nic Utilization I had a question about how everyone else utilizes the NICs inside your master and media servers. I have 1 master and 2 media. Like most systems these days, I have 3-4 NICs in each one. The administrator that setup our existing environment plumbed 1 NIC per machine, and the other NICs sit there, completely unused. At night, when our backup are running, it isn't unheard of for the NICs on all three machine to reach a high utilization level. This got me to thinking. I've read that you can set an option in the bp.conf file and have various clients backup to different interfaces on the same physical master and/or media server, but I've never actually deployed that feature. I've also heard of a technology called Link Aggregation Control Protocol (LACP) that allows you to tie multiple NICs together to increase the total bandwidth into your server. Does anyone else employ these technologies? Does everyone else just plumb one NIC and let the backups trickle in as fast as the LAN allows? Is there other aggregation technology out there that folks are using to utilize and squeeze more bandwidth out of those unused NICs? Thanks. - Heathe Kyle Yeakley ___ 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] retrying Error on job keeps going status 13
I had to replace the hardware on one of my media svers and now all my jobs on that media server end in status 13 Server O/S Windows 2003 Netbackup 6.5.3 Library Quantum (Adic) I2000 14 LTO2 drives Any ideas would surely be appreciated. Master server Job log 4/6/2010 10:01:33 AM - requesting resource scacidoc05-hcart2-robot-tld-0 4/6/2010 10:01:33 AM - requesting resource svcacibu1.NBU_CLIENT.MAXJOBS.scacidoc05 4/6/2010 10:01:33 AM - requesting resource svcacibu1.NBU_POLICY.MAXJOBS.1-doc05-test 4/6/2010 10:01:33 AM - granted resource svcacibu1.NBU_CLIENT.MAXJOBS.scacidoc05 4/6/2010 10:01:33 AM - granted resource svcacibu1.NBU_POLICY.MAXJOBS.1-doc05-test 4/6/2010 10:01:33 AM - granted resource 000385 4/6/2010 10:01:33 AM - granted resource IBMULTRIUM-TD213 4/6/2010 10:01:33 AM - granted resource scacidoc05-hcart2-robot-tld-0 4/6/2010 10:01:33 AM - estimated 0 kbytes needed 4/6/2010 10:01:35 AM - started process bpbrm (5340) 4/6/2010 10:01:44 AM - connecting 4/6/2010 10:01:44 AM - connected; connect time: 00:00:00 4/6/2010 10:01:45 AM - mounting 000385 4/6/2010 10:02:06 AM - mounted; mount time: 00:00:21 4/6/2010 10:02:07 AM - positioning 000385 to file 1396 4/6/2010 10:02:15 AM - Error bpbrm(pid=3740) could not write KEEPALIVE to COMM_SOCK 4/6/2010 10:02:43 AM - Error bpbrm(pid=3740) socket read failed, An existing connection was forcibly closed by the remote host. (10054) 4/6/2010 10:02:34 AM - positioned 000385; position time: 00:00:27 4/6/2010 10:02:34 AM - begin writing 4/6/2010 10:02:44 AM - Error bpbrm(pid=3740) could not send server status message 4/6/2010 10:02:55 AM - end writing; write time: 00:00:21 file read failed(13) Media server bpbkar log 10:50:39.706 AM: [5496.4724] 4 ov_log::OVInit: INF - Starting log file: F:\Program Files\Veritas\NetBackup\logs\BPBKAR\040610.LOG 10:50:39.706 AM: [5496.4724] 4 ov_log::OVInit: GENERAL Log Level: 2 10:50:39.706 AM: [5496.4724] 4 ov_log::OVInit: TCP Log Level: 3 10:50:39.706 AM: [5496.4724] 4 ov_log::OVInit: INF - the log mutex: 1776 BPBKAR NetBackup Backup/Archive 6.5GA [Oct 30 2008] Copyright 1993 - 2007 VERITAS Software Corporation All Rights Reserved. 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - WINSOCK.DLL Information: 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - Version: 2.0 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - Highest supported version: 2.2 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - Description: WinSock 2.0 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - System Status: Running 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - Max Sockets: 0 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - _pgmptr = 'F:\Program Files\Veritas\NetBackup\bin\bpbkar32.exe' 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - lpCmdLine = '-r 2678400 -ru root -dt 0 -to 300 -clnt scacidoc05 -class 1-doc05-test -sched Cumulative-Inc -st CINC -bpstart_to 300 -bpend_to 300 -read_to 300 -blks_per_buffer 127 -stream_count 4 -stream_number 4 -jobgrpid 962086 -use_otm -use_ofb -b scacidoc05_1270576234 -kl 400 -shm -fso -ct 13 ' 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - INI: drive=F, dir=\Program Files\Veritas\NetBackup 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - LOG: drive=F, dir=\Program Files\Veritas\NetBackup\logs 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - EXE: drive=F, dir=\Program Files\Veritas\NetBackup\bin 10:50:39.722 AM: [5496.4724] 2 date_debug: DAT - timezone: Pacific Standard Time, offset=28800, dst: Pacific Daylight Time 10:50:39.722 AM: [5496.4724] 2 date_debug: DAT - current time: 1270576239, 4/6/2010 10:50:39 AM 10:50:39.722 AM: [5496.4724] 2 date_debug: DAT - 01/01/94 UCT: 757382400, 12/31/1993 5:00:00 PM 10:50:39.722 AM: [5496.4724] 2 date_debug: DAT - 07/01/94 UCT: 773020800, 6/30/1994 5:00:00 PM 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - standard input handle = 548 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - standard output handle = 1848 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - standard error handle = 1856 10:50:39.722 AM: [5496.4724] 2 dtcp_setsocksize: TCP - setsockopt success on SO_RCVBUF: (socket: 548) (size: 33792) 10:50:39.722 AM: [5496.4724] 2 dtcp_setsocksize: TCP - setsockopt success on SO_SNDBUF: (socket: 548) (size: 33792) 10:50:39.722 AM: [5496.4724] 2 dtcp_setsocksize: TCP - setsockopt success on SO_RCVBUF: (socket: 1848) (size: 33792) 10:50:39.722 AM: [5496.4724] 2 dtcp_setsocksize: TCP - setsockopt success on SO_SNDBUF: (socket: 1848) (size: 33792) 10:50:39.722 AM: [5496.4724] 2 dtcp_setsocksize: TCP - setsockopt success on SO_RCVBUF: (socket: 1856) (size: 32768) 10:50:39.722 AM: [5496.4724] 2 dtcp_setsocksize: TCP - setsockopt success on SO_SNDBUF: (socket: 1856) (size: 32768) 10:50:39.737 AM: [5496.4724] 2 OVHasPrivileges: TCP - success: connection from host scacidoc05.landam.landamerica.net (10.212.171.38) bound to port (4551) 10:50:39.737 AM: [5496.4724] 4 tar_backup::V_SetupJobData: INF - dwJobData: 10:50:39.737 AM:
Re: [Veritas-bu] retrying Error on job keeps going status 13
What hardware did you change? Error 13/4 can be a real pain but they are often related to network issues or reading data off a file system. As this is happening to all your jobs it sounds network related Have you checked some of your system/NetBackup legacy logs? Also run a all log entries report on one of the job ids to check for more details regarding the error message Regards, Tal -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Preston, Douglas Sent: 12 April 2010 14:32 To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] retrying Error on job keeps going status 13 I had to replace the hardware on one of my media svers and now all my jobs on that media server end in status 13 Server O/S Windows 2003 Netbackup 6.5.3 Library Quantum (Adic) I2000 14 LTO2 drives Any ideas would surely be appreciated. Master server Job log 4/6/2010 10:01:33 AM - requesting resource scacidoc05-hcart2-robot-tld-0 4/6/2010 10:01:33 AM - requesting resource svcacibu1.NBU_CLIENT.MAXJOBS.scacidoc05 4/6/2010 10:01:33 AM - requesting resource svcacibu1.NBU_POLICY.MAXJOBS.1-doc05-test 4/6/2010 10:01:33 AM - granted resource svcacibu1.NBU_CLIENT.MAXJOBS.scacidoc05 4/6/2010 10:01:33 AM - granted resource svcacibu1.NBU_POLICY.MAXJOBS.1-doc05-test 4/6/2010 10:01:33 AM - granted resource 000385 4/6/2010 10:01:33 AM - granted resource IBMULTRIUM-TD213 4/6/2010 10:01:33 AM - granted resource scacidoc05-hcart2-robot-tld-0 4/6/2010 10:01:33 AM - estimated 0 kbytes needed 4/6/2010 10:01:35 AM - started process bpbrm (5340) 4/6/2010 10:01:44 AM - connecting 4/6/2010 10:01:44 AM - connected; connect time: 00:00:00 4/6/2010 10:01:45 AM - mounting 000385 4/6/2010 10:02:06 AM - mounted; mount time: 00:00:21 4/6/2010 10:02:07 AM - positioning 000385 to file 1396 4/6/2010 10:02:15 AM - Error bpbrm(pid=3740) could not write KEEPALIVE to COMM_SOCK 4/6/2010 10:02:43 AM - Error bpbrm(pid=3740) socket read failed, An existing connection was forcibly closed by the remote host. (10054) 4/6/2010 10:02:34 AM - positioned 000385; position time: 00:00:27 4/6/2010 10:02:34 AM - begin writing 4/6/2010 10:02:44 AM - Error bpbrm(pid=3740) could not send server status message 4/6/2010 10:02:55 AM - end writing; write time: 00:00:21 file read failed(13) Media server bpbkar log 10:50:39.706 AM: [5496.4724] 4 ov_log::OVInit: INF - Starting log file: F:\Program Files\Veritas\NetBackup\logs\BPBKAR\040610.LOG 10:50:39.706 AM: [5496.4724] 4 ov_log::OVInit: GENERAL Log Level: 2 10:50:39.706 AM: [5496.4724] 4 ov_log::OVInit: TCP Log Level: 3 10:50:39.706 AM: [5496.4724] 4 ov_log::OVInit: INF - the log mutex: 1776 BPBKAR NetBackup Backup/Archive 6.5GA [Oct 30 2008] Copyright 1993 - 2007 VERITAS Software Corporation All Rights Reserved. 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - WINSOCK.DLL Information: 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - Version: 2.0 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - Highest supported version: 2.2 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - Description: WinSock 2.0 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - System Status: Running 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - Max Sockets: 0 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - _pgmptr = 'F:\Program Files\Veritas\NetBackup\bin\bpbkar32.exe' 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - lpCmdLine = '-r 2678400 -ru root -dt 0 -to 300 -clnt scacidoc05 -class 1-doc05-test -sched Cumulative-Inc -st CINC -bpstart_to 300 -bpend_to 300 -read_to 300 -blks_per_buffer 127 -stream_count 4 -stream_number 4 -jobgrpid 962086 -use_otm -use_ofb -b scacidoc05_1270576234 -kl 400 -shm -fso -ct 13 ' 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - INI: drive=F, dir=\Program Files\Veritas\NetBackup 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - LOG: drive=F, dir=\Program Files\Veritas\NetBackup\logs 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - EXE: drive=F, dir=\Program Files\Veritas\NetBackup\bin 10:50:39.722 AM: [5496.4724] 2 date_debug: DAT - timezone: Pacific Standard Time, offset=28800, dst: Pacific Daylight Time 10:50:39.722 AM: [5496.4724] 2 date_debug: DAT - current time: 1270576239, 4/6/2010 10:50:39 AM 10:50:39.722 AM: [5496.4724] 2 date_debug: DAT - 01/01/94 UCT: 757382400, 12/31/1993 5:00:00 PM 10:50:39.722 AM: [5496.4724] 2 date_debug: DAT - 07/01/94 UCT: 773020800, 6/30/1994 5:00:00 PM 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - standard input handle = 548 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - standard output handle = 1848 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - standard error handle = 1856 10:50:39.722 AM: [5496.4724] 2 dtcp_setsocksize: TCP - setsockopt success on SO_RCVBUF: (socket: 548) (size: 33792) 10:50:39.722 AM: [5496.4724] 2 dtcp_setsocksize: TCP - setsockopt success on SO_SNDBUF: (socket: 548) (size: 33792) 10:50:39.722 AM: [5496.4724] 2 dtcp_setsocksize: TCP - setsockopt success on
Re: [Veritas-bu] retrying Error on job keeps going status 13
This was a scsi backplane on a dell server. It controlled my O/S drives. We replaced server with an IBM server and had to reinstall O/S, Installed two new Fiber cards fro san and tape library connections, Re did all zoning and updated all drives and O/S updates to the very latest of all drivers and patches as of 19:00 hours yesterday. I have a case open with support and they had me try the patch from http://support.microsoft.com/kb/940349 I rebooted the server after applying the patch This patch did not fix issue. Doug Preston -Original Message- From: Shekel Tal [mailto:tal.she...@uk.fujitsu.com] Sent: Monday, April 12, 2010 6:51 AM To: Preston, Douglas; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] retrying Error on job keeps going status 13 What hardware did you change? Error 13/4 can be a real pain but they are often related to network issues or reading data off a file system. As this is happening to all your jobs it sounds network related Have you checked some of your system/NetBackup legacy logs? Also run a all log entries report on one of the job ids to check for more details regarding the error message Regards, Tal -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Preston, Douglas Sent: 12 April 2010 14:32 To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] retrying Error on job keeps going status 13 I had to replace the hardware on one of my media svers and now all my jobs on that media server end in status 13 Server O/S Windows 2003 Netbackup 6.5.3 Library Quantum (Adic) I2000 14 LTO2 drives Any ideas would surely be appreciated. Master server Job log 4/6/2010 10:01:33 AM - requesting resource scacidoc05-hcart2-robot-tld-0 4/6/2010 10:01:33 AM - requesting resource svcacibu1.NBU_CLIENT.MAXJOBS.scacidoc05 4/6/2010 10:01:33 AM - requesting resource svcacibu1.NBU_POLICY.MAXJOBS.1-doc05-test 4/6/2010 10:01:33 AM - granted resource svcacibu1.NBU_CLIENT.MAXJOBS.scacidoc05 4/6/2010 10:01:33 AM - granted resource svcacibu1.NBU_POLICY.MAXJOBS.1-doc05-test 4/6/2010 10:01:33 AM - granted resource 000385 4/6/2010 10:01:33 AM - granted resource IBMULTRIUM-TD213 4/6/2010 10:01:33 AM - granted resource scacidoc05-hcart2-robot-tld-0 4/6/2010 10:01:33 AM - estimated 0 kbytes needed 4/6/2010 10:01:35 AM - started process bpbrm (5340) 4/6/2010 10:01:44 AM - connecting 4/6/2010 10:01:44 AM - connected; connect time: 00:00:00 4/6/2010 10:01:45 AM - mounting 000385 4/6/2010 10:02:06 AM - mounted; mount time: 00:00:21 4/6/2010 10:02:07 AM - positioning 000385 to file 1396 4/6/2010 10:02:15 AM - Error bpbrm(pid=3740) could not write KEEPALIVE to COMM_SOCK 4/6/2010 10:02:43 AM - Error bpbrm(pid=3740) socket read failed, An existing connection was forcibly closed by the remote host. (10054) 4/6/2010 10:02:34 AM - positioned 000385; position time: 00:00:27 4/6/2010 10:02:34 AM - begin writing 4/6/2010 10:02:44 AM - Error bpbrm(pid=3740) could not send server status message 4/6/2010 10:02:55 AM - end writing; write time: 00:00:21 file read failed(13) Media server bpbkar log 10:50:39.706 AM: [5496.4724] 4 ov_log::OVInit: INF - Starting log file: F:\Program Files\Veritas\NetBackup\logs\BPBKAR\040610.LOG 10:50:39.706 AM: [5496.4724] 4 ov_log::OVInit: GENERAL Log Level: 2 10:50:39.706 AM: [5496.4724] 4 ov_log::OVInit: TCP Log Level: 3 10:50:39.706 AM: [5496.4724] 4 ov_log::OVInit: INF - the log mutex: 1776 BPBKAR NetBackup Backup/Archive 6.5GA [Oct 30 2008] Copyright 1993 - 2007 VERITAS Software Corporation All Rights Reserved. 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - WINSOCK.DLL Information: 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - Version: 2.0 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - Highest supported version: 2.2 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - Description: WinSock 2.0 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - System Status: Running 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - Max Sockets: 0 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - _pgmptr = 'F:\Program Files\Veritas\NetBackup\bin\bpbkar32.exe' 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - lpCmdLine = '-r 2678400 -ru root -dt 0 -to 300 -clnt scacidoc05 -class 1-doc05-test -sched Cumulative-Inc -st CINC -bpstart_to 300 -bpend_to 300 -read_to 300 -blks_per_buffer 127 -stream_count 4 -stream_number 4 -jobgrpid 962086 -use_otm -use_ofb -b scacidoc05_1270576234 -kl 400 -shm -fso -ct 13 ' 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - INI: drive=F, dir=\Program Files\Veritas\NetBackup 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - LOG: drive=F, dir=\Program Files\Veritas\NetBackup\logs 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - EXE: drive=F, dir=\Program Files\Veritas\NetBackup\bin 10:50:39.722 AM: [5496.4724] 2 date_debug: DAT - timezone: Pacific Standard Time, offset=28800, dst: Pacific Daylight Time 10:50:39.722 AM: [5496.4724] 2
[Veritas-bu] NDMP multiple streams using NEW_STREAM directive bug: 6.5.3.1
Hello, Running into a new issue this week. I'm using NDMP option pack 6.5.3, and have read through the 6.5.4 release notes and nothing in there shows a fix to my issue (no new 6.5.5 NDMP MP was released). Anyone ever seen this happen? - An NDMP policy has multiple streams enabled, and NEW_STREAM directives within the selection list - The policy's schedules (any of them, daily, weekly, monthly, full, incr, diff, etc) will launch at the scheduled time under frequency-based scheduling. - When the backup backup completes, if the backup window is still open, the same schedule's backup will re-start exactly 1 minute after the backup completes. - This second backup will fail with SC 196, even though the backup window is open. It basically looks like the frequency of the backup is being enforced, but not by the scheduler, so it throws out fake status code 196's. This has only started happening since we added in the NEW_STREAM directives. Other NDMP policies setup in a similar manner (multi-stream, etc) all behave normally. Cheers, Jon La version française suit le texte anglais. This email may contain privileged and/or confidential information, and the Bank of Canada does not waive any related rights. Any distribution, use, or copying of this email or the information it contains by other than the intended recipient is unauthorized. If you received this email in error please delete it immediately from your system and notify the sender promptly by email that you have done so. Le présent courriel peut contenir de l'information privilégiée ou confidentielle. La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute diffusion, utilisation ou copie de ce courriel ou des renseignements qu'il contient par une personne autre que le ou les destinataires désignés est interdite. Si vous recevez ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans délai à l'expéditeur un message électronique pour l'aviser que vous avez éliminé de votre ordinateur toute copie du courriel reçu. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Upgrading Standard/Business Server to Enterprise
Has anyone upgrade a Business Server (or whatever the lite version is called) to an Enterprise edition? Is it just the license key? Regards, Patrick Whelan VERITAS Certified NetBackup Support Engineer for UNIX. VERITAS Certified NetBackup Support Engineer for Windows. mailto:netbac...@whelan-consulting.co.uk netbac...@whelan-consulting.co.uk http://www.linkedin.com/in/patrickjosephwhelan cid:image001.gif@01C99E80.E2717A60 image001.gifimage002.gif___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Backups not running, just stuck at Connecting.
Thanks for everyone reply. Much appreciated. Managed to solve the problem by rebooting the server. Still don't know what was the real cause behind it all. Strange ! [Shocked] +-- |This was sent by rtm...@yahoo.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] NBU and BMR - QLogic SAN driver incompatabilities
Been getting this error message for a while now in the BMR info collection phase of backups for servers running QLOGIC SAN drivers: Received BMR error: The driver 'QLogic Fibre Channel Adapter', of Version '9.1.8.17' is not compatible with WindowsPE. You may need to create a driver package using an earlier version of the driver that was WindowsPE compatible. (1) Other than back-leveling the QLOGIC drives on SAN-connected servers, has anyone found a way around this error so the QLOGIC drivers get installed along with the all the other drivers during the BMR recovery??? And just as an FYI: We have so far been unable to find a way to reconnect data-loaded SAN LUNS to BMR recovered servers without being forced to format the LUNS at reconnect time. That is another interesting situation, after the QLOGIC drivers have been manually re-installed following the BMR recovery. We are running NBU 6.5.5. on Windows 64-bit Master Servers. Thanks Much, Ed Scheef Tampa Electric Company (TECO Energy, Inc.) NOTICE: This email is intended only for the individual(s) to whom it is addressed and may contain confidential information. If you have received this email by mistake, please notify the sender immediately, delete this email from your system and do not copy or disclose it to anyone else. Although we take precautions to protect against viruses, we advise you to take your own precautions to protect against viruses as we accept no liability for any which remain. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Backup starts off strong, then does not complete.
Veritas Netbackup 5.1 environment Client = windows 2000 server media server = unix master server = unix - Backup unable to complete (full or incremental) - Starts of fine, tape gets mounted and writing starts. - Write speed is very good at the start, as shown below (rmt/1). - Backup progress goes from 0% - 26% very quickly, with 273664KB (1500 files) written. - I also noticed that when I kick start the backup, I see 6 bpbkar32.exe and bpfix.exe process threads in the Windows Task Manager. Is this normal? extended device statistics r/sw/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device 0.01.00.00.5 0.0 0.00.03.5 0 0 c1t0d0 0.01.00.00.5 0.0 0.00.03.5 0 0 c1t0d0s3 0.01.00.00.5 0.0 0.00.07.0 0 1 c1t1d0 0.01.00.00.5 0.0 0.00.07.0 0 1 c1t1d0s3 0.0 45.00.0 11519.9 0.0 0.10.01.5 0 7 rmt/1 - After that, I notice that after 3 hours, the completion rate is still at 26%. No changes in the number of files written. - The write speed then just drops to about 11 kw/s. - Finally the backup either ends with a code 54 or a 150. Please advice. Thank you in advance. +-- |This was sent by rtm...@yahoo.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Backup starts off strong, then does not complete.
What does your selection list look like? If you are using ALL_LOCAL_DRIVES I would break it up into the individual disks and run the policy one by one to see if a certain disk or volume is causing the issue. Have you looked in the tar log on the client? I've had issues similar to this on both Windows and Solaris servers when disks and/or file systems are going bad. -Jonathan ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Backup starts off strong, then does not complete.
I had this type of problem on some hpux file systems a few years ago. The problem was a user script that had gone bad and generated several million files in 1 directory. Netbackup started walking down that directory and basically never came out. The processes timed out because of it. Try what Jonathan said and back up smaller pieces at a time until you identify where it is failing. Jeff You might try checking the file system directories. On Mon, Apr 12, 2010 at 2:26 PM, LemonRuski netbackup-fo...@backupcentral.com wrote: Veritas Netbackup 5.1 environment Client = windows 2000 server media server = unix master server = unix - Backup unable to complete (full or incremental) - Starts of fine, tape gets mounted and writing starts. - Write speed is very good at the start, as shown below (rmt/1). - Backup progress goes from 0% - 26% very quickly, with 273664KB (1500 files) written. - I also noticed that when I kick start the backup, I see 6 bpbkar32.exe and bpfix.exe process threads in the Windows Task Manager. Is this normal? extended device statistics r/sw/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device 0.01.00.00.5 0.0 0.00.03.5 0 0 c1t0d0 0.01.00.00.5 0.0 0.00.03.5 0 0 c1t0d0s3 0.01.00.00.5 0.0 0.00.07.0 0 1 c1t1d0 0.01.00.00.5 0.0 0.00.07.0 0 1 c1t1d0s3 0.0 45.00.0 11519.9 0.0 0.10.01.5 0 7 rmt/1 - After that, I notice that after 3 hours, the completion rate is still at 26%. No changes in the number of files written. - The write speed then just drops to about 11 kw/s. - Finally the backup either ends with a code 54 or a 150. Please advice. Thank you in advance. +-- |This was sent by rtm...@yahoo.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu -- Jeff Cleverley Unix Systems Administrator 4380 Ziegler Road Fort Collins, Colorado 80525 970-288-4611 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NBU and BMR - QLogic SAN driver incompatibilities
Ed, I asked Symantec about this and was told the issue will be resolved in NBU 7 with the new version of Windows PE 2.1. The new version of PE will support the newer QLogic drivers. Dwayne Adams From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Scheef Jr, Ed E. Sent: Monday, April 12, 2010 1:18 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] NBU and BMR - QLogic SAN driver incompatabilities Been getting this error message for a while now in the BMR info collection phase of backups for servers running QLOGIC SAN drivers: Received BMR error: The driver 'QLogic Fibre Channel Adapter', of Version '9.1.8.17' is not compatible with WindowsPE. You may need to create a driver package using an earlier version of the driver that was WindowsPE compatible. (1) Other than back-leveling the QLOGIC drives on SAN-connected servers, has anyone found a way around this error so the QLOGIC drivers get installed along with the all the other drivers during the BMR recovery??? And just as an FYI: We have so far been unable to find a way to reconnect data-loaded SAN LUNS to BMR recovered servers without being forced to format the LUNS at reconnect time. That is another interesting situation, after the QLOGIC drivers have been manually re-installed following the BMR recovery. We are running NBU 6.5.5. on Windows 64-bit Master Servers. Thanks Much, Ed Scheef Tampa Electric Company (TECO Energy, Inc.) NOTICE: This email is intended only for the individual(s) to whom it is addressed and may contain confidential information. If you have received this email by mistake, please notify the sender immediately, delete this email from your system and do not copy or disclose it to anyone else. Although we take precautions to protect against viruses, we advise you to take your own precautions to protect against viruses as we accept no liability for any which remain. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
