Does automatic SQL backup truncate transaction logs?
Hi, I have a mixture of of simple and full recovery databases on my SQL Servers and I'm a bit confused how to handle the log truncating in BE 15. It does have the "Automatic" option for this scenario, but neither the option text nor the Admin Guide tell me if transaction logs of full recovery databases are truncated after the backup. More information would be highly appreciated. Thanks, Ralph
SQL Transaction Log job not running, no errors/logs
Having an issue that's very strange. There are 4 jobs eachconfigured for two of my SQL servers, so 8 jobs. The Mon-Thu Full Database backup jobs run to one library partition, the friday jobs run to the other partition for weekly, offsite storage. There are also TLog jobs configured and those are set to backup and flush the logs later in the same overnight. The issue is that the 4 TLog jobs do not run. The are scheduled to run tonight, just like they were last week. There is no lob jog or error message in BE or Wndows logs. It's almost like they get kicked off and just reschedule themselves for the next day. One thing I noticed is that I cannot configure the job to be a Full backup of the logs. When I configure the job as full, the icon is a full orange cylinder, as expected. Then when I choose the log/truncate option, I see the icon change to a half orange cylinder. When I save the config, the icon changes to the quarter orange cylinder, showing it listed asan Inc job. If there's no Full job for an Inc job to refer to, wouldn't that cause this? I'm guessing at this point. Since the issue is happening to both servers' job definitions, I know it's not some error or fluke, but I am perplexed. v14.1 r1786(.1093) 64b
BE 15 Fails to duplicate Most recent full backup
Hi, i can´t get the duplicate thing work on the BE 15 installation (FP1 is installed, no other updates are available). I created a plain new backup of a virtual sql server (Hyper-V) with GRT enabled for SQL and with an additional Log backup. The full backup to disk run´s from 09:20 - 10:47 and is successful. The catalog thing runs from 10:47 - 11:31 and is successful. The duplicate job runs from 12:30 and has the job status Skipped. All data has a retention (Keep for) time of 4 Days ... This is the error message i receive.. Error category : Error : e000e054 - The job was skipped because the source backup job is not present. I deleted the job definition multiple times and created a new job straight forware, no editing afterwards. What´s wrong with BE 15?
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
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