Agent for Microsoft SQL Server

353 Topics

Backup 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 Thanks
Solved
resolver101
13 years ago Place Backup Exec
12KViews
1like
4Comments
BE 2012 and Data Domain w/ DDBoost
Background: So we have Backup Exec 2012 and two Data Domain DD620's. We have all the required licensing including the Data Domain DD Boost and replication licenses. I have installed the Open Storage Technology (OST) plugin 2.5.0.3 as suggested for the version of BE. Both DD boxes are visable and connected to my BE server. I have foud some documentation and a video that explains some of what I am looking for but not entirely and most of it is for BE2010. The BE 2012 documentation from DD is not up to date yet. I am trying to setup backups as my tape drive has had enough and is not working properly. Anyone I have talked to just says you backup to it, then I continue finding little things that need to be done. No verify, no precompression, some said no deduplication in the job, other said server side dedupe because DDBoost manages it with OST plugin. Too much information and not enough people knowing what to tell me. The DD weekend support guys don't know the software titles they just know the hardware. I need help now unfortunately... Question: What settings do I use for Backups? I have Active Directory, Exchange, SharePoint, and SQL agents.
CRoth2
13 years ago Place Backup Exec
6.4KViews
1like
32Comments
Failed Final error: 0xe00084bd - The system cannot find the path specified - unable to restore file or directory.
Hello I can't backup only this Vm with Backup Exec 2014 since a very long time. They are no snapshot existed in snapshot Manager. When i select manually only one VM using snapshot technology .. Could you help me ? it says always .. And after the message appears.... ANd, Why it talk about restore ? I giev a backup not arestore. Error : e00084bd - The system cannot find the path specified - unable to restore file or directory. See the job log for details. Agent used : Yes Advanced Open File Option used : No
nfougeroux
10 years ago Place Backup Exec
5.5KViews
1like
16Comments
Catalog error on one particular sever
Hi I'm back. After small issue to upgrade to backup exec 2012 sp1a, I have a very strange error. If I make a full backup of my virtual servers (CSV cluster), the backup to disk works just fine. But when the jobs start to make a duplication to tape, I receive an error saying 'An error was encountered writing to the on-disk catalogs'. the final error is The job failed with the following error: An error occurred while retrieving catalog information I found this article http://www.symantec.com/business/support/index?page=content&id=TECH53393 but it was no solution. The error is only generated on a particular server.
ApieBe
13 years ago Place Backup Exec
5.3KViews
1like
10Comments
Logon account that was provided does not have the appropriate privileges to back up the SQL database
Recently I upgrade BackExec 2010 to 2012, updated remote agents etc... and I created all "new" jobs and started from scratch. I have 3 servers running Win2008 with MSSQL and two of them are backing up fine,but I am having problems with one particular server (Win2008 with MSSQL). Testing creditionals work fine, I use the System Logon Account. I have changed the creditionals to domain admins, I even used the SA logon account for access the MSSQL server and it always fails with the below errors. I have done the following: In SQL Server Management Server I made sure that the logon account used for backing up SQL database exists there. Made sure theLogon account was in the Sysadmin Role. Test Run Errors (only a partial list of the errors): Device : 3f4c28a6-a36c-4622-980c-f541f10538d3, DICOMSERVER\MSSQLSERVER Check status : Error: e0009b84, The job failed with the following error: The logon account that was provided does not have the appropriate privileges to back up the SQL database . Either assign the appropriate privileges to this logon account, or use another logon account. Device : 3F4C28A6-A36C-4622-980C-F541F10538D3, \\DICOMSERVER\C: Check status : Error: e0009b84, The job failed with the following error: The logon account that was provided does not have the appropriate privileges to back up the SQL database . Either assign the appropriate privileges to this logon account, or use another logon account. Job Alert Errors(only a partial list of the errors): Job ended: Friday, May 09, 2014 at 12:36:32 AM Completed status: Failed Final error: 0xe0008443 - One or more SQL Database consistency checks have failed. Final error category: Resource Errors For additional information regarding this error refer to link V-79-57344-33859 V-79-57344-65088 - WARNING: The DBCC NEWALLOC command requires SA rights. The consistency check cannot be completed. User 'guest' does not have permission to run DBCC checkdb for database 'msdb'. V-79-57344-65088 - WARNING: The DBCC NEWALLOC command requires SA rights. The consistency check cannot be completed. User 'public' does not have permission to run DBCC checkdb for database 'PRA_DICOM'. V-79-57344-65088 - WARNING: The DBCC NEWALLOC command requires SA rights. The consistency check cannot be completed. User 'public' does not have permission to run DBCC checkdb for database 'PSC_DICOM'. etc.....etc... Backup- DICOMSERVER\MSSQLSERVER Database \model was not found, or could not be accessed. Click an exception below to locate it in the job log Backup- DICOMSERVER\MSSQLSERVER V-79-57344-5891 - The object was not found, or could not be accessed (MS SQL backup).The item DICOMSERVER\MSSQLSERVER\model in use - skipped.
Solved
flahr
11 years ago Place Backup Exec
5.2KViews
1like
13Comments
Credentials Fail for MS SQL Server Backup
Hi All, I've just taken over a backup exec 2012 server and my main issue at the moment is that the person that set up the SQL backup, just did it as a file backup only - and had de-selected the MS SQL Server Instances. I've tried adding them to the backup, but the windows logon account credentials that I am using fail in the test credentials screen I can log in to the SQL server using the same credentials, and the user has the server roles of serveradmin and sysadmin assigned to them. What am I missing?
Azeronti
11 years ago Place Backup Exec
4.4KViews
1like
5Comments
Best solution to back up Citrix Xen Server
Hello, I am wondering what the best solution would be for the following: I have on Citrix Xen Server host that has 7 virtual machines on it. I am currently using PHD Virtual to back this up to a NAS. I am looking to move to different software for the backups. One of the virtual machines is running SQL and one is running AD and DNS. There is also one physical server that has AD, DNS, and DHCP on it that i would also like to back up in the same solution. What i was curious about is what is the best way to back all of this up? Is it Back Up Exec or System Restore? Or would neither work? I am looking for something that will back up to the existng NAS and allow for item level restores as well as fast restores of full VM's if ever needed. Second question is, assuming one of the two products will work is it best practice to install it on its own server or could it be installed on teh physical that is existing with AD, DNS and DHCP? I am assuming its own server and that is what i would shoot for, but for the sake of saving money i like to know my options. Thank you for your assistance.
Solved
downingtownryan
10 years ago Place Backup Exec
3.5KViews
0likes
4Comments
The configuration of the AdminConnection\TCP protocol in the SQL instance BKUPEXEC is not valid.
Hello all, I am recieving the following error in my logs "The configuration of the AdminConnection\TCP protocol in the SQL instance BKUPEXEC is not valid." I am running Server 2008 R2 x64, this was a clean install along with a new install of BE 2010. I found 2 articles on the Symantec site, this one: https://www-secure.symantec.com/connect/forums/sql-instance-bkupexec-not-validwhich links to a tech article ( http://support.veritas.com/docs/283949) that basically says it is not Symantecs issue in more wordsbut offers no suggestions on fixingthe error.The Belowarticle which referrs to some registry settings that are non existant on my machine, I do not want to go adding stuff randomly not knowing how much work this will generate for me if it doesn't work. I do not know why if it is a common issue that Symantec does not have a TechArticle that explains how to fix this issue (If it really is an issue). Appears thatsince this is SQLEXPRESS this may be the cause of a feature that is not enabled or an option with SQL Express. But it would be nice to know one way or another. (ERROR MESSAGE) Log Name: Application Source: SQLBrowser Date: 10/10/2010 11:04:42 AM Event ID: 3 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: NWMEDIA.oly.esri.com Description: The configuration of the AdminConnection\TCP protocol in the SQL instance BKUPEXEC is not valid. Event Xml: https://www-secure.symantec.com/connect/forums/start-backup-exec-agent-browser-and-backup-exec-job-engine-fails-after-restart """"""""" Hello, This warning "The Hello, This warning "The configuration of the AdminConnection\TCP protocol in the SQL insrtance BKUPEXEC ist not valid" is not generated by the Backup Exec installer, but rather the SQL installer. The warning does not have any effect on remote connections to the BKUPEXEC instance. http://support.veritas.com/docs/283949 This message appears because the TCP/IP Protocol for the instance is disabled. If desired, you can enable the TCP/IP Protocol for the instance and then configure the IP addresses you want the instance to listen on. You can try changing the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\MSSQLServer\SuperSocketNetLib\AdminConnection\Tcp\TcpDynamicPorts The default value is 0 change it to 1434. Restart the SQL service and the error from the SQL Browser stop being recorded at every startup. This link might be helpful: http://www.sqlcoffee.com/Troubleshooting008.htm """""""""" Any help on this would be appreciated
Solved
RSOLY777
15 years ago Place Backup Exec
3.4KViews
0likes
2Comments
12.5 SQL Backups failing
Hi, Running Backup Exec 12.5 SP3 on an SBS2008 server. Backups have been failing recently on the Verify stage of one of the SQL databases. Below are the errors from the logs Job ended: 15 November 2011 at 07:07:41 Completed status: Failed Final error: 0xe0008492 - Database Query Failure. See the job log for details. Final error category: Resource Errors For additional information regarding this error refer to link V-79-57344-33938 Backup- SBS2008 V-79-65323-3201 - An error occurred on a query to database IRIS. V-79-65323-3201 - Cannot open backup device 'IRIS_00__9cd33917_4f34_4b18_8bb1_e5f7dacda8ea_'. Operating system error 0x80770006(error not found). V-79-65323-3201 - An error occurred on a query to database IRISPRACTICE. V-79-65323-3201 - Cannot open backup device 'IRISPRACTICE_00__f0e3aabc_cf70_45ea_a424_1c78f9a9224d_'. Operating system error 0x80770006(error not found). V-79-65323-3201 - An error occurred on a query to database master. V-79-65323-3201 - Cannot open backup device 'master_00__151e5ec9_0db4_4a42_99d7_ace00fc46479_'. Operating system error 0x80770006(error not found). V-79-65323-3201 - An error occurred on a query to database model. V-79-65323-3201 - Cannot open backup device 'model_00__fc5c3199_9de4_4a79_9162_293e09733703_'. Operating system error 0x80770006(error not found). V-79-65323-3201 - An error occurred on a query to database msdb. V-79-65323-3201 - Cannot open backup device 'msdb_00__6443a086_decf_462f_8933_14199b48390e_'. Operating system error 0x80770006(error not found). Backup- WebApplication\Content-DB 1 (SBS2008\MICROSOFT##SSEE\SharePoint_AdminContent_d4e397f2-a27a-48a0-a628-d25db6672bab) V-79-57344-33938 - AOFO: Initialization failure on: "SBS2008". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). Snapshot provider error (0xE0008492): Database Query Failure. See the job log for details. Check the Windows Event Viewer for details. Backup- SBS2008 The item SBS2008\IRIS in use - skipped. The item SBS2008\IRISPRACTICE in use - skipped. The item SBS2008\master in use - skipped. The item SBS2008\model in use - skipped. The item SBS2008\msdb in use - skipped. Seems that it thinks the database is in use. I have AOFO on and nothing has changed in the configuration. can anyuone offer any help on how to resolve this? TIA Mark
Solved
markikona
13 years ago Place Backup Exec
3.1KViews
0likes
13Comments
V-79-57344-65085 - There was a problem running the DBCC
Hello I have created a new backup job for a server containing an SQL database(s). However I get various instances of the "V-79-57344-65085 - There was a problem running the DBCC." error ,which I believe relates to inconsistency checks;which has caused the job to fail the last 2 nights. I have tried running dbcc manually through SQL on the affected databases and it comes back with 0 errors. I am unsure how to proceed in fixing this job? Job Log for NIMROD.BAL.local Backup 00043-Incremental -------------------------------------------------------------------------------- Completed status: Failed See error(s) Expand AllCollapse All Job Information Job server: BACKUP01 Job name: NIMROD.BAL.local Backup 00043-Incremental Job started: Tuesday, August 25, 2015 at 7:00:03 PM Job type: Backup Job Log: BEX_BACKUP01_06371.xml Drive and media mount requested: 8/25/2015 7:00:04 PM Device and Media Information Drive and media information from media mount: 8/25/2015 7:00:06 PM Drive Name: Disk storage 0001 Media Label: B2D004747 Media GUID: {6e080236-bae8-4d59-aa5d-dc3fd557a981} All Media Used B2D004747 B2D004748 B2D004749 Job Operation - Backup Backup Options Media operation - Append to media, overwrite if no appendable media is available. Compression Type: None Encryption Type: None Backup Set Retention Period: 1 Week. Server - NIMROD.BAL.local Note: Resource: "NIMROD.BAL.local\MSSQLSERVER" is not snappable. Attempting to back up directly from the source volume. Network control connection is established between 10.8.2.8:55707 <--> 10.8.2.4:10000 Network data connection is established between 10.8.2.8:55708 <--> 10.8.2.4:50372 Database Consistency Checks Consistency checking AB Consistency Check Physical Only. Consistency check was completed. Consistency checking BoltonStockTake Consistency Check Physical Only. Consistency check was completed. Consistency checking DataTakeOn Consistency Check Physical Only. Consistency check was completed. Consistency checking FIFO_Backup Consistency Check Physical Only. Consistency check was completed. Consistency checking helpdesk Consistency Check Physical Only. Consistency check was completed. Consistency checking NewTraining Consistency Check Physical Only. V-79-57344-65085 - There was a problem running the DBCC. Error: 802, Severity: 17, State: 20. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped. Consistency checking ReportServer Consistency Check Physical Only. Consistency check was completed. Consistency checking ReportServerTempDB Consistency Check Physical Only. V-79-57344-65085 - There was a problem running the DBCC. [DBNETLIB][ConnectionRead (recv()).]General network error. Check your network documentation. Consistency checking SiteServices Consistency Check Physical Only. V-79-57344-65085 - There was a problem running the DBCC. Connection failure Consistency checking SO_PO_Restore Consistency Check Physical Only. V-79-57344-65085 - There was a problem running the DBCC. Connection failure Consistency checking StockTakeTest Consistency Check Physical Only. V-79-57344-65085 - There was a problem running the DBCC. Connection failure Consistency checking Test Consistency Check Physical Only. V-79-57344-65085 - There was a problem running the DBCC. Connection failure Consistency checking Training Consistency Check Physical Only. V-79-57344-65085 - There was a problem running the DBCC. Connection failure Consistency checking whd Consistency Check Physical Only. V-79-57344-65085 - There was a problem running the DBCC. Connection failure Consistency checking WinMan Consistency Check Physical Only. V-79-57344-65085 - There was a problem running the DBCC. Connection failure Consistency checking WinManMaster Consistency Check Physical Only. V-79-57344-65085 - There was a problem running the DBCC. Connection failure Set Information - NIMROD.BAL.local\MSSQLSERVER Backup Set Information Family Name: "Media created 8/25/2015 7:00:04 PM" Backup of "NIMROD.BAL.local\MSSQLSERVER" Backup set #1 on storage media #1 Backup set description: "NIMROD.BAL.local Backup 00043-Incremental" Backup Method: Log - Back up transaction log Microsoft SQL Server Agent: Started Backup started on 8/25/2015 at 9:14:32 PM. Backup completed on 8/25/2015 at 9:14:33 PM. Backup Set Summary Processed 0 bytes in 1 second. Throughput rate: 0.000 MB/min This backup set may not contain any data. Snapshot Technology: Started for resource: "\\NIMROD.BAL.local\D:". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS). The snapshot technology used by VSS for volume D: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7). Drive and media mount requested: 8/25/2015 9:14:36 PM No appendable media could be mounted. Switching to overwrite operation on scratch media. Drive and media information from media mount: 8/25/2015 9:14:38 PM Drive Name: Disk storage 0001 Media Label: B2D004748 Media GUID: {edef265e-3c95-4772-9559-dd7fbe238c70} Network control connection is established between 10.8.2.8:55707 <--> 10.8.2.4:10000 Network data connection is established between 10.8.2.8:52905 <--> 10.8.2.4:51004 Set Information - \\NIMROD.BAL.local\D: Backup Set Information Family Name: "Media created 8/25/2015 7:00:04 PM" Backup of "\\NIMROD.BAL.local\D:" Backup set #1 on storage media #1 Backup set description: "NIMROD.BAL.local Backup 00043-Incremental" Backup Method: Incremental - Using modified time Backup started on 8/25/2015 at 9:15:04 PM. Backup completed on 8/25/2015 at 9:15:11 PM. Backup Set Summary Backed up 402 files in 409 directories. Processed 52,075,082 bytes in 7 seconds. Throughput rate: 426 MB/min Snapshot Technology: Started for resource: "\\NIMROD.BAL.local\C:". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS). The snapshot technology used by VSS for volume C: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7). Drive and media mount requested: 8/25/2015 9:15:13 PM No appendable media could be mounted. Switching to overwrite operation on scratch media. Drive and media information from media mount: 8/25/2015 9:15:16 PM Drive Name: Disk storage 0001 Media Label: B2D004749 Media GUID: {e224467f-228a-46f7-90eb-2400dca0d5cf} Network control connection is established between 10.8.2.8:55707 <--> 10.8.2.4:10000 Network data connection is established between 10.8.2.8:52988 <--> 10.8.2.4:51050 Set Information - \\NIMROD.BAL.local\C: Backup Set Information Family Name: "Media created 8/25/2015 7:00:04 PM" Backup of "\\NIMROD.BAL.local\C:" Backup set #1 on storage media #1 Backup set description: "NIMROD.BAL.local Backup 00043-Incremental" Backup Method: Incremental - Using modified time Backup started on 8/25/2015 at 9:15:42 PM. Backup completed on 8/25/2015 at 9:18:09 PM. Backup Set Summary Backed up 1053 files in 205 directories. Processed 3,857,423,574 bytes in 2 minutes and 27 seconds. Throughput rate: 1502 MB/min Job Operation - Verify Server - NIMROD.BAL.local Drive and media mount requested: 8/25/2015 9:18:11 PM Drive and media information from media mount: 8/25/2015 9:18:11 PM Drive Name: Disk storage 0001 Media Label: B2D004747 Media GUID: {6e080236-bae8-4d59-aa5d-dc3fd557a981} All Media Used B2D004747 B2D004748 B2D004749 Set Information - NIMROD.BAL.local\MSSQLSERVER Verify Set Information Verify of "NIMROD.BAL.local\MSSQLSERVER " Backup set #1 on storage media #1 Backup set description: "NIMROD.BAL.local Backup 00043-Incremental" Verify started on 8/25/2015 at 9:18:11 PM. Verify completed on 8/25/2015 at 9:18:11 PM. Verify Set Summary Processed 0 bytes in 1 second. Throughput rate: 0.000 MB/min Server - NIMROD.BAL.local Drive and media mount requested: 8/25/2015 9:18:12 PM Drive and media information from media mount: 8/25/2015 9:18:12 PM Drive Name: Disk storage 0001 Media Label: B2D004748 Media GUID: {edef265e-3c95-4772-9559-dd7fbe238c70} Set Information - \\NIMROD.BAL.local\D: Data Verify Set Information Verify of "\\NIMROD.BAL.local\D: Data" Backup set #1 on storage media #1 Backup set description: "NIMROD.BAL.local Backup 00043-Incremental" Verify started on 8/25/2015 at 9:18:12 PM. Verify completed on 8/25/2015 at 9:18:14 PM. Verify Set Summary Verified 402 files in 409 directories. Processed 52,075,082 bytes in 2 seconds. Throughput rate: 1490 MB/min Server - NIMROD.BAL.local Drive and media mount requested: 8/25/2015 9:18:15 PM Drive and media information from media mount: 8/25/2015 9:18:15 PM Drive Name: Disk storage 0001 Media Label: B2D004749 Media GUID: {e224467f-228a-46f7-90eb-2400dca0d5cf} Set Information - \\NIMROD.BAL.local\C: Verify Set Information Verify of "\\NIMROD.BAL.local\C: " Backup set #1 on storage media #1 Backup set description: "NIMROD.BAL.local Backup 00043-Incremental" Verify started on 8/25/2015 at 9:18:15 PM. Verify completed on 8/25/2015 at 9:18:45 PM. Verify Set Summary Verified 1053 files in 205 directories. Processed 3,857,423,574 bytes in 30 seconds. Throughput rate: 7357 MB/min Job Completion Status Job ended: Tuesday, August 25, 2015 at 9:18:46 PM Completed status: Failed Final error: 0xe0008443 - One or more SQL Database consistency checks have failed. Final error category: Resource Errors For additional information regarding this error refer to link V-79-57344-33859 Errors Click an error below to locate it in the job log Backup- NIMROD.BAL.localV-79-57344-65085 - There was a problem running the DBCC. Error: 802, Severity: 17, State: 20. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped. V-79-57344-65085 - There was a problem running the DBCC. [DBNETLIB][ConnectionRead (recv()).]General network error. Check your network documentation. V-79-57344-65085 - There was a problem running the DBCC. Connection failure V-79-57344-65085 - There was a problem running the DBCC. Connection failure V-79-57344-65085 - There was a problem running the DBCC. Connection failure V-79-57344-65085 - There was a problem running the DBCC. Connection failure V-79-57344-65085 - There was a problem running the DBCC. Connection failure V-79-57344-65085 - There was a problem running the DBCC. Connection failure V-79-57344-65085 - There was a problem running the DBCC. Connection failure V-79-57344-65085 - There was a problem running the DBCC. Connection failure
Bolton_IT
10 years ago Place Backup Exec
3KViews
0likes
10Comments