discopy and appleshare servers
discopy and appleshare servers
- Subject: discopy and appleshare servers
- From: "Vince Jelenic" <email@hidden>
- Date: Fri, 19 Jan 2001 08:54:25 -0500
I thought it might be a good idea to backup my appleshare ASIP 6.3x
servers nightly.
rather than using retrospect (don't like that for server usage) , wanted
to script a solution.
so.
cobbled together a script which would do the following.
open disk copy,
by getting date info, and server startup volume info, it would create an
image file called
"server January 18".
I am having a problem here, though.
If I try to save a disk over 2 gigs into the image, diskcopy returns an
error, logical block sizes can't be larger than 404300 or somesuch
(ie.e no larger than 2 gigs).
ok. the disk itself is about 4 gigs, but only uses 300 MB or so.
I can get the physical size of the disk, and it return the 300 mb number
ok.
I can create the image file at 350 MB with diskcopy.
but when I try to "save in file x with options" in disk copy, I am
stumped.
disk copy wishes to back up the entire disk, all 4 gigs, thus returning
error.
the workaround I've found so far is
to create an image file of desired size (say 300 MB) with name of "server
January 18"
mount this disk.
run through the folders in the startup disk, copying over all items into
the mounted disk.
then quit disk copy.
this works great on a workstation.........
BUT, with an ashare server, a glitch..... the volume mounted is then
immediatly "shared" by ASIP,
and an error is returned (file in use or somesuch).
disk copy has entry to "save in file.... " but when trying this, it
REPLACES what was currently in the already created
image file with the next entry.
thus.... can't copy the DISK into the image file -- error on size.
and..... can't mount the disk image on asip server to copy allstuff into
it....
the crux of this problem seems to be that disk copy cannot seem to figure
out that the DISK is really only 300 MB large, not 2 gigs. when a disk
is dragged onto disk copy, it does indeed still report the full logical
size of disk , rather than used size.
any way to get around this ? I'm using Disk Copy 6.3.3.
I would love to automate this backup which currently takes operators about
3 hours every week to accomplish.
(make image, copy image to backup server volume off originating server, ).
I would like to have a backup image created once a week (or less) just
sitting waiting on a drive to be copied over to another volume (either
automated, or manual).
------ Vince Jelenic says:
"The only way to really ensure server security is to lock it in a sealed
room with the power off."