Hello,

Following a drive corruption, very few of the *.bin and *.bhd files in our deduplication drive dissapeared - and now the whole deduplication folder is offline, in 'undiscovered' state. I tried deleting and recreating it - that just removed it without being able to recreate it at all. The BackupExec deduplication Engine service refuses to start, and in the Spoold.log file we have entried like these:

June 04 05:34:36 ERR [0000000000DE9400]: 25002: _storeCheckContainers: container data file E:\DD_Files\data/70007.bin is missing

June 04 05:34:36 ERR [0000000000DE9400]: -1: _storeCheckContainers: container index file E:\DD_Files\data/72948.bhd is missing.

June 04 05:34:36 ERR [0000000000DE9400]: 25002: _storeCheckContainers: container data file E:\DD_Files\data/72948.bin is missing

June 04 05:34:36 ERR [0000000000DE9400]: 25002: Could not initialize DataStore Manager

June 04 05:34:38 ERR [0000000000DE9400]: 26016: Store Manager: Activate failure.

Does anyone have a utility that could fix this?

Would you please Advise which Logon Account should we provide to our  Backup Exec application  in order to avoid such Error Messages after performing our daily Backup Operations . I 've attached a screenshot of the Error msg the we are getting in our Backup Server .

Hello,

Recently the company i work for purchase two new Linux file server and we decided touse Symentac Backup Exec.

We choose a company specialized in this product for the installation. Everything work fine except one thing, on one of the server the client side deduplication does no work.

Normally, they both have the same configuration but for one it works and for the other it doesn't and i dont know why.

I've looked everywhere but i can't find why, so i came here to see if you have encourtered this problem too and if you have a solution ?

Thank you for your time.

During a test restore of some test documents of my fileserver I discovered that 4 out of 22 documents (Word&Excel) seem to be corrupt after restore. At first I thought it was related to degraded tapes. My intial restore was from tape. No errors show up during backup or restore.

This morning I restored the same content but now from a B2D and discovered I had the same problem.
To not overwrite the original contents, I restored to a redirected folder.

My backup job makes a backup of a DFS share.
FileServer\Shadow Copy Components\User Data\Distributed File System Replication\DFS Share\Test Folder

I restored the following data
FileServer\User Data\Distributed File System Replication\DFS Share\Test Folder

My FileServer is a Windows 2008 R2 Storage Server and my media server is a Windows 2003 x32 Backup Exec 2010 R3 server.

Has anyone seen this behaviour before?

Remko

Hi,

Perhaps my problem will be quick to solve for you, as I think it's a comprehension matter.

FACTS : I have a Backup Exec 2012 server on a physical server (Win2008 R2), and I'm running tests to make a non-authoritative backup of an Active Directory (the system state and system drive C) on a remote computer.

Because I don't want the remote computer to mess with others computer, it's on a different subnet and it communicates only with my Backup Server.

RESTORATION : I've selected this kind of restoration : "Complete the online restore or restore a computer system components" and then "Active Directory, ADAM/AD LDS and/or system state", and as a target, the C drive of the remote server. It's worked like a charm.

Now I've got a nice tree folders (Active Directory, Registry, ...) on the C drive, but I sincerly don't know what to do with this.

I've already tryed to use ntdsutil.exe to import it, or to reboot <F8> in Active Directory Restoration Mode ...

According to Symantec tutorial (http://www.symantec.com/business/support/index?page=content&id=TECH86323), to perform a non-authoritative remote backup of an AD, we just have to reboot the server, and it's finished (step 11). But as I followed the tutorial step by step until the number 11, I just couldn't get this to work.

if anyone have an idea how to deal with this, I woud greatly appreciate his help,
Thank you very much for your support :)

Regards,

Alexander.

Bonjour,

Mon entreprise à acheté récemment deux nouveaux serveurs de fichier tournant sous OES11 (novell). Nous avons choisi d'utiliser Symantec Backup Exec 12 pour gérer les sauvegardes de ces serveurs.

Nous avons fait appel à une entreprise extérieur spécialisé dans SBE pour faire l'installation. Tout fonctionne parfaitement excepté pour une chose : la déduplication coté client pour un des serveurs.

Les deux serveurs sont configurés pareil, ont le même OS et les mêmes composants. Pourtant sur l'un des serveurs la déduplication coté client fonctionnent et sur l'autre non.

J'ai cherché partout mais je n'arrive pas à trouver le problème. Je viens donc ici afin de voir si vous aussi vous avez eu ce genre de problème et si vous avez une solution à me proposer ?

Merci d'avance pour votre aide.

We have a problem where our BE agent crashes right at the beginning of a backup. This doesn't happen every time we run a backup, and it doesn't happen every day. It happens randomly and without warning, on b2d jobs and on tape jobs. It seems to affect 2-3 tape backups per week, and happens about 3 times a week on other jobs. The workaround we have is to restart the BE services, but we still lose a backup when this happens. I have tried dropping and rebuilding the database, but the problem persists. This is running on a 2008r2 server. Is this a known issue? Can you recommend a course of action?

Thanks!

Can someone tell me if this article is still valid?

http://www.symantec.com/connect/blogs/how-protect-backup-exec-itself

We are currently backing up the entire C Drive directory.  I need to know if all we need to backup is the Data & Catalogs folders for disaster recovery purposes.

I just addeda HP autoloader to our network and put in 8 new LTO5 tapes. All of the tapes show a capacity of 0 and the tape drive goes offline everytime I try an action

Where is “Overwrite Media When this Job Begins” in Backup Exec 2012?  According to my Data Migration report, it will be changed to “Append to media, overwrite if no appendable media is available” but I don’t like that because I only have limited storage space. I need to change that to “Overwrite Media When this Job Begins” on all my Backup-to-disk” jobs.  Where is this setting?

Check the attachment of what I am talking about.

Hi Guys,

     My bakcup exec encountered a trouble when back up data from a server (other servers are Okay), error informaitongs below;

Verify- \target server\   end of backup set encountered on HP 000x.

V-79-57344-34004 - End of data set was unexpectedly encountered.

Exceptions:

BackupV-79-57344-34108 - An unexpected error occurred when cleaning up snapshot volumes. Confirm that all snapped volumes are correctly resynchronized with the original volumes.

I think the problem should be caused by target server, not bakcup server, can you tell me how to troubleshoot  this issue, many thanks.

Hi,

where i can check and test the connection to my vCenter server in symantec backup EXEC 2010 R3.

thanks,

Deepak

Hello,

I'm getting E000FED1 while backing up a specific hyper-v guest with MS-SQL installed.

I'm using W2008R2 with SP1 and BE 2012 with SP1.

Could anyone help me?

