Hi,

I am trying to perform a clean job on our tape drive using symantec backup exec 12.0.

I just inserted a new cleaning tape,but still it says cleaning drive expired. On the backup console it still shows the old cleaning tape information. is there anything i need to do after inserting a new cleaning tape.

Attached the error message.

Hi,

Another set of BE queries...

I am trying to understand how the Duplication stage works in a job.

Currently I am targeting dedupe first... then adding a stage for Duplication...

Scenario 1

I create a job to perform full backups on Friday and differentials Monday to Thursday. For both stages I set them to start backing up data to the dedupe store at 6PM and cancel the job if it is still running at 8AM the next day. I then add two stages and select "Duplicate immediately after source task completes" and select Full for one stage and Differential for the other.

Are the duplication jobs bound by the schedule of backup? I.e if the backup job finishes at 7AM, will the duplication job cancel at 8AM or will it simply go on until it has finished?

Scenario 2

Instead of selecting "Duplicate immediately after source task completes" I select "According to schedule" and set it to "All backups" (Or "Selected backups" - I do not think this matters for this scenario)... This is then working fine... However at some point in the future I miss some duplication jobs (Issue with tape drive or tapes etc), or I just do not want to do any for a while so I place the duplication stage on hold... Once I take it off hold it is going to want to duplicate all the sets it has missed so far...

How can I avoid this (I want it duplicate all jobs going forward but not the ones it has already missed)... Can I simply remove the duplication stage and save the job, and then re-open it and add it back or do I have to re-create the entire job? I think BE2012 had a similar issue with duplicating media sets that had already been expired???

Scenario 3

I keep my "According to schedule" setting... How is this actually linked to the backup stage?? Does the duplicate stage wait for the backup stage to complete or do they both simply share the selection list? For example... If I create a job to perform full backups on Friday and differentials Monday to Thursday. For both stages I set them to start backing up data to the dedupe store at 6PM and cancel the job if it is still running at 9AM the next day. I then add the duplicate stage selecting "According to schedule" and set this to run at 8AM... If a backup job is still running at 8AM, (Assuming all the previous days jobs have already been duplicated) will the duplication task simply start and then fail because the backup job has not finished and therefore there is nothing to duplicate? Or it will duplicate what has already been backed up (Assuming multiple selections in a selection list...)?

If anyone can help I would appreciate it....

PS... It would be nice if Symantec had a Last Differential/Last Incremental option in the "According to Schedule" window... This would resolve a lot of my issues... as if I missed a duplication job I would know exactly what I was missing and would not have backups queued up for the next duplication window!

Hi,

i need to restore some Exchange 2010 PF items.
Backup works fine for backups of IFS and PFS ...

But restore failes with strange errors ...

I did a test backup of a small PF Folder, everything is fine (servername is mexiko).

Now i deleted this PF within outlook and tried to restore the PF.

I received strange errors, complaining about

V-79-57344-65069 - One or more items could not be read correctly during the backup. This may be due to corruption of the file system, controller, or disk, or if a portion of a file is locked. Review the Windows Event Logs, run the appropriate Windows diagnostic tool, and then try running the backup again.

V-79-57344-765 - Cannot set one or more properties for Backup Exec Alert: Job Success (Server: "JEMEN") (Job: "176.28.53.241 Datenbanken-Incremental - Datenbanken Log") .

I have a Windows 2012 R2 server with BE 2014 and latest hotfixes installed.
I have installed Exchange 2010 SP3 with CU3.

any idea

Thanks

Jürgen

Hello,

i need to restore some Exchange 2010 PF items.
Backup works fine for backups of Pulic Folder Store ...
But restore failes with strange errors ...

I did a test backup of a small PF Folder, everything is fine (servername is mexiko).

Now i deleted this PF within outlook and tried to restore the PF.

I received strange errors, complaining about

V-79-57344-65069 - One or more items could not be read correctly during the backup. This may be due to corruption of the file system, controller, or disk, or if a portion of a file is locked. Review the Windows Event Logs, run the appropriate Windows diagnostic tool, and then try running the backup again.

V-79-57344-765 - Cannot set one or more properties for Backup Exec Alert: Job Success (Server: "JEMEN") (Job: "176.28.53.241 Datenbanken-Incremental - Datenbanken Log") .

I have a Windows 2012 R2 server with BE 2014 and latest hotfixes installed.
I have installed Exchange 2010 SP3 with CU6.

Exchange Serer runs as a VM Guest on Hyper-V.

any idea

This is displayed during the job ...

Thanks

Jürgen

Hello folks!

We are running Backup Exec 2012, with a weekly backup of our primary server that has Exchange 2010.

