Hi!

I’m going to provide provide disaster resistant backup solution for my virtual infrastructure. I have two sites, first is production, the second is recovery site. Virtual machines are running on prodaction site and protected with SRM, so on the second site there is only placeholders. I want to create backup job and include there two locations site1/datacenter/vmfolder/* and site2/datacenter/vmfolder/*. In case of disaster, virtual maschines on the second site will appear so the next backup job will back them up. First site probably will not be available so BE will not create redundant copies of the same virtual machine. So my questions:

1. Will this solution work as i have described?

2. What will happen with placeholders, will they be backed up (cause until disaster they are not normal VMs) ?

Greetings,

My weekly backup is now breaking 200gb whereas my dailes are only 10-20gb. The weekly backup job specifies to backup working set last accessed in the last 5 days however im getting stuff thats not been accesed/modified for at least two months.

Any ideas as to why that may be happening?

Thanks

James

Hi All

We are running symantec backup exec 12.5 and I have been trying to clear up some space on the server.  I notice that there was alot of these files and wanted to move them somewhere else because they are huge. (Check screenshot below)

http://13l.imghost.us/wj/backupexec.PNG

However, I notice the next day that there are more files appeared which look the same and the space I freed up has gone again.  I am sure that I have stopped the scheduled backup looking at the job monitor:

http://13l.imghost.us/8rA.png

Could anyone help me idenitfy why its still running when it clearly says 'on hold'.  The server is small business server 2008.

Regards

Supermean

Hi All,

Am hoping someone can help.

We have a relatively new installation of BE2012 (latest service pack and patches). We have the VMWare agent licenced and installed along with the Windows agents on the actual VMs.

I have added the ESX server and run a backup with GRT enabled.

The backup finishes but the individual VMs are listed as if they are physical servers instead of VMs. This obviously in turn means that GRT recovery is not possible on the servers. The backup completed successfully but with the warning about GRT and I can confirm that I can restore the entire VM.

I have searched these forums and found that adding the ESX via its IP and not its FQDN can be an issue but it is not helping me out.

Any assistance much appreciated.

Good Morning all,

I am having an issue when backing up a particular server.

The server itself is a virtual server, I am not backing up the entire server just certain files on that server, each time the job runs is fails with the below error:

Hi there,

I noticed the Service Backup Exec DLO Administration Service is not started. In the application log on the server I see an error that it is missing a file (that file is indeed missing).

How can I get this file back? It seems to be missing for a while. But back-ups are running fine to tapes.

Thanks.

Marcel

---

FCB::Open: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'D:\Apps\SQL Server\Data\BE_DLO.mdf'. Diagnose and correct the operating system error, and retry the operation.

Hi , I have installed the Backup Exec Agent on Window 2008 Server R2  and I want to backup the second partition there. On Backup Exec Selection List Backup Exec Media Server ,  the Server Comes but the Partitition which i want to backup is greyed out ( I can not select it ). So what do you suggest i do?

Hi,

we have an issue with BE 2010 R3 and sharepoint 2013, does this version of BE support sharepoint 2013?

Shahin

I'm still getting used to Backup Exec 2012.  I'm trying to search for *.pst files on a server with 3 drive partitions (C:, D:, F:).  When I search it finds them on the D: drive but not the F: drive.  How do I direct Search to search on the whole server, not just the D: drive?  Or how do I direct it to only search on the F: drive?

I have the error covered in this TECH article: http://www.symantec.com/business/support/index?page=content&id=TECH202002

Does anybody have a fix or workaround for doing GRT-backups?

Non-GRT backups work fine.

I have a sql express instance on my vCenter server that symantec will not backup. It comes up with Unable to attach to \VIM_SQLEXP.

My first few troubleshooting steps have lead me to this point. When I go to backup properties, and I select test/edit credentials, all the accounts work except for SQL instance \VIM_SQLEXP. Error says test failed. The logon account symantec BUE is instructed has dbo rights on the SQL express server. As a test i have even used my domain admin account that also has dbo rights on the SQL server. None of the accounts work and the job continues to fail.

Any thoughts?

Symantec 2012

Server 2008 R2 SP2

SQL Server Express 2008

vCenter instance of SQL Express.

Ce commentaire est à destination de ceux qui se pose la question : doit-je migrer vers BackupExec 2012 ?

- La réponse la voici

   Mon infrastructure comporte une cinquantaines de machine (virtuelles et physiques confondues). Il y a encore Quelques jours 25 de ces serveurs etaient encore sauvegardés de manière simple et efficace avec BackupExec 2010 R3.

    le seul problème se situait au niveau de ma librairie de sauvegarde LTO5 (IBM TS3100) qui ne dupliquait pas à ses possibilité maximum (570MB/min alors qu'elle pouvait atteindre 3000MB/min quelques temps auparavant).

   Pour résoudre ce problème, on m'a conseillé de migrer vers la version 2012 (prise en charge par mon contrat de license). J'ai rapidement vu la situation non pas résolue mais changé en chantier inommable et pavé de mise à jour de hotfix sans pour autant résoudre mes problèmes.

   Sans compter l'interface graphique totalement gachée pour ne pas dire baclée.

• Il est impossible de visualiser un inventaire des bandes Virtuelles
• Il n'y a plus de JOB MONITOR donc impossible de voir ce qui s'exécute à l'instant même
• Une librairie virtuelle indique un status "ACTIVE" mais affiche "No job exists" lorsqu'on veux afficher les actions en cours (Que fait-elle ??)
• L'ancienne interface proposait de créer des stratégies pour les appliquer à des serveurs de manière simple (Ca n'existe plus). Il faut maintenant créer les taches de sauvegarde à la main (il existe bien des templates de base D2D2T D2D D2T etc mais cela ne prend pas en charge des modèle de planification). Si je veux modifier la planification de la sauevgarde d'un groupe de serveur ??

       - Le reporting est toujours aussi pauvre

• Aucun moyen de faire un report simple pour visualiser l'état des sauvegarde quotidienne.
• Aucun moyen de faire un report qui lie les données sauvegarde au bandes utilisée (inventaire de mallettes externalisée par exemple).

     (Heureusement BackupExec 2012 utilise une base de donnée SQL ce qui permet de faire tout cela à la main avec un script SQL. Encore faut-il avoir les compétences.)

     Parmis les erreurs constatées suite à la migration

• Certains système ne supporte plus Shadow Copies Components (Il faut le désactiver à la main).
• Les Librairies Virtuelles sur disque s'arrêttent sans raisons (Patch "Backup Exec 2012 revision 1798 Hotfix 201596").Mais ca ne résoud pas forcement le problème.

        - L'IDR est utilisable seulement si TOUS LES COMPOSANTS ne sont pas reunis (Dont le fameux SHADOW COPY COMPONENTS qui n'est plus compatible sur certaines versions !!)

• Mes librairies Virtuelles n'arrivent plus à faire leurs inventaire (même après le Patch Magique : hotfix 201596)

Les améliorations apportées :

• Je peux maintenant sauvegarder du Windows 2012 (domage que j'en ai pas !)

Et c'est à peu près tout (plutôt maigre comme avantage)

En conclusion :

• Incompatibilité matérielles diverses
• Changement dramatique d'interface au point que mon DSI m'a demandé s'il ne manquait pas des modules complémentaires.
• Le déploiement des agents nécéssite toujours le redémarrage des systèmes cibles (plutôt ennuyeux pour une infra en production).
• Les erreurs sont inexplicite (media error disk offline - mais lequel ???)
• Reporting plus que léger et difficile à utiliser
• Plus de stratégie de sauvegarde mais des jobs par serveurs
• Aucune visibilitée globale des taches en cours (JOB MONITOR).

Pour finir je vous conseille de bien réfléchir à vos contraintes pour effectuer cette opérations. Si vos systèmes se sauvegarde correctement, ne changez rien !!!

BV - Admin Exploitation

50 Serveurs - 400 Workstations

VMWare / NETAPP / IBM / BACKUPEXEC / NAGIOS / SQL

I'm working some test cases for DR of a pair of BE3600 appliances. One is setup as Central Admin Server and the other is Managed Backup Exec server. They each have a dedup storage and shared with the other server.

Anyone knows what are the proper procedures for doing DR in a CASO environment?

1) If CAS is down, I found that Backup Exec services won't even start on MBE !? I tried to follow the steps in a KB(TECH202149) which runs the setup wizard to change the MBE to a "Locally managed server" but that won't work (after reboot all BE services still not able to start). So what I need to do to get MBE running without a CAS? (is it possible?)

2) If MBE is down, how to remove it from CAS while the MBE is unreachable? When it is back, do I simply re-configure it as a new MBE to the CAS?

Thanks.

Joseph

Tasked with restoring an old GroupWise server to gain access to old emails. Complete NetWare noob, and IT from back in the day is long gone. GroupWise 7 was running on NetWare 6.5 OES. We have the software disks for NW and GW.

I've duplicated what I understand the old setup to be:

• A WS2003 box running BE 11d and Novell client for Windows and a DLT tape drive
• A NW 6.5 OES box with BE Remote Agent for NW using TCP/IP and host name registered in DNS and resolvable by NetBIOS name or FQDN by the Windows box

I've inventoried and cataloged the DLT tapes to the BE database and can browse the files and folders that were backed up. I can also browse the remote NW server from the WS box without any problem, using the default NetWare "admin" account.

I've verified RANW is running by using TELNET NETWARESERVERNAME 10000 from the Windows box. A connection is made.

Remote Agent authentication is my current problem.

For resource credentials, BE uses the same "admin" account as I'm successfully using with the NetWare Client. I've created a local Windows account named "admin" and am using that as the interactive user account and the BE service credentials. The NetWare "admin" account is set as the Default Account in the NetWare client for Windows. My limited understanding of NetWare is that this "admin" account is as fully priveleged as is "Administrator" in the Windows world.

If I use "admin" as the Default Logon Account username, and click Test All in Resource Credentials for a Restore, it says "Access is denied." under Test Results.

http://www.symantec.com/docs/TECH83381 suggests a number of things, all of which I've tried. Among them, it says to use .Username.Context format, but when I enter that, I get this message as soon as I click Test All: "Your default logon account could not be authenticated. The username or password may be incorrect. Click OK to edit your default logon account." When I click OK, I'm presented with the Edit Logon Credentials dialog. I've also tried ".admin" and ".admin.context.tree" with the same results. Only way I've found to get that dialog box to close is to revert to "admin".

http://www.symantec.com/docs/TECH56917 says the "Access is denied" result is a bug that may be fixed in a future version of BE. (If so, I have 11d server & agent fully patched, and the bug was never fixed!)

With it set to "admin" and disregarding the credentials test per TECH56917, if I try to do a test restore to the NW server, I get this in the Job Log:

In the Restore section, "Access is denied to Remote Agent"

In the Job Completion Status: "Final error: 0xe000fe29 - Authentication failed on connection to the server. Make sure that the user account has the appropriate permissions and that the password was typed correctly. Final error category: Security Errors. For additional information regarding this error refer to link V-79-57344-65065.

A test backup goes the same way; I can select the resources for backup and create the Job, but it fails, with the same entries in the Job Log.

So...anyone out there still know how to set logon credentials for a restore job against a RANW machine?

hi ,

i have many question about BE SBE 2012;

1. does the BE Small Business Edition 2012 must be installed in only a Microsoft Small Business Server..???
2. what is the benifits of using BE Small Business Edition 2012 in regards BE 2012
3. with the base line licence of BE Small Business Edition 2012,how many servers can i backup
4. wich licences do i need to backup if i have an Hyper-v running on microsoft SBS and have about 6 VM running on it with BE SBE ?

Thanks for your help

Hi,

i have two SBE2012.

Node1 windows 2008 EE ( hyperv + sbe2012 )

Node2 windows 2008 EE ( hyperv + sbe2012 )

i want to restore a virtual machine from one node ( node2) to another ( node1), but when i select BROWSE for select the machine ( different location ) the system returns the following error:

The list of servers for this domain is currently not available. Make sure that " computer browser " service for the domain is enabled.

The two node are not in domain , but in workgroup and the services " computer browser " is active.

Any idea?

thx.

Hello,

I come here again, because I'm proceeding my bunch of tests. Currently, I try to restore my main domain controller (Active Directory + DHCP + DNS) on a remote server.

The two servers are from Dell brand, physical.

The disk configuration "appear" to be the same (not the case apparently), but the system reserved and OEM partitions are recognized as incompatible, the size is ok.

*For the OEM, I've created a RAW partition instead of NTFS

• The system reserved partition is recognized as System, but not Active, when I boot on the SDR disk
• The OEM Dell Partition can't be manually created I think, I just need to the right file format I guess.

But my question, is why the System Reserved 100 Mb partition is not compatible ? I mean, it's the same both side !

Thanks in advance,

Regards,

Alex

Hi People,

I am attempting to get regular and consistently succesful backups using Backup Exec 2012 sitting on a 2008r2 server, running Exchange 2007.

I am relatively new to backup exec 2012 and have not really had problems with previous versions of the software so I may be missing critical elements that everyone else assumes and does by default.

Originally, the server was set to tape backup and this regularly failed with inconsistent tape error due to errors on the tape.
This I am happy to put down to a case of age of tape, condtions they were kept in etc etc.

In order to get away from tape we began testing to Backup-to-folders located on another machine on the network.
We split the original job into a number of smaller elements, specifcally an 'Exchange' backup and a daily 'Work' backup.  We then pointed each one of these backups to its own folder on the other machine.

We then created a brand new user account and followed the instructions as advised by Symantec in order to create an admin account.
This was then tested and all works great.

We then tested the backups manually and each one completed succesfully.
Finally we checked the times they took to complete and scheduled them to run automatically each evening ensuring that they did not overlap (although we did not see this being a major problem if they did as our tests showed they still ran fine)

----------

Some evening these backups work, some they do not (in fact most of the time they fail)
If we run the job manually, sometimes they work, sometimes they do not.
Nothing is being changed by us so its proving very difficult to find the exact cause.

Work Backup
This job fails with the message:

Our Backups to tape have slowed down, it happened overnight and had been running fine for months. I've done the usual things like clean the heads but this has made no difference. Having watched them realtime, the job rate (including verify) seems to get slower as the job progresses. Copying some files from one server to another seems fine, we did 150GB in about 30 mins to the Media Server.

Here's some job history and more detail because it seems to slow down once it starts to backup our main file server, which also holds our SharePoint SQL DB

This is the first item of the job, this happens to be our Media Server that the Tape Unit is connected. It shows the start time on on day, then the next and this looks ok

Backup started on 6/6/2013 at 1:03:10 AM.
Backup completed on 6/6/2013 at 1:21:16 AM.

Backup started on 6/7/2013 at 1:03:16 AM.
Backup completed on 6/7/2013 at 1:26:17 AM.
 

The the next part of the job, on a remote server which looks to be ok.

Backup started on 6/6/2013 at 1:22:24 AM.
Backup completed on 6/6/2013 at 1:26:23 AM.

Backup started on 6/7/2013 at 1:27:32 AM.
Backup completed on 6/7/2013 at 1:38:02 AM.

Next is our concern, the main file server, same amount of data but this has really slowed up.

Backup started on 6/6/2013 at 1:26:28 AM.
Backup completed on 6/6/2013 at 6:40:57 AM.

Backup started on 6/7/2013 at 1:38:08 AM.
Backup completed on 6/7/2013 at 11:10:05 AM.

The last part of the job is our Exchange Server (2010) which I suspect is delayed because of the one above.

I haven't copied any major data between the file server and media server, or run any test jobs because the backups are finishing late in the afternoon and wondered if anyone had some further ideas. I'm thinking of disabling the SOPHOS av tonight on the Media Server and also peforming some direct diags on the Tape unit itself.

Thanks