Tuesday, November 06, 2012 9:27 AM
I'm really starting to question how this product is over 5 years old and yet the way it manages certain aspects of backup is very basic.
We've had an example of a tape not being changed by mistake, this happens. Human error.
The next nights backup has half run on the previous tape. So now we have 1.5 days worth of data on one tape. We don't want that.
So the next morning we want to come in and try to rerun the ENTIRE tape backup job. I DO NOT want some data on one tape and some on another. Turns out rerunning the entire job is harder than it should be.... and we end up with a tape that I cannot mark as free because DPM 2012 says it is part of a protection group.... and that I must stop protection of that group in order to mark it as free.
Blindly, I follow the instruction and stop the protection of our critical business data...yet the tape will still not mark as free. (It did suggest I run a power shell script to force the tape as free, but that's about as user friendly as a linux install, and is another thread entirely)
So now, I have an unusable tape and no protection of my critical data...all because someone forgot to change a tape.
Very, very poor.
Tuesday, November 06, 2012 8:16 PMModerator
You can make a co-location protection group set and add the protection groups to that set, then under the ADVANCED option, change the Write period to 1 day. That will prevent the next days backups from being written to the previous days tape.
If you want to manually re-run a tape based backup for a certain recovery goal, you can use the power-shell script in this forum post.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.