The server has a 1TB drive, and a quick overview of the local partitions shows we are using 415GB.

Question 1 (primary):

The Backup-Full process just completed successfully and the backup set is taking up 407GB.

Immediately following that backup, Backup Exec seems to run a Backup-Full-Meta Data Index-Catalog 000##.

The web tells me this is an index of all the files stored in the aforementioned Backup-Full. That sounds perfectly reasonable.

Less reasonable, perhaps, is that this process (which also completed successfully) seems to be using up an additonal 280GB.

This is posing a problem as we only have a 1TB backup disk, and the bi-weekly differential (weighing in at 100GB, with another 100GB catalog) coupled with a small backup of our Sharepoint database (on a separate vm) is getting us very close to our cap.

Can someone please tell me if the 280GB is normal?

Question 2 (secondary):
The fellow that configured our application also set up two additional backups. One is a full backup of a different VM (the aformentioned Sharepoint databases reside ont hat VM), and another is a backup process for "Server Farm 1". Is this a normal thing that someone can explain to me? I'm relatively new to Backup Exec terminology, so I have a hard time differentiating between Symantec's structural processes and our IT team's configuration decisions. The configuration lists the following backup sets: "ConfigurationV4-DB (Server\Sharepoint\Sharepoint_ConfigurationDatabase)", "Microsoft Sharepoint Foundation Web Application", "Services", "Shared Services", "Sharepoint Foundation Search", and "WSS_Administration". I don't really understand why all these items need to be backed up separate from the full backup of our primary server, so any insight you can offer would be much appreciated.

Thanks everyone!

-Rich

I've just installed and configured Backup Exec 2014 on a Windows 2012 R2 Hyper-V server and I'm receiving the following exception when I attempt to run a differential backup of my VMs with GRT enabled:

During Granular Recovery Technology (GRT) operations, the necessary boot configuration files could not be loaded. Backups that were enabled for GRT may not be available for restore.

No data is available for restore for these differential backups.  Full backups succeed without issue.  This exact error happens on both environments that I've installed BE 2014.  Guest VMs are all Gen 2 VMs and both have 2012 and 2012 R2 guest VMs.

I started managing a server that has an old copy of Backup Exec V12.0

I could never get console to work.

I did an uninstall by add/remove but it did nothing. Program is still there.

I know this is a probvlem. Several searches point to a KB article that is no longer there. The KB is to manually remove it.

I either need the instructions for a Manual remove of Backup exec 12.0 or is there a Cleanwipe for this?

I can enter the file extension which I want to backup in "Backup Selections" => "Include/Exclude" => "Name", can I enter more than one extension, such as "**.DAT; **.EXE"?

Moreover, should I use one or two asterisks?

BE2014 restore of Exchange 2013 DAG:

-) restore folder to .pst, okay

-) restore db is okay too

-) restore of individual items, e.g. mails to original location Inbox failed with V-79-57344-959, attached the error-file

-) restore a mailbox to .pst works 

Exchange 2013 running on W2012, Backup on W2k8r2, BE2014 patched with HF218257.

Hi! Can anyone tell me how many CEU/CPEs are earned when taking the Backup Exec 2012 Administration course? I can't seem to find that information when I look at the course description nor anywhere else on the training site. Thanks!

Backup Exec 2012, Server 2003, Exchange 2007, Exchange agent installed.

For the first time I have tried to restore an individual email that was deleted yesterday, it is on my last two hard drive backups (in addition to tape). I am restoring from disk (not tape) to the original location and have selected “recreate user accounts and mailboxes if they don’t exist”.

I have tried a few times but keep getting the error below.

The job failed with the following error: Unable to attach to a resource. Make sure that all selected resources exist and are online, and then try again. If the server or resource no longer exists, remove it from the selection list. Edit the selection list properties, click the View Selection Details tab, and then remove the resource. "

Most things on the web refer to log-on credentials but the “test credentials” shows success. 

Do you have any advice on what I should try next?

Thanks,

Julian

Hi Support,

I'm getting this strange error that re-ocours when running the daily backups, I'm using BackupExec 2010 R3 on Server 2008 R2.

Job ended: 29 July 2014 at 03:24:00
Completed status: Failed
Final error: 0xe00002f7 - Cannot extract mailbox messages from the Exchange backup. Review the job log for more information.
Final error category: Resource Errors

For additional information regarding this error refer to link V-79-57344-759

Backup- \\EXCHANGE10\Microsoft Information Store\earthlondon
V-79-57344-759 - Unable to complete the operation for the selected resource using the specified options for the following reason: VFF Open Failure.  This can be caused by low memory or disk resources.
 

Any suggestions on troubleshooting?

