ghettoVCBg2 or ghettoVCB?

Similar Questions

• ghettoVCB in ESXi4.  It work?

  Hello

  I'm trying to run a backup script VMs ghettoVCB in ESXi 4.  Somehow, it does not work.  When I check there is not bash in ESXi 4.

  The script runs with the bash?

  If necessary is there a way I can activate or install bash in ESXi 4?

  TIA

  Nadine

  @Superkikim is incorrect (you think ghettoVCBg2), ghettoVCB works on the classic ESX Console of Service or not supported Busybox of ESXi console, license is not relevant here.

  The current version supports (i) ESX 3.5 and 4.0, it will run under the appropriate default shell and from ESXi 4.0, the Busybox console no longer has a symbolic link to/bin/ash-> / bin/bash, but once again the script handles that. Make sure you download the latest version of the script and go through the documentation at: ghettoVCB.sh - alternative free for virtual machine backup of for ESX (i) 3.5, 4.x & 5.x .

  In the future, just after on the VMTN document so I see on the other I can miss my scripts issues.

  =========================================================================

  William Lam

  VMware vExpert 2009

  Scripts for VMware ESX/ESXi and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

  Twitter: @lamw

  repository scripts vGhetto

  Introduction to the vMA (tips/tricks)

  Getting started with vSphere SDK for Perl

  VMware Code Central - Scripts/code samples for developers and administrators

  150 VMware developer

  If you find this information useful, please give points to "correct" or "useful".

• GhettoVCB: /tmp/ghettoVCB.work: file exists

  

  Hello world

  I use ghettoVCB, recently, I got this error when I tried to do a dryrun or a backup.

  "/ tmp/ghettoVCB.work": file exists

  Ash: wrong number

  I looked in all the documentation, but nothing about this problem as possible. Maybe I need to delete some records, I don't know...

  Best regards

  Samuel

  Everything works now...

  I compare two esxi with the same configuration and I noticed that this directory "ghettoVCB.work" do not exist on the other for the same operations esxi...

  I just delete this folder and the issue is fix.

• Free ghettoVCB.sh u3 ESXi 4.1: line 836: syntax error: bad substitution

  I can't ghettoVCB.sh to run on free ESXi v4.1.

  Copied the .sh and .conf files in/ghettoVCB-master.  When I get home. /ghettoVCB.sh I get:

  ghettoVCB.sh: line 836: syntax error: bad substitution

  If I try/bin/ash ghettoVCB.sh I get exactly the same thing.

  The execute bit is set:

  / ghettoVCB-Master # ls-l

  -rw - 1 root root 1140 15:37 README.md Nov 6

  -rwx - x - x 1 root root 17555 6 Nov 15:37 ghettoVCB - restore.sh

  -rw - 1 root root 747 6 Nov 15:43 ghettoVCB.conf

  -rwx - x - x 1 root root 64593 6 Nov 16:23 ghettoVCB.sh

  -rw - r - r - 1 root root 11 Nov 6 15:39 vms_to_backup

  I do not see a log ghettoVCB file in / tmp.

  How can I solve this please?

  In case someone else gets the same problem - I finally worked it out.  ESXi 4.1 update 3 do not have the latest version of ghettoVCB.sh.  I guess the version of bash in the console busybox is old and does not support the syntax of some of the improvements made to the script.

  I managed to get an older version of the MKSbackup script and it works fine.

