The Backup Exec sad me 'Low disk space'.
I saw the media-s, and I found a lot of rewritable media on 'full' disk.
My Question:
Why Backup Exec not reuse rewritable media?
How can I change Media to rewriteble?
How can I delete Media with stored (retired) data? Because if I delete data manualy, then BE not refresh inventory.
Thanks for help
Gyula
Afternoon all,
This is my first post and was wondering if anyone could shed some light on a recurring backup failure I keep getting.
The Server is Server 2003 (SBS) SP2 and I am running Backup Exec 2010 R3 on it.
I run a daily "Full" backup which Overwrites the media and runs fine most days. However, every 3 weeks the job will fail with the error message (see attachment).
It appears to be related to the GRT aspect of the exchange backup but am unsure as to why it fails every 3rd week but is fine other than that?
Any help would be appreciated.
Regards
Dan
I have seen in the documentation that this is not a recommended practice but we are short on resources.
Can a CASO server also function as an MMS and Optimized DeDuplication target for remote office replication?
In this configuration, I can share remote MMS dedup disk with the CASO but since the target for the replication is already on the CASO, I don't have the option to share with the CASO.
When configuring backup jobs, and the replication job stages, I am unable to select the taget dedup disk as it is not available. Am I doing something wrong or is this why it is not a recomemended practice?
-Kevin
Hi Dudes,
My Backup Exec 2012 is generating job logs in another language. How can I modify them to English?
Thanx!
Hi,
Refer to capture, some backup sets has been expired within 3-12 Feb. This tape re-use this week start from 18 Feb but I found all expired backup set still existing. As I remember all expired backup sets will be removed after new backup. So what's the problem ??
These tape currently using the same tape drive and same slot with the same settings.
Thanks
Hello all.
This is actually a follow up on my post https://www-secure.symantec.com/connect/forums/installing-hotfix-201596-broke-my-system
This case, is still not solved and I guess it has long ago be given up by Symantec support. They are now not responding to any of my mails and I guess its the "Symantech way" of dealing with customers. Dont respond and the problem will go away by itself. Since Symantec does not care much and I'm stuck with Backup Exec 2012 at least for a while longer I've tried a different approach. Installing from scratch on new servers and moving dedup jobs over to the new servers.
I've installed a new CASO server and added the deduplication option following the admin guide. When it comes to the deduplication storage I have read and configured my storage as mendtioned in the "Best practices for Backup Exec 2012 Deduplication Option".
So far so good. But I am experiencing plenty problems even with a clean install. For the new servers, I configured a dedup storage and a plain disk storage. Jobs going to the disk storage seems to work fine. Jobs going to the dedup storage is a whole different story. I can sucessfully run 3-4 jobs before BE2012 reports:
"Robotic library destination element full error
I am having an issue on all my BE servers where the "Right Click" menu in the server backup set does not fully display. Is there anyone out there with this issue?
The setup is a CAS and a Media server using deduplication folders on Windows 2008 R2.
It doesent work on ether the CAS Server, Media Server, or a Windows 7 workstation with the management tools installed.
hi
backup exec 2012 sp3 jobs fail on centos 5.9 when Backing up Files with arabic characters in file name . is anyone know how can i fix this?
My exchange backups are failing with the following error:
Final error: 0xe0001211 - The volume that is used for the staging location must be a writable NTFS volume that is local to the Backup Exec Server. Also, the volume must have the same sectore size as the volume from which the exhcange log files were backed up. See the job log for details. Final error category: Resource Errors.
I did come across the article on the Symantec site for this particular error, but its not that helpful what so ever. I did make sure that the Temp folder is not hidden on the drive of the media server and it has more than enough space. I'm not using AOF and using GRT. Any suggestions would be apprecaited. Thank you
Years ago when I setup BE on our many servers and sites I was instructed (against my better judgment) to use a shared domain admin AD account rather than a common AD user account for the BE application and use it as the default logon account. Now 10 years later our security wants us to stop using it.
I have created a common AD user account with no particular rights, put it in the ADMINISTRATORS group of the BE server, changed the services to use this account and created and set the default BE account for it as well as switched the backup jobs to use it. All that's left is the System Logon Account. I cannot delete it, I cannot change it, it refuses to allow it.
I have used from the BE app itself menu -> NETWORK -> LOGON ACCOUNTS and set the NEW account as default and public. When trying to delete the OLD account that currently is the BESLA it refuses stating that a whole list of users (including myself) has it set as their default. More than once it has offered to swap the jobs out to another account, I've chosen my NEW account and it ran only to error leaving the old account as BESLA. Several of the users it lists are not even with the company any more.
I tried to use BEUTIl, which asks for the account name and password, acts like it does something, sometimes producing an error sometimes, sometimes not and it never works. The OLD account is still the BESLA.
I've rebooted and restarted the BEservices several times. I’ve even attempted to use the OLD account as the logon to Windows thinking since it has higher credentials than my own account it may work. Nada, nothing works.
Security plans on deleting the OLD account soon. While backups now work the way it is with the new account being used everywhere else in BE having the BESLA set for the OLD account makes me worry.
Is there a secret to tearing this thing out forcibly? I don't want to reinstall BE because I have a ton of jobs, catalogs, history and settings I don't want to replicate.
What exactly does the BESLA do anyway after installation? If the AD account to which it is set is deleted will it jeopardize my backups?
We are running BE 11, 12 and 12.5 and 2010 all over the USA. I have not tried it on any other machine but this 2010 server.
I have some partners in crime here at work that built a new VCenter server and so it is a different name.
So my VM backups are not working.
I looked for a bit and do not see a quick way to just point the backups for the servers that are failing to the new VCenter server that they are hooked up to now?
Or do I have to recreate the jobs??
Thanks
Mike
Hi
I'm currently using Backup Exec 2010 R3 SP3 with an 8 slot autoloader which has 1 tape device in it, if I were to add an additional 8 slot autoloader with 1 tape device in it would I need to purchase an LEO licence?
The licencing PDF states - per drive in library past the first drive in each library - but I not sure I follow.
Thanks in advance
Andy
Hi Folks,
I am new to Symantec Backup.We are using only one storage device .we have created arround 15 jobs.
But here my problem is i tried to run one backup job its running successfully but when i tried to run remaining backup jobs in the job status its saying that "Ready, No Idle Devices are available".In the storage properties concurrent write sessions was set to 1.
Is it possible to run all backup jobs at a time(simultaneously).If there please let me know the best way.
Please help me with this .
Thanks
Hi,
I've subscribed to the Backup Exec 2012 Software Compatibility List (SCL). Every time I am notified that there's an update, I get disappointed because the compatibility of Oracle Linux 6 has not made any progress. Currently, it's still at 6.1 while I have system running on 6.3 or above.
I hope Symantec could put some effort on this area.
Bonjours à tout les membes du forum.
j'ai un souci avec ma sauvegarde
j'ai planifié la sauvegarde de mon serveur d'applications
- une sauvegarde complete qui sauvegarde tous le serveur et
- une sauvegarde differentiel qui doit etre effectué chaque jour.
mais lorsque l'heure de sauvegarde arrive, il il commence et m'envoie à la fin un message d'erreur que vous verrez joint à ce fichier
vraiment s'il vous plais aidez moi pour pouvoir reussir mes sauvegardes
merci
coordialement
Hello,
Our client is using DFS-R on Windows Server 2008R2.
We perform full backup's of three DFS machines in the customer's environment through Shadow Copy Component.
Customer registered thet DFS Replication stops and combines it with the backup / restore of DFS machines.
The client requires clarification.
How backupexec'a agent affects the DFS service?
Does it stop at the time the snapshot, or for the duration of the entire backup job, and maybe quite "hot".
Is it possible to stop the replication of the backup and did not get up?
Thanks for help.
Greetings
Marcin
I am running backup exec 2012 sp3 with the agent for vmware installed. I can add my vcenter server and see all of my virtual machines. When I select a virtual machine it shows all associated .vmdk files as selected but when the backup completes (it says successfully) it is only 22KB and it says it didn't backup any virtual disks. Has anybody seen this before?
Hi Guys,
We are using Backup Exec 2010 R3 and we run the following backup Schedual;
Friday Night - Full System Backup, and Duplicate Full Weekly
Saturday - Thursday - Dail Differental and then followed by a Daily Differentail Duplicate Backups
The First backup that run backups backup to disk connected to the local server. The duplicates run to tape in a tape drive connected to the server.
I am currently having an issue with the Daily Differentail backups where I am seeing the following error;
e0009444 - The requested source duplicate backup sets catalog record could not be found. Perhaps the media containing the source backup sets was previously deleted.
I have checked the Daily Differential backup for this server and found that it is running perfectly, there are rules in place that stop the Duplicate backup or prevent it from running untill the Daily Deferentail has completed.
Does anyone have any suggestions for what might be casuing this issue?
Kind Regards
We are attempting to copy our mission critical vms to an offsite server for high availability in the event of disaster at our HQ office. All of the vms have replicated without issue so far (AD Domain Controller, print/file share server, terminal server, etc.) But with Exchange 2010 we've encountered an error. With VSS quiescing enabled, our BackupExec backups fail every time. BackupExec is configured to backup the Exchange server directly, through the Backup Exec Remote Agent for Exchange, so it should have no knowledge of it even being a virtual machine, yet it's still taking a snapshot of the machine before backing up. Currently Advanced Open File is enabled on the backups, so that may be what's causing the snapshot to happen each time. We've tried replication with VSS enabled and with it disabled, and the backups only run when it's disabled. I've also tried to configure the replication with VSS enabled and then pause replication before the backup starts, and it still fails.
My question is, has anyone gotten Backup Exec backups to run on Exchange with quiescing enabled? If so how? Does anyone run Exchange backups without Advanced Open File enabled? Do the backups run successfully and able to restore?
If not, does anyone run Exchange replication without quiescing? If so, have you recovered the Exchange machine successfully and does it come up as a dirty shutdown?
We're currently running Backup Exec 2010 R3 and Exchange 2010. The Exchange runs on Server 2008 R2 and VMware replication is the 5.5 appliance on vSphere 5.5.
Thank you for any help in this.