Thanks alot

There is a known issue within BE 2012 where for whatever reason, jobs that were confingured in the console mysteriously disappear, and a flashing warning icon appears in the lower left corner of the application window that states "The query for JobView failed".  I have read in several posts that there was a specific hotfix for this issue and that Service Packs as early as SP1a and SP2 resolve the issue.

When I encountered this issue, I ran Live Update and was offered Service Pack 4 which I installed, then presented a hotfix which I subsequently installed.  However, neither of these installs resolved the issue as it still persists.

I have read in other posts that deleting records from the BEDB database in SQL resolved the issue, however, the posts did not specify which records from which tables needed to be deleted, and I am not comforatble with arbitrarily deleting database records without first knowing the impact a deletion will have on related tables.

Does anyone have any suggestions on how one might resolve this issue either through specifics on which table(s) to delete specific records from, or through another working solution that I have not mentioned above?

I am using BE 2012 64-Bit running on a Dell Server with Windows Server 2008 R2 installed.

My Backup Exec 2012 SP4 installation continues to act up. I know that I should upgrade to BE2014 but my requests on that front haven't been very successful either. In the meantime, please bear with me.

The last incremental run "failed" with these errors listed in the job log:

Sichern- \\GOLGI.artegic.local\C:Verzeichnis TEMP\Backup Exec\MP00\C\Backup\2013-05\ wurde nicht gefunden, oder es war kein Zugriff möglich.
Im Verzeichnis befindliche Dateien oder Unterverzeichnisse werden nicht gesichert.
V-79-57344-33967 - Das Verzeichnis bzw. die Datei wurde nicht gefunden, oder der Zugriff ist nicht möglich.
V-79-57344-65033 - Directory not found. Cannot backup directory \TEMP\Backup Exec\MP00\C\Backup\2013-06 and its subdirectories.
V-79-57344-65033 - Directory not found. Cannot backup directory \TEMP\Backup Exec\MP00\C\Backup\2013-07 and its subdirectories.
V-79-57344-65033 - Directory not found. Cannot backup directory \TEMP\Backup Exec\MP00\C\Backup\2013-08 and its subdirectories.
V-79-57344-65033 - Directory not found. Cannot backup directory \TEMP\Backup Exec\MP00\C\Backup\2013-09 and its subdirectories.
V-79-57344-65033 - Directory not found. Cannot backup directory \TEMP\Backup Exec\MP00\C\Backup\2013-10 and its subdirectories.
V-79-57344-65033 - Directory not found. Cannot backup directory \TEMP\Backup Exec\MP00\C\BEW-4649c0a3beb14030a2b40466c5bbfc7a and its subdirectories.
V-79-57344-65033 - Directory not found. Cannot backup directory \TEMP\Backup Exec\MP00\C\BEW-ff5afad9123e40408a2536656840f390 and its subdirectories.
V-79-57344-65033 - Directory not found. Cannot backup directory \TEMP\Backup Exec\MP00\C\Config.Msi and its subdirectories.
V-79-57344-65033 - Directory not found. Cannot backup directory \TEMP\Backup Exec\MP00\C\dakotaag and its subdirectories.
V-79-57344-65033 - Directory not found. Cannot backup directory \TEMP\Backup Exec\MP00\C\Documents and Settings and its subdirectories.
V-79-57344-65033 - Directory not found. Cannot backup directory \TEMP\Backup Exec\MP00\C\Dokumente und Einstellungen and its subdirectories.
V-79-57344-65033 - Directory not found. Cannot backup directory \TEMP\Backup Exec\MP00\C\Drivers and its subdirectories.
V-79-57344-65033 - Directory not found. Cannot backup directory \TEMP\Backup Exec\MP00\C\Hotfix and its subdirectories.
V-79-57344-65033 - Directory not found. Cannot backup directory \TEMP\Backup Exec\MP00\C\MSOCache and its subdirectories.
V-79-57344-65033 - Directory not found. Cannot backup directory \TEMP\Backup Exec\MP00\C\PerfLogs and its subdirectories.
V-79-57344-65033 - Directory not found. Cannot backup directory \TEMP\Backup Exec\MP00\C\Program Files and its subdirectories.
V-79-57344-65033 - Directory not found. Cannot backup directory \TEMP\Backup Exec\MP00\C\Program Files (x86) and its subdirectories.
V-79-57344-65033 - Directory not found. Cannot backup directory \TEMP\Backup Exec\MP00\C\ProgramData and its subdirectories.
V-79-57344-65033 - Directory not found. Cannot backup directory \TEMP\Backup Exec\MP00\C\Programme and its subdirectories.
V-79-57344-65033 - Directory not found. Cannot backup directory \TEMP\Backup Exec\MP00\C\Recovery and its subdirectories.
V-79-57344-65033 - Directory not found. Cannot backup directory \TEMP\Backup Exec\MP00\C\System Volume Information and its subdirectories.
V-79-57344-65033 - Directory not found. Cannot backup directory \TEMP\Backup Exec\MP00\C\Users and its subdirectories.
V-79-57344-65033 - Directory not found. Cannot backup directory \TEMP\Backup Exec\MP00\C\Windows and its subdirectories.
V-79-57344-65033 - Directory not found. Cannot backup directory \TEMP\Backup Exec\MP00\C\xampp and its subdirectories.
Verzeichnis TEMP\Backup Exec\MP00\E\ wurde nicht gefunden, oder es war kein Zugriff möglich.
Im Verzeichnis befindliche Dateien oder Unterverzeichnisse werden nicht gesichert.
V-79-57344-33967 - Das Verzeichnis bzw. die Datei wurde nicht gefunden, oder der Zugriff ist nicht möglich.
Verzeichnis TEMP\Backup Exec\MP00\T\ wurde nicht gefunden, oder es war kein Zugriff möglich.
Im Verzeichnis befindliche Dateien oder Unterverzeichnisse werden nicht gesichert.
V-79-57344-33967 - Das Verzeichnis bzw. die Datei wurde nicht gefunden, oder der Zugriff ist nicht möglich.
Verzeichnis TEMP\Backup Exec\MP00\Volume{d71c15c5-c185-11e3-9488-806e6f6e6963}\ wurde nicht gefunden, oder es war kein Zugriff möglich.
Im Verzeichnis befindliche Dateien oder Unterverzeichnisse werden nicht gesichert.
V-79-57344-33967 - Das Verzeichnis bzw. die Datei wurde nicht gefunden, oder der Zugriff ist nicht möglich.