• There is enough free space at guest vm disks.
• Backup of VM this never worked before. (I'm trying to set up this job)
• There are no vss or sql errors inside the VM or in host eventlog.

Logfile from Backup-Exec:

BEREMOTE: [06.04.13 23:36:32] [7664]     2013-06-04T23:36:32.392 [besc]               - VssSnapshotVolume::GetWriterMetaData() - IVssBackupComponents::GatherWriterMetadata complete.
BEREMOTE: [06.04.13 23:36:32] [7664]     2013-06-04T23:36:32.392 [besc]               - Initialized VSS Snapshot Provider
BEREMOTE: [06.04.13 23:36:32] [7664]     2013-06-04T23:36:32.392 [writermanager]      - Starting to generate file list based on SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToSnapshot. (Function: LoadExcludeFiles, Line: 31)
BEREMOTE: [06.04.13 23:36:32] [7664]     2013-06-04T23:36:32.392 [writermanager]      - Adding C:\Windows\softwaredistribution\*.* /s to exclude list. (Function: LoadExcludeFiles, Line: 181)
BEREMOTE: [06.04.13 23:36:32] [7664]     2013-06-04T23:36:32.392 [writermanager]      - Adding C:\ProgramData\Microsoft\RAC\* to exclude list. (Function: LoadExcludeFiles, Line: 181)
BEREMOTE: [06.04.13 23:36:32] [7664]     2013-06-04T23:36:32.392 [writermanager]      - Adding C:\ProgramData\Microsoft\RAC\StateData\* to exclude list. (Function: LoadExcludeFiles, Line: 181)
BEREMOTE: [06.04.13 23:36:32] [7664]     2013-06-04T23:36:32.392 [writermanager]      - Adding C:\ProgramData\Microsoft\RAC\Outbound\* to exclude list. (Function: LoadExcludeFiles, Line: 181)
BEREMOTE: [06.04.13 23:36:32] [7664]     2013-06-04T23:36:32.392 [writermanager]      - Adding C:\ProgramData\Microsoft\RAC\PublishedData\* to exclude list. (Function: LoadExcludeFiles, Line: 181)
BEREMOTE: [06.04.13 23:36:32] [7664]     2013-06-04T23:36:32.392 [writermanager]      - Adding C:\ProgramData\Microsoft\RAC\Temp\* to exclude list. (Function: LoadExcludeFiles, Line: 181)
BEREMOTE: [06.04.13 23:36:32] [7664]     2013-06-04T23:36:32.392 [writermanager]      - Started enumerating all UserProfile directories. (Function: GetUsersProfiles, Line: 228)
BEREMOTE: [06.04.13 23:36:32] [7664]     2013-06-04T23:36:32.392 [writermanager]      - Finished enumerating all user profile directories. (Function: GetUsersProfiles, Line: 242)
BEREMOTE: [06.04.13 23:36:32] [7664]     2013-06-04T23:36:32.392 [writermanager]      - User profile related files excluded from backup: (Function: LoadExcludeFiles, Line: 134)
BEREMOTE: [06.04.13 23:36:32] [7664]     2013-06-04T23:36:32.392 [writermanager]      - Adding C:\Windows\system32\config\Journal\AppData\Local\Microsoft\Outlook\*.ost to exclude list. (Function: LoadExcludeFiles, Line: 143)
BEREMOTE: [06.04.13 23:36:32] [7664]     2013-06-04T23:36:32.392 [writermanager]      - Adding C:\Windows\system32\config\RegBack\AppData\Local\Microsoft\Outlook\*.ost to exclude list. (Function: LoadExcludeFiles, Line: 143)
BEREMOTE: [06.04.13 23:36:32] [7664]     2013-06-04T23:36:32.392 [writermanager]      - Adding C:\Windows\system32\config\systemprofile\AppData\Local\Microsoft\Outlook\*.ost to exclude list. (Function: LoadExcludeFiles, Line: 143)
BEREMOTE: [06.04.13 23:36:32] [7664]     2013-06-04T23:36:32.392 [writermanager]      - Adding C:\Windows\system32\config\TxR\AppData\Local\Microsoft\Outlook\*.ost to exclude list. (Function: LoadExcludeFiles, Line: 143)
BEREMOTE: [06.04.13 23:36:32] [7664]     2013-06-04T23:36:32.408 [fsys\shadow]        -  IID_IVssExamineWriterMetadataExQuery Interface Successful
BEREMOTE: [06.04.13 23:36:32] [7664]     2013-06-04T23:36:32.408 [fsys\shadow]        - Informational: Outputing VSS Writer Metadata to:'C:\Program Files\Symantec\Backup Exec\logs\{D61D61C8-D73A-4EEE-8CDD-F6F9786B7124} - Task Scheduler Writer.xml' in SHADOW::OutputWriterMetadata
BEREMOTE: [06.04.13 23:36:32] [7664]     2013-06-04T23:36:32.408 [fsys\shadow]        -  IID_IVssExamineWriterMetadataExQuery Interface Successful
BEREMOTE: [06.04.13 23:36:32] [7664]     2013-06-04T23:36:32.408 [fsys\shadow]        - Informational: Outputing VSS Writer Metadata to:'C:\Program Files\Symantec\Backup Exec\logs\{75DFB225-E2E4-4D39-9AC9-FFAFF65DDF06} - VSS Metadata Store Writer.xml' in SHADOW::OutputWriterMetadata
BEREMOTE: [06.04.13 23:36:32] [7664]     2013-06-04T23:36:32.408 [fsys\shadow]        -  IID_IVssExamineWriterMetadataExQuery Interface Successful
BEREMOTE: [06.04.13 23:36:32] [7664]     2013-06-04T23:36:32.408 [fsys\shadow]        - Informational: Outputing VSS Writer Metadata to:'C:\Program Files\Symantec\Backup Exec\logs\{0BADA1DE-01A9-4625-8278-69E735F39DD2} - Performance Counters Writer.xml' in SHADOW::OutputWriterMetadata
BEREMOTE: [06.04.13 23:36:32] [7664]     2013-06-04T23:36:32.408 [fsys\shadow]        -  IID_IVssExamineWriterMetadataExQuery Interface Successful
BEREMOTE: [06.04.13 23:36:32] [7664]     2013-06-04T23:36:32.408 [fsys\shadow]        - Informational: Outputing VSS Writer Metadata to:'C:\Program Files\Symantec\Backup Exec\logs\{66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE} - Microsoft Hyper-V VSS Writer.xml' in SHADOW::OutputWriterMetadata
BEREMOTE: [06.04.13 23:36:32] [7664]     2013-06-04T23:36:32.533 [fsys\shadow]        -  IID_IVssExamineWriterMetadataExQuery Interface Successful
BEREMOTE: [06.04.13 23:36:32] [7664]     2013-06-04T23:36:32.564 [fsys\shadow]        - Informational: Outputing VSS Writer Metadata to:'C:\Program Files\Symantec\Backup Exec\logs\{E8132975-6F93-4464-A53E-1050253AE220} - System Writer.xml' in SHADOW::OutputWriterMetadata
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.626 [fsys\shadow]        -  IID_IVssExamineWriterMetadataExQuery Interface Successful
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.626 [fsys\shadow]        - Informational: Outputing VSS Writer Metadata to:'C:\Program Files\Symantec\Backup Exec\logs\{A65FAA63-5EA8-4EBC-9DBD-A0C4DB26912A} - SqlServerWriter.xml' in SHADOW::OutputWriterMetadata
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.626 [fsys\shadow]        - Informational: Writer:SQL Server 2005 Logical Path:SRVHOST2\BKUPEXEC Component:master not added to logical directory tree in SHADOW::GenerateLogicalBackupDirectoryTree
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.626 [fsys\shadow]        - Informational: Writer:SQL Server 2005 Logical Path:SRVHOST2\BKUPEXEC Component:model not added to logical directory tree in SHADOW::GenerateLogicalBackupDirectoryTree
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.626 [fsys\shadow]        - Informational: Writer:SQL Server 2005 Logical Path:SRVHOST2\BKUPEXEC Component:msdb not added to logical directory tree in SHADOW::GenerateLogicalBackupDirectoryTree
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.626 [fsys\shadow]        - Informational: Writer:SQL Server 2005 Logical Path:SRVHOST2\BKUPEXEC Component:BEDB not added to logical directory tree in SHADOW::GenerateLogicalBackupDirectoryTree
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.626 [fsys\shadow]        -  IID_IVssExamineWriterMetadataExQuery Interface Successful
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.626 [fsys\shadow]        - Informational: Outputing VSS Writer Metadata to:'C:\Program Files\Symantec\Backup Exec\logs\{BE000CBE-11FE-4426-9C58-531AA6355FC4} - ASR Writer.xml' in SHADOW::OutputWriterMetadata
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.626 [fsys\shadow]        - Informational: Writer:Automated System Recovery Logical Path:ASR Component:ASR not added to logical directory tree in SHADOW::GenerateLogicalBackupDirectoryTree
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.626 [fsys\shadow]        - Informational: Writer:Automated System Recovery Logical Path:Volumes Component:Volume{e89d6116-5f1b-11e2-aab2-806e6f6e6963} not added to logical directory tree in SHADOW::GenerateLogicalBackupDirectoryTree
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.626 [fsys\shadow]        - Informational: Writer:Automated System Recovery Logical Path:Volumes Component:Volume{e89d6117-5f1b-11e2-aab2-806e6f6e6963} not added to logical directory tree in SHADOW::GenerateLogicalBackupDirectoryTree
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.626 [fsys\shadow]        - Informational: Writer:Automated System Recovery Logical Path:Volumes Component:Volume{c0f71250-654a-11e2-b32e-e0db5512ba49} not added to logical directory tree in SHADOW::GenerateLogicalBackupDirectoryTree
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.626 [fsys\shadow]        - Informational: Writer:Automated System Recovery Logical Path:Volumes Component:Volume{c0f71249-654a-11e2-b32e-e0db5512ba49} not added to logical directory tree in SHADOW::GenerateLogicalBackupDirectoryTree
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.626 [fsys\shadow]        - Informational: Writer:Automated System Recovery Logical Path:Volumes Component:Volume{c0f71242-654a-11e2-b32e-e0db5512ba49} not added to logical directory tree in SHADOW::GenerateLogicalBackupDirectoryTree
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.626 [fsys\shadow]        - Informational: Writer:Automated System Recovery Logical Path:Volumes Component:Volume{c39e8616-62a5-11e2-b32e-e0db5512ba4b} not added to logical directory tree in SHADOW::GenerateLogicalBackupDirectoryTree
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.626 [fsys\shadow]        - Informational: Writer:Automated System Recovery Logical Path:Disks Component:harddisk4 not added to logical directory tree in SHADOW::GenerateLogicalBackupDirectoryTree
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.626 [fsys\shadow]        - Informational: Writer:Automated System Recovery Logical Path:Disks Component:harddisk3 not added to logical directory tree in SHADOW::GenerateLogicalBackupDirectoryTree
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.626 [fsys\shadow]        - Informational: Writer:Automated System Recovery Logical Path:Disks Component:harddisk2 not added to logical directory tree in SHADOW::GenerateLogicalBackupDirectoryTree
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.626 [fsys\shadow]        - Informational: Writer:Automated System Recovery Logical Path:Disks Component:harddisk1 not added to logical directory tree in SHADOW::GenerateLogicalBackupDirectoryTree
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.626 [fsys\shadow]        - Informational: Writer:Automated System Recovery Logical Path:Disks Component:harddisk0 not added to logical directory tree in SHADOW::GenerateLogicalBackupDirectoryTree
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.626 [engidrapi]          - IsSystemBootedUsingEFIFirmware() - Enter
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.657 [engidrapi]          - IsSystemBootedUsingEFIFirmware() - (No) - Exit
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.657 [fsys\shadow]        -  IID_IVssExamineWriterMetadataExQuery Interface Successful
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.657 [fsys\shadow]        - Informational: Outputing VSS Writer Metadata to:'C:\Program Files\Symantec\Backup Exec\logs\{4969D978-BE47-48B0-B100-F328F07AC1E0} - BITS Writer.xml' in SHADOW::OutputWriterMetadata
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.657 [fsys\shadow]        - Informational: Writer BITS Writer contains no components in SHADOW::GenerateLogicalBackupDirectoryTree
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.657 [fsys\shadow]        -  IID_IVssExamineWriterMetadataExQuery Interface Successful
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.657 [fsys\shadow]        - Informational: Outputing VSS Writer Metadata to:'C:\Program Files\Symantec\Backup Exec\logs\{AFBAB4A2-367D-4D15-A586-71DBB18F8485} - Registry Writer.xml' in SHADOW::OutputWriterMetadata
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.657 [fsys\shadow]        -  IID_IVssExamineWriterMetadataExQuery Interface Successful
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.657 [fsys\shadow]        - Informational: Outputing VSS Writer Metadata to:'C:\Program Files\Symantec\Backup Exec\logs\{4DC3BDD4-AB48-4D07-ADB0-3BEE2926FD7F} - Shadow Copy Optimization Writer.xml' in SHADOW::OutputWriterMetadata
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.673 [fsys\shadow]        - Informational: Writer Shadow Copy Optimization Writer contains no components in SHADOW::GenerateLogicalBackupDirectoryTree
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.673 [fsys\shadow]        - Informational: Writer:Shadow Copy Optimization Writer Logical Path:null Component:null not added to logical directory tree in SHADOW::GenerateLogicalBackupDirectoryTree
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.673 [fsys\shadow]        -  IID_IVssExamineWriterMetadataExQuery Interface Successful
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.673 [fsys\shadow]        - Informational: Outputing VSS Writer Metadata to:'C:\Program Files\Symantec\Backup Exec\logs\{542DA469-D3E1-473C-9F4F-7847F01FC64F} - COM+ REGDB Writer.xml' in SHADOW::OutputWriterMetadata
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.673 [fsys\shadow]        -  IID_IVssExamineWriterMetadataExQuery Interface Successful
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.673 [fsys\shadow]        - Informational: Outputing VSS Writer Metadata to:'C:\Program Files\Symantec\Backup Exec\logs\{A6AD56C2-B509-4E6C-BB19-49D8F43532F0} - WMI Writer.xml' in SHADOW::OutputWriterMetadata
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.673 [fsys\shared]        - Attach to Shadow?Copy?Components
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.673 [fsys\vrtsrv]        -   VRTSRV:Status override - enabling auto mount in VirtualServer::AttachToDLE:833
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.673 [fsys\shared]        - Attach to VRTSRV::\\SRVHOST2.dom.local\Hyper-V?Virtual?Machine\SRVSQL2
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.845 [fsys\shadow]        - Informational status FS_AT_ROOT (0xE000FE0A) in SHADOW::GetBackupObjInfo
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.845                      - Using Hyper-V interface and tools
BEREMOTE: [04.06.13 23:36:32] [7664]     Using Hyper-V interface and tools
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.860                      - GetFirstVM() GetVMs_() complete
BEREMOTE: [04.06.13 23:36:32] [7664]     GetFirstVM() GetVMs_() complete
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.860                      - GetFirstVM() GetHAVMs_() complete
BEREMOTE: [04.06.13 23:36:32] [7664]     GetFirstVM() GetHAVMs_() complete
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:32.860                      - Leave GetFirstVM()
BEREMOTE: [04.06.13 23:36:32] [7664]     Leave GetFirstVM()
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:33.328 [fsys\vrtsrv]        -   VRTSRV:Informational - IVirtualMachine::GetVM returned VM for: SRVSQL2 (SRVSQL2)
BEREMOTE: [06.04.13 23:36:33] [7664]     2013-06-04T23:36:33.328 [fsys\vrtsrv]        -   VRTSRV:Settings for Excluding VMs that are in a saved state during backup time is 1
BEREMOTE: [06.04.13 23:36:34] [7664]     2013-06-04T23:36:33.796 [fsys\vrtsrv]        -   VRTSRV:Informational - IVirtualMachine::GetVM returned VM for: SRVSQL2 (SRVSQL2)
BEREMOTE: [06.04.13 23:36:34] [7664]     2013-06-04T23:36:33.796 [fsys\shadow]        - Informational: Processing root in SHADOW::AddToSnapshotSet
BEREMOTE: [06.04.13 23:36:34] [7664]     2013-06-04T23:36:34.202 [fsys\vrtsrv]        -   VRTSRV:Informational - IVirtualMachine::GetVM returned VM for: SRVSQL2 (SRVSQL2)
BEREMOTE: [06.04.13 23:36:34] [7664]     2013-06-04T23:36:34.202 [fsys\vrtsrv]        -   VRTSRV:Settings for Excluding VMs that are in a saved state during backup time is 1
BEREMOTE: [06.04.13 23:36:34] [7664]     2013-06-04T23:36:34.639 [fsys\vrtsrv]        -   VRTSRV:Informational - IVirtualMachine::GetVM returned VM for: SRVSQL2 (SRVSQL2)
BEREMOTE: [06.04.13 23:36:34] [7664]     2013-06-04T23:36:34.639 [fsys\shadow]        - Writer Microsoft Hyper-V include file list:
BEREMOTE: [06.04.13 23:36:34] [7664]     2013-06-04T23:36:34.639 [fsys\shadow]        - Writer Microsoft Hyper-V exclude file list:
BEREMOTE: [06.04.13 23:36:35] [7664]     2013-06-04T23:36:35.107 [fsys\vrtsrv]        -   VRTSRV:Informational - IVirtualMachine::GetVM returned VM for: SRVSQL2 (SRVSQL2)
BEREMOTE: [06.04.13 23:36:35] [7664]     2013-06-04T23:36:35.107 [fsys\vrtsrv]        -   VRTSRV:Settings for Excluding VMs that are in a saved state during backup time is 1
BEREMOTE: [06.04.13 23:36:35] [7664]     2013-06-04T23:36:35.544 [fsys\vrtsrv]        -   VRTSRV:Informational - IVirtualMachine::GetVM returned VM for: SRVSQL2 (SRVSQL2)
BEREMOTE: [06.04.13 23:36:35] [7664]     2013-06-04T23:36:35.544 [fsys\shadow]        - WriterID {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE} InstanceID {9D1776C4-2A7D-44CC-8A14-A3F07DFBCAE2} selected for backup or restore.
BEREMOTE: [06.04.13 23:36:35] [7664]     2013-06-04T23:36:35.544 [fsys\shadow]        - Component SRVSQL2 file list:
BEREMOTE: [06.04.13 23:36:35] [7664]     2013-06-04T23:36:35.544 [fsys\shadow]        -   o: E:\SRVSQL2\Virtual Machines\6AC5C8A2-E434-4C64-A198-E6E011D76BBD.xml
BEREMOTE: [06.04.13 23:36:35] [7664]     2013-06-04T23:36:35.544 [fsys\shadow]        -   o: E:\SRVSQL2\Virtual Machines\6AC5C8A2-E434-4C64-A198-E6E011D76BBD\* /s
BEREMOTE: [06.04.13 23:36:35] [7664]     2013-06-04T23:36:35.544 [fsys\shadow]        -   o: E:\SRVSQL2\SRVSQL2_C_fixed.vhd
BEREMOTE: [06.04.13 23:36:35] [7664]     2013-06-04T23:36:35.544 [fsys\shadow]        -   o: G:\Hyper-V\SRVSQL2\SRVSQL2_Daten.vhd
BEREMOTE: [06.04.13 23:36:35] [7664]     2013-06-04T23:36:35.544 [fsys\shadow]        -   o: H:\Hyper-V\SRVSQL2\SRVSQL2_Log.vhd
BEREMOTE: [06.04.13 23:36:35] [7664]     2013-06-04T23:36:35.544 [fsys\shadow]        -   o: H:\Hyper-V\SRVSQL2\SRVSQL2_Log2.vhd
BEREMOTE: [06.04.13 23:36:35] [7664]     2013-06-04T23:36:35.544 [fsys\shadow]        -   o: H:\Hyper-V\SRVSQL2\SRVSQL2_TempDB.vhd
BEREMOTE: [06.04.13 23:36:35] [7664]     2013-06-04T23:36:35.544 [fsys\shadow]        - Component SRVSQL2 Writer's exclude file list:
BEREMOTE: [06.04.13 23:36:35] [7664]     2013-06-04T23:36:35.544 [fsys\shadow]        -   o: C:\Windows\softwaredistribution\*.* /s
BEREMOTE: [06.04.13 23:36:35] [7664]     2013-06-04T23:36:35.544 [fsys\shadow]        -   o: C:\ProgramData\Microsoft\RAC\*
BEREMOTE: [06.04.13 23:36:35] [7664]     2013-06-04T23:36:35.544 [fsys\shadow]        -   o: C:\ProgramData\Microsoft\RAC\StateData\*
BEREMOTE: [06.04.13 23:36:35] [7664]     2013-06-04T23:36:35.544 [fsys\shadow]        -   o: C:\ProgramData\Microsoft\RAC\Outbound\*
BEREMOTE: [06.04.13 23:36:35] [7664]     2013-06-04T23:36:35.544 [fsys\shadow]        -   o: C:\ProgramData\Microsoft\RAC\PublishedData\*
BEREMOTE: [06.04.13 23:36:35] [7664]     2013-06-04T23:36:35.544 [fsys\shadow]        -   o: C:\ProgramData\Microsoft\RAC\Temp\*
BEREMOTE: [06.04.13 23:36:35] [7664]     2013-06-04T23:36:35.544 [fsys\shadow]        -   o: C:\Windows\system32\config\Journal\AppData\Local\Microsoft\Outlook\*.ost
BEREMOTE: [06.04.13 23:36:35] [7664]     2013-06-04T23:36:35.544 [fsys\shadow]        -   o: C:\Windows\system32\config\RegBack\AppData\Local\Microsoft\Outlook\*.ost
BEREMOTE: [06.04.13 23:36:35] [7664]     2013-06-04T23:36:35.544 [fsys\shadow]        -   o: C:\Windows\system32\config\systemprofile\AppData\Local\Microsoft\Outlook\*.ost
BEREMOTE: [06.04.13 23:36:35] [7664]     2013-06-04T23:36:35.544 [fsys\shadow]        -   o: C:\Windows\system32\config\TxR\AppData\Local\Microsoft\Outlook\*.ost
BEREMOTE: [06.04.13 23:36:35] [7664]     2013-06-04T23:36:35.544 [fsys\shadow]        -   o: \*.config.cch /s
BEREMOTE: [06.04.13 23:36:35] [7664]     2013-06-04T23:36:35.544 [fsys\shadow]        -   o: \*.config.cch.* /s
BEREMOTE: [06.04.13 23:36:36] [7664]     2013-06-04T23:36:36.012 [fsys\vrtsrv]        -   VRTSRV:Informational - IVirtualMachine::GetVM returned VM for: SRVSQL2 (SRVSQL2)
BEREMOTE: [06.04.13 23:36:36] [7664]     2013-06-04T23:36:36.012 [fsys\vrtsrv]        -   VRTSRV:Settings for Excluding VMs that are in a saved state during backup time is 1
BEREMOTE: [06.04.13 23:36:36] [7664]     2013-06-04T23:36:36.495 [fsys\vrtsrv]        -   VRTSRV:Informational - IVirtualMachine::GetVM returned VM for: SRVSQL2 (SRVSQL2)
BEREMOTE: [06.04.13 23:36:36] [7664]     2013-06-04T23:36:36.495 [besc]               - SnapshotBackupEngine::scan_file_system() : Volume List size (before prune): 0x0000000e
BEREMOTE: [06.04.13 23:36:36] [7664]     2013-06-04T23:36:36.495 [besc]               - SnapshotBackupEngine::scan_file_system(): Volume List size (after prune): 0x0000000e
BEREMOTE: [06.04.13 23:36:36] [7664]     2013-06-04T23:36:36.495 [besc]               - Adding volume: 'E:'
BEREMOTE: [06.04.13 23:36:36] [7664]     2013-06-04T23:36:36.495 [besc]               - VssSnapshotVolume::AddVolumeToSnapSet
BEREMOTE: [06.04.13 23:36:36] [7664]     2013-06-04T23:36:36.495 [besc]               -   Device name: [VRTSRV::\\SRVHOST2.dom.local\Hyper-V?Virtual?Machine\SRVSQL2], Volume name: [E:]
BEREMOTE: [06.04.13 23:36:36] [7664]     2013-06-04T23:36:36.495 [besc]               -   Set bsdMachineName_: [VRTSRV::]
BEREMOTE: [06.04.13 23:36:36] [7664]     2013-06-04T23:36:36.495 [besc]               - Exit VssSnapshotVolume::AddVolumeToSnapSet - successfully
BEREMOTE: [06.04.13 23:36:36] [7664]     2013-06-04T23:36:36.495 [besc]               - Adding volume: 'G:'
BEREMOTE: [06.04.13 23:36:36] [7664]     2013-06-04T23:36:36.495 [besc]               - VssSnapshotVolume::AddVolumeToSnapSet
BEREMOTE: [06.04.13 23:36:36] [7664]     2013-06-04T23:36:36.495 [besc]               -   Device name: [VRTSRV::\\SRVHOST2.dom.local\Hyper-V?Virtual?Machine\SRVSQL2], Volume name: [G:]
BEREMOTE: [06.04.13 23:36:36] [7664]     2013-06-04T23:36:36.495 [besc]               - Exit VssSnapshotVolume::AddVolumeToSnapSet - successfully
BEREMOTE: [06.04.13 23:36:36] [7664]     2013-06-04T23:36:36.495 [besc]               - Adding volume: 'H:'
BEREMOTE: [06.04.13 23:36:36] [7664]     2013-06-04T23:36:36.495 [besc]               - VssSnapshotVolume::AddVolumeToSnapSet
BEREMOTE: [06.04.13 23:36:36] [7664]     2013-06-04T23:36:36.495 [besc]               -   Device name: [VRTSRV::\\SRVHOST2.dom.local\Hyper-V?Virtual?Machine\SRVSQL2], Volume name: [H:]
BEREMOTE: [06.04.13 23:36:36] [7664]     2013-06-04T23:36:36.511 [besc]               - Exit VssSnapshotVolume::AddVolumeToSnapSet - successfully
BEREMOTE: [06.04.13 23:36:36] [7664]     2013-06-04T23:36:36.511 [besc]               - SnapshotBackupEngine::snap_file_systems. Start...
BEREMOTE: [06.04.13 23:36:36] [7664]     2013-06-04T23:36:36.667 [fsys\shadow]        - Informational: calling IVssBackupComponents::AddComponent for Component SRVSQL2 in SHADOW::SetSelectedForBackup
BEREMOTE: [06.04.13 23:36:36] [7664]     2013-06-04T23:36:36.682 [besc]               - MakeValidVolumeName: volume=[\\?\Volume{c39e8616-62a5-11e2-b32e-e0db5512ba4b}] and vol_name=[\\?\Volume{c39e8616-62a5-11e2-b32e-e0db5512ba4b}\]
BEREMOTE: [06.04.13 23:36:37] [7664]     2013-06-04T23:36:36.963 [besc]               - MakeValidVolumeName: volume=[\\?\Volume{c0f71249-654a-11e2-b32e-e0db5512ba49}] and vol_name=[\\?\Volume{c0f71249-654a-11e2-b32e-e0db5512ba49}\]
BEREMOTE: [06.04.13 23:36:37] [7664]     2013-06-04T23:36:37.228 [besc]               - MakeValidVolumeName: volume=[\\?\Volume{c0f71250-654a-11e2-b32e-e0db5512ba49}] and vol_name=[\\?\Volume{c0f71250-654a-11e2-b32e-e0db5512ba49}\]
BEREMOTE: [06.04.13 23:36:37] [7664]     2013-06-04T23:36:37.509 [besc]               - Starting PrepareForBackup wait
BEREMOTE: [06.04.13 23:36:42] [7664]     2013-06-04T23:36:42.033 [besc]               - PrepareForBackup done
BEREMOTE: [06.04.13 23:36:42] [7664]     2013-06-04T23:36:42.033 [besc]               - VssSnashotVolume::PrepareToSnapVolumeSet() - done. LastError_: 0x0
BEREMOTE: [06.04.13 23:36:42] [7664]     2013-06-04T23:36:42.158 [engidrapi]          - CDiskLayoutImplementation::GetAutoMount: AUTOMOUNT is enabled
BEREMOTE: [06.04.13 23:36:42] [7664]     2013-06-04T23:36:42.158 [besc]               - VssSnashotVolume::DoSnapshotSet() - calling DoSnapshotSet.
BEREMOTE: [06.04.13 23:36:42] [7664]     2013-06-04T23:36:42.158 [besc]               - VssSnashotVolume::DoSnapshotSet() - Starting wait for snap to complete...
BESERVER: [04.06.13 23:36:43] [10680]     -1 SecurityBO: Successfully setup RAWS certs.
MONITORI: [06.04.13 23:36:50] [0000]     Script 'MOM Backward Compatibility Service State Monitoring Script' completed with the following output: (empty)
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               - VssSnashotVolume::DoSnapshotSet() - Wait is done...
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Entering VssSnapshotVolume::RegisterWithOrphanage(). SnapshotSetID_ = {01ef3d4a-2146-45c2-81f7-134cfdbccfa0}
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               - VssSnashotVolume::SnapVolumeSet() - done. LastError_: 0x0
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               - VssSnapshotVolume::GetSnapSetProperties() - for BE only
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               - -------Begin snapshot property dump------
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               - ==> VSS snapshot properties:
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Snapshot Count            = 3
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Snapshot SetId            = {01ef3d4a-2146-45c2-81f7-134cfdbccfa0}
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Snapshot Id               = {08b3368a-a076-4fc8-b610-052d19bd4cdf}
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Provider Id               = {b5946137-7b9f-4925-af80-51abd60b20d5}
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Provider Name             = Microsoft Software Shadow Copy provider 1.0
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Creation Timestamp        = 04.06.2013 23:36:49
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Original Volume Name      = \\?\Volume{c39e8616-62a5-11e2-b32e-e0db5512ba4b}\
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Originating Machine       = SRVHOST2.dom.local
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Service Machine           = SRVHOST2.dom.local
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Exposed Name              = NULL
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Exposed Path              = NULL
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Status                    = VSS_SS_CREATED
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Snapshot DeviceObject     = \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy92
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Snapshot Attributes       = 0x420000
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -    VSS_VOLSNAP_ATTR_DIFFERENTIAL

     VSS_VOLSNAP_ATTR_AUTORECOVER
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               - ==> VSS snapshot properties:
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Snapshot Count            = 3
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Snapshot SetId            = {01ef3d4a-2146-45c2-81f7-134cfdbccfa0}
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Snapshot Id               = {85151009-ea99-4806-88cf-db2fd2305e0e}
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Provider Id               = {b5946137-7b9f-4925-af80-51abd60b20d5}
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Provider Name             = Microsoft Software Shadow Copy provider 1.0
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Creation Timestamp        = 04.06.2013 23:36:49
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Original Volume Name      = \\?\Volume{c0f71249-654a-11e2-b32e-e0db5512ba49}\
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Originating Machine       = SRVHOST2.dom.local
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Service Machine           = SRVHOST2.dom.local
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Exposed Name              = NULL
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Exposed Path              = NULL
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Status                    = VSS_SS_CREATED
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Snapshot DeviceObject     = \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy93
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Snapshot Attributes       = 0x420000
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -    VSS_VOLSNAP_ATTR_DIFFERENTIAL

     VSS_VOLSNAP_ATTR_AUTORECOVER
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               - ==> VSS snapshot properties:
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Snapshot Count            = 3
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Snapshot SetId            = {01ef3d4a-2146-45c2-81f7-134cfdbccfa0}
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Snapshot Id               = {ae31dc1f-e7d4-4b3b-9814-cf47710de6de}
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Provider Id               = {b5946137-7b9f-4925-af80-51abd60b20d5}
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Provider Name             = Microsoft Software Shadow Copy provider 1.0
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Creation Timestamp        = 04.06.2013 23:36:49
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Original Volume Name      = \\?\Volume{c0f71250-654a-11e2-b32e-e0db5512ba49}\
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Originating Machine       = SRVHOST2.dom.local
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Service Machine           = SRVHOST2.dom.local
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Exposed Name              = NULL
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Exposed Path              = NULL
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.238 [besc]               -  Status                    = VSS_SS_CREATED
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.253 [besc]               -  Snapshot DeviceObject     = \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy94
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.253 [besc]               -  Snapshot Attributes       = 0x420000
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.253 [besc]               -    VSS_VOLSNAP_ATTR_DIFFERENTIAL

     VSS_VOLSNAP_ATTR_AUTORECOVER
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.253 [besc]               - -------End of snapshot property dump------
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.253 [besc]               - VssSnashotVolume::GetSnapshotProperties() - done. LastError_: 0x0
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.394 [fsys\shadow]        - Status VSS_E_WRITERERROR_RETRYABLE (0x800423F3) State 5 getting Writer Microsoft Hyper-V VSS Writer ID {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE} Instance ID {9D1776C4-2A7D-44CC-8A14-A3F07DFBCAE2} status in SHADOW::GetWriterStatus
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.394 [fsys\shadow]        - Status FS_WRITER_STATUS_FAILURE (0xE000FED1) returned getting Writer status during SNAPSHOT_NOTIFICATION::PostSnapshot
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.394 [fsys\vrtsrv]        -   VRTSRV:Status FS_WRITER_STATUS_FAILURE (0xE000FED1) calling FS_SnapshotNotification in VirtualServer::SnapshotNotification:500
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.409                      - Using Hyper-V interface and tools
BEREMOTE: [04.06.13 23:36:51] [7664]     Using Hyper-V interface and tools
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.425                      - GetFirstVM() GetVMs_() complete
BEREMOTE: [04.06.13 23:36:51] [7664]     GetFirstVM() GetVMs_() complete
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.425                      - GetFirstVM() GetHAVMs_() complete
BEREMOTE: [04.06.13 23:36:51] [7664]     GetFirstVM() GetHAVMs_() complete
BEREMOTE: [06.04.13 23:36:51] [7664]     2013-06-04T23:36:51.425                      - Leave GetFirstVM()
BEREMOTE: [04.06.13 23:36:51] [7664]     Leave GetFirstVM()
BEREMOTE: [06.04.13 23:36:54] [7664]     2013-06-04T23:36:53.671 [fsys\vrtsrv]        - VirtualServer::SnapshotNotification: checking 'E:\SRVSQL2\SRVSQL2_C_fixed.vhd'
BEREMOTE: [06.04.13 23:36:54] [7664]     2013-06-04T23:36:53.687 [fsys\vrtsrv]        - VirtualServer::SnapshotNotification: MBR disk signature 0xcc7b25d4
BEREMOTE: [06.04.13 23:36:55] [7664]     2013-06-04T23:36:54.966 [fsys\vrtsrv]        - VirtualServer::SnapshotNotification: checking 'G:\Hyper-V\SRVSQL2\SRVSQL2_Daten.vhd'
BEREMOTE: [06.04.13 23:36:55] [7664]     2013-06-04T23:36:54.982 [fsys\vrtsrv]        - VirtualServer::SnapshotNotification: MBR disk signature 0x16b26fb1
BEREMOTE: [06.04.13 23:36:55] [7664]     2013-06-04T23:36:55.013 [fsys\vrtsrv]        - VirtualServer::SnapshotNotification: checking 'H:\Hyper-V\SRVSQL2\SRVSQL2_Log.vhd'
BEREMOTE: [06.04.13 23:36:55] [7664]     2013-06-04T23:36:55.029 [fsys\vrtsrv]        - VirtualServer::SnapshotNotification: MBR disk signature 0x16b26fbe
BEREMOTE: [06.04.13 23:36:55] [7664]     2013-06-04T23:36:55.060 [fsys\vrtsrv]        - VirtualServer::SnapshotNotification: checking 'H:\Hyper-V\SRVSQL2\SRVSQL2_TempDB.vhd'
BEREMOTE: [06.04.13 23:36:55] [7664]     2013-06-04T23:36:55.060 [fsys\vrtsrv]        - VirtualServer::SnapshotNotification: MBR disk signature 0x16b26fbf
BEREMOTE: [06.04.13 23:36:55] [7664]     2013-06-04T23:36:55.075 [fsys\vrtsrv]        - VirtualServer::SnapshotNotification: checking 'H:\Hyper-V\SRVSQL2\SRVSQL2_Log2.vhd'
BEREMOTE: [06.04.13 23:36:55] [7664]     2013-06-04T23:36:55.091 [fsys\vrtsrv]        - VirtualServer::SnapshotNotification: MBR disk signature 0x11c0b443
BEREMOTE: [06.04.13 23:36:55] [7664]     2013-06-04T23:36:55.107 [fsys\vrtsrv]        - VirtualServer::SnapshotNotification: checking '\\.\PHYSICALDRIVE0'
BEREMOTE: [06.04.13 23:36:55] [7664]     2013-06-04T23:36:55.122 [fsys\vrtsrv]        - VirtualServer::SnapshotNotification: MBR disk signature 0x7d7287dd
BEREMOTE: [06.04.13 23:36:55] [7664]     2013-06-04T23:36:55.122 [fsys\vrtsrv]        - VirtualServer::SnapshotNotification: checking '\\.\PHYSICALDRIVE1'
BEREMOTE: [06.04.13 23:36:55] [7664]     2013-06-04T23:36:55.122 [fsys\vrtsrv]        - VirtualServer::SnapshotNotification: MBR disk signature 0x4226d852
BEREMOTE: [06.04.13 23:36:55] [7664]     2013-06-04T23:36:55.138 [fsys\vrtsrv]        - VirtualServer::SnapshotNotification: checking '\\.\PHYSICALDRIVE2'
BEREMOTE: [06.04.13 23:36:55] [7664]     2013-06-04T23:36:55.138 [fsys\vrtsrv]        - VirtualServer::SnapshotNotification: MBR disk signature 0x4226d851
BEREMOTE: [06.04.13 23:36:55] [7664]     2013-06-04T23:36:55.138 [fsys\vrtsrv]        - VirtualServer::SnapshotNotification: checking '\\.\PHYSICALDRIVE3'
BEREMOTE: [06.04.13 23:36:55] [7664]     2013-06-04T23:36:55.138 [fsys\vrtsrv]        - VirtualServer::SnapshotNotification: MBR disk signature 0x4226d850
BEREMOTE: [06.04.13 23:36:55] [7664]     2013-06-04T23:36:55.138 [fsys\vrtsrv]        - VirtualServer::SnapshotNotification: checking '\\.\PHYSICALDRIVE4'
BEREMOTE: [06.04.13 23:36:55] [7664]     2013-06-04T23:36:55.138 [fsys\vrtsrv]        - VirtualServer::SnapshotNotification: MBR disk signature 0x4226d857
BEREMOTE: [06.04.13 23:36:55] [7664]     2013-06-04T23:36:55.138 [besc]               - SnapshotBackupEngine - SNAPSHOT_NOTIFICATION::PostSnapshot failed with fstatus: 0xe000fed1
BEREMOTE: [06.04.13 23:36:55] [7664]     2013-06-04T23:36:55.138 [besc]               - Error SnapshotBackupEngine::snap_file_systems failed.
BEREMOTE: [06.04.13 23:36:55] [7664]     2013-06-04T23:36:55.138 [ndmp\ndmpsrvr]      - ndmpdSnapshotPrepare2: Snapshot error. ErrorCode: 0xe000fed1 ErrorLevel: 1 Error Src: 3
BEREMOTE: [06.04.13 23:36:55] [7664]     2013-06-04T23:36:55.138 [ndmp\ndmpsrvr]      - ndmpdSnapshotPrepare2: sending reply...
BEREMOTE: [06.04.13 23:36:55] [7664]     2013-06-04T23:36:55.138 [besc]               - Attached [0x2e72e0]
BENGINE:  [06.04.13 23:36:55] [9232]     2013-06-04T23:36:55.138 [besc]               - ndmpcSnapshotPrepare2: Snap shot error. ErrorCode: 0xe000fed1 ErrorLevel: 1 Provider: 2
BENGINE:  [06.04.13 23:36:55] [9232]     2013-06-04T23:36:55.138 [loops]              - Exit NDMPSnapHostBackupEngine::SnapSingleVolume
BENGINE:  [06.04.13 23:36:55] [9232]     2013-06-04T23:36:55.138 [loops]              - Enter NDMPSnapHostBackupEngine::TrackSnappedBSD
BENGINE:  [06.04.13 23:36:55] [9232]     2013-06-04T23:36:55.138 [loops]              - Exit NDMPSnapHostBackupEngine::TrackSnappedBSD
BENGINE:  [06.04.13 23:36:55] [9232]     2013-06-04T23:36:55.138 [loops]              + ndmpsnaphostbackupengine.cpp (2256):
BENGINE:  [06.04.13 23:36:55] [9232]     2013-06-04T23:36:55.138 [loops]              | Exit NDMPSnapHostBackupEngine::ProcessCurBSD
BENGINE:  [06.04.13 23:36:55] [9232]     2013-06-04T23:36:55.138 [loops]              - Enter NDMPSnapHostBackupEngine::AdvanceToNextBSD
BENGINE:  [06.04.13 23:36:55] [9232]     2013-06-04T23:36:55.138 [loops]              - Exit NDMPSnapHostBackupEngine::AdvanceToNextBSD
BENGINE:  [06.04.13 23:36:55] [9232]     2013-06-04T23:36:55.138 [loops]              - Exit NDMPSnapHostBackupEngine::ProcessBSDList
BENGINE:  [06.04.13 23:36:55] [9232]     2013-06-04T23:36:55.138 [loops]              - Exit NDMPSnapHostBackupEngine::ProcessBSDs
PVLSVR:   [04.06.13 23:36:55] [10692]     VDSLib: Raw events: count: 1

      Event: VDS_NF_DISK_MODIFY

      Disk ID: {25FB0F6A-A0C0-4D49-98DB-BD3D99D3DB5E}
PVLSVR:   [04.06.13 23:36:55] [10692]     VDSLib: Raw events: count: 1

      Event: VDS_NF_DISK_MODIFY

      Disk ID: {CB2181FB-2487-4356-84FD-A7BA71C7A4C3}
PVLSVR:   [04.06.13 23:36:55] [10692]     VDSLib: Raw events: count: 2

      Event: VDS_NF_DISK_MODIFY

      Disk ID: {1A7E75DF-3058-42CA-BBED-B5F485CAA1C3}

      Event: VDS_NF_DISK_MODIFY

      Disk ID: {7BACB5B4-5686-4861-BEB0-D0AD2FA6C823}
PVLSVR:   [04.06.13 23:36:55] [10692]     VDSLib: Raw events: count: 1

      Event: VDS_NF_DISK_MODIFY

      Disk ID: {A13434A2-1979-439B-8EA3-26AA74CA8861}
BESERVER: [04.06.13 23:36:58] [6628]     -1 SetServiceStatus: state: SERVICE_RUNNING check point: 0 wait hint: 0
BENGINE:  [06.04.13 23:36:58] [9436]     2013-06-04T23:36:58.211 [server]             - Updating status for: 'SRVHOST2 Backup-Gesamt' (0x1 0x0)
BENGINE:  [06.04.13 23:36:58] [9436]     2013-06-04T23:36:58.211 [server]             - Status for: 'SRVHOST2 Backup-Gesamt' updated
BEREMOTE: [06.04.13 23:37:11] [7664]     2013-06-04T23:37:10.660 [besc]               - Unattaching [0x2e72e0]
BEREMOTE: [06.04.13 23:37:11] [7664]     2013-06-04T23:37:10.660 [besc]               - Attempting to delete VSS snapshot set: {01ef3d4a-2146-45c2-81f7-134cfdbccfa0}
BEREMOTE: [06.04.13 23:37:11] [7664]     2013-06-04T23:37:10.676 [besc]               - VSS snapshot set deleted. Snapshot SetID = {01ef3d4a-2146-45c2-81f7-134cfdbccfa0}
BEREMOTE: [06.04.13 23:37:11] [7664]     2013-06-04T23:37:10.676 [besc]               - Freeing gathered writer metadata
BEREMOTE: [06.04.13 23:37:11] [7664]     2013-06-04T23:37:10.676 [besc]               - Releasing vss interface 0x2e72e0
BEREMOTE: [06.04.13 23:37:11] [7664]     2013-06-04T23:37:10.676 [fsys\shared]        - Detach from VRTSRV::\\SRVHOST2.dom.local\Hyper-V?Virtual?Machine\SRVSQL2
BEREMOTE: [06.04.13 23:37:11] [7664]     2013-06-04T23:37:10.676 [fsys\shared]        - Detach from Shadow?Copy?Components

Hi

I initially posted this question back in December (see

https://www-secure.symantec.com/connect/forums/backup-exec-solution-sbs-2011-premium-add

) 

 At the time, BE for Windows 2012 was not available - clearly, that has now changed.

Finally, we have just taken delivery of the server hardware and so I am now looking to order the backup solution.

As per my initial post, the solution consists of:-

- 2 physical servers, each running 2 virtual machines under Windows 2012 Hyper-v:-

The first physical server will run two VMs:-

1. Physical server 1 (aka PS1), VM 1 - SBS 2011 standard roles (i.e. AD, Exchange, Sharepoint)
2. Physical server 1, VM 2 - Traditional File server (running Windows 2012 standard)

Similarly, physical server 2 will also run two VMs:-

1. Physical server 2 (aka PS2), VM 3 - SBS 2011 premium (i.e. SQL server) and backup AD
2. Physical server 2, VM 4 – Print and RDS server (running Windows 2012 standard)

As a MINIMUM, I am looking to back up the DATA on VMs 1, 2 and 3

Ideally, if budget permits, I would also like to backup the four virtual machines on the two physical servers.

VM 1 and VM3 are running SBS 2011, which covers Sharepoint, Exchange, SQL Server and Active Director

VM 2 is a file server (e.g. Word, Excel, PDFs etc) under Windows 2012 standard

What is the most cost-effective BackupExec licensing model, to achieve this, please ?

Kind regards

Horatio_too

Can someone tell me if i am Wrong. I am backup up Exchange directly to tape without passing to disk first. From reading it seems that the only way to restore using GRT or any data is to restore the whole backup to disk then select the data to restore ?

This doesnt sound right to me but everytime I look at GRT and restoring to exchange.

I get the following prerequisites

Exchange tools need to be installed on Backup Server

Full backup of the mail store on disk.

Any info on this would be helpful.

Kind Regards

Hello,

My problem is when i do a differential backup it just backup empty folder.

First i did a full backup (work fine) then i added new file on my server and i did a differential. I got all the new folder but whitout any files in it.

If anyone as a idea of what my problem can be, please help me.

I'm using backup exec 2012 with oes 11 server.

Thanks.

Howdy folks,

I've worked my way through numerous threads and tried several suggested solutions but still cannot make any headway on this issue. Hope someone can point me in a new direction.

I've got BUExec 2010 (ver. 13.0 rev. 2896) running on a Windows Server 2008 x32 machine and I'm trying to backup a RHEL 5 x64 machine. I've been running this particular setup for several years now without any trouble until about a month ago - it may have begun after I rebooted my RHEL machine (first reboot in 8 months).

When I try to browse the RHEL directories from BUExec, the system hangs. I can see the machine, I can connect, it asks me for credentials (root) which it accepts and then shows [ROOT] to the right of the RHEL computer icon, but when I try to expand the directory it hangs.

Here's what I've tried...

I have SE Linux enabled but currently suppressed.

I've disabled IPv6 on both the Windows and RHEL machines.

I've checked my credentials several times.

I've uninstalled RALUS, deleted the jobs and selection list, restarted BUExec services, reinstalled RALUS - still can't browse remote directories.

I've collected a BUExec log file on the RHEL machine when trying to access the directories. Evidently, it seems to connect ok. For some reason it seems to be trying to use the wrong set of credentials, BASIC/BUMonkey - the user on the Windows Server - it should be using ROOT. Then starts spewing about 2.5 millions lines of connection errors which is what is hanging it before it finally bails. I am at a loss at when to try next. Below is the beginng of the log file - I've clipped it when it begins the repetitive errors.

Any help would be appreciated.

----------------------------------------------------

: Starting BE Remote Agent
: Requested no generation of log file
: No configuration file specified.  Using default.
: Log to console: enabled
: Successfully set the supplementary groups of the process
: Initialized locks for SSL callbacks
: Starting NDMP processor
: NDMPDMainThreadFunc spawned: grpid=1, tid=-514971328
: FS_InitFileSys
:   libbedsnt5.so could not be loaded: 0x       2 (2)
:   libbedssql2.so could not be loaded: 0x       2 (2)
:   libbedsxchg.so could not be loaded: 0x       2 (2)
:   libbedsxese.so could not be loaded: 0x       2 (2)
:   libbedsmbox.so could not be loaded: 0x       2 (2)
:   libbedspush.so could not be loaded: 0x       2 (2)
:   libbedsnote.so could not be loaded: 0x       2 (2)
:   libbedsmdoc.so could not be loaded: 0x       2 (2)
:   libbedssps2.so could not be loaded: 0x       2 (2)
:   libbedssps3.so could not be loaded: 0x       2 (2)
:   libbedsupfs.so could not be loaded: 0x       2 (2)
:   libbedsshadow.so could not be loaded: 0x       2 (2)
:   libbedsoffhost.so could not be loaded: 0x       2 (2)
:   loaded libbedsvx.so
:   loaded libbedsrman.so
:   loaded libbedssms.so
:   loaded libbedssmsp.so
:   libbedsra.so could not be loaded: 0x       2 (2)
:   libbedsdb2.so could not be loaded: 0x       2 (2)
:   loaded libbedsedir.so
:   libbedsvmesx.so could not be loaded: 0x       2 (2)
: Initializing FSs
: FS 1 failed to initialize: 0xE000FE46
: Function called: RMAN_InitFileSys
: Using 'UTF-8' Encoding.
: Using vfm path /opt/VRTSralus/VRTSvxms from config.
: Sucessfully set VFM_PRIVATE_ROOT env to /opt/VRTSralus/VRTSvxms.
: VFM_PRIVATE_ROOT was set with value /opt/VRTSralus/VRTSvxms
:      VXMS Initialization OK.
: Detected Mounted Filesystem: type <ext3> mounted at </>
: Detected Mounted Filesystem: type <proc> mounted at </proc>
: Detected Mounted Filesystem: type <sysfs> mounted at </sys>
: Detected Mounted Filesystem: type <devpts> mounted at </dev/pts>
: Detected Mounted Filesystem: type <ext3> mounted at </pub>
: Detected Mounted Filesystem: type <ext3> mounted at </usr/local>
: Detected Mounted Filesystem: type <ext3> mounted at </home>
: Detected Mounted Filesystem: type <ext3> mounted at </var>
: Detected Mounted Filesystem: type <ext3> mounted at </data>
: Detected Mounted Filesystem: type <tmpfs> mounted at </dev/shm>
: Detected Mounted Filesystem: type <binfmt_misc> mounted at </proc/sys/fs/binfmt_misc>
: Detected Mounted Filesystem: type <rpc_pipefs> mounted at </var/lib/nfs/rpc_pipefs>
: Detected Mounted Filesystem: type <afs> mounted at </afs>
: INFORMATIONAL: Zero value found for 'DisableRMAL' from ralus.cfg, allowing RMAL to initialize
: ndmpRun
: Successfully resolved the "ndmp" service to port: 10000 (host order)
: NrdsWatchThread spawned: grpid=1, tid=-433452736
: NrdsAdvertiserThread spawned: grpid=1, tid=-422962880
: NrdsAdvertiserThread spawned: grpid=1, tid=-412473024
: NDMP Daemon Running..
: BETCPListener successfully installed a signal handler for SIGTERM
: Could not create an IPv6 socket at this time, reason:An error occurred during a socket creation operation: Error Code: 97, System Error Message: Address family not supported by protocol
: SocketService::IsSystemDualIP: No support found for IPv6 currently
: Started NDMP Listener on port 10000
: NrdsAdvertiserThread: advertisement cycle started.
: RMAN_EnumSelfDLE: AgentConfig GetOracleDBNames returned error. If Oracle Agent is installed, please run AgentConfig.
: NrdsAdvertiserThread: EnumSelfDLE for file system 14 returned 0(0x0) and 0 DLEs
: BENetConfigEx: Successfully refreshed adapter information.
: NrdsAdvertiserThread: EnumSelfDLE for file system 22 returned 0(0x0) and 1 DLEs
: NrdsAdvertiserThread: Nrds Message Len : 129.
: VX_RemoveDLE: DestroyDLE()
: This instance of BETCPListener was not requested to install a signal handler and hence will not install one!
: ConnectToServerEndPoint: dest=192.168.1.2, service=6101
: CreateConnection type=0 on socket 5 via BESocket OK
: NrdsAdvertiserThread: send of Tango.zo.ncsu.edu type 22 subtype 0 to target=192.168.1.2 port=6101 succeeded
: This instance of BETCPListener was not requested to install a signal handler and hence will not install one!
: ConnectToServerEndPoint: dest=glaurung.basic.local, service=6101
: CreateConnection type=0 on socket 5 via BESocket OK
: NrdsAdvertiserThread: send of Tango.zo.ncsu.edu type 22 subtype 0 to target=glaurung.basic.local port=6101 succeeded
: NrdsAdvertiserThread: advertisement cycle complete.  Waiting 240 minutes before advertising again.
: NrdsAdvertiserThread: negative (purge) advertisement cycle started.
: NrdsAdvertiserThread: no purge is pending.
: NrdsAdvertiserThread: negative (purge) advertisement cycle complete.  Waiting 240 minutes before advertising again.
: Control connection accepted : connection established between end-points 192.168.1.17:10000 and 192.168.1.2:55637
: ndmpCreateConnection
: conHandlerFunc for conn'n=483047792 spawned: tm=0x1cc770c0, grpid=2, tid=-401983168
: ndmpdConnectionHandler: received connection(5).
: ndmpSendRequest: message:0x502
: sent          seq#: 1 msg: 0x502
: ndmpProcessRequests
: ndmp_recv_msg
: ndmpdConfigGetServerInfo:
: ndmpSendReply: message:0x108
: ndmpFreeMessage: message:0x108
: ndmpProcessRequests
: ndmp_recv_msg
: ndmpdConfigGetServerInfo:
: ndmpSendReply: message:0x108
: ndmpFreeMessage: message:0x108
: ndmpProcessRequests
: ndmp_recv_msg
: ndmpdConnectOpen: protocol_version:3.
: ndmpSendReply: message:0x900
: ndmpFreeMessage: message:0x900
: ndmpProcessRequests
: ndmp_recv_msg
: ndmpdConfigGetAuthAttr:
: ndmpSendReply: message:0x103
: ndmpFreeMessage: message:0x103
: ndmpProcessRequests
: ndmp_recv_msg
: ndmpdPKCSSession: mode:start.
: ndmpSendReply: message:0xf33b
: ndmpFreeMessage: message:0xf33b
: ndmpProcessRequests
: ndmp_recv_msg
: ndmpdConnectClientAuth: auth_type:BEWS2.
: LogonUser failed for user: BASIC\BUMonkey because LogonUser: Password is Null for user
: LogonUser failed for user: BASIC\BUMonkey
: ndmpSendReply: message:0x901
: ndmpFreeMessage: message:0x901
: ndmpProcessRequests
: ndmp_recv_msg
: ndmp_readit: Caught message on closed connection. Socket 0x5 len 0x0
: ndmp_readit: ErrorCode :: 2 : 0x       2 (2)
: ndmp_process_messages: detected eof
: ndmpFreeMessage: message:0x0
: FreeFormatEnv( cur_fmt=0 )
: FreeFormatEnv( cur_fmt=0 )
: ndmpDestroyConnection
: Control connection accepted : connection established between end-points 192.168.1.17:10000 and 192.168.1.2:55638
: ndmpCreateConnection
: conHandlerFunc for conn'n=483048096 spawned: tm=0x1cc770c0, grpid=2, tid=-401983168
: ndmpdConnectionHandler: received connection(5).
: ndmpSendRequest: message:0x502
: sent          seq#: 1 msg: 0x502
: ndmpProcessRequests
: ndmp_recv_msg
: ndmpdConfigGetServerInfo:
: ndmpSendReply: message:0x108
: ndmpFreeMessage: message:0x108
: ndmpProcessRequests
: ndmp_recv_msg
: ndmpdConfigGetServerInfo:
: ndmpSendReply: message:0x108
: ndmpFreeMessage: message:0x108
: ndmpProcessRequests
: ndmp_recv_msg
: ndmpdConnectOpen: protocol_version:3.
: ndmpSendReply: message:0x900
: ndmpFreeMessage: message:0x900
: ndmpProcessRequests
: ndmp_recv_msg
: ndmpdConfigGetAuthAttr:
: ndmpSendReply: message:0x103
: ndmpFreeMessage: message:0x103
: ndmpProcessRequests
: ndmp_recv_msg
: ndmpdPKCSSession: mode:start.
: ndmpSendReply: message:0xf33b
: ndmpFreeMessage: message:0xf33b
: ndmpProcessRequests
: ndmp_recv_msg
: ndmpdConnectClientAuth: auth_type:BEWS2.
: ndmpSendReply: message:0x901
: ndmpFreeMessage: message:0x901
: ndmpProcessRequests
: ndmp_recv_msg
: ndmpdPKCSSessionData:
: ndmpSendReply: message:0xf33c
: ndmpFreeMessage: message:0xf33c
: ndmpProcessRequests
: ndmp_recv_msg
: ndmpdPKCSSessionData:
: ndmpSendReply: message:0xf33c
: ndmpFreeMessage: message:0xf33c
: ndmpProcessRequests
: ndmp_recv_msg
: ndmpdConfigGetHostInfo:
: BENetConfigEx: Successfully refreshed adapter information.
: ndmpSendReply: message:0x100
: ndmpFreeMessage: message:0x100
: ndmpProcessRequests
: ndmp_recv_msg
: ndmpdConfigGetServerInfo:
: ndmpSendReply: message:0x108
: ndmpFreeMessage: message:0x108
: ndmpProcessRequests
: ndmp_recv_msg
: ndmpdConfigGetHostInfo:
: BENetConfigEx: Successfully refreshed adapter information.
: ndmpSendReply: message:0x100
: ndmpFreeMessage: message:0x100
: ndmpProcessRequests
: ndmp_recv_msg
: ndmpdPropSet:
: ndmpdPropSet properties before:
: ndmpdPropSet properties after:
: NDMP_PROP_PEER_PRODUCT_TYPE=BEWS
: NDMP_PROP_PEER_OS_TYPE=NT
: NDMP_PROP_PEER_PROTOCOL_VERSION=6.4
: UTILITY_PARTITION_OEMIDS=
: SPS_SERVER_LIST=
: PDI_BKUP_TEMP_LOCATION=C:\TEMP
: ndmpSendReply: message:0xf270
: ndmpFreeMessage: message:0xf270
: ndmpProcessRequests
: ndmp_recv_msg
: ndmpdBEWSBrowseScanBegin:
: ndmpdBEWSBrowseScanBegin: Created dataSetHandle
: ndmpdBEWSBrowseScanBegin: Created dataSetHandle->browseObject
: ndmpdBEWSBrowseScanBegin: malloc'd uchar_ary
: ndmpdBEWSBrowseScanBegin: MapDsTypeToAuthBits complete
: ndmpdBEWSBrowseScanBegin: DeasciifyAndDecrypt complete
: ndmpdBEWSBrowseScanBegin: copied uname and pwd
: DS_OpenSelectionService
: RMAN_FindDrives - Oracle RMAN Agent not authorized.
: VX_FindDrives: Creating DLE: [ROOT]
: FS_ResolveDevName: [\]
: FS_BlowOutMachine: entered -->\\Tango.zo.ncsu.edu<--
: ******************************************************************************
: Initial DLE Tree
: -->[ROOT]<-- address 0x00001CD407A0 type 22 subtype 0 feature bits 0x03020601 0x00000000 dataId 49 bedsId 49 bedsVer 0
: End of List
: FS_ResolveDevName: [\]
: FS_BlowOutMachine: FS_ResolveDevName returns -->\\Tango.zo.ncsu.edu<-- as the machineName
: FS_BlowOutMachine: processing as local machine
: FS_BlowOutMachine: failed to find machine DLE in DLE tree, attempting DLE create
: FS_CreateTempDLE
: ====>VX_CreateTempDLE
: VX_CreateTempDLE: Creating DLE: \\Tango.zo.ncsu.edu
: FS_BlowOutMachine: trying to attach to newly created DLE
: ====>VX_AttachToDLE
: Resetting hard link info
: Hard link info has been reset
: VX_AttachToDLE: initializing mount list
: VX_AttachToDLE: create mount list returned 0
: Adding any excluded filesystems
: Excluding filesystem type devpts
:             AddToExcludedDirsList: Directory /dev/pts added to exclude list
: Excluding filesystem type proc
:             AddToExcludedDirsList: Directory /proc added to exclude list
: Excluding filesystem type sysfs
:             AddToExcludedDirsList: Directory /sys added to exclude list
: Excluding filesystem type rpc_pipefs
:             AddToExcludedDirsList: Directory /var/lib/nfs/rpc_pipefs added to exclude list
: Excluding filesystem type tmpfs
:             AddToExcludedDirsList: Directory /dev/shm added to exclude list
: Excluding filesystem type ftp
: Excluding filesystem type ntfs
:     BlowupChildren: Did not find DLE \\Tango.zo.ncsu.edu\[ROOT] in list. Creating new.
: RMAN_SurrogateCalling - Oracle RMAN Agent not authorized.
: VX_SurrogateCalling: Tango.zo.ncsu.edu
: VX_RemoveDLE: DestroyDLE()
: Attach to: \\Tango.zo.ncsu.edu
: FS_BlowOutMachine: attached successfully
: FS_BlowOutMachine: found -->\\Tango.zo.ncsu.edu<-- in DLE tree
: FS_BlowOutMachine: detaching from newly created DLE
: Detach from: \\Tango.zo.ncsu.edu
: Resetting hard link info
: Hard link info has been reset
: ******************************************************************************
: Modified DLE Tree
: -->[ROOT]<-- address 0x00001CD407A0 type 22 subtype 0 feature bits 0x03020601 0x00000000 dataId 49 bedsId 49 bedsVer 0
: -->\\Tango.zo.ncsu.edu<-- address 0x00001CD413D0 type 22 subtype 0 feature bits 0x03020603 0x00004002 dataId 49 bedsId 49 bedsVer 0
:     -->\\Tango.zo.ncsu.edu\[ROOT]<-- address 0x00001CD574F0 type 22 subtype 0 feature bits 0x03020601 0x00000000 dataId 49 bedsId 49 bedsVer 0
: End of List
: FS_BlowOutMachine: returning 0
: ====>VX_AttachToDLE
: Resetting hard link info
: Hard link info has been reset
: VX_AttachToDLE: initializing mount list
: VX_AttachToDLE: create mount list returned 0
: Adding any excluded filesystems
: Excluding filesystem type devpts
: Excluding filesystem type proc
: Excluding filesystem type sysfs
: Excluding filesystem type rpc_pipefs
: Excluding filesystem type tmpfs
: Excluding filesystem type ftp
: Excluding filesystem type ntfs
: Attach to: \\Tango.zo.ncsu.edu
: ndmpSendReply: message:0xf315
: ndmpFreeMessage: message:0xf315
: ndmpProcessRequests
: ndmp_recv_msg
: ndmpdBEWSBrowseScanEnd:
: ndmpdBEWSBrowseScanEnd: setting dataSetHandle
: ndmpdBEWSBrowseScanEnd: dataSetHandle complete
: ndmpdBEWSBrowseScanEnd: making the handle available
: ndmpdBEWSBrowseScanEnd: freeing the dataSetHandle
: ndmpdBEWSBrowseScanEnd: ERROR: NDMP_NO_ERR
: ndmpSendReply: message:0xf317
: ndmpFreeMessage: message:0xf317
: ndmpProcessRequests
: ndmp_recv_msg
: ndmpdBEWSBrowseScanBegin:
: ndmpdBEWSBrowseScanBegin: Created dataSetHandle
: ndmpdBEWSBrowseScanBegin: Created dataSetHandle->browseObject
: ndmpdBEWSBrowseScanBegin: malloc'd uchar_ary
: ndmpdBEWSBrowseScanBegin: MapDsTypeToAuthBits complete
: ndmpdBEWSBrowseScanBegin: DeasciifyAndDecrypt complete
: ndmpdBEWSBrowseScanBegin: copied uname and pwd
: FS_ResolveDevName: [\]
: FS_BlowOutMachine: entered -->\\Tango.zo.ncsu.edu\[ROOT]<--
: ******************************************************************************
: Initial DLE Tree
: -->[ROOT]<-- address 0x00001CD407A0 type 22 subtype 0 feature bits 0x03020601 0x00000000 dataId 49 bedsId 49 bedsVer 0
: -->\\Tango.zo.ncsu.edu<-- address 0x00001CD413D0 type 22 subtype 0 feature bits 0x03020603 0x00004002 dataId 49 bedsId 49 bedsVer 0
:     -->\\Tango.zo.ncsu.edu\[ROOT]<-- address 0x00001CD574F0 type 22 subtype 0 feature bits 0x03020601 0x00000000 dataId 49 bedsId 49 bedsVer 0
: End of List
: FS_ResolveDevName: [\]
: FS_BlowOutMachine: FS_ResolveDevName returns -->Tango.zo.ncsu.edu<-- as the machineName
: FS_BlowOutMachine: processing as local machine
: FS_BlowOutMachine: returning 0
: ====>VX_AttachToDLE
: Resetting hard link info
: Hard link info has been reset
: VX_AttachToDLE: initializing mount list
: VX_AttachToDLE: create mount list returned 0
: Adding any excluded filesystems
: Excluding filesystem type devpts
: Excluding filesystem type proc
: Excluding filesystem type sysfs
: Excluding filesystem type rpc_pipefs
: Excluding filesystem type tmpfs
: Excluding filesystem type ftp
: Excluding filesystem type ntfs
: Attach to: \\Tango.zo.ncsu.edu\[ROOT]
: ====> VX_ChangeDir
: ====> VXX_ChangeDir : apath : , asize : 1
: ====>ChangeDir : psize : 1
:         vx_stat_by_name: Getting stat of /
:         vx_open_by_name: Opening object name : /, openflags : B
:         vx_open_by_name: new handle =0x1cd91330
:         vx_stat_by_name: Getting stat of /var
: ====> VX_CloseDir
: VX_SetupWorkPath: dss_cur_dir is not valid
: VX_SetupWorkPath: req size is 119
: VX_SetupWorkPath: req size after strsize(sname) is 119
: VX_SetupWorkPath: path is /. copying cur dir and sname
: VX_SetupWorkPath: path with cur dir is /
:         vx_stat_by_name: Getting stat of /
: ====> VX_FindFirst
: last_slash called with non absolute path name '*.*'
:         vx_stat_by_name: Getting stat of /
:         vx_open_by_name: Opening object name : /, openflags : B
:         vx_open_by_name: new handle =0x1cd91330
:         vx_stat_by_name: Getting stat of /var
: VX_ModPathDDB (get_it): full_name_ptr : var, size : 4
: VX_ModPathDDB (get_it): wide name : var, size : 16
: ====> VX_FindNext
:         vx_stat_by_name: Getting stat of /etc
: VX_ModPathDDB (get_it): full_name_ptr : etc, size : 4
: VX_ModPathDDB (get_it): wide name : etc, size : 16

When I try to select  servers from Exchange 2010 Dag in symantec backup exec 2012 , I am getting a strange error message and not able to select  the servers . 

This is under preferred DAG members to backup from . 

error message is :

microsoft sql server does not appear to be running

any help would be appreciated .  I am also attaching screen shots

Hello everyone.

I'm just walking into Symantec as this is a new position for me and its kinda everywhere and out of control and I was hoping I could get a better handle on it.

Is it possible within the BEData folder to create a fodler for each server,

For example

BEData

   Mailserver

   Fileserver

   DNS

etc

just trying to find an easier to way clean items up.

Much appreciated.

Hallo liebe Community,

ich stehe vor folgender Anforderung mit BackupExec 2012.

Anforderungen:
Einer meiner Kunden wünscht eine ausfallsichere BackupExec Umgebung. Diese Umgebung soll zwei BackupExec Medienserver auf zwei Rechenzentren aufteilen. Es soll eine tägliche Sicherung auf eine virtuelle Tape Library, die per FC angebunden ist, gemacht werden. Anschließend sollen die gesicherten Daten auf eine ebenso mit FC angebundene physikalische Tape Library kopiert/dupliziert werden. Die beiden Library sind ebenso auf die Rechenzentren aufgeteilt. Die Verwaltung der Sicherungs- und Wiederherstellungs Jobs und möglichst alle anderen Konfiguration sollen an einer Stelle gemacht werden können.
Optimal wäre außerdem noch, dass ein Sicherungsjob beim Ausfall eines Medienservers automatisch auf dem verbleibenden Medienserver neu gestartet wird. Falls dieses Ziel nicht erreicht werden kann, ist das nicht allzu dramatisch.

Folgende Gedanken habe ich mir gemacht:
Ich installiere zwei physikalische Server. Einen im RZ01 und den anderen im RZ02. Außerdem installiere ich einen virtuellen Server im VMware HA Cluster. Auf dem virtuellen Server installiere ich BackupExec 2012 mit CASO. Die beiden anderen Server installiere ich als gemanagede Medienserver. Ich zone die beiden Server so, dass beide die virtuelle und die physikalische Library sehen können.
Alle meine Jobs (Sicherungen und Wiederherstellungen) konfiguriere ich dann am virtuellen BackupExec CASO Server und deligiere diese an meine Medienserver.

Jetzt stellen sich bei mir folgende Fragen:
- Gehen meine Gedanken grundsätzlich schonmal in die richtige Richtung oder bin ich am falschen Pfad?
- Ist eine BackupExec Installation mit Microsoft Cluster vielleicht der richtigere bzw. bessere Ansatz?
- Kann ich problemlos mit den beiden Medienserver auf die Librarys zugreifen oder benötige ich dazu die "BackupExec Share SAN Storage Option"?

Wäre super, wenn mir jemand da weiterhelfen oder den Schubs in die richtige Richtung geben kann.
Danke schonmal!

Viele Grüße
Marco