That error is generated when the backup trys to create a temporary directory on the backup mountpoint. It sounds like the user you have mounted the mountpoint at doesn't have write permission.

If you want, you can manually test this by SSHing (enable SSH and use the admin user and password) into the JumpBox and running the following command using your SAMBA/CIFS username password:

sudo /sbin/mount.cifs //server/path/ /jumpbox/temp_backup_mount \ 
-o noauto,noperm,rw,user=username,password=password

Then you can test to see if you can write in /jumpbox/temp_backup_mount.

touch /jumpbox/temp_backup_mount/test_file.txt

Or you can look on your Win 2003 Server box for logs, they might provide some insight.

Austin

got that fixed ... win 2003 security policy setting ....

now getting:
Error creating temp dir.

when I try to run a backup

getting this error when trying to connect to a windows server 2003 share when trying to configure backups:

cli_negprot: SMB signing is mandatory and we have disabled it.

Pricing for JumpBox assurance is still being determined though it will most likely be an annual charge.

When you're ready to try an import into a newer appliance let us know through the Contact form. http://www.jumpbox.com/contact I'd suggest waiting until the next release is ready.

Cool! Any pricing details on subscription to the JumpBox Assurance program? Annual or monthly? Cost?

I'll need to engage assistance to forward-port our CRM data. Its not very big (couple MB), so shouldn't be difficult and can probably be done using mysql command line load into the database. Its a .sql file, so very straight forward.

Thanks!

The vTiger 0.5 release is not updateable. The latest release (0.6.11) is intended to be updateable although it isn't well tested at this point and it doesn't have an update key installed. We'll be releasing a new version next week that contains a Beta update key and will update as we release fixes. After a 1.0 release the beta key will be disabled and a subscription to the JumpBox Assurance program will be required to continue receiving updates.

The 0.6.11 release also includes the VMWare tools so it will shutdown cleanly from the VMWare console.

If you have a backup from 0.5 the only way to include that into a newer appliance is for us to do it manually. If you have real data in 0.5 we can probably arrange that.

We'll look at getting a fix for the MSXML error into the next release as well.

Forgot about the :3000 interface for shutdown/restart and update. With the v0.5 beta jumpbox vTiger appliance, will the "update" button update the appliance to full v1.0 when it becomes available?

Currently running the v0.5 beta - will a full version "update" be available when the jumpbox is released as version 1.0?

Stopping the VM instance from the Vmware Console is not a "clean" shutdown (without vmware tools installed), is it? Where is the "shutdown" command in the Web UI?

The v0.5 appliance seems fairly solid, however have encountered one bug (which I found a resolution for on the vTiger forum): "MSXML Object Can Not Be Initialized"

http://forums.vtiger.com/viewtopic.php?p=37234#37234
Parameter adjustments regarding memory allocation for vTiger

With a "backup" .sql file, how do I restore this into the updated beta 0.6.11 appliance?

There will be a JumpBox specific backup/restore facility in a future release that will provide a way to restore into an appliance. The current vTiger backup facility is usable to backup the vTiger data and restore it into a custom installation of vTiger.

For shutdown you can stop it from the VMWare console or you can also log into the JumpBox administration interface and use the shutdown command there.

The appliance will be self updating with no export/import required. We will begin testing that facility in a few weeks.

I have the vTiger jumpbox appliance running, and enabled backups (FTP). These are working, however wondering about the process of performing a restore? The backup files are a .sql file, so my guess is using the mysql client to push data back into the database? Will the "admin" authentication credentials provide sufficient security to do this?

With the availablity of the vTiger 0.6beta, what is the process of exporting and importing the database on the new appliance instance?

Is there a specific shutdown procedure (other than "vmrun stop /vm/vmname" or using the vmware client to shut down the VM)?

When updates become available for 0.5beta (like 0.6beta and vTiger 5.02 or 5.03), will the "update" button update the appliance and the application, or is a safer update process to download the new (updated) appliance and export/import the database data?