(The cute mix of English and German is a fallout of my last WebEx session with Symantec support where the engineer set my Backup Exec language to English. I have since deleted the registry key he added, but apparently some parts of Backup Exec cling a bit longer to that setting than others. Anyway, the German parts say exactly the same thing as the English ones.)

The directory "C:\Temp\Backup Exec" is empty except for a single file named "ese.dll", and I don't remember ever seeing anything else in it. So Backup Exec is correct in reporting that all these directories do not exist. The big question is: why does it complain about that, and should I care?

The job log also reports:

Snapshot Technology: Started for resource: "\\GOLGI.artegic.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).

(Sic!) So even if a directory "C:\Temp\Backup Exec\MP00" with all these subdirectories did exist when the nightly run was started and was somehow removed during the backup run, shouldn't the snapshot technology have prevented that complaint?

After a VMware Tools update on one of my VMs backed up with Application GRT, Backup Exec 2012 SP4 started complaining:

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 'lexware'. However, only one VSS Provider can be used on a virtual machine. You must uninstall the VMware VSS Provider. 

Indeed, the VSS support component of VMware Tools had mistakenly be installed with the update. However, after manually uninstalling that component as recommended by http://www.symantec.com/docs/TECH142521, the error persists.

What can I do?

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?

I'm new to backing up to the cloud. I know how to enable it in BE2014 but how do you actually back up to the cloud. One of our clients would like to backup to the Cloud so I'd like to get familiar with the process. Does it get backed up to the drive and then it gets pushed to let says Amazon or Google cloud or does it backup directly to? Right now we are runing server 2012 and backup exec 2014.

After the Installation from Backup Exec my Backup Exec Server Service fails. The Event View says internal Error 536813108 and the backup exec server service detect an schema error. Who can help me ?

A few very basic questions relating to backup exec 2012:

1) On the backup and restore tab - how accurate is the data held with the last backup column

2) How do servers appear in the backup and restore tab in the BE 2012 console, i.e. how do you register a new server in backup exec? Or is it doing an inventory of your network and reporting the status of all servers - or just those "registered in BE?"

Hi,

As above really...

I am creating backups of VM's (VMware) using AVVI agent with SAN Transport. These VM's do not have the Backup Exec RAWS agent installed.

I have selected the VSS Copy option with no GRT options.

When I do a backup of a server which has SQL installed looking at the MSDB.dbo.backupset table it shows the AVVI backup by Backup Exec as having

is_snapshot as 1 (Meaning snapshot backup)

is_copy_only as 0 (Meaning not a Copy Only)

Should this not be being flagged as a Copy Only backup so the AVVI VMDK backup does not interfere with SQL Agent based backups?

Does this mean the AVVI agent is in fact performing a full SQL backup?

Thanks