Netbackup Questions for level 1 and level 2
Hi All, Kindly share the netbackup administrator interview questions for L1 and L2 engineer. If any one have link kindly share. Netbackup 6.5 and 7.0 And also, share the all documetns link for netbackup7.0 Thanks and Regds, SagarSolved22KViews3likes7CommentsStatus Code 59 - Access to the Client was not Allowed
I am receiving this error on a backup job. This is Netbackup 7.1 running on a Windows Server 2008 R2 Enterprise 64bit system. I have looked through other forum discussions on this, but haven't had any luck trying to fix this myself. Below are the job details and i have attached the BPCD log for futher assistance. 5/23/2012 3:41:52 PM - Info nbjm(pid=33196) starting backup job (jobid=200208) for client polaris.daykimball.org, policy PACS.Images.on.Polaris, schedule Incremental 5/23/2012 3:41:52 PM - Info nbjm(pid=33196) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=200208, request id:{206810E6-849C-4247-B470-B23EC1D76E6E}) 5/23/2012 3:41:52 PM - requesting resource PUCK_Scalar24_LTO2_R1 5/23/2012 3:41:52 PM - requesting resource puck1.NBU_CLIENT.MAXJOBS.polaris.daykimball.org 5/23/2012 3:41:52 PM - requesting resource puck1.NBU_POLICY.MAXJOBS.PACS.Images.on.Polaris 5/23/2012 3:41:53 PM - granted resource puck1.NBU_CLIENT.MAXJOBS.polaris.daykimball.org 5/23/2012 3:41:53 PM - granted resource puck1.NBU_POLICY.MAXJOBS.PACS.Images.on.Polaris 5/23/2012 3:41:53 PM - granted resource 000079 5/23/2012 3:41:53 PM - granted resource IBM.ULTRIUM-TD2.000 5/23/2012 3:41:53 PM - granted resource PUCK_Scalar24_LTO2_R1 5/23/2012 3:41:53 PM - estimated 0 Kbytes needed 5/23/2012 3:41:53 PM - begin Parent Job 5/23/2012 3:41:53 PM - begin Snapshot, Start Notify Script 5/23/2012 3:41:53 PM - Info RUNCMD(pid=15820) started 5/23/2012 3:41:53 PM - Info RUNCMD(pid=15820) exiting with status: 0 Status 0 5/23/2012 3:41:53 PM - end Snapshot, Start Notify Script; elapsed time: 00:00:00 5/23/2012 3:41:53 PM - begin Snapshot, Step By Condition Status 0 5/23/2012 3:41:53 PM - end Snapshot, Step By Condition; elapsed time: 00:00:00 5/23/2012 3:41:53 PM - begin Snapshot, Stream Discovery Status 0 5/23/2012 3:41:53 PM - end Snapshot, Stream Discovery; elapsed time: 00:00:00 5/23/2012 3:41:53 PM - begin Snapshot, Read File List Status 0 5/23/2012 3:41:53 PM - end Snapshot, Read File List; elapsed time: 00:00:00 5/23/2012 3:41:53 PM - begin Snapshot, Create Snapshot 5/23/2012 3:41:55 PM - started process bpbrm (2552) 5/23/2012 3:41:56 PM - Error bpbrm(pid=2552) bpcd on polaris.daykimball.org exited with status 59: access to the client was not allowed 5/23/2012 3:41:56 PM - Info bpbrm(pid=2552) polaris.daykimball.org is the host to backup data from 5/23/2012 3:41:56 PM - end writing Status 59 5/23/2012 3:41:56 PM - end Snapshot, Create Snapshot; elapsed time: 00:00:03 5/23/2012 3:41:56 PM - begin Snapshot, Stop On Error Status 0 5/23/2012 3:41:56 PM - end Snapshot, Stop On Error; elapsed time: 00:00:00 5/23/2012 3:41:56 PM - begin Snapshot, Delete Snapshot On Exit Status 0 5/23/2012 3:41:56 PM - end Snapshot, Delete Snapshot On Exit; elapsed time: 00:00:00 5/23/2012 3:41:56 PM - begin Snapshot, End Notify Script 5/23/2012 3:41:56 PM - Info RUNCMD(pid=34688) started 5/23/2012 3:41:56 PM - Info RUNCMD(pid=34688) exiting with status: 0 Status 0 5/23/2012 3:41:56 PM - end Snapshot, End Notify Script; elapsed time: 00:00:00 Status 59 5/23/2012 3:41:56 PM - end Parent Job; elapsed time: 00:00:03 access to the client was not allowed(59)Solved18KViews1like3CommentsSnapshot provider error (0xE000FED1): A failure occurred querying the Writer status.
Running Backup Exec 12.0 Small Business Server Suite Rev. 1364 og getting random failing file data-backupjobs with error code E000FED1: Backup- E: DataV-79-57344-34110 - AOFO: Initialization failure on: "Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). Snapshot provider error (0xE000FED1): A failure occurred querying the Writer status. Check the Windows Event Viewer for details. Writer Name: Event Logs, Writer ID: {EEE8C692-67ED-4250-8D86-390603070D00}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Writer Name: Windows Internet Name Service, Writer ID: {F08C1483-8407-4A26-8C26-6C267A629741}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during thaw operation (10). When runningVSSADMIN LIST WRITERS - command from prompt I'm given the following output: C:\Documents and Settings\xxx>VSSADMIN LIST WRITERS vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001 Microsoft Corp. Writer name: 'System Writer' Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Instance Id: {e1eae7cb-e621-4ab2-ba63-e5a534cc5e7a} State: [1] Stable Last error: No error Writer name: 'FRS Writer' Writer Id: {d76f5a28-3092-4589-ba48-2958fb88ce29} Writer Instance Id: {51359454-ca5e-44f2-bbde-6fd81712dcc1} State: [1] Stable Last error: No error Writer name: 'SqlServerWriter' Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a} Writer Instance Id: {dc2f12b7-d951-41ba-8724-bc474e7a5f7e} State: [1] Stable Last error: No error Writer name: 'MSDEWriter' Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277} Writer Instance Id: {5cb6d93a-bb72-4a0d-b90b-e6174402c580} State: [1] Stable Last error: No error Writer name: 'WINS Jet Writer' Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741} Writer Instance Id: {a0bbbb7a-8d3d-47ae-93b2-7f7e008365d0} State: [10] Failed Last error: Retryable error Writer name: 'NTDS' Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757} Writer Instance Id: {3be2277a-66e1-43f1-a484-446320b9681f} State: [1] Stable Last error: No error Writer name: 'COM+ REGDB Writer' Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f} Writer Instance Id: {23e6136d-6943-4108-90cb-a40089bad1b9} State: [1] Stable Last error: No error Writer name: 'Registry Writer' Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485} Writer Instance Id: {8ae68311-ead2-4af4-8009-874337783ecc} State: [1] Stable Last error: No error Writer name: 'Event Log Writer' Writer Id: {eee8c692-67ed-4250-8d86-390603070d00} Writer Instance Id: {bc0eb6b5-835b-4a97-a8d0-7ba5f6db426e} State: [1] Stable Last error: No error Writer name: 'IIS Metabase Writer' Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366} Writer Instance Id: {8a3a101e-0dfd-46a2-9334-8ac0d57bf929} State: [1] Stable Last error: No error Writer name: 'WMI Writer' Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} Writer Instance Id: {af7bf8db-a57e-47a8-a0b5-3a754d46f58a} State: [1] Stable Last error: No error The following warnings and errors is shown in Windows Event Viewer: Event Type: Error Event Source: ESENT Event Category: ShadowCopy Event ID: 2004 Date: 09-10-2012 Time: 01:09:09 User: N/A Computer: SERVER01 Description: wins (3316) Shadow copy 13 time-out (70000 ms). Event Type: Warning Event Source: VSS Event Category: None Event ID: 12290 Date: 09-10-2012 Time: 01:09:29 User: N/A Computer: SERVER01 Description: Volume Shadow Copy Service warning: ESENT ERROR {f08c1483-8407-4a26-8c26-6c267a629741} WINS Jet Writer: -2402. hr = 0x00000000. Event Type: Error Event Source: Backup Exec Event Category: None Event ID: 34113 Date: 09-10-2012 Time: 06:20:30 User: N/A Computer: SERVER01 Description: Backup Exec Alert: Job Failed (Server: "SERVER01") (Job: "MANDAG-DATA") MANDAG-DATA -- The job failed with the following error: A failure occurred querying the Writer status. The data selected for the backup-job is pure files and System State. The server is a Windows Small Business Server 2003 SP2.Solved18KViews1like12CommentsSolution for VSS exceptions with VMware guests / VM tools
Hi everyone, We have been experiencing VSS issues with VMware guests in regards to the installed Backup Exec Agent and a previously installed VMware Tools VSS option. Uninstalling the VMware Tools VSS option in various ways including restarts did not fix our issues. If you search the internet for solutions, you find many attempts but no real solution or explanation. One of our admins spend several hours with the Veritas support without a solution, he was about to escalate the issue with them, when we found the root cause and could actually fix our issues. First the steps to solve this: Uninstall the VMware Tools VSS option (no restart will be requiered) Make sure VMware VSS service was deleted If this is not the case, you might need to do so manually and remove additional DLL's etc. as well as restart the system, but this is independent from this solution You might have already done steps 1 and 2 but you still get VSS exceptions from the backup that says you have more than one VSS agent installed: V-79-8192-38331 - The backup has detected that both the VMware VSS Provider and the Symantec VSS Provider have been installed on the virtual machine 'hostname'. However, only one VSS Provider can be used on a virutal machine. You must uninstall the VMware VSS Provider. Now you wonder what causes this and you get stuck You could uninstall the Veritas/Symantec Backup Exec Agent and only back the system up per VMDK You would lose the GRT / granular backup / restore capabilities Check your registry for the following reg key HKLM\System\CurrentControlSet\Services\BeVssProviderConflict If this key exists, but your VMware VSS provider is uninstalled, you need to follow up with step 5 Open a notepad as administrator Open this file in the notepad C:\ProgramData\VMware\VMware Tools\manifest.txt Search for the following two entries: Vcbprovider_2003.installed vcbprovider.installed Make sure both of them are set to FALSE, most likely one of them is TRUE Run a test backup This test backup now should not show the exception anymore The registry key should vanish (refresh/press F5) without you taking action So what happened? You uninstalled the VMware Tools VSS provider, but this manifest file did not get updated. We actually could see that it sometimes does get updated and sometimes does not. This seems to be some kind of issue with the VMware Tools uninstalled/installer. But why this manifest.txt file? As we found out, there scripts that get executed by Symantec/Veritas Backup Exec before the backup. You might find them in two locations, and it seems to depend a bit on the Windows version which script is executed (at which location). You could edit them both and just undo the checks in the scripts, but this wouldn't be correct. It is more correct to update the manifest.txt file. If you want to, you can check the date/time of the manifest.txt file before you change it - you might see it was not updated while you uninstalled the VMware Tools VSS provider (assuming you did only do this and not do additional installs/uninstalls within the VMware Tools / please note as well that this only is true when you still experienced those issues). Now, back to those scripts, you find them here: C:\Windows C:\Program Files\Symantec\Backup Exec\RAWS\VSS Provider The name of the script that matters: pre-freeze-script.bat This script checks several DLLs, registry entries, paths and on Windows 2008 and newer the ProgramData-Path for this specific manifest.txt file and the two entries mentioned. Once you uninstall the VMware VSS provider, and the file did not get updated, you might see this issue and wonder how to solve it. The solution is to simply update it to mirror the uninstallation of the VMware VSS provider (vcbprovider). We double checked this with several installations and could see if the file actually gets updated, those two values are set to FALSE, if it doesn't, at least one of the values remains true, what causes the pre-freeze-script.bat to write the registry key mentioned earlier and therefor causing the issue in the backup - exceptions. If you still have the same issues after updating the manifest.txt, simply check all the DLL's that are mentioned in the script and make sure they don't exist. You might also consider to manually delete the registry-key (it seems to be just a dumy-key) to make sure there is no issue that prevents the script from deleting it. Make sure it does not re-appear after a backup! Otherwise you might still have some DLLs left on your system that cause the script to re-create the registry key. Hope this helps a few of you out there. This was an ongoing issue for a while and I came accross those issues many times ever since Windows 2008. This applies to Windows 2008 R2, Windows 2012, Windows 2012 R2 and pretty sure to Windows 2016 as well. It helped us getting rid of those issues completely and actually not even needing a single restart of the guest VM to solve the issues (removing the VMware VSS provide did not need a restart). Regards Florian RossmarkSolved14KViews2likes10CommentsBackup Exec log files 38GB
We've had an issue with our server due to lack of free space. We've examined the contents of the drive and "C:\Program Files\Symantec\Backup Exec\Logs\" is taking up 38GB of space. Can you tell me why it would take up this much space please? More importantly how do i cap it at say 10GB? We are using Backup Exec 2010 R3 on a windows 2007 sbs server. All our backups are backup to disk folders on removable drives and we backup also backup exchange and SQL. Thanks, your help is appreciated ThanksSolved12KViews1like4Comments"Netbackup Client Service" doesn't start: windows error 1057. NB 7.0 Windows Server 2003 x86
Hi all, I have a Windows Server 2003 SP1 x86 with a NB 7.0 client installed. Recently I have rebooted it due to Windows updates. After that "Netbackup client service" doesn't start and I receive the windows error 1057 "The Account Name is Invalid or Does Not Exist". Before reboot this service was configured with a local windows account and it worked fine. This account have never changed nor password. I need this NB service works on local account due to several backup scripts. I have tried all: another local account with necessary rights (Manage auditing and security log, act as part of the operating system, create a token object, member of "Backup operators" windows group, ...), re-install NB software, ..., without successfull results. Has anyone have this issue too? Thanks.Solved11KViews0likes14Commentshow to force a queued job to be cancelled? (without a job PID) is it possible?
I know that by cmd "taskkill /pid 7900 -f" we can cancel a running job by force. But is there a way to cancel a job that has been queued thus without a "job pid" ? There are a lot of jobs that are queued and that I need to cancel by force since they are not responding by the normal way. I normally use this cmd "TASKKILL /PID # -F" for jobs with an assigned PID (process id), but I need to find a way to cancel jobs without pid. if someone could assist me with this, that will be great, cheers thanks10KViews1like2Commentsbpfis errors in problem report
I have a Windows 2003 (x86) Standard SP2 Client in a MS-Windows policy that is completing successfully as far as the Activity Monitor is concerned but faor the last couple of weeks we have been seeing entries as below in the Problem Report: Errorfrom client clientname.domainname.co.uk: ERR - Send bpfis state to masterserver.domainname.co.uk failed. status = 25 Error from client clientname.domainname.co.uk: ERR -Get bpfis statefrom masterserver.domainname.co.uk failed. status = 25 Error from client clientname.domainname.co.uk: ERR -Delete bpfis statefrom masterserver.domainname.co.uk failed. status = 25 The Microsoft VSS rollup pack has since been applied to the server which is know to resolve VSS problems in 2003 but the issue remains. My environment is Windows 2008 R2 (x64) Enterprise for Master/Media running NetBackup 7.1.0.4 Has anyone else come across this issue before or have any idea what may be causing it? Many thanks, MikeSolved10KViews1like9CommentsBackupExec 2010 dropping tape drive offline
Hi, This is a new topic to re-open the issue discussed here: https://www-secure.symantec.com/connect/forums/tape-drive-goes-offline-second-backup Just to recap on the issue itself: Running BE2010 Trial on Windows Server 2008 R2 x64. Hardware is Dell R710 rack server, connected to a HP Ultrium 1760 LTO4 SAS drive via a Dell PERC 6/E SAS Adaptor card. This is what’s happening: Setup and run a backup job with full verify. I’ve tested up to a 250GB job and it completes fine the first time around. After completion of first job, rerun the same backup job (after tweaking the media overwrite/append etc settings) The job immediately fails, reporting the drive as offline – cannot bring drive back online using BackupExec administrator Close BackupExec administrator, restart BackupExec Device/Media service (which also restarts associated service dependencies). Re-open BackupExec administrator - drive appears to be online again, ready for another job to be kicked off. I’ve completely replaced: Numerous LTO tapes The Dell SAS adaptor that connects the Dell server to the HP rack chassis The HP Rack chassis that houses the 1U internal HP LTO4 Ultrium 1760 SAS drive, SAS adaptor board and all The internal HP LTO Ultrium 1760 drive itself We’ve verified that all above component drivers and firmware are fully up to date. This problem occurs with both Symantec Tape Drive drivers and HP's official LTO4 tape drivers, To me, the following facts suggest that the problem lies with BackupExec itself: After the drive goes offline, a simple restart of the BackupExec services seems to bring it back online again If the drive goes offline, and I stop the BackupExec Device/Media service, I can still access the drive using HP LTT utility, and HP Data Protector Express – only BackupExec detects the drive as offline. We’ve replaced all possible hardware components and the problem still remains This problem only ever occurs with BE, I'm testing with HP Data Proctector Express and MS's Data Protection Manager - all work fine. Luckily, I haven't bought a license for BackupExec yet, however this means I doubt Symantec Support will be willing to spend too much time on it, so I might be forced to go with MS's Data Protection Manager instead if I can't get a resolution soon. Has anyone seen/resolved this issue before? AlistairSolved8.8KViews1like40CommentsSLP duplications are not starting after activating
Hi, I have a question regarding SLP behavor. Can anybody tell how long does it take to duplications to get started after activating them. All SLPs were in inactive state as we had problem with the tape drive. Now tape drive fixed and i have activated them, but no duplication jobs are running. Is there anything in the guide which says how long does it take them to start. Appologies for my bad english. :)Solved8.7KViews1like12Comments