Video Screencast Help

Cannot overwrite/associate RDX cartridges

Created: 13 Jul 2012 • Updated: 13 Jul 2012 | 36 comments
Agility's picture

Hello all,

I've had an SBS2011 installation running Backup Exec 2012 running for 6 weeks now, backing up to an RD1000 drive (Dell server).  Everything was brand new, the server, the software and the RDX drives.  All has been running well up till this week when one of the backups started failing, complaining that the RDX was not overwritable.  Looking at the All Media view, I can see that two of the RDXs have gone into a different media set (Backup Exec and Windows NT Backup Media) and have been put onto complete overwrite/append protection.  This appears to have happened autonomously.

I've tried to associate the problem RDXs with the correct media set, but the option is greyed out.  I've wiped them, re-inventoried and even formatted them in Windows, but nothing I do seems to "unlock" them.  I've checked the physical lock switch on them hasn't been set, so now I'm stumped.  I've even brought a brand new RDX, and as soon as it went into the server it went into the same status.

I've just applied SP1a, to no avail.  Does anyone have any suggestions?

Comments 36 CommentsJump to latest comment

Colin Weaver's picture

if this is IMG (GRT) backup folders that are not deleting on IMG in BE 2012 then it is likely to be

Agility's picture

Many thanks, I've got a case logged so I'll post updates as they come in.

KevinLuke's picture


Have you received any updates? I have ran into this same issue. I implemented an RDX1000 Drive on a brand new server running Windows 2011 SBS. The media somehow automagically moved themselves from the Media Set I had created to the Backup Exec and Windows NT Backup Media set. This has been causing failures to my backups. I am no long able to write to the media or move it back to the correct media set. Thoughts?

Andrew Griggs's picture


No updates yet, I've had a couple of Symantec techs connect in to one of the affected SBS servers to see the problem first hand and I've also got another Webex booked in for next week for a higher-level tech. 

In the interim I've been manually removing the older backup files from the BEX gui, but I believe someone further down this post has posted the command-line instruction to script this action.

I'll update this post accordingly.

0zzY's picture

Hi all.

I have the same problem. Any news about it?

In addition i can't overwirte the media after the retention period, BE ask me a new RDX disk without overwrite!

VJWare link's are broken

Colin Weaver's picture

If the BKF files themselves are not being deleted/overwritten then check that you are set to use recyclable media before scratch and not the other way around.

For the IMG media we are still researching the issue in the technote I posted earlier.

0zzY's picture

and what about the problem to associate media to other media-set? (images linked by agility in the first post)

Colin Weaver's picture

I don't know what the MHB files are but the FLDR objects are container objects and by design are located in the NT Backup ... media set (hence they cannot be moved by design)

Backup Exec 2012 does not expose the IMG and BKF files to you however if it did you would see the BKF files are in the media sets defined by the jobs.

BTW whilst not finalized it looks like the next version of BE will use Data Lifecycle Management (DLM)  for RDX drives as well. As such media sets will then ony be used for tapes. DLM is currently used by standard disk storage but not removable (RDX) 

0zzY's picture

MHB are FLDR objects renamed.

By default a new media is defined as "BE and Win NT backup media", before the last update i was able to associate media to different media set..

0zzY's picture

I have totally removed BE2012 and reinstalled, but the problem remains.. I can't associate media to media set different from the default "Bexec and winNT backup media"..

..any news about it?

bingabong's picture

I have the same problem with my new SBS2011 server running Backup Exec 2012. RDX Drive is used. My media gets used then ends up in the 'Backup Exec and Windows NT Backup Media' Media Set so i can longer append to them.

I've read TECH192382 - is there any further update to this?

Should i be raising a support call for this?

Colin Weaver's picture

Please define what you mean by media - as already metioned if you mean the cartridge object itself then by design it is restricted to the NT Backup set and cannot be moved.

If you mean the BKF files and IMG folders that are held inside the RDX cartridge these do use media sets but the information is not displayed to you in the console and we do have a defect about IMG folders not being reclaimed/deleted/overwritten causing the cartridges to fill up. We have a controlled release of a orphan hotfix designed to address this issue but you have to log a formal support case to get it as it is not yet a public release