• GhettoVCB and the Question of the snapshot

  I ' n trying to back up a computer virtual with GhettoVCB and its failure by saying a snapshot is present.  There isn't one in the Snapshot Manager so I created a snapshot and then made a completely remove but it is always a failure.

  I had a quick glance in the data store, and I can see that there is a delta file.  I think its an old file snapshot that is not used, but wanted to check before I deleted the.  It is the directory listed since the data store;

  drwxr-xr-x 1 root root 3780 18 Oct 12:40.

  drwxr-xr-t 1 root root 1960 19 June at 09:03.

  -rw - r - r - 1 root root 7 Sep 2013 chw - vm - 02.cheeswrights.local 73 - 346bdcd4.hlog

  -rw - 1 root root 8589934592 Sep 11 2013 chw - vm - 02.cheeswrights.local - 346bdcd4.vswp

  -rw - r - r - 1 root root 13 18 Oct 12:40 chw - vm - 02.cheeswrights.local - to the .xml

  -rw - 1 root root 6554112 18 Oct 12:41 chw - vm - 02.cheeswrights.local - ctk.vmdk

  -rw - 1 root root 107374182400 Oct 12:52 chw - vm - 02.cheeswrights.local - flat hard 18

  -rw - 1 root root 8684 18 Oct 12:41 chw - vm - 02.cheeswrights.local.nvram

  -rw - 1 root root 620 18 Oct 12:40 chw - vm - 02.cheeswrights.local.vmdk

  -rw - r - r - 1 root root 46 18 Oct 12:40 chw - vm - 02.cheeswrights.local.vmsd

  -rwxr-xr-x 1 root root 4243 18 Oct 12:40 chw - vm - 02.cheeswrights.local.vmx

  -rw - 1 root root 0 Sep 7 2013 chw - vm - 02.cheeswrights.local.vmx.lck

  -rw - r - r - 1 root root 283 17 Oct 09:28 chw - vm - 02.cheeswrights.local.vmxf

  -rwxr-xr-x 1 root root 4250 18 Oct 12:40 chw - vm - 02.cheeswrights.local.vmx ~.

  -rw - 1 root root 252071936 13 February 2014 chw - vm - 02.cheeswrights.local_1 - 000001 - delta.vmdk

  -rw - 1 root root 364 13 February 2014 chw - vm - 02.cheeswrights.local_1 - 000001.vmdk

  -rw - 1 root root 4915712 18 Oct 12:41 chw - vm - 02.cheeswrights.local_1 - ctk.vmdk

  -rw - 1 root root 322122547200 Oct 12:52 chw - vm - 02.cheeswrights.local_1 - flat hard 18

  -rw - 1 root root 624 18 Oct 12:40 chw - vm - 02.cheeswrights.local_1.vmdk

  -rw - r - r - 1 root root 1366075 28 June 2011 vmware - 4.log

  -rw - r - r - 1 root root 1294553 July 5, 2011 vmware - 5.log

  -rw - r - r - 1 root root 1285971 Aug 23, 2011 vmware - 6.log

  -rw - r - r - 1 root root 1295743 26 April 2013 vmware - 7.log

  -rw - r - r - 1 root root 1318787 July 31, 2013 vmware - 8.log

  -rw - r - r - 1 root root 240174 Sep 7 2013 vmware - 9.log

  -rw - r - r - 1 root root 44435410 18 Oct 12:42 vmware.log

  And it's the .vmx for the virtual machine disks:-

  scsi0:0. FileName = "chw - vm - 02.cheeswrights.local.vmdk"

  scsi0:1.filename = "chw - vm - 02.cheeswrights.local_1.vmdk"

  scsi0:2.filename = ' / vmfs/volumes/522857d3-a99e32f2-6ca5-3c4a92f58408/chw-vm-02.cheeswrights.local/chw-vm-02.cheeswrights.local.vmdk '.

  Given the two files associated with the snapshot are dated in February, and the .vmx isn't SEO and I sure to delete following text: -.

  -rw - 1 root root 252071936 13 February 2014 chw - vm - 02.cheeswrights.local_1 - 000001 - delta.vmdk

  -rw - 1 root root 364 13 February 2014 chw - vm - 02.cheeswrights.local_1 - 000001.vmdk

  Thank you!

  I tend to say yes, it seems that, in this case, they are obsolete files. However, if you can afford a short downtime, I recommend you stop the virtual machine, create a subdirectory, move the files to capture two instant in the new subdirectory and then put on the VM again. If everything works as expected, you can then delete the files.

  André

