So today i was looking into a more space effective way to look after the Groupwise backups and came up with the following solution, i had seen DBCopy and want impressed…why do i need to copy the data every night to have a backup when i have the data in snapshot already?
I’ve only been administering Groupwise for about 2 weeks with no experience before so go easy on me 😉
As we use Nimble storage the easiest way to i thought to get the data back was to use our current nimble snapshots, clone a LUN, add it to vmware, locate the disk of the machine and add it back to the live machine, then point Groupwise to the cloned disk for its backup source.
In my head sounded like a 5 minute task…and it would of been but for the SUSE Linux machine not automatically adding the disk.
So my process for this was (quick notes il add more pictures and process later) –
Connect the second disk in vmware then hop on to the SUSE Linux box with SSH.
Run the following commands
echo "- - -" > /sys/class/scsi_host/host0/scan
then
Fdisk -l
find your disk then mount it
mount -t ext3 /dev/sdb2 /mnt/hd2
then just add the location as a backup source in Groupwise on the admin console and away you go.
just to add some more to this…if you add a disk that isnt already formatted as in a new new disk to Suse Linux you would need to format it,
to partition the disk
fdisk /dev/sdc
to format the partition.
mkfs.ext3 /dev/sdc1