Easy way to update to latest VM?

AFAIK that's pretty much what it was designed for! Obviously test your new appliance to make sure all is well before you delete the old one.

sorry, not very familair with those things. 👎

how i get old appliance to upgrade in vsphere? i start 11.1 as iso in my current vm and there is an upgrade option?

Check out the TKLBAM FAQ on pricing.

i missed the title... sorry. is TKLBAM free?

excellent. tks guys!

i get this now. any idea?

> tklbam-backup --simulate
CREATING /TKLBAM 
FULL UNCOMPRESSED FOOTPRINT: 1.06 GB in 21910 files 
########################## 
## FIXCLOCK HOOK FAILED ## 
########################## 

Amazon S3 and Duplicity need a UTC synchronized clock so we invoked the 
following command:: 

ntpdate -u pool.ntp.org 

Unfortunately, something went wrong... 

30 Jan 00:27:19 ntpdate[6471]: no server suitable for synchronization found 
Traceback (most recent call last): 
File "/usr/bin/tklbam-backup", line 266, in <module> 
main() 
File "/usr/bin/tklbam-backup", line 241, in main 
hooks.backup.pre() 
File "/usr/lib/tklbam/hooks.py", line 31, in pre 
self._run("pre") 
File "/usr/lib/tklbam/hooks.py", line 28, in _run 
(fpath, self.name, state, e.exitcode)) 
hooks.HookError: `/etc/tklbam/hooks.d/fixclock backup pre` non-zero exitcode (1) 

It seems from your error message that for some reason TKLBAM is unable to syncronise the appliance clock with UTC. First thing I'd check is network connectivity.

As a first step to troubleshooting this I'd try to ping the default time server (pool.ntp.org):

ping pool.ntp.org

Depending on the result of that you will get an idea of where to look next. If the ping succeeds then I would try manually running the command (ntpdate -u pool.ntp.org) at the CLI and see what error it throws.

If the ping fails then the error will give you a clue. If it complains of a "unknown host" then it's probably flakey nameserver/DNS (or no internet connection at all) try using a reliable one such as Google's (8.8.8.8). If it resolves the name to an IP ok but complains "Destination Host Unreachable" then check for a firewall/proxy or other internet connectivity issues between your appliance and the internet.

The only other thing I can think of is perhaps a firewall or proxy interfering with the connection between your server and the time server.

NTP uses UDP port 123. Check that you haven't got any firewall or proxy blocking you.

i can ping normally but i get same error (no server suitable for synchronization found) when trying to ntpdate -u manually.

i realized that i get the same problem and error when using the system time panel in webmin. i tried to change to other servers (icluding a local one), to avail.

our campus' firewall might block that port. i'll have to check after new year.