| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 8721.1 | | XIRTLU::schott | Eric R. Schott USG Product Management | Wed Feb 05 1997 12:34 | 9 |
| Use the database backup program?
Use LSM to make a mirror, and split the mirror?
I thought dd does do error checks, but not comparison...
Write your own program?
|
| 8721.2 | | IOSG::MARSHALL | | Wed Feb 05 1997 13:12 | 7 |
| Call me hopelessly na�ve, but:
cp /dev/disk1 /dev/disk2
cmp /dev/disk1 /dev/disk2
?
Scott
|
| 8721.3 | dd then cmp? | QUARRY::reeves | Jon Reeves, UNIX compiler group | Wed Feb 05 1997 13:14 | 5 |
| Assuming the database is quiet at the time of the copy, you can use cmp after
the dd to confirm the copy is identical.
If the database isn't quiet, then you'll definitely need a vendor-specific
copy program.
|
| 8721.4 | | NABETH::alan | Dr. File System's Home for Wayward Inodes. | Wed Feb 05 1997 17:27 | 5 |
| dd(1) will probably be a better choice than cp(1) for making
the copy, because dd(1) will use the transfer size of your
choice. Since raw disks will treat a long read (beyond the
end of a device) as an error, getting the right transfer
size could be important.
|
| 8721.5 | dd the LSM raw volume?? | DYOSW5::WILDER | Does virtual reality get swapped? | Sun Feb 09 1997 17:00 | 9 |
| Okay, the general consensus seems to be dd. Now, the 60GD database is
really 18 4GB spindles with 46 LSM stripped volumes. Now, if I use dd,
do I pass dd the LSM raw volume name (/dev/rvol/....)? Also, since
these are raw volumes, will the default dd blocking factor be okay?
Thanks,
/jim
|