Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

DeDuplication not purging, Manual Purge Errors Out

Created: 13 Nov 2013 • Updated: 13 Nov 2013 | 4 comments

Hello.  We are running Backup Exec 2012 on a Windows 2003 R2 64-Bit machine.  The jobs are set to a 2 week cycle to connect via an IScsi port to a Quantum NDX8 device.  This was working properly however; recently, starting running out of space and therefore the jobs won't run.  The secondary copy of the full backup set  which runs as an option on the backup job to an externally attached RDX drive is working properly. 

The initial errors that we were seeing were in the jobs themselves, we were coming up with errors indicating the media could not be overwritten.

In looking at the issue, the old backup sets are not purging properly.  Followed Symantec Article #TECH192557, http://www.symantec.com/business/support/index?page=content&id=TECH192557.  However; ran into the following issue described in Article #TECH206214, http://www.symantec.com/business/support/index?page=content&id=TECH206214

 

So, therefore, my issue is how do I purge some old information and then tweak the backup set parameters so it purges properly per the retention time so the backups can begin to run again.  Backup less at the moment.  Thoughts? 

 

Thanks in advance for your help.

Operating Systems:

Comments 4 CommentsJump to latest comment

CraigV's picture

...the fine print in that TN urges customers with this issue to contact Symantec. I'd recommend this, and while doing so, ask them how to manually do so.

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

teiva-boy's picture

Its an interesting thing to note that NBU isn't certified with iSCSI without 10GBe, and that wasn't till 7.5. That you have to be able to write at over 200MB/s.

I'm surprised BE is allowed to use iSCSI at all. They use the same puredisk dedupe engine...

There is an online portal, save yourself the long hold times. Create ticket online, then call in with ticket # in hand :-) http://mysupport.symantec.com "We backup data to restore, we don't backup data just to back it up."

Smileyville's picture

Thanks for your responses.  Since this has been working for several months, I will go ahead and open a case with Symantec.  If you have other suggestions, please let me know. 

Smileyville's picture

I opened a case, but didn't get really far, basically he told me to do the same thing from this article to manually http://www.symantec.com/business/support/index?page=content&id=TECH130103, Tech130103, and then do an inventory.  Though for whatever reason it didn't error our while doing this with the tech, it reclaimed no space at all and now I'm at 0.  So, thinking the best thing to do, move the data to another storage space not tied to the backups and not backed up and start over.  So, reading the articles, the retention period should really be full backups once a week that are kept for once a week so they are overwritten.  The daily backups should be incrementals, again retention set to 1 week so they overwrite accordingly the following week.  Then the exteranl RDX tapes can handle the copy of the full data and I can rotate those for 4 weeks.

 

Thoughts?  What other settings or options can I select to ensure that this deduplication on disk storage work properly so we don't keep arriving at this out of space, error filled state and have reliable backups?

 

Any input is appreciated.  Thanks.