Hallo every body.

We use backup exec symantec 2010. Now i got a problem. I want to change the daily tape, but i can not eject the library. There is a sign tape Jammed, type DF. The question are: 1. what the meaning of this? 2. How to solve it? 3. all the slot give sign empy, but it is not empty. Since that happed i can not make back up anymore. Please help, it urgen. My email is : fesudiyono@mendelcollege.nl.

Please help me it is urgent!

Edhy.

Every week I get this error, since upgrading to BE 2014:

\\SELMA.rl.int\C:\Windows\SYSVOL\sysvol\rl.int\DO_NOT_REMOVE_NtFrs_PreInstall_Directory was not found, or could not be accessed.

I've looked at the other threads, and they all reference windows upgrades.  This was/is a clean install of Windows 2008 R2.  This is, however, an upgrade from BE 2010 R3 to 2014.  This has been a problem every since the upgrade.  I've tried 'excluding' the file from the backups, but it still errors.  I guess it has to find it to exclude it.  I can find the directory, is't there, just hidden (RHSD) , with permisions that dont include the BE service account and exclude 'List Folders' and 'Read' permisons to domain administrators and SYSTEM.  This is on the same machine BE is installed on, so Media Server and secondary Domain Controller

Is this as simple as adding Read and List Files and Folders to SYSTEM.  I'm hesitant to add the backup service account, but that seems logical too.  Thoughts?

Dan

My previous thread about this got locked, so I'm starting a new one:

Every once in a while, one of the jobs on my BackupExec 2012 media server backing VMware VMs with GRT reports, for one of the VMs:

V-79-57344-38725 - Ein oder mehrere virtuelle Datenträger enthalten Datenträger, die Granular Recovery Technology (GRT) nicht unterstützten. Für diese Datenträger können keine selektiven Wiederherstellungen ausgeführt werden. 

Translation: One or more virtual storage media contain storage media that did not support GRT. For those storage media no selective restores can be performed.

On the next run, the same VM will usually back up just fine again. The VMs for which this happens vary across the whole set. Indeed, on the last three backup runs, I had two different VMs reporting this problem, ie. one did not support GRT on the incremental backups Wednesday and Thursday but did on the full backup Friday night, while another one did support GRT on Wednesday and Thursday but not on Friday, and both of these didn't see any problem supporting GRT on Tuesday.

On my last posting I got the recommendation to open a support case should this happen again, but that's always extremely time-consuming and frankly I don't see how it might lead anywhere as Symantec support, in my experience, needs problems to be reliably reproducible in order to investigate them.

Dear All,

