01-08-2013 08:11 AM
We have just taken over the support of a Windows 2008 (SBS 2011) server running on VMWare, with an RDX drive.
BE sees the disk in the storage drive, but for some reason the disk has been set to do not overwrite (infinate). Having read a number of forums etc they all suggest that moving the disc to Scratch media will allow us to change the state to You can overwrite the disk.
However 'associate with media set' is greyed out, so I cant make the disk scratch and therefore cant use the disk. This is stopping us running a backup job.
I'm obviously missing a trick here, This would be so easy in previous versions of BE....
Any help greatfully received
Thanks in anticipation.
Solved! Go to Solution.
01-08-2013 09:03 AM - edited 08-08-2018 12:08 AM
The FLDR media by design can only be in the media set that BE puts it in. (Backup Exec and NT Backup set) This media object however represents the whole cartridge, not the individual backup sets on the cartridge which my have been backed up at different times.
However the FLDR object is not what gets overwritten, the logical object that is overwritten (or possibly reclaimed) is the IMG folder or BKF file, which does represent all or part of a backup set (have a look inside your RDX cartridge using Windows Explorer to see what I mean as these are not exposed inside the Backup Exec console but logically will be in the media set you defined in the backup jobs.)
We have a defect for not being able to reclaim/overwrite IMG folders on RDX media which will cause your RDX disks to fill up - current fix is Latest Hotfixes plus a beta/private/orphan fix which you have to have an active support case to be issued with.
We also have a defect for not being able to delete the FLDR media, which should only be needed if you are completely retiring an RDX cartridge - current fix is the Latest Hotfix
Not being able to move the FLDR media between media sets was reported as a defect originally, however it is by design - you should not be able to move this type of media object between sets.
EDIT: Public docs
http://www.symantec.com/docs/TECH192382
http://www.symantec.com/docs/TECH191513
http://www.symantec.com/docs/TECH191711
01-08-2013 09:03 AM - edited 08-08-2018 12:08 AM
The FLDR media by design can only be in the media set that BE puts it in. (Backup Exec and NT Backup set) This media object however represents the whole cartridge, not the individual backup sets on the cartridge which my have been backed up at different times.
However the FLDR object is not what gets overwritten, the logical object that is overwritten (or possibly reclaimed) is the IMG folder or BKF file, which does represent all or part of a backup set (have a look inside your RDX cartridge using Windows Explorer to see what I mean as these are not exposed inside the Backup Exec console but logically will be in the media set you defined in the backup jobs.)
We have a defect for not being able to reclaim/overwrite IMG folders on RDX media which will cause your RDX disks to fill up - current fix is Latest Hotfixes plus a beta/private/orphan fix which you have to have an active support case to be issued with.
We also have a defect for not being able to delete the FLDR media, which should only be needed if you are completely retiring an RDX cartridge - current fix is the Latest Hotfix
Not being able to move the FLDR media between media sets was reported as a defect originally, however it is by design - you should not be able to move this type of media object between sets.
EDIT: Public docs
http://www.symantec.com/docs/TECH192382
http://www.symantec.com/docs/TECH191513
http://www.symantec.com/docs/TECH191711
02-25-2013 08:21 PM
Hi
There are a final solution for TECH192382??
Thanks¡