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.
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
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?
I have the same issues. Called tech support and they referred me to http://www.symantec.com/business/support/index?page=content&id=TECH187957. 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.
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.
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.
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?
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.)
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.
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
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 http://www.symantec.com/docs/TECH192382
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
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.