• Disaster recovery with Ghettovcb on EXSI

  Hello team,

  I started working with EXSI and the backup and restore of virtual machine through ghettoVCB successfully completed.

  But I got over a spot...

  situation is something like:

  1. what got esxi crashed then how to quickly recover the new esxi?

  2 and if the new exsi is created then the new deployment of the backup of virtual machine on exsi?

  The team please provide guidelines about this situation...

  
  

  
  

  
  

  
  

  
  

  
  

  
  

  Thank you

  Hi sumitanand,

  It is technically possible to clone partitions starting ESXi? Maybe you can, but you should never do that.

  As Phatsta mentioned already install a new host is done in a very short period of time (depending on your hardware you can minutes)

  In addition, you can indeed do a boot from the disk backup (or just install on USB and do that 2 times on different USB sticks) however...

  What happens if your host is completely dead? You get a new server with different hardware... and specific drivers from different vendors? Your cloned image does not work, then, as the excellent.

  In addition, using a cloned image of ESXi is completely supported.

  If you want to save configuration ESXi host using something like this:

  PowerCLI: ESXi 5.0 / 5.1 ESXi backup host & restore the usefulness of GUI - VI - Toolkit

  and then apply to your freshly installed ESXi host.

  --

  Wil

• GhettoVCB restore problem

  Hi all!

  Don't know where I can my problem public.

  I have the following problem.

  I use VMWARE ESXI 1746974 and running fine GhettoVCB 5.5.0. Script does compressed backups.

  When I try to perform recovery tests, I found problems.

  If I understand there is no possibility to restore directly from .gz. So to restore, first I extracted archives .gz with the command "tar -zxvf". Finally, after extracting I got only 2 files. test - flat hard and test.vmx, but not test.vmdk, so cannot use ghettovcb - restore.sh and cannot manually add it to the stock.

  Strange, but when I copy on the windows machine and extract it with 7-zip twice (first after extracting I have 1 file with the same name as the archive and no extention, the second time I have 3 files and test.vmdk - girl and have fully working machine).

  I know that I can copy work VM test.vmdk and just put it in the extracted folder and I have to work VM, is not good solution but my backups will be not fully functional without it.

  There may be another linux instead of tar command -zxvf, or maybe there is some other stuff that I don't know.

  Please, help me to finish my backup solution.

  -rw - root/root 54975581388800 2014-07-02 23:15:09 1CSRV-2014-07-02_23-15-01/1CSRV-flat.vmdk

  Something seems wrong here. Look at the file size indicated by the file 1CSRV - flat hard: 54975581388800 bytes are 51200 GiB. I guess 7zip shows GiB 50 in the index of archives and the original vmdk was 50GiB as well?

  It is possible that it is a bug on the binary tar of busybox ESXi. Maybe you can test with smaller tarballs and others too big, I can at least "détarer" small files without problem on my hosts.

• Send Mail ghettoVCB on ESX 3.5

  Hello

  I configured ghettoVCB.sh pour a backup, but when the backup is finished, so I read in another forum that ESX 3.5 doesn't have the option of sending mail as on later versions, ESX 3.5 does not send mail as it does the ESXi 5.0 for example!

  I would like to know if it's true is it you please, in case it's not true, comment can do pay ESX 3.5 sending the mails, I well opened port 25 SMTP as I did on an ESXi 5.0, when I checked the SMTP port opening everything is OK.

  Thank you in advance.

  Hello

  I found the solution, it GEN simply download the add-on mail missing on ESX 3.5 version, the module is NETCAT, install in ESX, open the firewall, the SMTP in port 25 and declare your ESX Server IP in the relay Exchange permissions. If you need more details don't hesitate not! :-)

  Thank you

• ghettoVCB-restoration on ESXI 5.01

  Dear the genius William Lam.

  Merry Christmas.

  I tried to restore a backup of virtual machine with 'ghettoVCB-restore '.

  the back was created using the script "ghettoVCB.sh".

  I had upgraded 87 of the script line:

  "If [" ${ESX_VERSION} "=="5.0.0"]; then ".

  TO

  "If [[" ${ESX_VERSION} "=="5.0.0"]] |" [["${ESX_VERSION}" == "5.1.0"]]; then ".

  After that the script 'ghettoVCB - restore' shows the following error:

  "ERROR: this script must be run by \"root\ '! "

  If I had removed the part of the rest of the script:

  [

  If [!] '' whoami' ' is 'root']; then
  recorder "ERROR: this script must be run by \"root\ '! "
  echo "ERROR: this script must be run by \"root\ '! "
  Output 1
  FI

  ]

  the bachup restore operation was completed successfully.

  But there was some errorrs, I think it is releated to the following:

  the value of $VM_DISPLAY_NAME!

  the log file has been corrpted

  the date value (START_TIME and END_TIME)

  Could you please check out the script and solve problems?

  Thank you

  I've updated ghettoVCB - restore.sh to solve the two problems you mentioned to support 5.1 ESXi host as well as the use of a different mechenism for checking for the root user. I was able to save/restore a virtual machine, then that give a try and I hope that you will be able to get the papers this time where you tap on certain issues.

  You can download the updated version, which is still being worked on in a branch of test https://github.com/lamw/ghettoVCB/tree/merge-test and simply click on the "ZIP" up that will give you a download of all files and simply replace the script ghettoVCB - restore.sh

  Happy holidays

