Hi

I am getting this error on Backup Exec 15 only on the System State Job:

V-79-57344-41488 - Due to one or more errors in \\SERVERNAME.misc.local\System?State, this backup cannot be used for conversion to virtual machines, Simplified Disaster Recovery (SDR), or a complete online restore.
V-79-57344-33928 - Access Denied. Cannot backup directory \ and its subdirectories.

Only System State is selected on the selection list

There is a Full and Incremental

AOFO is switched on

Does anyone have any ideas?

Hi All,

I have symantec backup exec 2014 on windows server 2008. but the local HDD space is running on low & cant delete the data present.

Can i create SAN vloume on HP/any storage and mount the lun using iSCSI to windows server, add the lun as iCSCI Hardisk

create local data disk in symantech & use this disk for backup purpose.

has any one tried this, how is the performance of the BE & media server.

Thanks

Hi all,

I have a Server 2012 running out of space. So I need a solution for next month till we go on ne storage. My Plan is to enable deduplication on Windows Server 2012.

My Backup System is Backup Exec 2012 14 Rev. 1798

As I know it is possible to backup with BE 2012 the dedup Data from Server 2012.

And it will re-dedup the data so my volume will running out of space. Is their any strategy to work with dedup volumes?

I mean it make no sense to use Windows Server 2012 dedup and BE 2012 as I see.

Thanks to all.

Hi,

Why am i getting this error on most of my jobs ??? and what does it mean ????

Backup- \\ServerName\C:V-79-57344-41488 - Due to one or more errors in \\ServerName\C:, this backup cannot be used for conversion to virtual machines, Simplified Disaster Recovery (SDR), or a complete online restore.

Storage device "NS Storage" reported an error on a request to write data to media.

Error reported:

The file or directory is corrupted and unreadable.

V-79-57344-34036 - An unknown error has occurred

So one of the benefits of 15 Feature Pack 1 as advertised was up to 62% shorter backups with LTO tape drives.  having updated to FP1, my backup times remain the same.

Without going into the specifics of the systems, I updated all the agents etc to the latest version, are there other tricks that need to be done to increase the speed?  We are backing up directly to tape, with real servers, not virtual.

Does this speed increase just impact virtual servers?

I'm running BE 2012  on Windows 2011 SBS to backup up itself and two Hyper-V VMs.  When I go to "Test/Edit Credentials", I see all of the drives, Hyper-V, System State and SQL Server Instance.  Fine, but I also see two other drives that do not exist.  Those two drives do not appear in the Resource listing, just the Test/Edit Credentials listing, and obviously fail every credential test.  (Needless to say, they don't appear in Disk Management either.)

What is the best way to delete these two phantom entries?

Thanks much.

Hi 

Here is the envt details

BE 15 running on Windows 2012 R2 with the latest patch on the OS and BE Media Server.

Vmware ESXi 6 with VM running Windows 2012 R2 and BE 15

I am trying to backup a DFS server and getting extremely slow throughput of about 1500 MB/min

Further drilling down I found that the system state backup runs at about 250MB/min which is extremely slow. The data backup for the same server/VM can get me speed of about 3000MB/min. 

I am running agent based backups as this DFS server is clustered with a RDM disk hence agentless backup will not work.

Antivirus exclusions for the BE exe has been taken care of and that is not the cause for the slowness. The network is a 1Gb network. 

To further narrow down the issue I ran the windows native backup tool (wbadmin) to backup system state and I still get a speed of only 250 MB/min which rules out the backup software as a cause. 

This should then make it a OS/DFS issue however does anyone have any suggestions on how to proceed further. 

I have checked with the VMware admin and the OS engineer and they dont seem to have any issues with any of their tasks/operations 

Few other points to mention

- The 2nd node of the DFS cluster also exhibits similar slowness

- Non DFS VM's system state backup as expected gives better performance

Any suggestions ?

Hi, I have a Backup Exec 15 installed on 2008 R2. No licenses for agents or options. it is just a file server and need to backup the server itself.

When i run the jobs created, it provides the E000847e error saying that the product is not licensed for the operation. but the test run works fine.

Dont know what the problem is. I just need to back up the local server, no remote servers or computers, just the one server that has BE 15 installed on it.

correct me if i am wrong but doesnt the BE installation have an agent for the local machine, if so, why am i facing this issue?

Any help would be appreciated.

PS: i am new to the thing and was stuck with this product

Hello,

is there any possibility to increasing the waiting time for duplications? The Problem is, that a lot of Backup Jobs start at the same time. The duplicate should start after the backup has finished. But sometimes the library is reserved by another duplications. So the duplicate Job has to wait more than 24 hours and get into the status missed. Is there any possibility to increase this timeout?

Thank you very much in advance,

