server we are on is a DS710i which was launched back in late 2011 it seems - from what I can see it should have come with dual 1tb drives but for some reason we seem to just have 1.
so far the backup seems to have completed. a 7GB tar took about 1 day to complete. luckily they were taking regular backups of the db so not much to replay after the last backup on that gets restored.
@johnhooks that's nothing - it was twice that yesterday
they are trying to run the backup with all the services still running - it's a billing/invoicing server and statements are going out and being processed today. I've said we should turn off services to run the backup and migration
yes - that is happening now. the problem at the moment is the speed of the back up because of the errors we're getting on the drive. the backup is moving along at a snail pace apparently. I can't even type in a command to terminal without a huge lag.
% df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00 913G 144G 724G 17% /
udev 3.9G 4.0K 3.9G 1% /dev
tmpfs 786M 384K 786M 1% /run
none 5.0M 0 5.0M 0% /run/lock
none 3.9G 0 3.9G 0% /run/shm
/dev/sda1 236M 56M 168M 25% /boot
# lvdisplay
--- Logical volume ---
LV Name /dev/VolGroup00/LogVol00
VG Name VolGroup00
LV UUID 1cohna-I14w-vCBO-yHV8-qMtP-vN6a-UTFqTG
LV Write Access read/write
LV Status available
# open 1
LV Size 927.46 GiB
Current LE 237429
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 252:0
Let me just preface that this was inherited and steps are being taken now to move to a more reliable system setup. Need to work on resolution rather than what someone should have done before. (backups, monitoring, etc.)
Single drive, dedicated remote host @ Fasthosts, with a failing drive with no backups. Drive is using lvm.
What is the best way to try and salvage the data to move it on another server.?
I will update in a sec with more details on the setup.
I ended up re-installing xenserver and the updates worked this time around.
Why not just a Mango Lassi add a bit of vodka/gin as desired.
@scottalanmiller hmm, something new to learn. reading through this now: http://lwn.net/Articles/476263/
@scottalanmiller
Maybe I didn't explain it correctly or I'm not sure what you mean...
From what I understood in order to resize a volume you need to shutdown the host: http://support.citrix.com/article/CTX120865
Not what I want to do.
On the Rackspace server, I just add each 1tb volume (1tb is max storage you can add at a time) to the host as needed and then add that live into the volume group for the video storage. the application isn't away of any changes and continues to write to that same space. This is all that I did...
fdisk /dev/xvdx
t
8e
w
mkfs -t ext4 -c /dev/xvdx1
pvcreate /dev/xvdx1
vgextend VolGroup00 /dev/xvdx1
lvextend -l +100%FREE /dev/VolGroup00/data
resize2fs /dev/VolGroup00/data
I've built out a decent size NVR server on a 12 disk LFF, DL180 G6 and thinking about how I manage the disk space as it grows. I have a single RAID volume that I've created on the server and allocated 30GB initially for the OS and thinking I add storage in 1TB chunks as needed to the recording volume. The server is going to be used for other VMs so allocating all the space at once doesn't work.
The virtual disks are all using LVM so growing these for either the OS or storage will be done by adding additional logical volumes. I've setup a server in Rackspace like this and attached new block storage volumes to the server as disk space requirements grew. It seems to work well and haven't had any issues in 1yr of running that server doing it this way.
Are there any nuances to configuring the LVMs now anticipating them growing as time goes on? Any other words of advice for managing storage in a situation like this?
We are using Xima Chronicall with our Avaya IP Office system. Looks like it works with ShoreTel but don't think NEC.
@KOOLER said:
We're working with Seagate now to make their 8TB (and 10 and 14 soon) drives usable for ANYTHING but it turns out even log-structured file system eliminating random and small writes does not help much. Still trying to find a solution, no ETA yet.
Are you looking at mostly host managed solutions in this case to get the best performance?
thanks for the tips. i didn't have vm tools installed on some hosts but didn't have a chance to check again today so perhaps tomorrow success after ensuring tools are installed on all hosts. they are all on HP Proliants and just Ubuntu/Win hosts so nothing unusual that I'd expect to not support this I hope.
@Dashrender @Jason @scottalanmiller it's not a very crowded/busy side to our office. only about half the desks you see ever have someone in them and it's finance, bi teams who all work very quietly. it's the visits from the other side of the office we have to contend with and no cubical would prevent someone walking up to you as a distraction.
@coliver said:
@Dashrender said:
@coliver said:
My real question for @larsen161... What is the chair on the other side of the desk for? No one will be able to see you through the monitors!
LOL that is another desk.
That open air thing seems to be all the rage in younger tech companies.
that and everyone wearing headphones so they don't hear the other people around them....Oh... I didn't even notice that. I'd hate to be that user with hot exhaust and fan noise of that switch.
It's the SG 200-26 model - no sound at all, super quiet. My Mac Pro's fan is louder at times. I did have a new 2960X on the desk at one point when configuring it and it got a few comments on it's noise.
@coliver @nadnerB had about 10 mac mini's to configure one day and we had a spare switch lying around and it ended up becoming a permanent fixture of the desk. I'm wishing it's was PoE now - you can see two camera's but the other 8 are scattered around the office
I managed to get a window seat when we expanded into the south wing of our floor.
@Danp yup, that was it. now onto troubleshooting the next set of errors. First one was quite obvious, destination host didn't have enough RAM. The other two though I'm not finding a table of what those feature codes translate to.
vm.migrate(...) [601ms] =!> XapiError: HOST_NOT_ENOUGH...36296192)
vm.migrate(...) [738ms] =!> XapiError: VM_LACKS_FEATUR...cdfd0954)
vm.migrate(...) [639ms] =!> XapiError: VM_LACKS_FEATURE_SU...1cdfd0954)
Am I missing some vital info, it seem to be truncating some details there when I run the following to get those results
sudo systemctl status xo-server.service