Symantec Netbackup 7 licensing
Hi All, I'd like to know if I'm getting this correctly. I'm planning to getNetbackup 7 Starter Editionaccording tob-symc_netbackup_7_core_DS_12995286-2.en-us.pdf(http://eval.symantec.com/mktginfo/enterprise/fact_sheets/b-symc_netbackup_7_core_DS_12995286-2.en-us.pdf)Table 2. the Edition comparison the Starter Edition can have 5 Server (supported clients) does this means i can have the following backup items: 1x ESXi 4 server (using vStorage API for inline deduplication - Change Block Tracking) 1x Solaris SPARC + Oracle DB 10gR2 1x Linux 1x Windows Server + Share Point 2007 (Granular restore) 1x Windows Server + Exchange Server 2007(Granular restore) all of the above with bare metal restore capability. Since it is said that i could have: Server Clients, Tape Drive and Database Agents included ? yes I understand that Deduplication is not included here since it will need another license to spend. I'm getting confused here of which product that i should get :-| Would be good if anyone can clarify this please ?Solved1.2KViews4likes6CommentsUnable to Start Symantec VSS writer service in services.msc
Hi All, I'm having problem in starting the Symantec VSS writer from the services console, see the following diagnosis log: Log Name: System Source: Service Control Manager Date: 15/09/2010 4:41:48 PM Event ID: 7023 Task Category: None Level: Error Keywords: Classic User: N/A Computer: MOSSDEV01.domain.com Description: The Backup Exec VSS Provider service terminated with the following error: The class is configured to run as a security id different from the caller #################################################################################################### Here's the pop up message content when i tried to start the service manually from the services.msc: Windows could not start the Backup Exec VSS Provider service on Local Computer. Error 0x80004015: The class is configured to run as a security id different from the caller #################################################################################################### C:\Windows\system32>vssadmin list writers vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001-2005 Microsoft Corp. Writer name: 'System Writer' Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Instance Id: {34de22c6-4a77-4af6-9ae6-1b4eee4d629b} State: [1] Stable Last error: No error Writer name: 'SqlServerWriter' Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a} Writer Instance Id: {c6074e09-4962-4290-9639-d8cc7d08f644} State: [8] Failed Last error: Non-retryable error Writer name: 'ASR Writer' Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4} Writer Instance Id: {b7312b38-21e6-4256-a6a4-22b7d092a631} State: [1] Stable Last error: No error Writer name: 'Registry Writer' Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485} Writer Instance Id: {f9a08539-b34b-43f0-9f4e-e063721c801d} State: [1] Stable Last error: No error Writer name: 'Shadow Copy Optimization Writer' Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f} Writer Instance Id: {f66756d6-4aab-487d-a9c8-47fe2cc8e8d6} State: [1] Stable Last error: No error Writer name: 'IIS Metabase Writer' Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366} Writer Instance Id: {0af9df28-119b-4177-9ea1-7f84eeadbdb8} State: [9] Failed Last error: Timed out Writer name: 'COM+ REGDB Writer' Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f} Writer Instance Id: {9ba3b2c3-4947-4cb9-894b-d084464aef29} State: [1] Stable Last error: No error Writer name: 'SPSearch VSS Writer' Writer Id: {57af97e4-4a76-4ace-a756-d11e8f0294c7} Writer Instance Id: {9f4ab399-ff20-4dae-9063-7b737d52edd3} State: [9] Failed Last error: Timed out Writer name: 'OSearch VSS Writer' Writer Id: {8d5f38cd-fb7a-49ca-ae1b-21d1f017d8f9} Writer Instance Id: {b87cc4be-935b-4479-ac5d-618a41767a0f} State: [9] Failed Last error: Timed out Writer name: 'WMI Writer' Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} Writer Instance Id: {76d8b78a-0c87-464f-b538-4fee7c515f42} State: [9] Failed Last error: Timed out Writer name: 'BITS Writer' Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0} Writer Instance Id: {b18c717e-2d37-4987-b84b-87bebd77a629} State: [1] Stable Last error: No error Writer name: 'IIS Config Writer' Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6} Writer Instance Id: {9f5a29f8-93f8-48a6-8330-605423ad951b} State: [9] Failed Last error: Timed out C:\Windows\system32> ############################################################################################ Can anyone share their experience in resolving this issue please ? This happens on Windows Server 2008 Standard x64 which has SQL Server 2008 SP1 and SharePoint 2007 SP2 Thanks, AWT1.6KViews3likes4CommentsBackup SharePoint Error since it needs SQL Server agent ?!?!?!!
Hi All, I'm having problem in backing up my SharePoint Server 2007 which is installed in one single server deployment with SQL Server 2008 as well here's the error log: ###################################################################################################################### Job ended: Thursday, May 27, 2010 at 11:00:17 PM Completed status: Failed Final error: 0xe000fe3c - Before you can back up this resource, you must purchase and install a license key for the appropriate Backup Exec agent. See Job Log for details. Final error category: Security Errors For additional information regarding this error refer to link V-79-57344-65084 ###################################################################################################################### Backup- MOSSDEV01.domain.comV-79-57344-65084 - Before you can back up this resource (MOSSDEV01.domain.com\MOSSDB), you must purchase and install a license key for the appropriate Backup Exec agent. For information about how to obtain a license key, go to the following URL: https://redirector.symantec.com?src=inpdt&pdt=be&action=t A selection on device \\MOSSDEV01.domain.com\Shadow?Copy?Components was skipped because of previous errors with the job. A selection on device \\MOSSDEV01.domain.com\System?State was skipped because of previous errors with the job. Verify Insufficient memory available. V-79-57344-33858 - A memory allocation request failed. The computer may be running low on virtual memory. ###################################################################################################################### Backup- MOSSDEV01.domain.comV-79-57344-65268 - AOFO: Initialization failure on: "MOSSDEV01.domain.com\MOSSDB". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). V-79-10000-10896 - SQL Prepare for Freeze failed for snapshot. ###################################################################################################################### how can this happens ? I just want to backup my SharePoint but i have to purchase another agent for SQL Server 2008 ? can anyone help please ? ThanksSolved748Views3likes7CommentsBE 2010 - RAWS SharePoint 2007 Agent usability scope
Hi All, May I know what does this BE 2010 Agent for SharePoint can do compares to the built in SharePoint Farm backup utility ? Does it able to restore the whole farm content into the new server after i rebuild the new server and install the RAWS agent ? Thanks.Solved510Views3likes3CommentsHow to do complete SharePoint Server restore using BE 2010 agent ?
To All Experts here, I'd like to perform a complete MOSS 2007 content disaster recovery from the existing single instance server (SQL Server 2008, Windows Server 2008, SharePoint 2007 SP1) all in one and into the newly built server with the same name. I have created the new Windows Server 2008 R2 + SQL Server 2008 SP1 and MOSS 2007 SP2 and I haven't execute the server configuration wizard to create the same port number of the SSP, CA and the SQL Server DB yet. Assuming the old server name MOSSDEV01 has been destroyed, how can i make sure that the user can still access the MOSS 2007 content without having to experience broken link here and there and tell them to update all of the bookmarks ? What does the BE 2010 SharePoint agent do in this case ? which DB is backed up ? Any idea and suggestion would be greatly appreciated Thanks.Solved325Views3likes2CommentsAfter upgrading to BE 2012 Sharepoint jobs fails, Access Denied.
Hi After upgrading and thenreinstalling BE 2012 my Sharepoint 2007SP3jobs failes. Much like the old http://www.symantec.com/business/support/index?page=content&id=TECH163882, fixed in 2010R3 SP2. Completion status: Failed Final error: 0xe0001602 - Access is denied (Share point backup). Final error category: Security Errors For additional information regarding this error refer to link V-79-57344-5634 This Exception may also show up: Backup- Sharepoint - 80\Content-DB1 (SERVERNAME\SHAREPOINT\WSS_Content) When I create the job the Test credentials check out OK, all passes. But the the job runs and it failes, when I the go in and check the credentials again they failed. Any one else with this problem? Solution? regards Robert1.5KViews2likes11CommentsSharePoint 2007 agent backup Error: The job failed with the following error: The directory is invalid.
Hi All, I've already followed the article in this page to backup and set permission of my SharePoint 2007 SP2 Farm:http://www.symantec.com/business/support/index?page=content&id=TECH75907 but then when i perform backup it failed with the following log: Job ended: Monday, September 20, 2010 at 11:17:29 AM Completed status: Failed Final error: 0xe000fe09 - The directory is invalid. Final error category: Resource Errors For additional information regarding this error refer to link V-79-57344-65033 the Test Run performed successfully, but I still don't understand why it failed miserably when doing the real backup job. Any kind of help would be greatly appreciated. Thanks,Solved551Views2likes4CommentsBE 2010 R2 - SharePoint Server 2007 agent backup error ?
Hi Everyone, I've just upgraded the Agent for my SharePoint Server 2007 SP2 with the latest BE 2010 R2 agent then i reboot the server, However the job is always failing with the following error message: The job failed with the following error: A failure occurred querying the Writer status. Backup- MOSSDEV01.domain.com\MOSSDB Database \master was not found, or could not be accessed. Database \model was not found, or could not be accessed. Database \msdb was not found, or could not be accessed. Database \ReportServer$MOSSDB was not found, or could not be accessed. Database \ReportServer$MOSSDBTempDB was not found, or could not be accessed. Database \SPDiagDiagnoseMOSSDEV01 was not found, or could not be accessed. Backup V-79-57344-65233 - AOFO: Initialization failure on: "\\MOSSDEV01.domain.com\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: Windows Management Instrumentation, Writer ID: {A6AD56C2-B509-4E6C-BB19-49D8F43532F0}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). V-79-57344-65233 - AOFO: Initialization failure on: "\\MOSSDEV01.domain.com\System?State". 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: Automated System Recovery, Writer ID: {BE000CBE-11FE-4426-9C58-531AA6355FC4}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Writer Name: COM+ Class Registration Database, Writer ID: {542DA469-D3E1-473C-9F4F-7847F01FC64F}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Writer Name: Internet Information Services, Writer ID: {2A40FD15-DFCA-4AA8-A654-1F8C654603F6}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Writer Name: Internet Information Services, Writer ID: {59B1F0CF-90EF-465F-9609-6CA8B2938366}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Writer Name: Registry, Writer ID: {AFBAB4A2-367D-4D15-A586-71DBB18F8485}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9). Writer Name: System Files, Writer ID: {E8132975-6F93-4464-A53E-1050253AE220}, Last error: The VSS Writer timed out (0x800423f2), State: Failed during freeze operation (9).Solved721Views2likes6CommentsBackup Exec 2010R2 agents upgrade
Hi All, I've just successfully install BE 2010 R2, i wonder if i should upgrade the agents in all o my systems (Exchange, SHarePoint, SQL Server or Domain Controllers) for it to work properly ? from the what's new the R2 only affecting SharePoint server 2010, while mine is 2007 do i still have to upgrade it ?641Views2likes4Comments