Shell backup script – Windows SMB / Linux Server

prepare

  • copy all files in one folder
  • modify backup-start.sh with your path and configs
  • make a btrfs partition
  • create a subvolume for the backup path
  • create a cronjob

start

backup modes

  • smb
  • sshs
  • sshnosymlink
  • sshsudoftp

backup-start.sh

backup-script.sh

services-snapshots.sh

 

Bad RAID controller

IMG_26022014_084034

If you have a UCS chassis where the VMs go offline and you can’t access the VMs with vSphere, you may have to reboot the chassis via the IMC web interface. But, when you reboot it and watch it via the IP KVM console, this is what you don’t want to see:

OK, so get TAC on the phone and have them send you the replacement controller. Hopefully, you have 4 hour response. Here is the link to replace the RAID controller in the UCS chassis:
After replacing the RAID controller, you will want to make sure to copy the drive configuration to the newly replaced controller. This was not documented in the card replacement documentation. Here is the link to do this. Follow the instructions EXACTLY:
Verify the virtual devices show up on the RAID controller during bootup. Things still might go south. The vSphere client may show CUCM and UCXN as missing. This is because the datastores are not there. TAC will need to re-add the datastores for you, possibly via CLI. More than likely, the file system will have errors on the VMs. It may be so bad that the won’t boot, so you will need to mount the Recovery CD, boot to it, then choose the option to fix the file system errors. After that, grab a beer. The servers should come up just fine.
see -> http://iptbuzz.blogspot.de/2011/10/bad-raid-controller-on-ucs-c210-m2.html