New Camera Server

CamServer VNC Screenshot.

This is the new camera server that was just put into service today.  Compaq Ultra Small Form Factor DC-7700, running at 3.40GHz with 3GB of RAM and a 160GB Sata Hdd.  It is backed up using Ghost 15.

I see no real need to attach a  display to this box, as I can remote into it and do anything that I need to.

Only things left to do, are to move it to the other servers (at the moment, it’s not where it’s going to end up), and get the other cameras up and running.  😀

See, give a computer geek time off, and he feels the ‘need’ to improve the network infrastructure, heh.  Let’s see: yesterday, I upgraded the CRAB server’s storage drive, today I set up the camera server…..  Thinking about possibly upgrading the server’s Fedora OS sometime soon.  😉

Server upgrade and cloning has begun!

Server

This morning, I removed the backup drive, installed the new drive in the hot swap bay, and started prepping the drive at about 0900 Hrs.  Instead of using fdisk to partition the disk, I used another tool that is a bit easier, more flexible, and should be included in most every modern Linux distributions:  gparted.

So, as root user, I did the following:

# parted /dev/sdc mkpart primary 1m 100%
Information: You may need to update /etc/fstab.

# parted /dev/sdc “unit b print”
Model: ATA ST2000DM001-1CH1 (scsi)
Disk /dev/sdc: 2000398934016B
Sector size (logical/physical): 512B/4096B
Partition Table: msdos

Number  Start             End                 Size                 Type     File system  Flags
1      1048576B  2000398843903B  2000397795328B   primary

Notice that the start is at the 1 Meg spot, and not at 63, the way fdisk defaults.  This ‘aligns’ the partition structure and should result in higher performance.  Now, it was time to create the filesystem.  Here is the output:

# mkfs.ext4 /dev/sdc1
mke2fs 1.41.10 (10-Feb-2009)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=1 blocks, Stripe width=0 blocks
122101760 inodes, 488378368 blocks
24418918 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
14905 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848

Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 35 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.

By now, it was 0915 Hrs, and it was time to mount the new drive and start ‘cloning’ as before mentioned using ‘cp -rp’.

It’s now about 1015 Hrs, and the cp process has run an hour or so, and I see that it’s clipping right along at about a rate of 225GB/hour.  😉

# df -h

/dev/sdb1             917G  764G  107G  88% /mnt/storage
/dev/sdc1             1.8T  224G  1.5T  13% /mnt/new

At this rate, I don’t expect it to take more than a couple more hours.  Then, I will have to do the ‘disk swap dance’.  😉

Server hard drive upgrade due to start tomorrow morning.

2TB WD hdd

 

Starting tomorrow morning, 30 Aug 2014, I will be starting the storage drive upgrade to 2TB.  I will be suspending all backup scripts during  this upgrade, which I will be completed within the week, barring unforseen complications.  Usage after the upgrade will be  rather transparent.  This will also allow for more storage space and some ‘relocation’ of things from / and /home utilizing some symbolic links.  Server usage for during  the upgrade, should continue as normal, except for a very short period right at the end when the drives are swapped in the bays.  I would not expect noticeable delays for ftp and web requests during the cloning process.  SSH use might be a little slower than usual, though.  I will try to keep everyone posted about the status of the upgrade operation in comments to this post.  Thanks to everybody for their patience during this necessary

Cloning directories and files.

Well, now that I’ve gone over preparing the new 2TB /dev/sdc1, I will go over cloning the contents of the 1TB /dev/sdb1 to /dev/sdc1.  It is easy, since /dev/sdb1 (/mnt/storage/) has just one large partition.  So, I wish to copy those directories and files over to /dev/sdc1 (/mnt/disk1), while preserving ownership, permissions, and filestamps.

First you MUST become root user.

$ cp -rp /mnt/storage/* /mnt/disk1/

It means: copy everything recursively, while preserving file attributes from /mnt/storage/ to /mnt/disk1/.  😉

Since the 1TB drive is fairly full, this will take some time to complete, but the nice part is that the server’s operation isn’t interrupted.  After the task completes, I shall unmount both drives.  Then, remove the 1TB drive, move the 2TB drive from its present bay to the (now) empty  bay, and reinstall the backup drive into its original bay.  Remount the drives, and everything is back in order.  Since the stream is ‘using’ the 1TB drive, I’ll have to temporarily stop it, and restart it when the swap is complete, as well as send a broadcast message to any users that are on the system using ftp or shell processes.

$ wall The /mnt/storage/ drive will be unavailable in five minutes.

This will send the message listed after ‘wall’ to all terminals on the system.

If you have users that ignore the broadcast, you will have to kick them out, but I will cover that at a later date, if I remember.