We also have annother defect where the media that represenets the RDX cartridge cannot be deleted - this will be fixed soon (althogn may possibly also have an orphan Hotfix - I am not in office to check)

Cédric L.'s picture


I join this conversation since I upgrade my BE 2010R3 to 2012 and have similar issues with my RDX cartridges.

My jobs with a LTO work just fine, but with RDX, I experiment the issues describe above : my RDX cartridge are directly associated with the 'Backup Exec and Windows NT Backup Media' so I cannot overwrite them, ans the second point is I can just append on a new cartridge until it's full, and not overwrite despite the expiration date is over ( )

The RDX cannot be delete (like : ) and cannot be move to another media set (I create one for RDX).

Did I misanderstund something or is there a fix for this ? Or did I call the support ?

thank you for your help.

Chuck Bridgeland's picture

Just to chime in, I'm having the exact same issue: SBS2011, Backup Exec 2012.  Fully patched (liveupdate finds no updates to apply).

We have 3 cartridges, we want to do a three week rotation (full on day, incremental the rest of the week, cycle through the three cartridges on a weekly basis). 

The link provided by VJware in the first reply:

First issue -

provides hotfixes for older versions of Backup Exec.

The workaround here (, I can do, but I'm not sure our customer will remember to do this.

We kind of need a fix. 

Colin Weaver's picture

If you need a fix urgently we have an Orphan update this is released under controlled cirumstances as Orphan updates are similar in nature to Beta releasse

As such to get the Orphan you MUST log a formal support case

Andrew Griggs's picture

Hi Colin,

I've received the Orphan update (a few weeks ago now actually), but as the affected servers all belong to my customers, I've been hesitant to apply the update.  Is there an ETA for the official fix?

My customers have also been hit with a second RDX issue TechID 192382: IMG folders not being overwritten when located inside RDX media.  I've logged a second case for this problem, again, do you have any further details regarding the ETA for a fix?

Many thanks,


EvilJester's picture

Same issue here too. SBS2011 and BE2012, can't change RDX media association. Works fine on server 2008R2 with BE2012, why the problems with SBS?

TTG's picture

Just to recap:

1. RDX Media moved to  NT Backup set - by design. Can we name the cartriges at least so it doesnt create 10000 different ones? It creates a new name every time I swap a catrige.

2. It should append/overwrite anyway because the append/overwriteapplies to the IMG and not to the media itself. If is doesn't, request the orphan hotfix?

3. In order to delete the media we can run the following command (since we can't move it to the Retired Media Set and the "delete" action is greyed out.) 

Get-BEMedia "fldr000019" | Remove-BEMedia - force

Deleting Media

Suppose you want to delete a tape from BE. If you use the GUI, then you would need to associate it with the retired media set before you can delete it. With BEMCLI, you do it with one command, e.g.

Get-BEMedia -name "000001L4" | Remove-BEMedia -Force

The -Force parameter will delete the media even if it is not in the Retired Media set. This is certainly faster than using the GUI.

Andrew Griggs's picture

Quick update for anyone watching this thread.  Hotfix for being unable to delete RDX media is out:

I'll be installing it this week and will post my findings.

I am also testing the orphan hotfix for GRT backup sets not expiring and I'm seeing good results, so hopefully the official fix will go live soon.

Colin Weaver's picture

That hotfix covers just for deleting the FLDR media from the console, which you should only need to do if you are retiring a cartridge from being used by Backup Exec.

 If you have the IMG folders not reclaimed/overwritten issue and you apply the Hotfix mentioned in TECH191513, then you will need an updated version of the orphan/private fix - now numbered as 26.12

LPTCsupport's picture

The hotfix for deleting the FLDR media from the console is no longer available.  Also we are having the issue with that requires the orphan fix 26:12 but I am very hesitant to deploy this into a production environment.  What is the ETA on an official fix for this?

Colin Weaver's picture

Hotfix 199190 was withdrawn due to a stability issue with the BESERVER process.

Orphan 26.12 depended on Hotfix 199190 so should only be used if you have that Hotfix and are not seeing BESERVER stability problems.

If you are seeing BESERVER stability problems with Hotfix 199190 then please uninstall it and use Orphan 26.11 for the RDX IMG reclaim issue instead

You will need to speak to Tech support to be issued with the correct orphan version if you do not already have it.

A complete replacement for Hotfix 199190 (with a new number) will be released soon.

Will Salen's picture

I have the same issues.  Called tech support and they referred me to  They stated I would have to manually delete the RDX media the first time after changing the registry entry but from that point on it should be able to overwrite.  Since I use a different RDX media each week, will will not be able to test automatic overwrite for another 4 weeks.

Colin Weaver's picture

If you have the IMG folders filling up the RDX disk issue then the technician should have referred you to

Note: This tech was recently been edited to state that a supported hotfix is available as long as you log a formal support case.

Colin Weaver's picture

Sorry Will, you should get the case re-activated and if necessary quote this forum thread to get the private fix.

Chuck Bridgeland's picture

So, I've applied the service pack manually.  This appeared to go successfully  I've made the registry change.  Then I restart services and run BE 2012.  Liveupdate sees SP1a as needing to be installed and attempts to install, but that fails.

How can I tell if SP1a is properly installed?

The cartridges I'm working with are still stuck in the "Backup Exec and Windows NT" media set, with no expiration (so, presumably no grooming), and still with no option to them to the backup set I want them in.

So, I'm not sure this is helping me.

Is this going to be fixed, or should I be looking for a different backup product?

Colin Weaver's picture

THE IMG delete will eventually be fixed by public fix, however for the time being YOU MUST log a formal support case to receive the controlled/private release

Also note we are not fixing the FLDR* media being seen in the  NT Backup set as that bit is actually by design, the bit you are missing is it is not actually FLDR media that get deleted/reclaimed to free up space once their retention period expires it is the IMG and BKF media that is contained inside an FLDR and these media types are not obviously exposed in the console

With regards SP1a check in installed updates within the Backup Exec admin console as the LibveUpdate link tio what is already instaleld sometimes get stuck on SP1a (oh and you should log a separate formal support case for that issue as well so we can investigate.)

IGE's picture

Hi, i have the same problem on our Backup Server. It's possible to get the Fixpack ?

Thanks in advance.

Colin Weaver's picture

You have to log a formal support case to get the update it CANNOT be issued via a forum request.

And customers that already have the fix are not allowed to distribute private/orphan fixes to 3rd parties without Symantec permission.

lsvasset's picture

Colin, is their a patch#/orphan# we can refer to when calling/creating a ticket?

lsvasset's picture

Colin, is thier a patch#/orphan# we can refer to when calling/creating a ticket?

Daniel Donaldson's picture

Hi there,

is this fix out? I appear to be having the same issue with my customer running bexec2012, their rdx carts don't want to overwrite any longer, despite a valid overwrite protection schedule

Colin Weaver's picture

The Hotfix that was released just over a week ago (201596) does not address IMG reclaim issue on RDX but does address the ability to delete an FLDR media object should you ever need to. Note : It remains by design that this media object type is fixed to the NT Backup ... etc media set.

The Orphan (Beta) update for the IMG reclaim has had to been updated to be compatible with the new hotfix so if you apply the new hotfix make sure you get the updated Orphan via a formal support case. Bear in mind it is recommended that you remove any orphans before installing newer Hotfixes. Anyone who already has an older version of the Orphan should still have an open case and should just contact their current engineer.

If you need the Orphan and don't know the details then you can just quote

 Currently (and this is subject to change) the public fix for this will be in the same planned update that will suppprt things like Windows 2012 and ESX 5.1

Keith Fountain's picture

We have resolved this issue as follows.

Create a file called RDX.cmd and populate it with the line below. Put it in a folder on the hard drive of your BUE server, such as imgcleanup.

for /f "tokens=*" %%i in ('dir %1 /b') do rd "X:\%%i" /s /q

Where X is the drive letter of your RDX drive.

Set a pre command in your job to call the file, so C:\imgcleanup\RDX.cmd "X:\img*"

When the job starts it will clear ALL of the folders that start with img from the drive you specify. We have been using this solution for a couple of years now and it works perfectly. Please ensure you run this in a test environment before deploying to your production servers.

This will obviously work for disk based storage as well as RDX drives by replacing "X:\img*" with either a mapped drive letter or unc path.