Jobs stuck indefinitely in Queued Status
We have had an ongoing issue for about 2 months now, and since we have had a clean build (3 times now) for Backup Exec 2012. We have opened numerous cases with Symantec to resolve this, and they claim the first time that HotFix 209149 (see http://www.symantec.com/business/support/index?page=content&id=TECH204116 ) corrects the issue. The issue is also noted by seeing Robotic Element errors stating that OST media is full and it brings the "virtual" slot for the PureDisk or OST storage device offline. Restarting the services in BE only makes the problem worse and causes a snowball effect whereby jobs constantly error in the ADAMM log files. Essentially, the jobs never can get a concurrency/virtual slot and they stay Queued forever. I have seen others on this Forum with this problem, and while the Forum administrator seems to mark them as "Solved", they are not - because I see the threads drop off with no resolution identified. Are other people having this problem? If so, how are you overcoming it? Once it starts the environment is essentially dead in the water because the jobs never start (they sit Queued forever) - save for one concurrency which for our size environment is only 1/4 the need we have. We use CAS and 4 MMS servers with 2008 R2 with all patches applied, PureDisk 32TB volume on each MMS, Data Domain OST connection to DD-670 OST with OST-Plug 2.62 (28TB), replicated catalogs, and duplicate jobs for optimized deduplication between MMSs. We run BE 2012 SP3 clean - we reinstalled with SP3 slipstreamed because Symantec said this problem could be fixed through database repair by them manually or by reinstall...we chose reinstall (even though they did offer to "fix" the issue with database repair). We chose reinstall to validate whether SP3 truly fixes the issue. It is clear to us it does not. We are looking for anyone else who has had this problem to report into this forum. Thank you, Dana14KViews4likes15CommentsCatalog Error - V-79-10000-10660
Hi All, I find myself managing (or trying to) our regular backup strategy. That server will be different each time and i havent seen the error on more than one server during each nightly backup. Catalog Error V-79-10000-10660 - An error was encountered writing to the on-disk catalogs. A synthetic backup of this resource will not include the data backed up by this operation until the next full or incremental backup of this resource runs. My Steps to fix the issue 1) Re-name the catalog folder to create a new set of catalogs. 2) Where I can find a catalog for the failed job, delete it from the new catalog folder, but i cannot always find a relating xml/fh file. I might fix an occurence of this issue but a new one occur from a different serverduring the very next run. Any pointers that may be causing this error to occur would be great. I apologise for any miscommunication through inaccurate use of terminology, as i havent been in this area all that long, feel free to ask qus. Thanks in advance. RLSolved3.6KViews0likes6CommentsBE2014 Deduplication - how many concurrent jobs do you run, what spec is your backup server?
Hi I have a couple of quick questions about the dedupe store concurrent jobs setting (for a standard dedupe store running on the media server, with no external devices andno OSTs). What do people normally leave the setting at? It's looking like i'm going to be running quite a few jobs at once, but i'm hesitant to perform more than 3 jobs at once as it might slow all the jobs down to much I have BE running as a VM, with 2 x dual core processors, with 32GB of RAM. If i double this to 8 cores in total, will it help me run more concurrent jobs efficiently? Thanks in advance for your opinionsSolved2.8KViews0likes11CommentsBackup Exec Replication & Recovery
Hi, Using BE 2012 SP1, I've successfully setup a job to backup and replicate the de-duped data toour DR site. The master server is configured as aCentral Administration Server (CAS)and the DR site server is setup as a Managed Media Server (MMS). Backup, replication and restores are working fine from both sitesbut I noticed that when the CAS server becomes unavaialble, the MMS is no longer able to perform any backup/restore operations and some of the BE services arestopped. I would like to be able to recover backups from the DR site in the event that the master site/server is offline. What must I configure to ensure theMMS server remains operational evenif the CAS server is offline? ThanksSolved2.8KViews1like3CommentsVery slow Backup Exec Console (GUI)
Hello Everyone i have serious problem with Backup Exec Admin Console, its very Slow , Sometime its take 15 minutes to open the console , editing the jobs are worst it takes10-20 minutes to edit a job (sometime with query time out.) i can see SQL Information & Storage Error related log in Windows Event viewer as Below: Source: Backup Exec EventID : 57345 Database Exception Context:SaveNrdsAgent Error:-536837662: ::-2147217900:Error in Fetching Lock:........ ------------------------------------------------------------------------------------------------------------------------------------------ Source:Backup Exec EventID:58053 Bavkup Exec Alert:Storage Error Backup Exec was unable to initialize andcommunicate with the device [HP MSL G3 Series 8.60] (the system cannot find the pathspecified.) ...... -------------------------------------------------------------------------------------------------------------------------------------------------------- i tried to Repair BEDB but BEUtility cant connect to SQL server , with error of "Cannot Start SQL Server Service" ,i tried to fix that with Changing registry setting for SQL Instance then its gets worst ! windows gone in complete fail ( after restarting server , all the windows services failed to start) so i changed back registry keys. BE 2014 SP2 ( 2 server - CAS & MBES) on windows server 2012 R2 with SQL 2008 EnterpriseR2 SP2 . BE Use Local SQL Server withInstance of"MSSQLSERVER" (BEUTILITY Want to use BKUPEXEC) Recently i have Upgraded my servers to SP2 , during the SP2 Update CAS server failed to install the update but after a few tries its updated to SP2 Successfully. ( the Problem appeared after SP2 Upgrade) We have 2 HP MSL Libraries , backup exec is only using one of them (over FC) and other is connected to another backup system but BE can See It. the other library was in offline mode until recently we delete it from BE Console ( ithink it has somthing to do with GUI ProblemTECH204561) SymHelp says the Database Schema is Older than Backup Exec Version ( i triedTECH50537but still getting same error) this server is so important for us , we cannot reload the database we have more than 200 Jobs on it with 150 TB of Backup data. I really apperciate it if anyone can help me with that. thanksSolved2.6KViews1like4CommentsEnvironement CASO unable to share storage dedup
Hi I have a Backup exec Server CASO 2014 SP2 it's a VM with Server 2012 R2 The managed Backup exec Server 2014 SP2 on Server 2012 R2 it's a physical server Ibm X3400 M3 I can't share the dedup storage of MBES with the Backup exec server CAS2.4KViews1like22CommentsBackup Job is missed?
Our backup duplicate job to shared device statusis always missed and when the schedule is coming up to backup, "Ready,The Backup Exec Server that the catalog requested is not available to process this job" is written in the job status? Why?what ı have to do? and where is configurationthe scheduled time window? Please help usSolved2.2KViews0likes4CommentsMerge data (tape catalogs, indexes) from BE 2010 to new 2012 servers
Some similar requests give me the impression that the following cannot be done. I'm hoping someone can tell me I'm wrong. I have two backup systems running in parallel: one is a standalone BE 2010 media server with an attached tape library; the other is a 2012 CASO infrastructure with two media servers. I want to attach the tape library from the 2010 server to one of the 2012 media servers and retire the 2010 server. How can I migrate the tape catalogs etc. from the 2010 server to BE 2012? I don't need to migrate the jobs, we will create new backup jobs on 2012, but I do need to be able to perform historical restores from the tapes written by the 2010 server over the last few years. There are many tapes; recalling and cataloging all the tapes would be a big job. For example, would this work: Upgrade the BE2010 server (let's call it old-server) to BE2012 Add old-server to CASO and centralise (distribute?) the database & catalogs Move the tape library to one of the other BE2012 media servers Test that the new server can do restores from old tapes Remove old-server (will this remove the catalogs etc.?)Solved1.9KViews0likes14CommentsThe queried backup sets contain two backup sets with the same ID
Hi, After some serious disaster on BE15(latest patch), I managed to get the server running again. However I am facing a different issue. When I select the deduplication storage and select Backup Sets tab, I see "Load Failed... The queried backup sets contain two backup sets with the same ID." . This happened after I removed this member server from CASO environment. I checked the catalog files and they are present. I also tried the "Catrebuildindex -r" method mentioned at the post "https://www-secure.symantec.com/connect/forums/duplicate-backup-sets-same-id". This had happened a couple of times when the server was a managed server in CASO environment but after a couple of F5, I was able to see the Backup Sets and even start restores. Any ideas?1.9KViews0likes3CommentsBE2014 Optimized Duplication - 'Loading Media - Duplicate' for hours
Hi There, I have BE2014 on the latest version, and my architecture is as follows: -Production Environment, with CASO, Duplication Add-on, and a local dedupe store on this windows 2012 R2 server. (no extra devices connected) -DR environment, with a BE managed server out there, and Deduplication Add-on (no extra devices involved out there either). I have a dedupe store shared out on this managed server (shared with the CASO server in Production) -At present, there is a 1GB LAN connection between the two servers/sites. I have my backup jobs defined on the CASO server in production, and thedata is being saved to the dedupe store in Production just fine. I havea stage added to duplicate the data over to the shared store over in DR, but the jobs are taking forever (too long for the backup window at present). Every time i check in on it, it's almost constantly stuck on 'Loading Media - Duplicate' Anyone got any ideas? Thanks in advance1.9KViews0likes9Comments