• ghettoVCBg2 does not work for crontab on vMA 5.1

  Greetings,

  Recently updated our environment 4.1 to 5.1 all autour, ESXi and Vcenter vMA.  Copied from all the ghettoVCBg2.pl and all my backup script and fixed control version and other issues so that he could work on 5.1.  Now it works well when it is run from the console, but will not crontab run.  No error is reported, the cron log shows just that she started the script.  If I redirect the output of STDS in the crontab entry to a file, the file is created, but empty.

  Here's the sanitized script that is called from the crontab to start work.

  #! / bin/bash
  #
  LD_LIBRARY_PATH = / opt/vmware/vma/lib64: / opt/vmware/vma/lib
  export LD_LIBRARY_PATH
  PATH = / usr/kerberos/bin: / usr/local/bin: / bin: / usr/bin: / usr/java/jre-vmware/bin: / sbin: / usr/sbin: / home/vi-admin/bin
  export PATH
  CD/home/vi-admin/ghettoVCBg2
  #
  /Home/VI-Admin/ghettoVCBg2/ghettoVCBg2.pl--vmlist output /home/vi-admin/ghettoVCBg2/backup_lists/server--/home/vi-admin/ghettoVCBg2/backup_logs/ghettoVCBg2-server.log
  #

  GhettoVCBg2 log contains the following (for each host server) error message:

  12/10/2012 17:14:32 - debug: hand: Login by vi-fastpass at: host.domain.local
  12/10/2012 17:14:40 - warn: cannot connect to: host.domain.local - perhaps in offline or inaccessible - jump

  This worked well minus 4.1, works from the command line, won't work from cron.  Anyone has any ideas, what is the problem?

  Thank you

  Joe

  I had the same problem in 5.1.

  Add the following code to your wrapper script/head of crontab

  PERL_LWP_SSL_VERIFY_HOSTNAME = 0

• Missing /ghettoVCB folder

  Has ghettoVCB installation and it works fine manually. I added the Task tab yesterday to run at 12:30 a.m., I find a ghettoVCB.log file that has 0 bytes, and the file /gettoVCB file is missing. What's happening on two of my VM host servers, anyone has an idea what is the cause?

  If you add custom in ESXi filesystem files/folders, they are not automatically stored without additional tasks. You put the scripts in a data store to ensure that they persist through reboots of the system.

  These two items are useful if you want to persist in saying /ghettoVCB

  http://www.virtuallyghetto.com/2011/08/how-to-persist-configuration-changes-in.html

  http://www.virtuallyghetto.com/2011/08/how-to-persist-configuration-changes-in_09.html