Daniel

Hi,

I've never used Backup Exec and I Iwould like to know if Backup Exec can answer my requests before to decide to use it for our customers.

Context:

We install our application at our customers, the application use an Oracle database

- The size of database can vary from 30GB to 600GB

- The database is install in a Windows server 2003,2008 or 2012

- The objectif is to backup the Oracle Database running on the server

- Only 1 database to backup (for each installation)

- The backup destination will be a shared network directory

- 1 full backup per day

Requirements:

- Backup Exec + Agent should install on the same server

- Backup should run automatically once a day.

Questions:

- In case when the server crashes, does it easy to restore the database in the other server ?

- Does Backup Exec uses RMAN to do the Oracle database backup ?

- Does the backup set can be used by RMAN ?

- Does it common to install Backup Exec on the same server ? what is your recommandations ?

Regards,

Charles.

Hi

I woke for a small IT-Consulting company in Norway.

Recently a customer came to us with an external hard drive with backup exec backups on.
The server that took the backups was unfortunately deleted (before we entered the picture).

How can I restore a database from this hard drive?

Do I need backup exec? If so, how do I check Backup Exec version?

Is there a program for just restoring?

Thanks in advance

Using BE 2010 R2 (no I am not goinf to update to R3)

When I do a restore job the resource view shows backups from years ago which cannot possibly exist.

In fact, if I schedule a restore I get the error 'e000810d - Physical Volume Library Media not found' which I am pretty sure means the B2D file has long expired and been delete or overwritten.

Is there something I should run to keep the resource index up to date so that it only shows what is actually available for retore?

Many thanks

Dear,

i have one question for Library Expantion Option (LEO).

i have 2 LTO in my company, LTO4 and LTO5 each have1 tapedrives oneachLTO.

if i want to backup data to Tape in2LTOsimultaneously because the data isbacked upsomuch. And2LTOthatwillbe usedforbackupandrestore

how manylicensesLEO should I buy?

please advice. thank you

I am using Backup Exec 15 on a Windows 2012 R2 mashine.

A have already installed the FP1:

But LiveUpdate tries to reinstal it for new:

Hallo  zusammen

ich habe einige Virtuelle Maschinen mit SQL Express. Jetzt stellt sich mir die Frage, ob eine VMDK SIcherung ausreicht oder ob ich die SQL Instanzen nach wie vor mit dem SQL Agent sichern muss, um im Wiederherstellungsfall ggf. einen konsistenten Zustand zu erreichen?

Freue mich schon auf Eure Tipps und Ideen. 

LG Thomas

I'm using Backup Exec 2014. And I want virtualize physical server Windows Server 2003 R2 with SQL Server 2000 installed.

I created One-time convertion to a virtual machine job. In the job I checked all resources.

This job finished with error: V-79-57344-833 :

The copy-only backup type is only supported by Microsoft SQL Server 2005 and later releases.

How can I convert physical server in this case?

Hello,

I've got a problem on my server.
My server is a Windows server 2008 backuping himself with a backupexec 2012. This windows server is a Domain Controller isolated and in his own domain.
He is the only one connected to a LTO4 solution.

My server crashed, I reinstalled Windows 2008 on the machine and reinstalled backupexec 2012.

When I try to restore a full backup from the tape on himself, he rejects it. I think he doesn't want to overwrite his own OS and disk.

Do you have some advice for my problem?

TLDR:
Windows server 2008 + backup exec 2012 (with LTO4 connected).
Need to restore on himself after a crash, doesn't want to restore on himself.

Further to this issue - I am getting the following error in the backup logs:

Job ended: Wednesday, August 26, 2015 at 10:06:31 AM

Completed status: Failed Final error: 0xe00094a1 - The trial period for Backup Exec or for an agent or option has expired.

You must enter the serial number to continue. Final error category: Job Errors

I have the V-RAY installed on the Backup server and am backing up the separate Hypervisor.
The Hypervisor (Windows Hyper-V) has the agent installed and the Windows VMs also have agents installed. I have set the backup so that the only items being backed up are the VMs thmeselves.

Is there any way to get more informative information on which license is failing?

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

I'm looking for some thoughts on where to begin looking for a problem we encountered last night.

We're running backups to a Seagate 8TB USB drive using a USB3.0 port. Typically our nightly incrementals are between 400 and 700MB/min and the full backups end up around 2000-2500MB/min.

Last night we now see a speed of 130MB/min.

We had some trouble with the USB drives and Windows not releasing the driver, so a reboot was required. (we always eject the USB media rather than just unplugging it). And we also just added a new disk to the RAID array, but the full that ran after that upgrade was fine.

Any thoughts about what to test or look for?

I'm thinking i'll just try a reboot and re-test. It seems really random.