OMRF-ISG Archives

OMRF's Information Support Group

omrf-isg@SPEEDY.OUHSC.EDU

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Mime-Version:
1.0
Sender:
OMRF's Information Support Group <[log in to unmask]>
Subject:
From:
Alan Shields <[log in to unmask]>
Date:
Wed, 7 Jul 2004 15:04:07 -0500
In-Reply-To:
Content-Type:
text/plain; charset=us-ascii
Reply-To:
OMRF's Information Support Group <[log in to unmask]>
Parts/Attachments:
text/plain (20 lines)
On Wed, Jul 07, 2004 at 11:28:10AM -0500, Jerrod Howard wrote:
> The whole reason for this is we got a new tape backup system that will do
> 600gig, which will cover our whole imaging server. Right now we have 4
> partitions of 60 gig so we can fit each array on one tape for full backups.
> Now I can get them all in one tape, but on two of the arrays, I need to
> expand them since they are filling up so fast, and a few others I need to
> shrink. Before I start tampering with the array though, I'm going to do full
> backups on tape as well as copy over to a new server, then blowout and
> rebuild it into one array (for both my sanity and for administration
> purposes on my end). I have a gigabit switch in the office that I'll just
> drop between them and get it rolling on saturday and come up on Sunday and
> get the array done. I'll have it all on tape as well as doing an integrity
> check on the data moved. Then move it all back and be done with it (I hope).

Great. Definitely do the integrity check. I don't know why, but Windows
file transfer has more than once screwed up files for me. Odd, as TCP is
a reliable protocol.

Alan

ATOM RSS1 RSS2