• VMware vSphere Hypervisor (ESXi 5) con ghettoVCB via nfs

  Hello to all,

  Ho da poco started due Server ESXi 5 free nel quale gireranno some virtual machine. Soluzione per I just backup ho scelto con ghettoVCB a montage non oocita di una risorsa che arrived da AIX nfs server.

  He problema che sorto sono e I backup di tempi. In prima battuta I wanted does it save in terms off line (poweroff prima della clonazione) my unfortunately no ho Così tanto tempo disponibile per lasciare spente vm. Ho quindi deciso di passare alla terms snapshot Reed is questo mi obbliga ad usare the ghettoVCB - restore.sh by disco script of it ricreare (corretto vero?).

  I have tempi che ottengo sono i seguenti:

  2012-03-06 08:14:37 - info: CONFIG - VERSION = 2011_11_19_1

  2012-03-06 08:14:37 - info: CONFIG - GHETTOVCB_PID = 370838
  2012-03-06 08:14:37 - info: CONFIG - VM_BACKUP_VOLUME = / vmfs/volumes/backup/ESX01
  2012-03-06 08:14:37 - info: CONFIG - ENABLE_NON_PERSISTENT_NFS = 1
  2012-03-06 08:14:37 - info: CONFIG - UNMOUNT_NFS = 1
  2012-03-06 08:14:37 - info: CONFIG - NFS_SERVER = 10.10.10.10
  2012-03-06 08:14:37 - info: CONFIG - NFS_MOUNT = /img_vmware
  2012-03-06 08:14:37 - info: CONFIG - VM_BACKUP_ROTATION_COUNT = 1
  2012-03-06 08:14:37 - info: CONFIG - VM_BACKUP_DIR_NAMING_CONVENTION = 2012-03-06_08-14-36
  2012-03-06 08:14:37 - info: CONFIG - DISK_BACKUP_FORMAT = thin
  2012-03-06 08:14:37 - info: CONFIG - POWER_VM_DOWN_BEFORE_BACKUP = 0
  2012-03-06 08:14:37 - info: CONFIG - ENABLE_HARD_POWER_OFF = 0
  2012-03-06 08:14:37 - info: CONFIG - ITER_TO_WAIT_SHUTDOWN = 3
  2012-03-06 08:14:37 - info: CONFIG - POWER_DOWN_TIMEOUT = 5
  2012-03-06 08:14:37 - info: CONFIG - SNAPSHOT_TIMEOUT = 15
  2012-03-06 08:14:37 - info: CONFIG - LOG_LEVEL = info
  2012-03-06 08:14:37 - info: CONFIG - BACKUP_LOG_OUTPUT = /opt/ghettoVCB/esx01bk.log
  2012-03-06 08:14:37 - info: CONFIG - VM_SNAPSHOT_MEMORY = 0
  2012-03-06 08:14:37 - info: CONFIG - VM_SNAPSHOT_QUIESCE = 0
  2012-03-06 08:14:37 - info: CONFIG - VMDK_FILES_TO_BACKUP = all
  2012-03-06 08:14:37 - info: CONFIG - EMAIL_LOG = 0
  2012-03-06 08:14:37 - info:
  2012-03-06 08:14:40 - info: start the backup for SRVPROVA
  2012-03-06 08:14:40 - info: creation of snapshot "ghettoVCB-snapshot-2012-03-06" for SRVPROVA
  Destination disk format: thin provisioned VMFS
  Cloning disk ' / vmfs/volumes/datastore1/SRVPROVA / SRVPROVA hard '...
  Clone: 96% in fact.
  2012-03-06 09:39:41 - info: Instant withdrawal of SRVPROVA...
  2012-03-06 09:39:41 - info: backup duration: Minutes 85,02
  2012-03-06 09:39:41 - info: backup to SRVPROVA!

  Ho anche tried a por knew una cartella del local datastore my went fine, tra clonazione e meeting via sftp not e che miglioro di tanto.

  Come da newspaper sia it vmdk della machine virtual applications (screenshot clonazione o) of the di quello che sono in formato thin-provision! It could essere anche questo un problema?

  Some dritta avete da darmi?

  Grazie 1000

  Absent, gli 85 minuti sono tempo it cui fa tutto Ghetto it backs up, no instant sola.

  Vedi capture instant nell 'activity di vCenter o dell' ESXi, secondo e some lasted.

  Luca.

• Email and GhettoVCB

  Hello world

  Is it possible to put more than one messaging feature in ghettoVCB.conf when the backup is complete?

  [email protected] ; [email protected] does not work.

  Thank you!

  Yes it is possible. Please refer to the documentation ghettoVCB

