Impressions of BackupExec 2012
Is it just me, or does anyone else absolutely HATE the redesign of Backup Exec? I have worked with BE since version 8, and I have become acutely familiar with the menus, where everything is, and how it works. This redesign of the UI reminds me of the differences between Microsoft Office 2003 and Office 2007, only much worse. Menus are now hidden behind other menus, and everything has a completely counter-intuitive feel. At first, I thought that the feeling would pass as I grew more familiar with the product, but in fact my dislike has grown as I have found more issues. Does anyone else feel the same way?22KViews56likes417CommentsNetBackup Basics and how to make YOUR life easier ...
This entry is intended to cover a number of issues that I see time and time again with members posting questions on the forum, and from my experience as a NBU TSE. The advice below is intended ... (1) To make your life easier (2) To assist in making a quicker resolutions (A) Command Issues *************** A common question - Where is the <command> I cannot find it ? The vast majorty of NetBackup binaries are located in the following directories, therfore by simple looking, you should find the command. You could also search, using the search feature in windows, or the find command in Unix. Unix/ Linux /usr/openv/netbackup/bin /usr/openv/netbackup/bin/support /usr/openv/netbackup/bin/admincmd /usr/openv/volmgr/bin There are also so 'scripts' available in /usr/openv/netbackup/bin/goodies Windows <install path>\veritas\netbackup\bin <install path>\veritas\netbackup\bin\support <install path>\veritas\netbackup\bin\admincmd <install path>\veritas\volmgr\bin There are also some 'scripts' available in <install path>\veritas\netbackup\bin\goodies It is even easier, if you add these paths to the PATH variable of the operating system. This allows you to run commands without having to type in the comlete path each time, or, cd to the directory. Unix: Add the directories to the PATH variable in the .profile file in the home directory of the user you log in as. For example ; PATH=$PATH:/usr/openv/netbackup/bin/admincmd:/usr/openv/netbackup/bin:/usr/openv /netbackup/bin/goodies:/usr/openv/netbackup/bin/support:/usr/openv/volmgr/bin:/u sr/openv/java:/netbackup:/opt/sfw/bin:/netbackup/scripts:/opt/VRTSaz/bin/vxazd:/ opt/VRTSat/bin/:/opt/VRTSaz/bin/:/opt/vormetric/mseo/server/bin:/opt/vormetric/m seo/agent/bin:/usr/openv/db/bin Windows: Add the directories the the PATH user variable (Right click computer, Properties, Advanced System Settings, Environment Variables (Path is under System variable ), For example. C:\Perl\site\bin;C:\Perl\bin;C:\Oracle\Ora92\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\Program Files\RSA SecurID Token Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files\Symantec\pcAnywhere\;C:\Program Files\QuickTime\QTSystem\;C:\Program Files\Enterprise Vault\EVClient\;C:\Program Files\Symantec\Workspace Virtualization\;C:\Program Files\Veritas\NetBackup\bin;C:\Program Files\Veritas\NetBackup\bin\admincmd (B) Insufficient information ************************ Starting a post with a question such as ... My media is getting frozon during a job, what do I do ? .. is virtually useless, EVERY post should be started with information simailar to these questions ... Initial Information recommended for all issues: 1. The exact error message (if an error is given) 2. During which type of operation does the problem occur ? For example, Backup, Duplication, Vault, Restore etc. 3. At what point in the job does the issue occur, for example, right at the beginning. 4. Which system(s) are involved? For example, Master Server, Media Server - Please provide system names. 5. Please submit the support report from the master and any relevant Media Servers in the environment. 6. Is this a reoccurring issue ? 7. What was the system doing at this time ? 8. Please send in the contents of the details tab in the Activity Monitor for the job. 9. What logs or screenshots are available? 10. Has this worked previously? If so, when was the last time it DID work? 11. Have there been any environmental; system; or configuration changes? 12. When did the problem begin? 13. How often does the problem occur? 14. Is a similar configuration working properly? (C) Is NetBackup the cause ********************** Many NetBackup issues, commonly, Tape/ Library issues and Networking issues are nothing to do with NBU, and the issue cannot be fixed through NetBackup commands. NetBackup often reports and issue, but is nothing to do with the cause. Consider this: If you uninstall NetBackup, what are you left with ??? Hopefully ... An operating system A network Storage devices, tape or disk So. straight away, it can been seen that that these three things are totally separate from NBU. Clearly there is 'interaction' between them, for example, tape drives are 'configured' in NetBackup after all, but NetBAckup does not control these and if the advice given is to investigate from a hardware perspective, or OS issue, this is exactly what needs to be done. In my experience, the majority of Network and Tape /Library issues have nothing to do with NetBackup, and the investigation should start with the vendor / network support. (D) NetBackup Engineers are not hardware engineers. If you have a hardware issue, speak to hardware type people ... (E) Document your system. Any backup environment should be documented, with the documents kept up-to-date. An excellent start to this is to run : nbsu -c -t every day and keep the outputs, (perhaps back them up to tape.) You will note I have not told you exactly where this command is, please see point (A). (F) Logs: On occassion, we will ask for logs ... See this technote, it contains everything you need to know. http://www.symantec.com/docs/TECH75805 When you send logs in, if the issue happens at say 15.00, we don't need the past weeks worth of logs, edit the log down so you send in for example, 14.30 - 16-00. (Note, sometimes the logs will be needed for a longer period, but usually / generally, the logs areound the time of the issue are fine). Also, please rename logs to the process name (NOT for the case of Unified logs (see technote above).) NetBackup defines different (legacy) logs simply by the folder name they are in, which isn't ideal. This means if we ask for say bptm and bpbrm log, both will have exactly the same filename (log.<date>). Please rename these to <process_name>.log.<date> ) The nbcplogs command is very good, it simplifies the collections of logs. Have a go at learning to use this command. http://www.symantec.com/docs/HOWTO43784 You should be able to set up logs without assistance, all that should be required is that we ask, pleased send bptm, bpbrm logs from the media server, or, please send vx logs 111, 116, 117, 118. You should automatically know that these should be gathered, probably with the verbose levels increased. (G) Every log sent in for a problem, must cover the same time period. It is no good sending in bptm from Monday and bpbrm from Tuesday, yes, people actually do this ... (H) If we ask for (example) bpmedialist -m <media id>, please DO NOT send the binary. Please run the command and send the output. I'm sure your binaries are very nice, but I have some of my own - thanks. (I) Our favorite question is "What changed". The usual answer is "Nothing has changed". Generally speaking, NBU does NOT break on it's own, 99% of the time, something HAS changed. I've not yet worked out if people just have no idea who is changeing what and when, or if they just deny making any changes - but if a change has been made, we will find it, it just may take considerable time, adding days or even weeks to the time it takes to resolve an issue. It's better to be truthful and say "I am not aware of any changes" than categorically deny that any changes have been made. (J) If you make a change, write it down somewhere (preferably in a change file on the system) - see (I) above (K) Backups fail, get used to this idea, it is part of being a backup administrator. Do NOT start making changes because of a single failure, this leads to broken systems. (L) If you make a change, and it does not fix the problem, revert it. DO NOT MAKE MULTIPLE CHANGES WITHOUT RECORDING THEM. It can be very very difficult to find an issue, if multiple changes have been made that cause the same symptoms. Consider this : I go home and the light does not work. (Unknown to me, the fuse is broken) I have three possibilities The light switch is broken The light bulb is broken The fuse is broken I decide to change the bulb, unfortunately the bulb I put in is also broken. (I have now introduced another 'fault' that gives the same symptoms as the originally fault). Next I change the fuse, but due to the broken buld, the light does not work. Unknown to me, I have now fixed the originally issue, but I cannot tell due to the faulty bulb fitted, So, from this example you can see how it is possoible to to completely break a system - avoid doing this. (M) NetBackup Engineers are not network engineers, if you have a network issue, go and talk to network type people (N) Just because NetBackup reports and error, DOES NOT mean it caused the error. This is particularly true for network, tape and library issues. (O) Read this - http://www.symantec.com/docs/TECH169477 If your systems/ issue fits a description in the technote, no matter how many times you ask, the answer will be the same. (P) Hardware vendors often blame NBU, especially when it comes to tape/ library issues. This is why the technote in (O) was written, to help prove that NBU is not at fault. (Q) Any backup system MUST be designed before being installed, else it WILL fail. Backup design does NOT start with pressing buttons, it starts with a peice of papaer and a pen. (R) If you want to know how to do something, try looking in the manuals. MASTER Compatibility list: http://www.symantec.com/docs/TECH59978 Master Download List : http://www.symantec.com/docs/TECH65429 Late Breaking News Links : http://www.symantec.com/docs/TECH74904 NBU 6.5 Documentation: http://www.symantec.com/docs/TECH52878 NBU 7.0 Documentation: http://www.symantec.com/docs/TECH126327 NBU 7.1 Documentation: http://www.symantec.com/docs/TECH154178 NBU 7.5 Documentation: http://www.symantec.com/docs/DOC5138 HOWTO Videos: http://www.symantec.com/docs/HOWTO41825 (S) These are the 'minimum' skills thay ANY NetBackup Administrator should have ... 1/ Create and correctly collect NetBackup logs for a given time period ( see http://www.symantec.com/docs/TECH75805 ) 2/ Understand when NetBackup probably isn't the cause (see http://www.symantec.com/docs/TECH169477 ) 3/ Understand Operating system commands to list attached hardware, change /create directory, edit a file, configure network 4/ Understand basic NetBackup concepts : Setting up policies Configure devices via Device Wizard Delete devices Use and undersnd trhe meaning of results in scan/ tpautoconf / scsi_command (hint, see point (O) Understand on which machine the basic NBU processes run Run backups from the GUI Run restores from the GUI Master = nbemm/ bprd/ nbjm/ nbemm Media = bpbrm / bptm Client = bpcd / bpbkar / tar Understand the basic principles of a catalog backup and how to set it up Understand that NetBackup DOES NOT CONTROL your network, we ONLY use what we are given Understand that NetBackup does NOT write/ read to/ from tape - this is done by the operating system Understand the idea of 'density' (eg. hcart, hcart2 etc ...) Understand barcode rules, media id generation rules and how to set them up Understand how to inventory a library Understand how to use the robtest command and the meaning of the output Undersnad the difference between multi-streaming and multi-plexing Understand the idea of storage units Understand the idea of media pools If you are stuck on any of these, first thing, see point (R) (T) It is not the job of people on the forum (or Symantec support) to read the manuals for you (U) If something is unsupported (ie. not in the manuals) DO NOT DO IT. (V) When you are asked to do steps 1, 2, 3, 4, 5 Please ensure you do ALL the steps, and not just the ones you feel like doing. We don't ask for the steps because we have nothing better to do, we ask for them because we need ALL of them. (W) Please do not make changes just because you can. Any change to a system should be fully justified, researched, and recorded accurately in the system documentation. The system documentation should be so detailed, it contains every change made and when, and the current setting of EVERYTHING that has been changed from the default- are you doing this ? Regards, Martin7.1KViews41likes39CommentsError writing security data stream
I have a Windows 2003 server with 9 drives running Oracle 9i. On Monday, drives J & K failed and we lost ALL data on these 2 drives. Drive J contained SWAN02.ORA, SWINDX02.ORA, and USER01.ORA. Drive K contained RBS01.ORA, RBS02.ORA, ORATEMP.ORA & UNDOTBS10.ORA. These files were all backed up about 8 hours prior to the drive crash using the BE Oracle Agent. I now need to restore all files from J & K back to the repaired drives. Currently, Oracle is NOT running because of these missing data files. Data on other drives was NOT affected. When I attempt the restore using the Oracle Agent in BE, I receive the message "Error writing security data stream" for all files and then they are skipped. Any suggestions?871Views26likes1CommentDeduplication folder stays offline
Forum, We upgraded Backup Exec from 2010-R3 to 2012-SP1. We have the dedupe option for both versions. The upgrade was done two weeks ago and we have been running dedupe jobs successfully. Now the deduplication folder will not come online. We have about 10TB of backups extending back 6 months. Under “Storage” this message is displayed next to the dedupe folder: This device has not been discovered correctly. Cycle the services on _CoSRV-BEX to retry device discovery. This alert is also logged: Backup Exec was unable to initialize and communicate with the device [SYMANTECOstLdr MACF] (The handle is invalid.). Click the link below for more information on how to diagnose the problem. http://www.symantec.com/business/support/index?page=answers&startover=y&question_box=V-275-1017 note the above link is for 2010, not 2012. Actions taken: Using the BE Services mgr, the services were recycled (many times) – no improvement. The server was rebooted – no improvement. Using the BE Services mgr, the services (including the dedupe services) were recycled – no improvement. The server and drive array were powered off and powered back on. All is normal. We did recycle the services with and without the dedupe services after this power up - no improvement. FYI We have a Dell PowerEdge R710 and an MD1200 array for the local D: drive, which has the dedup folder and nothing else. The server runs Win Server 2008R2 and has 64GB RAM. There are no hardware errors. The physical array is normal and drive D can be browsed. Live Update shows we are up-to-date. Some google searches suggest solutions for 2010, not 2012 . . . that the solution is to remove the target servers from the devices window, and disable client side dedupe. How can that be done in 2012? I have opened a support ticket with Symantec, but I cannot get them to call me back. Symantec advises that they will have the Deduplication support team call me back. I was promised a call back 3 ½ hours ago, but that hasn’t happened. I have called back twice with the ticket number and been shunted over to the voice mail of engineer that owns the ticket. Is there any hope for this? Should I look for a replacement to Backup Exec? ... Frustrated and hoping we don't have to restore anything.Solved4.2KViews25likes2CommentsOpsCenter Status Code "HTTP Status 503 - Servlet action is currently unavailable"
We had a vendor install the latest OpsCenter for us. They have since come and gone and our team never verified it was working. When we click on the web UI login we immedietly get the 503 status. I'm not having much luck online in looking for possible remedies. Would love suggestions on troubleshooting and correcting this.520Views23likes0CommentsGlossary - To make sense of the alphabet soup
Below is a glossary of acronyms and terms used in this forum AD Active Directory ADAMM Advanced Device And Media Management ADRA Active Directory Recovery Agent AES Advanced Encryption Standard AFE Automatic File Exclusion AMHV Agent for Microsoft Hyper-V AOF Advanced Opened File BE 2012 and above AOFO Advanced Opened File Option Up to BE 2010 AP Append Period AVVI Agent for VMWare Virtual Infrastructure B2D Backup-to-Disk B2D2T Backup-to-Disk and then to tape B2V Backup-to-Virtual BE 2012 and above BE Backup Exec BEMCMD Backup Exec Commandline Applet Up to BE 2010 BEMCLI Backup Exec Management Command Line Interface BE 2012 and above BESA Backup Exec Service Account BESR Backup Exec System Recovery CAS Client Access Server (used in relation with Exchange) CAS Central Admin Server CASO Central Admin Server Option CCR Cluster Continuous Replication(for Exchange) CDO Collaboration Data Ojects CIFS Common Internet File System CPS Continuous Protection Server Up to BE 2010 CSV Cluster Shared Volume DAG Database Availability Group DAOS Domino Attachment and Object Storage DC Domain Controller DDI Device Driver Installer dedup deduplication DFS Distributed File System DLO Desktop & Laptop Option DLM Data Life-cycle Management BE 2012 and above DR Disaster Recovery DSF DeDuplication Storage Folder ELS Enterprise Licensing System BE 2012 and above EMT Exchange Management Tool EV Enterprise Vault FC Fibre Channel GA General Availability GAL Global Address List GRT Granular Recovery Technology HCL Hardware Compatibility List IDR Intelligent Disaster Recovery Up to BE 2010 IPL In-Product Licensing BE 2012 and above LCR Local Continuous Replication (for Exchange) LEO Library Expansion Option LU LiveUpdate LUN logical unit number MAPI Messaging API MBES Managed Backup Exec Server BE 2012 and above media server machine where BE is loaded MITM man-in-the-middle (attack) MMS Managed Media Server Up to BE 2010 MOSS Microsoft Office SharePoint Server NAS Network-attached Storage NBU NetBackup NDMP Network Data Management Protocol NFR Not For Resale NSF or .nsf Lotus Domino mail database file OP original post - first post in the discussion OPL Overwrite Protection Level OPP Overwrite Protection Period OST Open Storage Technology P2V Physical-to-Virtual RALUS Remote Agent for Linux and Unix System RAMS Remote Agent for Macintosh Systems RAWS Remote Agent for Windows System RDM Raw Disk Mapping remote server machine that is backed up by BE RHEL Red Hat Enterprise Linux RMALS Remote Media Agent for Linux Servers RPO Recovery Point Objective RSG Recovery Storage Group RTO Recovery Time Objective SAN Storage Area Network SBE Small Businness Edition SBS Small Businness Server SCL Software Compatibility List SDR Simplified Disaster Recovery BE 2012 and above SEP Symantec Endpoint Protectioni SLF Symantec License File BE 2012 and above SP service pack SSO Shared Storage Option SSP Simplified System Protection BE 2012 and above SSR Symantec System Recovery UNC Universal Naming Convention VCB VMware Consolidated Backup VM Virtual Machine VTL Virtual Tape Library VSP VERITAS Volume Snapshot Provider VSS Volume Snapshot Service or Volume Shadow Copy Service WORM Write Once, Read Many WSS Windows SharePoint Services1.1KViews23likes11CommentsFailed authentication on only ONE server
Hi, I recently had to reset the pw that the BE software uses. I have 8 servers that run BE, some using v9.1 and some still using v8.6. Some of them backup just the server they run on, some of them backup workstations and other servers, as well. I have a win2k domain. I reset the pw on the backup exec service account which is a member of the domain admin group. Then I reset the pw in all instances of BE on all the servers. 7 of them are fine with the pw change, the 8th one gives me authentication failure as soon as I try to run the job. All servers are running win2k, all are using the EXACT SAME account for BE. Obviously I have already tried resetting the server in question but that doesnt work. I dont understand how this could work on 7 out of 8 servers, and not the 8th. It was working fine on all the servers before I reset the pw. Suggestions? Sharyn551Views20likes2CommentsBackup Exec 2012
I get this message after upgrade of BEDB from 12.5 to 14.0 After upgrade to Backup Exec 2012 from previous versions all jobs fail with Dispatch failed status and following error is seen “Unable to load the job configuration information. What should I do?!Solved1.9KViews17likes2Comments