I hear what you are all saying, but you can't backup what was there yesterday, and the vast majority of the time when a failure occurs it will be faster to just rebuild as restoring from the backup would start with a rebuild anyway. We're talking a VMware hypervisor install.... not anything like building KVM out on a Linux install. Also with the restore process for VMware, I would have had to place this host in maintenance mode. Since this client does not have the resources for a full N+1 setup, some of his guests would have experienced an outage. Instead of having downtime, I simply re-created the accounts. Zero business interruption. Mike K. On Thu, Jun 20, 2013 at 5:11 PM, Chuck <cstickelman@xxxxxxxxxx> wrote: > I agree with Mike Bell, the host should be backed-up as well as the > guests. > > > On Thu, 2013-06-20 at 14:50 -0400, Mike wrote: > > On 06/20/2013 01:52 PM, M. Knisely wrote: > > > This is a VMware host... there's no backup... I have backups of the > > > guests, but not the host. > > > > > > UID:GID 99 is the default for this user on VMware. In VMware the > > > UID:GID of 65534 is for "nfsnobody"... another account I have to > recreate. > > > > > > Mike K. > > > > > > > Hmmm, to my way of thinking the host is more important than the guests. > > Having at least /etc/ backed up would alleviate many headaches. > > > > Mike > > > > To unsubscribe send to ncolug-request@xxxxxxxxxxxxx with 'unsubscribe' > in the Subject field. > > > > > To unsubscribe send to ncolug-request@xxxxxxxxxxxxx with 'unsubscribe' in > the Subject field. > >