When I click on the tools > recipient  an error appears in the event viewer (.net runtime 2.0 error - event ID 1000 - Faulting application beserver.exe, version. I want to add a new email address to the notifications. Its a windows 2003 standard SP2 server

Backup Exec then falls over the communications go off-line and the backup exec server services shuts-down.

I logged a call with Backup exec and they just said its a 3rd party issue (.Net) and not a lot they can really do

I may need to uninstall .net 2.0 and re-install from the BackupExec 2010 CD (as suggested from symantec). Has anyone seen this error and fixed this?

I have ran a repair in Backupexec and this did not fix it.

Let me know

Thanks

We have Backup Exec 2012 on a server and we moved the server to a new domain. Ever since then, when BE is launched, it can't connect because it's trying to reach the old domain. Is there a way I can easily copy the backup jobs that are already created? I'd really hate to have to set them up again.

Thanks.

Hi,

We have the following :-

1. MS Exchange 2013 CU2 on Win 2012 Server STD (64 bit) as VM in VMware.

2. BE 2014 on Windows 2008 Std (32bit). in a physical server.

IS there going to be any challange to take backup and GRT restore

These Exchange server is on HA based Exchange 2013 (two server).

Thanks
 

Hello,

Is it possible to start job on BE server from RALUS client?

This is because the data must be previously prepared by some scripts.

Hi everyone.

I am having problems with Symantec Backup Exec Agent 2014. 

I have installed Symantec Backup Exec 2014 on a Windows Server 2012. Now to perform a test I have installed Backup Exec Agent on a client computer (Windows 7 Enterprise) in order to backup some files. Please note that the client and the server are in the same domain. All services are running. Unfortunately, I cannot backup any files as it always as the Remote Agent cannot establish a trusted connection to the server. 

I have try several to establish trust between the client and the server through the Server window on the Backup Server Exec. It shown me that it had establish the trust. However, I cannot perform any backup as it always shown me the error message Remote Agent not trusted. 

On the Backup Agent Utility on the client, on the security tab it gives this warning message: "Unable to initialise certificate store path". Can someone help me please. Is the problem with the domain or the services. Thanks

3 hosts in the Hyper-V 2012 cluster and few CSV volumes.

The slow backup performance (around 1xxx MB/min in backup exec) will occure when it meets the following scenario :

1. VM on Node 1 and CSV 1

2. CSV 1 owner is Node 2

When i change the owner of CSV 1 to Node 1, the backup performance will return to normal (over 6000MB/min in Backup exec).

Currently running Backup Exec 2010 R3 on a Windows Server 2008.

We are in the middle of moving serving servers on to a new domain which this verison of BE is currently residing on.

One of the engineers wanted to move a server across but didn't inform us.  The server was taking out of the old domain, renamed and re-introduced into the new domain.  

Now when the backups run we see an error message:

Error Category:Resourse Errors

Error:e000felf - The device cannot be found

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

I can understand what has happened.  (server needed to be removed from BE before the server was taking out of the old domain and renamed)

Question I have is there any way of taking this server out of the backup schedule without deleting the schedule and recreating it?

Can the server be deleted from BE so the schedule doesn't refer to it?

If someone can help, that would be greatly appreciated.

Regards

Hitesh

Buenos días.

Tengo un servidor con el sistema operativo Windows 2003 y Symantec Backup Exec 2012.

El servicio Backup Exec Remote Agent for Windows no termina de arrancar y tampoco consigo detenerlo. He utilizado la herramienta taskkill y lo detiene.

Se ha reiniciado el servidor y tampoco.

Rogaría por favor una respuesta.

Muchísimas gracias por la atención prestada.

Hi I was wondering if its possible to backup to a remote server (NOT ON THE SAME NETWORK), through Backup Exec?

I have a Synology NAS213 at home and I want to make backup to that location.

Can I use FTP to backup to my NAS, will backup exec accept something like (just an example):  ftp://188.179.180.190:21/backup

Or is there any way to do this at all?

Kind regards

Michael

I am running Backup Exec 2012 SP4 (ver 14 Rev 1798) running on a Windows Server 2008R2 SP1 dedicated physical server.  This server backs up a number of physical and virtual Windows servers to a deduplication disk store located on the same box.  In the BackupExec\Logs directory there is a log file that is growing at about 100MB per day.  It contains the same message repeated many times a second:

[08/25/14 16:29:27]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:27]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:27]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:27]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:27]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:29]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:29]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:29]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:29]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:29]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:29]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:29]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:29]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:29]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:30]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:30]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:30]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:30]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:30]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:30]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:30]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:30]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:30]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:30]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:30]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:30]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:30]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:30]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:30]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:30]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:30]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:30]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945
[08/25/14 16:29:30]:[6548:4512]:[1]: DynamicQuery::DeleteObject(line 2360) : DynamicQuery::DeletePdi : DSPDIEnumerator::DeletePdi Call Failed EngineError Code -536836945

Can anyone tell me what this means and how to fix this?

We are currently running Backup Exec 2012 SP4 on a Windows 2008 R2 server.  For security reasons we need to upgrade the SQL 2005 Express to SQL 2012 Express.  I am looking for some instructions on how to do this with the least amount of headaches.  I appreciate any help you can give me.

Maurice

Hello all

I need to transfer the catalog from backupexec 2012 on a windows 2008 R2 server to backupexec 2014 on a windows 2012 server

Is any safe way to do it?

or else how can i migrate the old version backupexec (jobs not neccessary) to the new 2014 in a different server ans OS ?

