Datasheet
Acano X Series Server and Virtualized Deployments
Acano Solution R1.6: Support FAQs 76-1022-08-K
Page 14
This script logs into the Acano server at 192.168.10.21 using a login account called
“configbackup”. It then issues the backup snapshot command to create a backup called
ServerBackup. It then logs out of SSH and logs in again with SFTP using the same username,
and copies the ServerBackup.bak file storing it locally at the path /home/acano/configbackups
with the name ServerBackup_year-month-day.bak (e.g. ServerBackup_2014-7-10.bak).
Edit the script as needed for the Acano server IP address, login details and folder path to the
local server (as well as backup names, if ServerBackup is not ideal).
#!/bin/bash
ssh configbackup@192.168.10.21 << !
backup snapshot ServerBackup
!
sleep 5
sftp configbackup@192.168.10.21 << !
get ServerBackup.bak /home/acano/ServerBackup_$(date +%Y-%m-%d).bak
bye
!
Example cron job
When added using crontab –e this cron job will run the script at
/home/acano/ServerBackup.sh at 1:00 AM local time as set on the Linux PC.
0 1 * * * /home/acano/ServerBackup.sh
Can I use the same certificate on two Acano services?
While it is possible to use the same certificates on two services, it is not recommended.
Certificates have a CN field which is for the Common Name: this should match the service’s
FQDN and should be the name you use to access it. If this is not the case, most services will
complain and display certificate warnings.
For internal services such as the Web Admin Interface, this is not really an issue, and the errors
can be dismissed. However, for external services such as WebRTC, this normally causes people
concern because they do not know whether they should trust the website or not.
Therefore we suggest using a unique certificate for every service. However, see the next FAQ.
Can I use wildcard certificates?
Yes, except for Lync which rejects them when presented – see the next FAQ.
Wildcard certificates cost more but can be used on multiple servers. In these wildcard
certificates, you can define the CN field to be *. example.com for example and then any server
that is named something. example.com will be matched as correct for this CN. This allows you to
put the certificate on emailserver. example.com, webserver. example.com, ftpserver.
example.com, etc. and use just this one certificate.
However, there are some limitations; in the example above anything named beyond that scheme
will not work, such as acano.video. example.com.