• Problems using ghettoVCB.sh

  Hello and thx in advance

  hope someone can help with my little problem, iam running an esxi4 with wm Server 2 which works perfectly. I have in the two last days studying the options for the backup and came across the ghettoVCB.sh script that I have used with some success for a few days. But my NAS/NFS server apparently could not take the load when deleting old backup jobs, that's why I created a new server nfs (opensuse)

  with xfs as file format. mounted nfs on the esxi and everything went well. but when I run the backup operation, it says the following:

  2011-09-23 19:33:13 - info: # final status: ERROR: all virtual machines failed! ######

  2011-09-23 19:33:13 - info: = ghettoVCB JOURNAL END ==

  ==============================

  Command ' ghettoVCB/ghettoVCB.sh f ghettoVCB/backup_secdc.
  has failed with the return code 6 and error message
  {(vim.fault.DuplicateName)
  dynamicType = < unset >
  faultCause = (vmodl. NULL in MethodFault),
  name = "backup2."
  object = "vim. Datastore:192.168.0.155:/ESXi',.
  MSG = ' the name 'backup2' already exists.',
  }.
  I tried to rename in the script but I keep telling myself the same work exists, the other day, a reboot helped, but since it's a server running, I can't restart every time, if someone could give me some advice, I would appreciate it really :-) maybe I need to disassemble something iam not sure!
  

  
  

  I've seen it from time to time, where the host ESX (i) implements cache server NFS + name of the volume and if you umount and back using a different volume name, he thinks that there are still. Do you have mount/unmount using the vSphere Client or the command line? I usually saw this glitch by using command line tools, especially with vimsh (vim - cmd)?

• help with the snapshot files orphans and ghettovcb on esxi3.5

  I'm trying to back up a single vm on my box esxi3.5 but ghettovcb guard complain that there is already a snashop

  
  

  None of them appear in the snashot Manager.

  I tried creating and deleting a snapshop using snapshot Manager, but these files persist and prevent the backup of this virtual ghettovcb machine.

  any help out there?

  should I remove?

  I'm under esxi3.5

  / vmfs/volumes/4af43c5b-3edb7050-7ec1-000e7feef085/SiteServer # ls-l
  -rw - 1 root root 16820736 29 August 08:13 siteserver-000001 - delta.vmdk
  -rw - 1 root root 229 29 August at 08:05 siteserver - 000001.vmdk
  -rw - 1 root root 16820736 29 August at 08:17 siteserver-000002 - delta.vmdk
  -rw - 1 root root 236 29 August 08:13 siteserver - 000002.vmdk
  -rw - 1 root root 16820736 29 August at 08:17 siteserver-000003 - delta.vmdk
  -rw - 1 root root 236 29 August at 08:17 siteserver - 000003.vmdk
  -rw - 1 root root 16820736 29 August at 08:20 siteserver-000004 - delta.vmdk
  -rw - 1 root root 262 29 August at 08:19 siteserver - 000004.vmdk
  -rw - 1 root root 419473920 29 August at 09:03 siteserver-000005 - delta.vmdk
  -rw - 1 root root 236 29 August at 08:59 siteserver - 000005.vmdk
  -rw - 1 root root 83929600 29 August at 09:24 siteserver-000006 - delta.vmdk
  -rw - 1 root root 262 29 August at 09:06 siteserver - 000006.vmdk
  -rw - 1 root root 16820736 29 August at 09:27 siteserver-000007 - delta.vmdk
  -rw - 1 root root 236 29 August at 09:24 siteserver - 000007.vmdk
  -rw - 1 root root 18915 29 August at 09:24 siteserver - Snapshot672.vmsn
  -rw - 1 root root 402653184 29 August at 08:59 siteserver - f7f25df0.vswp
  -rw - 1 root root 21484431360 29 August at 08:05 siteserver - flat hard
  -rw - 1 root root 8704 29 August at 08:59 siteserver.nvram
  -rw - 1 root root 403 29 August to 01:23 siteserver.vmdk
  -rw - 1 root root 847 29 August at 09:24 siteserver.vmsd
  -rwxr-xr-x 1 root root 1894-29 August at 09:24 siteserver.vmx
  -rw - 1 root root 265 June 3, 2010 siteserver.vmxf
  -rw - r - r - 1 root root 136146 29 August at 08:47 vmware - 0.log
  -rw - r - r - 1 root root 22071 Aug 4 12:54 vmware - 1.log
  -rw - r - r - 1 root root 17245 25 July 00:54 vmware - 2.log
  -rw - r - r - 1 root root 16997 25 July 00:49 vmware - 3.log
  -rw - r - r - 1 root root 0 25 July 00:45 vmware - 4.log

  
  -rw - r - r - 1 root root 16712 25 July 00:42 vmware - 5.log
  -rw - r - r - 1 root root 58064 29 August at 09:25 vmware.log

  Yes. The reason why you need to take another cliché is only in order to activate the clear all"" button. Because we don't need the memory, you can take the snapshot without it.

  André