Remote Agent for Windows Servers

651 Topics

Backup Job Rate more than halved when backing up Hyper-V VM vs Physical Server
Hi, We recently P2Ved one of our fileservers, prior to which we were able to backup with a job rate of 2GB+/min and a total backup runtime of around 15 hours. Since P2Ving the server, we now only get a job rate of around 900MB/min and the total runtime is now around 32 hours. Does anybody know why the job rate would have drop so significantly? Environment Details: We have gigabit ethernet between the VM host and iSCSI SAN (Dell Powervault MD3200i) and we backup to tape (a Dell PowerVault TL2000) The VM is a Hyper-V VM running on a Hyper-V cluster but we are not using the Hyper-V agent for backing up, just the standard RAWS agent, OS is W2K8 R2 Standard The server BE is installed on is physical with the tape library connect via SAS, BE version is 2010 R3 SP1, OS is W2K8 R2 Enterprise Cheers Adam.
Solved
adamf83
13 years ago Place Backup Exec
1.2KViews
7likes
4Comments
BE 12.5 for SBS trying to use Remote Agent for Win 2008 server says not compatable.
I have Backup Exec 12.5 for SBS server installed on my SBS 2008 Standard server. I have pushed the agent to a Windows Server 2008 Standard. It pushes to it fine, but when I open the Backup AGent on the 2008 Standard, it tells me it is not compatible with the OS. I have installed the Service Pack 2 for the BE 12.5. Any Help Please. Thanks
Solved
suesa
13 years ago Place Backup Exec
692Views
6likes
3Comments
Backup Exec 2014 - Cannot do Hyper-V VM incrementals on Server 2012
None of the Hyper-V VM clients on my Server 2012 host can do an incremental backup. I get the following error. A Full backup was run on this virtual machine, since the option to fall back to a full backup was selected. Incremental\\Differential backup methods are not supported for this virtual machine. All of these failing clients have no problem with the full backups. The clients are either Server 2008 R2 or Server 2012 - both types fail. All clients have the latest appropriate Hyper-V client tools/drivers installed. I can find no problems in the log files. I am having no trouble with incremental backups with the VMs on my Server 2008 R2 host. These VMs are all running on VHDX files, on simple volumes. Very simple expanding VHDX, no deduplication going on or anything else fancy. I've checked and I'm pretty sure these hosts all have a logical sector size of 512. The VHDX files are all on the local drives of the Hyper-V host - no iSCSI or shares or clustering, etc. Is the problem is that "Symantec incremental backup" doesn't work on Server 2012 Hyper-V VMs, or maybe doesn't work with VHDX files? Thanks for any insight.
Solved
today
11 years ago Place Backup Exec
948Views
3likes
3Comments
Unable to update Backup Exec 2012 remote agent to 2014 agent
Hi. I performed the update from Backup Exec 2012 to Backup Exec 2014 on my server yesterday which went fine, but now I'm left with only one problem. I have only one server out of 56 other servers that will not take the remote agent update from the 2012 version to the new 2014 version. I first tried to do the push install and that failed. So, then I tried to do a manual install and that failed. I've tried updating to the latest version of .Net Framework, which is 4.5.2 and running all Microsoft Updates too. After searching extensively on the forums here I've been unable to conclude as to why just this one server didn't work with the any method of install. All servers are 64bit 2008 R2, only a couple are 2003 R2. I've also went through some tech articles on how to manually remove the agent, from the registry too; at first I couldn't even remove it through Programs and Features. So now whenever I try to install the agent, in particular when I try installing it manually by copying the folders off of the media server, the installation gets stuck at the removal point and then fails. Also,the installer tells me I have the old version still installed even though I can't find any traces on the server. See attachment of my screenshot. What do you suggest?
all2surreal
11 years ago Place Backup Exec
1.9KViews
3likes
9Comments
BE2014 Dedup storage device keeps jobs queued, only 1 job runs at a time
Backup exec 2014 with dedup storage on a local disk. Concurrent operations has been set to 8. BE Media server has been rebooted several times. Yet when a number of jobs that kick off at the same time start, all with the dedup disk as the destination, only one runs, the others sit at queued, then the first job finishes and one of the jobs sitting at queued starts processing and so on. Its as if the concurrent operations value is being ignored and is set to 1 when it isn't. These jobs have GRT enabled and are all using windows agent. What could be missing? With the jobs runningin sequence instead of parallel is obviously stretching our backup window. Thanks.
Solved
talja
11 years ago Place Backup Exec
638Views
3likes
2Comments
Exchange Information Store not visible due to missing permissions
Hello, I have a little problem with setting up a backup job for Microsoft Exchange 2010. The whole system is set up as follows: - Backup Exec Server 2012 on Windows Server 2008 R2 - Exchange 2010 ManagementConsole is installed in exactly the same version as is on the SBS2011 (I'm able to access the Exchange Server through the management console installed on the Backup Exec Server) - Microsoft Exchange 2010 on Microsoft Windows Small Business Server 2011, Agent for Windows is installed - User domain\bexec was created in the AD and is member of the groups Domain Administrators and Exchange Organization Administrators, this user has also local Administrator privileges on all machines that need to be backed up - User domain\bexec has a mailbox which is visible in the global address list - The username domain\bexec is unique within the first five characters However, somehow I am not able to backup the Exchange Server, the information store is not available for selection when I set up the backup job, just the HDDs and System State. When I run the Symantec Help Tool I get the following errors: Does anybody know, if I'm missing something? Thank you very much in advance Best regards Markus
Solved
xylo
11 years ago Place Backup Exec
3.7KViews
3likes
10Comments
Completed with exceptions: system volume information
We have BE 2012 running on Windows 2008 R2 server. We are backing up 5 volumes located on the server. 4 of them are LUNs from P2000 g3 SAS, directly connected via SCSI cable. System seems them as DAS disks. I: LUN1 P: LUN2 L: LUN3 E: LUN4 D: Local volume (4 RAID5 disks) Shadows copies have been enabled on all volumes.I can browse/restore data . I have plenty free space left. I have limit set as well and it is far away of reaching it. Now for no particular reasons Backup Exec 2012 completed with exception for P: I: volumes with the following warning: - Snapshot Technology: Initialization failure on: "\\xxxxx-xxx\P:". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS). V-79-10000-11242 - VSS Snapshot error. Out of disk space, or could not find an NTFS volume while creating the snapshot. Microsoft Volume Shadow Copy Service (VSS) requires an NTFS volume with enough free disk space for each physical or virtual disk volume to cache the data that changes during the backup job. Consult the Microsoft documentation for more information. That what happens when I backup to tape (LTO5 via HP Utrium 3000). When destination is HDD, I can see the following (exception for I and P): Unable to open the item \\XXXXXX-XXX\I:\System Volume Information\{573950ac-d772-11e2-905b-984be107e958}{3808876b-c176-4e48-b7ae-04046e6cc752} - skipped. Unable to open the item \\XXXXXX-XXX\I:\System Volume Information\{58fa8a79-d38e-11e2-9f73-984be107e958}{3808876b-c176-4e48-b7ae-04046e6cc752} - skipped. Unable to open the item \\XXXXXX-XXX\I:\System Volume Information\{753d8583-d9c7-11e2-94dc-984be107e958}{3808876b-c176-4e48-b7ae-04046e6cc752} - skipped. Unable to open the item \\XXXXXX-XXX\I:\System Volume Information\{753d8dd8-d9c7-11e2-94dc-984be107e958}{3808876b-c176-4e48-b7ae-04046e6cc752} - skipped. Unable to open the item \\XXXXXX-XXX\I:\System Volume Information\{8a2652dd-d88f-11e2-905b-984be107e958}{3808876b-c176-4e48-b7ae-04046e6cc752} - skipped. Unable to open the item \\XXXXXX-XXX\I:\System Volume Information\{a89b127f-d51e-11e2-905b-984be107e958}{3808876b-c176-4e48-b7ae-04046e6cc752} - skipped. Volume E: (which is the LUN from the same P2000 box) is OK. All volumes have this folder in the root. That’s OK, that’s how MSS/VSS works. And that’s where shadow copies are held. So what’s wrong then?! It is definitely not P2000 box that cause the problem as E volume is OK. (I tried hardware provider (HP) for VSS as well btw, without any results.) Any ideas ? Thanks
Nilldot
12 years ago Place Backup Exec
564Views
3likes
1Comment
An informational alert "SDR Full Backup Success" is observed in Backup Exec 2012 when a Full backup job completes successfully
Hi everybody, Is there anyway to configure BE 2012 to avoid all SDR informational alert or an automated way to clear it? Why genrating an alert if all task result is a success? Thanks in advanced. PS : See articleTECH181489
Solved
daames
12 years ago Place Backup Exec
1.1KViews
3likes
3Comments
How to execute a backup from an Agent
Hello, It's possible to specify a Backup exec server with the moduleBEMCLI,exemple "Get-BEJob "Computername" ",aswas done with the command bemcmd -c"Server"and Backup Exec 2010 ? Thank you
Solved
Exounet
11 years ago Place Backup Exec
651Views
3likes
2Comments
Exchange Information Store not available in selection list
I have a new backup server with Backup Exec 2010 R3. I am trying to backup the Information store on the Exchange 2007 (SP1) server but it is not available on the selection list. I can backup the flat files of the server. I do have the Exchange agent license. Troubleshooting: Uninstalled and reinstalled remote agent on the Exchange server (several times) Uninstalled and reinstalled the Exchange option on the media server Did a "repair" of Backup Exec on the media server Ran BE_Support Tool.exe (in the RAWS directory) on the Exchange Server. No Warnings. (It did originally say that I needed to run a VSS hotfix which I did). Permmissions all check out. Ran remote agent in debug mode. some dlls "not found": Example: bedsxchg.dll could not be loaded: The specified module could not be found. The following article talks about this issue with BUE 12. http://www.symantec.com/business/support/index?page=content&id=TECH58430 S
Solved
yakattack
13 years ago Place Backup Exec
4.7KViews
3likes
34Comments