lamw / ghettoVCB

ghettoVCB
MIT License
1.29k stars 365 forks source link

not running cron jobs #312

Open robina80 opened 8 months ago

robina80 commented 8 months ago

hi all,

i know my ghettoVCB works on both my esxi servers as when i run this command manually on both of them

/opt/ghettovcb/bin/ghettoVCB.sh -a -g /opt/ghettovcb/backupconfig -e /opt/ghettovcb/excludevms -d dryrun

this is what is in my backupconfig file

VM_BACKUP_VOLUME=/vmfs/volumes/datastore99/backup DISK_BACKUP_FORMAT=thin VM_BACKUP_ROTATION_COUNT=1 POWER_VM_DOWN_BEFORE_BACKUP=0 SNAPSHOT_TIMEOUT=15 ENABLE_COMPRESSION=0 VM_SNAPSHOT_MEMORY=0 VM_SNAPSHOT_QUIESCE=0 ALLOW_VMS_WITH_SNAPSHOTS_TO_BE_BACKEDUP=0 EMAIL_LOG=1 EMAIL_DEBUG=1 EMAIL_SERVER=10.110.130.68 EMAIL_SERVER_PORT=587 EMAIL_DELAY_INTERVAL=1 EMAIL_TO=to@domain.com EMAIL_FROM=from@domain.com

it runs and i get an email from both servers so all is working

but its not running the cron as i dont get emails from them

as ive got the email debig on (i think its 1) how can i check the logs

thanks, rob

robina80 commented 8 months ago

ok so it has created a log in both servers in /tmp and this is one of them

2024-03-13 01:55:06 -- info: Initiate backup for lon-c-smtp10 2024-03-13 01:55:06 -- info: Creating Snapshot "ghettoVCB-snapshot-2024-03-13" for lon-c-smtp10 Failed to clone object parameters Destination disk format: VMFS thin-provisioned

2024-03-13 01:57:16 -- info: ERROR: error in backing up of "/vmfs/volumes/datastore3/lon-c-smtp10/lon-c-smtp10_1.vmdk" for lon-c-smtp10 Failed to clone object parameters Destination disk format: VMFS thin-provisioned

2024-03-13 01:57:16 -- info: ERROR: error in backing up of "/vmfs/volumes/datastore3/lon-c-smtp10/lon-c-smtp10.vmdk" for lon-c-smtp10 2024-03-13 01:57:18 -- info: Removing snapshot from lon-c-smtp10 ... 2024-03-13 01:57:18 -- info: Backup Duration: 2.20 Minutes 2024-03-13 01:57:18 -- info: ERROR: Unable to backup lon-c-smtp10 due to error in VMDK backup!

2024-03-13 01:57:21 -- info: Unable to create "/vmfs/volumes/datastore99/backup/lon-c-xrdp10"! - Ensure VM_BACKUP_VOLUME was defined correctly

the other server the error im getting in the logs

2024-03-13 01:54:24 -- info: Initiate backup for iris_admin 2024-03-13 01:54:24 -- info: Creating Snapshot "ghettoVCB-snapshot-2024-03-13" for iris_admin Destination disk format: VMFS thin-provisioned Cloning disk '/vmfs/volumes/datastore3/iris_admin/iris_admin.vmdk'... ^MClone: 10% done.Failed to clone disk: Input/output error (327689).

2024-03-13 01:57:44 -- info: ERROR: error in backing up of "/vmfs/volumes/datastore3/iris_admin/iris_admin.vmdk" for iris_admin 2024-03-13 01:57:49 -- info: Removing snapshot from iris_admin ... 2024-03-13 01:57:49 -- info: Backup Duration: 3.42 Minutes 2024-03-13 01:57:49 -- info: ERROR: Unable to backup iris_admin due to error in VMDK backup!

2024-03-13 01:57:51 -- info: Unable to create "/vmfs/volumes/datastore99/backup/lon-corp-dc02"! - Ensure VM_BACKUP_VOLUMEwas defined correctly`

the backup datastore is good tho as when i do a ls i can see the dir and some VMS it backs up is succesfull

robina80 commented 8 months ago

i changed on each server the "VM_BACKUP_VOLUME" path so both servers have there own folder to save the backups to so

esxi01 - VM_BACKUP_VOLUME=/vmfs/volumes/datastore99/backup/esx01 esxi02 - VM_BACKUP_VOLUME=/vmfs/volumes/datastore99/backup/esx02

and now all of a sudden my backups are working again as i got an email from both servers saying all vms backed up ok

robina80 commented 8 months ago

forgot to mark as closed

robina80 commented 7 months ago

im going to re open this as im still getting the same error, even tho ive changed the "VM_BACKUP_VOLUME" its saving to the new location and the error went away but now its back with the same error ie it cant save to that folder

even tho i can ls the dir ie so the dir is there and it can locate it?

any help please? @lamw

dpanic commented 7 months ago

I had similar issue.

But my cron worked, and sudenly last night didnt' work.

I am uploading backups to Synology NAS.

I will investigate more, if this issue perrsist. However I would love to figre out what happened.

robina80 commented 7 months ago

ok ive got it working again, ive left it couple of days/week as to see if it was producing the same error but so far ive been getting emails from both servers saying backup successful

in the end i changed my cron on both servers so they run on alternative days from eachother as i think my NFS NAS couldnt cope with all the traffic same time from both esx01 and esx02

dpanic commented 7 months ago

Mine is working as well.

I logged in to the Synology NAS and switched off hard disk hibernation. I think that was the problem.

robina80 commented 7 months ago

Mine is working as well.

I logged in to the Synology NAS and switched off hard disk hibernation. I think that was the problem.

as you mentioned this i checked mine and same as my TNAS the hard drives were set to sleep after 30 minutes of inactivity, set it to never now