A little late on this one, but I would
also recommend making a copy of what images exist on disk before you expire
them and save it. This way, if you do end up expiring an image with no
copy, you at least know which one it is and can be prepared if a restore
request comes your way. In short, always do your homework. Also, if you
script this, make DANG sure that you test your script thorougly before
running it on all of your images.This also helps to stave off any occurrences
of Mr. Murphy and his laws.
Rusty Major, MCSE, BCFP, VCS ▪
Sr. Storage Engineer ▪ SunGard Availability Services ▪ 757 N. Eldridge
Suite 200, Houston TX 77079 ▪ 281-584-4693
Keeping People and Information Connected®
▪ http://availability.sungard.com/
P
Think before you print
CONFIDENTIALITY: This e-mail (including
any attachments) may contain confidential, proprietary and privileged information,
and unauthorized disclosure or use is prohibited. If you received
this e-mail in error, please notify the sender and delete this e-mail from
your system.
Tim Hoke <thoke AT northpeak DOT org>
Sent by: veritas-bu-bounces AT mailman.eng.auburn DOT edu
01/26/2009 04:35 PM
|
To
| Ed Wilts <ewilts AT ewilts DOT org>
|
cc
| Matthew Stier <Matthew.Stier AT us.fujitsu DOT com>,
veritas-bu AT mailman.eng.auburn DOT edu
|
Subject
| Re: [Veritas-bu] Clearing DSSU's. |
|
Here's the general process I think I would follow.
First, stop directing any backups to DSSU until your "maintenance"
is done.
Run bpimmedia to see which images are on your dssu (bpimmedia -disk_stu
<stu label>
For each of those images, run bpimagelist to see how many copies there
are (bpimagelist -backupid <BID>)
For those images which don't have a copy on tape, duplicate it (kick off
your de-stage job)
For those images that do have multiple copies, expire the dssu copy (bpexpdate
-backupid <BID> -d 0 -copy <#>)
Repeat those steps until you're sure you have all your data protected.
The bottom line though is to make sure that before you go deleting (expiring)
anything, you've got the data protected. You don't want to accidentally
erase an image that is ONLY on disk.
-Tim
On Mon, Jan 26, 2009 at 3:43 PM, Ed Wilts <ewilts AT ewilts DOT org>
wrote:
On Mon, Jan 26, 2009 at 3:24 PM, Matthew Stier <Matthew.Stier AT us.fujitsu DOT com>
wrote:
Background: Solaris 10 master/media server with several
filesystems mounted from SAN to act as DSSU's. Backups are done using
cron initiated backup scripts, which call the applicable policy. Whe the
policy is completed, another script dumps each DSSU to tape.
Issue: Need to rebuild the filesystems hosting the DSSU's. Since
these tapes are already backed up to tape, what do I need to do to purge
all the images?
What you need to do is for each image on tape, verify that you have 2 copies
and then expire the disk copy. It's a little bit tricky because you'll
be expiring copy 1. If there is no copy 2 (say for some reason the
image failed to destage), you've deleted your only copy. If all goes
well, you'll have an empty DSSU in the end.
You can also do a brute force rm of the disk images but that's a bit hostile
since a restore will attempt to restore from disk rather than tape - you
could expire the disk image if you run into this so that the tape copy
is preferred, but as I said, it's ugly.
.../Ed
Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE
ewilts AT ewilts DOT org
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|