Start a Conversation

Unsolved

This post is more than 5 years old

614

November 12th, 2008 07:00

Customer deleted archived files and requested a restore.

We just ran into our first restore request for files that had been archived and it's been hell.
Someone deleted a folder with about 500 files in it last week. About 200 of them had been moved to centera and purged from the extended drive. DX did it's job and deleted the files off of centera as well.
The user placed a restore request and our ops group did a full restore of the folder onto the extended drive. At this point I get involved because DX starts throwing out warnings that it can't fetch the file.

Since then I spent hours on the phone with support to get the restored stub files deleted the best thing they have come up with is for me to disable the DX drivers, reboot the server, delete the stub files, reenable the drivers.

To get her files back I did another restore of the folder from a backup taken before we archived the drive and then coppied the non stub files from the newer restore over the old pre-archive restore.

I'm guessing I'm not the only one that has run into this and I'm wondering what people do to get around it. I've considered enabling the DX recycling bin so that the files won't be deleted from centera when a user issues the delete command. I'm hesitant to do that because I read a warning that if the stubs are restored from backup they will work, but then when the recycling bin is cleared out down the road it will nuke the archived copy of the file leaving a worthless stub out in the restored file location.

I also need to document the procedure so that I can hand it off to our ops group. Would it just be best to tell them to do all file restores for those extended drives to another location and then look for / remove any stubs before copying it to the extended drive?

I think I'm starting to get a pretty good idea how all of this works, I'd just like to know what other people are doing to get around some of these difficulties.

9 Posts

January 13th, 2009 16:00

We got around this by doing a little trick on DX. We archive items in monthly folders. We also set retention on the files. To protect ourselves, we increment the retention by a day. What this gives us is a great deal of protection for next to nothing.

If a user deletes the files, DX will delete that pointer to the blob, but not the actual blob because it has retention set. We can do a Restore Files from the media and get back the first pointer to that file, then increment it again to protect ourselves.

Very simple, but very worth it.

41 Posts

January 13th, 2009 18:00

You can use DX Recycler Bin feature (more info on the guide) or enable retention on the files.

If DX recycler Bin is enabled and there "was" an accidental deletion of files, you can restore them.

When you perform file restore from tape backup, always restore full files..not just tags.. It would be meaningless if you restore tags if the files was previously deleted.
No Events found!

Top