Thanks .

My SQL db backup is completing with this exception: 

V-79-40960-37914 - Database DBNAME is configured to maintain transaction logs.  Transaction log backups are not being performed.  This will result in the log growing to fill all available disk space.  Regular log backups should be scheduled or the database should be changed to the simple recovery mode.

It's doing this for 4 databases. I checked my transaction log backup job and under Selections, I noticed those 4 databases were not checked. I checked them all off and figured that would be the end of it but the next backup still threw that warning again telling me that log backups are not being performed.

here's a screenshot the log backup selection list

As you can see, those 4 databases are selected.

I am trying to build a test environment based on my production environment (single domain).  I have done this in the past using BE 2010.  I have recently gone to BE2014 and am now trying to build from scratch starting with a media server and then restoring a DC (the one with the Operations Master Roles).  The media server is up (though it's not a clone of production, its just a new server with backup to disk files that have been cataloged). 

SDR backups are enabled in my production environment and I have the DR file.  I have tried to do the restore by booting to a new SDR disk and then attaching a local USB drive with the backup files and DR file.  This starts working but fails at the system state restore.  I have also tried doing a manual recovery by installing the correct operating system (Windows 2008 R2) and pushing out the agent to it and restoring the C: drive with no issue but once it gets to the system state, I get the same error message as the SDR restore which is:

Final error: 0xe000fee1 - A failure occurred writing an object.

Restore - \\servername\system?state

V-79-57344-65249 - A failure occurred writing an object.  Error writing security data stream.

I have tried several different ways such as fully restoring all components at once or just restoring the C: drive and then after doing the system state.  I've tried doing this in a normal startup as well as Directory Services Restore Mode.  Nothing works and always fails with the same error during the system state restore.  The C: drive restore is always successful.  All credential checks pass and are all set to use to the local administrator password on the new server.  I'm wondering if that is the problem since when it becomes a DC, there are no more local administrator accounts.  However, since this is the first DC in the test environment, I cannot use a domain admin account either to do the restore, since one doesn't exist yet.  However, this wouldn't be the case with the local SDR restore failing. 

I have made sure that restore over existing files, restore all information for files and directories and preserve tree were all selected and "mark this server as the primary arbitrator for replication when restoring folders managed by the File Replication Service or when restoring SYSVOL in System State" is selected.

I do not have Symantec Endpoint Protection so this article does not apply to me: http://www.symantec.com/docs/TECH216782

The symptons in this old article (http://www.symantec.com/docs/TECH61916 ) are exactly what happen to me: "After the restore of the System State fails, the server will reboot itself and be left in a completely unusable state. The server will boot into a black screen, then eventually reboot itself, and get stuck in a loop where it continually does the same reboot."  This workaround and solution both don't apply to me.

I have followed this guide: http://www.symantec.com/business/support/index?page=content&id=TECH86323 which worked in 2010 but am having no luck in 2014.  The 2014 admin guide unfortunately lacks information on this topic.  I also wish there was an updated guide as this one is 3 years old and doesn't pertain to BE2014 (or even 2012 for that matter) or to any new server OS's.

I have not yet opened a ticket with Symantec on this and may have to but figured I'd start here since it's easier.  Any help you can provide will be appreciated. 

Thanks in advance.

I need to dermine if service pack 1 is installed on a Linux system running BE2010 R2, the RALUS version shows 4164.5, but I not able locate any document showing that it is SP1.  Any help is apprectiated.

Hi,

I've been looking into protecting our backup tapes with either encryption or password protection.

We basically perform a backup to disk onto the backup exec server every night and then a duplicate job copies these to tape. We are using a HP StorageWorks Ultrium 920 LTo3 drive.

I know that encryption is going to add an overhead to our jobs so I thought it could just be added to the duplicate tape jobs that copy data to the tapes - not the actual backup to disk jobs. Is this feasible?

Would this have inpact on the backups that are done to disk?

Is the above drive capable of hardware encryption or do I need to set software encryption? Is another option just top password protect the tapes - although I can't see this option?

Thanks in advance.