BeatificaBytes

• Configure Synology DNS + DD-WRT to access my blog from both Intranet and Internet

  1 January 2014

  My blog is hosted at home on my NAS and accessed using the fully qualified domain name www.beatificabytes.be. Configuring adequately the Synology’s DNS service and my Buffalo router running DD-WRT, I can access it both from Internet and my Intranet using that url.

  Click to Read MoreClick to Close

  To make my blog accessible from Internet, I have configured the “DDNS” service of my Synology.  Thanks to this “DDNS” Service, “Synology” links a hostname like “myNas.Disktation.me” to the dynamic IP I get from my Internet Provider – currently “Belgacom”. Next, I have configured a CNAME “www.beatificabytes.be” at my Domain Provider “Servage.net” as an alias of this hostname “myNas.Disktation.me”.

  My VDSL Modem being the device physically accessible with the dynamic IP obtained from my Internet Provider, it is configured to forward incoming Internet traffic to my Buffalo router. And this one is forwarding the traffic for my blog to my NAS.

  It obviously works fine for accesses from Internet. But if I try to access my NAS with that hostname from my home network (my intranet), the VDSL Modem does not forward me to the NAS via the router. Instead, I am redirected by the DNS of my Internet Provider to a page (http://Intranet IP of my Modem/dns_error) displaying:

  Your internet connection is up, please close your browser and restart it again.
  
  Uw internetverbinding is hersteld, gelieve uw browser eerst te sluiten en
  daarna opnieuw te starten.
  
  Votre connection internet fonctionne correctement, veuillez fermer votre
  navigateur et le redémarrer.

  My previous solution was to define the hostname www.beatificabytes.be in the host file (under C:\Windows\System32\drivers\etc) of my PC. So, instead of being resolved into the dynamic IP got from my Internet Provider (reason why I was reaching my VDSL Modem), that hostname was resolved directly into the IP of my NAS.

  Using the host file is however a real pain as it must be completed and maintained manually on all the devices. Also, it only works fine for Windows machines and not for my Phone, my Tablet, etc… So, I wanted a more global solution.

  I found that I could configure a host file directly on my Buffalo Router as explained here: http://commonbits.wordpress.com/2013/03/26/using-dd-wrt-for-local-dns-and-dhcp/. More details here: http://www.dd-wrt.com/wiki/index.php/DNSMasq_as_DHCP_server.

  I could also simply configure my Buffalo Router to provide each DHCP client with the IP of the ppen DNS of Google (8.8.8.8. and 8.8.4..4) instead of the DNS of my Internet Provider.

  But I was interested in testing the DNS Server package of Synology. And I found that it’s not that hard to configure it to resolve the hostname locally instead of querying the DNS of my Internet Provider.

  First, configure the NAS like this:

  1. Install and run the DNS Server Package via the Package Center
  2. Open the DNS Server Panel via DSM Start > DNS Server
  3. Select the “Zones” tab
  4. Click on “Create” and select “Master Zone”
  5. Select a “Domain type”: forward zone
  6. In “Domain name”, enter the domain name used by the blog
  7. In “Master DNS server”, enter the IP address of the NAS
  8. Keep other settings as by default and click “Ok”.
  9. Double click the new entry to edit its content. You should see two prefilled records respectively of type “A” and “NS”.
  10. Click on “Create” and add a new record of type “A”
      1. Name: (leave blank)
      2. TTL: (use the default)
      3. IP address: type the IP address of the NAS
  11. Also add another record of type “A” with Name “www”.

  And that’s it for the DNS Server configuration. I didn’t change anything else, including in the “Resolution” tab, …

  Next, configure the DD-WRT like this:

  1. Go to the tab Services
     1. Set “Used Domain” = WAN
     2. Set “LAN Domain” = Any name you want. It does not need to be the domain name of the blog. I am using my “Workgroup” (Yes, I still use a that)
     3. Check that the NAS has a static IP configured in the “Static Leases” table
     4. Set “DNSMasq” = Disabled
  2. Go to the tab Setup > Basic Setup
     1. Set “Connection Type” = Automatic Configuration – DHCP
     2. Set “Router Name” = SomeName
     3. Set “Hostname” = Same name as above
     4. Set “Domain Name” = (I kept it blank as I am not really working with a domain at home)
     5. Set “Local IP Address” = x.x.x.x (E.g.: 192.168.0.1)
     6. Set “Subnet Mask” = 255.255.255.0
     7. Set “Gateway” = local IP of the VDSL Modem (E.g.: 192.168.1.1)
     8. Set “Local DNS” = local IP of my NAS
     9. Set “DHCP Type” = DHCP Server
     10. Set “DHCP Server” = Enabled
     11. Set “Static DNS 1” = 0.0.0.0 (Later, I did set here the IP of my Adsl Modem which is configured to forward the DNS request to my Internet provider. I could also have use Google DNS: 8.8.8.8 or 8.8.4.4)
     12. Set “Static DNS 2” = 0.0.0.0
     13. Set “Static DNS 3” = 0.0.0.0
     14. Set “WINS” = 0.0.0.0
     15. Set “Use DNSMasq for DHCP” = unchecked
     16. Set “Use DNSMasq for DNS” = unchecked

  This is working for me but DNSMasq being disabled, there is no caching on the DNS name resolution or even on the NetBios name (DNSMasq can intelligently add DHCP leases to its DNS database, providing local name lookups for any DHCP client, static or dynamic). And solving names seems to me precisely quite slow for the Browsers. So, I decided to try to enable DSNMasq.

  1. Back into the Tab “Services”,
     1. Set “DNSMasq” = Enabled
     2. Set “Local DNS” = Disabled (If I enable it, I lose access to the Synology DSN ?!)
     3. Set “No DNS Rebind” = Enable
     4. Set “Additional DNSMasq Options” = (I kept it blank but was hesitating to enforce a strict order on the DNS to be used to resolves name):
        1. strict-order
        2. dhcp-option=6,<NAS IP comes here>,8.8.8.8,8.8.4.4 (ex.: I use here the open DNS of Google).
  2. Finally, in the tab Setup > Basic Setup
     1. Set “Use DNSMasq for DHCP” = checked
     2. Keep “Use DNSMasq for DNS” = unchecked (If I check it, I lose access to the Synology DSN ?!)
     3. Set “DHCP-Authoritative” = checked.

  I am actually not convinced this is correct and improving the resolution in any way. So,”to be continued”… But in the meantime, I can access my blog with its fully qualified domain name from both my Intranet and Internet and now a bit more about DNS configuration :p

  Notice:  You can have a lot of troubles while testing the various settings on the DD-WRT as many values are cached either on the Synology, or on your PC. Ideally, you should reboot all the devices after each change in the router settings. At least, reset the network interface of your NAS (telnet as root and execute /etc/rc.network restart) and renew your PC network settings (ipconfig /release and ipconfig /renew). Best would be to do that after a Router reboot (telenet as root and execute reboot)

  

  Synology

• The perfect AirPlay Speaker for my Synlogy

  13 December 2013

  I just bought 3 x Philips Fidelio SoundAvia wireless speaker AD7000W/12 with AirPlay. This model is must cheaper than any other AirPlay device and fully compatible with my Synology DS209+ running the Audio Station of DSM 4.2.

  Click to Read MoreClick to Close

  

  I paid only 109€ (instead of the official price: 149€) for this device, which is reported as a good one (Look for reviews on the web). It’s especially much cheaper than any other devices except the Philips DS3800W/10. But this last one, which actually used to be more expansive than the AD7000W/12 in the past, is not as good although better designed. I took 3 AD7000W/12 (for the price of one single Soundlink Air, the cheapest Bose AirPlay device). I will  use them respectively in the bathroom, in the kitchen and in my room.

  It’s perfect for a Synology as there is not useless feature, like a docking for iStuff that don’t need, no remote control as I have my mobile phone, etc… So I paid only for what I really need: a basic AirPlay Speaker.

  Take note that there is no need for an iPad, iPod or iPhone to configure the Philips Fidelio AD7000W/12. It’s presumed to be configurable auto-magically via WPS but I didn’t succeed to do so (I.e.: using the PBC – Push-Button Configuration – which is the WiFi setup button on the back of the device). Fortunately, it is really easy to configure the AD7000W/12 with a browser from any wireless client device such as a tablet, a laptop, a mobile phone, …

  Notice: when unwrapping the device, on the connectors at the back of device, there is a sticker explaining that one has to push the physical WiFi setup button for 5 sec to configure the network for the first time. This could be confusing if you read next the Quick Guide. Indeed, this one explains two ways to connect the device to the WiFi router: a first method using WPS and a second method using an iStuff. In both cases, you have to press the physical WiFi setup button. But the mistake would be to press this button for 5 seconds when using the WPS method. It must only be pressed for 5 seconds if you want to use the second method. So, here is my experience:

  1. Switch on the device. The button is on the back, close to the top, next to the Volume + and – buttons.
  2. On the back too, there is a green led blinking rapidly in the middle of the WiFi setup button, at the bottom, on the right of the USB connector. Wait for 35 sec until it starts to blink slowly. The device is then ready to be configured.

  To connect the AD7000W/12 to a WiFi router using a browser (Connect the devices one by one if you have several):

  1. Press the WiFi setup button for 5 sec (= blinks 5 times). The led will then start to blink alternatively green and orange.
  2. Soon after you should see, with your wireless client device, a new opened WiFi network  named like Philips_Fidelio_AirPlay. Connect to that network.
  3. Open a browser and navigate to 192.168.1.1 to access the network configuration page of the AD7000W/12. If you are using a laptop, althoug configured to get an IP via DHCP, you could have to reconfigure it to use a fixed IP like 192.168.1.2, gateway 192.168.1.1, mask 255.255.255.0. I had to do even after I didn’t succeed with a simple “IPConfig /renew”. With a mobile and a tablet, it worked out of the box.
  4. In the configuration page, edit the name of the device to make it unique and select the SSID of the WiFi network on which it will have to connect. It works fine with my network configured to use WPA2.
  5. Type the Passphrase of the WiFi network and Apply the configuration.
  6. The led will restart to blink rapidly in green.
  7. As soon as device is connected on the selected WiFi network, it produces a clear “Beep” sound and the led stops blinking.

  

  To connect the device using WPS:

  1. Press the WPS button on your WiFi router. It has better be configured to use WPA2
  2. Press the WiFi setup button on your device (a simple click of less than 1 sec). The led will start to blink alternatively red, green and orange.
  3. Wait for up to 2 minutes. The device should auto-magically connect on the WiFi router and produce a clear “Beep” sound once connected.

  This second approach didn’t work for me ?!

  As soon as the Philips Fidelio AD7000W/12 is connected on the WiFi network, it becomes available as a target device for the Synology Audio Station (either in the Web UI or in the Apps for mobile). One can see targets like “XXX( DLNA)”, “XXX (AirPlay)” and “Multiple AirPlay Device” where XXX is the name you gave to the device (“Philips Fidelio ####” by default). All those targets work but you will possibly have to be patient for the music to arrive with DLNA targets (?). I takes a few seconds more than with AirPlay on my infra.

  If you don’t want to see the speaker as both an AirPlay device and a DLNA device, you must tick “Do not Search for DLNA devices” in the “options” tab of your Audio Station’s settings.

  Notice that the feature “Multiple AirPlay Device” only works if turned on from Audio Station “browser based”. It means that you must first select that target in the Audio Station’s web based UI. You will then be prompted to select which AirPlay devices must be used. Once this is done, you can use the “Multiple AirPlay Device” target also within the Audio Station Apps for tablets and mobiles. There is no support (today) to select via the mobile App which devices are part of the target “Multiple AirPlay Device”.

  Notice also that selecting the target device is really easy on a mobile phone via the App. First select the music to be played in a library. Then, on the next screen you will be able to select the target:

  

  For an unknown reason, it’s not as obvious with the App on my tablet ? To select the target on my table I have indeed to open the settings of the App. This is really not convenient at all!

  Notice finally that each device has its own queue. So you can then switch between target devices and manage their queues independently.

  

  Hardwares, Synology

• Send Custom (email) Notifications from scripts running on a Synology

  1 December 2013

  I use a custom script on my Synology DS209+ (DSM 4.2) DS713+ (DSM 5.1) to backup the databases and was recently asked how to notify the administrator about the success or the failure of that script. The easiest solution is to use the native Notification mechanism of the DSM. It notifies not only by email but also with popup messages, SMS, Skype, etc….

  If you are using DSM 6.x, look at the new version of this post, located here.

  Click to Read MoreClick to Close

  First, create the texts for the Notifications to be sent:

  1. Open a dos command prompt
  2. Execute: telnet <YourSynoHostname>
  3. Login as ‘root’
  4. Use the password of your Administrator
  5. Execute: cd /usr/syno/synoman/webman/texts/
  6. Execute: ls
  7. Now you see a list of folders for each language supported by your Synology. Assuming that your DSM is configured to run in English (the default), we will use here after the folder ‘enu’ (but read the notice at the end of this post if you want to configure Notifications for another language)
  8. Execute: cp enu/mails /volume1/web/
     1. I presume here that the web station is enabled, otherwise, copy the file ‘mails’ in any other shared folder.
     2. This file contains the Notification messages used by the Synology.
  9. Open now this file ‘mails’ with notepad++: \\<yourSynoHostname>\web\mails
  10. Add two new “tags” at the end of the file. E.g.: “MySqlBkpError” and “MySqlBkpOK” (see bellow for details to possibly be used for those tags)
  11. Save the changes.
  12. Back to the telnet console, execute: cp /volume1/web/mails enu/mails

  [MySqlBkpError] Category: Backup/Restore,Important
  Title: Database backup failed
  Subject: Database backup on %HOSTNAME% has failed

  Dear User,

  Database backup on %HOSTNAME% has failed.

  [MySqlBkpOK] Category: Backup/Restore
  Title: Database backup succeeded
  Subject: Database backup on %HOSTNAME% has succeeded

  Dear User,

  Database backup on %HOSTNAME% has successfully completed.

  Next, complete your script to notify the Administrator about the Success or Failure of its last action:

  1. Edit your script with notepad++ once it has been copied in a shared folder of your Synology as made here above with the file ‘mails’.
  2. After the action to be reported, add the code here bellow.
  3. Save your changes and copy the file back to its original location

  if [ $? -eq 0 ] then /usr/syno/bin/synonotify MySqlBkpOK
  else /usr/syno/bin/synonotify MySqlBkpError
  fi

  Now, define those custom Notifications to let them appear in the “Advanced” tab of the “Control Panel” > “Notifications” pane where you will be able to enable “email”, “sms”, … for them.

  1. Go back to the telnet console and execute: cp enu/notification_category /volume1/web/
     1. If you want to define those notifications for another language, used the adequate folder instead of ‘enu’.
     2. Notice that I presume you are still in the path set previously, i.e.: /usr/syno/synoman/webman/texts/
  2. Edit the file ‘notification_category’ with notepad++
  3. Look for the following definition in that file: {“group”:”Backup/Restore”,”name”:”NetBkpS3OK”,”title”:”Amazon S3 backup completed”}
  4. Insert the following definition next to it (don’t forget the coma), save the changes and copy the file back to its original location: cp /volume1/web/notification_category enu/notification_category

  ,{“group”:”Backup/Restore”,”name”:”MySqlBkpOK”,”title”:”Database Backup completed”},{“group”:”Backup/Restore”,”name”:”MySqlBkpError”,”title”:”Database Backup failed”}

  Finally, check that the “Notifications” are enabled on your Synology and tick options like emails, SMS, … for the new tags:

  1. In your DSM, go to “Control Panel” > “Notification” > “E-Mail”
  2. Tick the option “Enable e-mail notifications”.
  3. Complete all the fields in that tab. At least: SMTP server, SMTP port, SMTP authentication and Primary email.
  4. Send also a test mail from this tab to verify your settings.
  5. Go next to the “Advanced” tab
  6. Tick the “E-mail” option (and possibly others) for the two new tags which appear now in the list.
     1. If the tags do not appear, close and reopen the control panel.
     2. The tags appear with their title “Database Backup completed” and “Database Backup failed”

  And here are the outcomes: a popup message and an email

  

  

  Pay attention that the tags are case sensitive ! Also backup the changes you made in the file ‘mails’ and ‘notification_category’ as they will be overwritten for sure when you will update the DSM… Finally, delete the files ‘mails’ and ‘notification_category’ from your web folder…

  Notice: to declare Notifications for other languages, you will apply the tips here above in the files under your own language folder. A reader, Kasak, kindly reported however that he had to declare the ‘tags’ not only in the ‘mails’ file under the folder of his language (E.g.: ‘fre’), but also under the English (enu) folder.

  Notice: as reported by another reader, Pieter Hooftman, you will see your notifications in Control Panel > Notifications > Advanced tab if and only if you filter them on “All Notifications”. If you need to filter your custom notifications, you have to add it into each section of the file “notification_category” (there is one section per filter). Concretely, look for each occurrence of {“group”:”Backup/Restore”,”name”:”NetBkpS3OK” and insert your in front.

  Notice: as reported by k13tas, it’s much easier to reuse an existing notification and customize its text via Control Panel > Notification > Advanced. Indeed, customized text are not lost after a DSM update. That being said, once a custom notification added in the file “notification_category”, you can also customize its text. Once this is done, the notification will always be available to be used with /usr/syno/bin/synonotify, even after a DSM update, although not visible anymore in the Advanced tab – which is far from ideal.

  As creating manually custom notifications is far from ideal, please vote for my feature request on Synology’s forum: http://forum.synology.com/enu/viewtopic.php?f=3&t=92727

  

  Synology

• Synology surveillance station: Internet Explorer has stopped working

  19 November 2013

  Since two days, each time I open a Preview, a Live View or the Timeline in my Surveillance Station, IE crashes. Presuming it could due to the Synology ActiveX used by those features, I have removed that one. And Bingo, it’s fixed.

  Click to Read MoreClick to Close

  No idea how that ActiveX has been corrupted, but here it how to remove it.

  1. Press Alt–X to open the Tools menu
  2. Select “Manage Add-ons”
  3. In Add-on Types, keep “Toolbars and Extensions” selected
  4. Scroll down to find the extension “SS3Object Control”. Select it.
  5. In the bottom pane, click on “More information”
  6. You have now a popup window “More information” with a “Remove” button at the very bottom. Click that button.
  7. Reopen Surveillance Station. The ActiveX will be re-installed. But now, the problem is gone…

  

  Synology

• Access Synology from Windows 8 with a Windows Live ID

  19 December 2012

  Since I did upgrade my PC from Windows 7 to Windows 8 and did start to use my Microsoft account (Windows Live ID) to sign in, I am prompted for credentials when I try to  access shared folders on my Synology, although I did create an account with the same name on the NAS. The Credential Manager (formerly known as Windows Vault) is the solution!

  Click to Read MoreClick to Close

  First, to be sure that I did create an  account with the same name as my Windows Live Id on the Synology, I did check the name of that Live Id in C:\Users. It was the very same.

  However, that’s not the name sent by Windows 8 to the NAS.

  I could provide valid credentials but I don’t want to do that at each access. And unfortunately,  the old good “Remember my credentials” checkbox seems to be gone in Windows 8. But the feature behind this option (Windows Vault) is still available.

  1. If you are not on the Start Screen, type “Ctrl-Esc”
  2. Once on the Start Screen, type “Control” and select the search result “Control Panel”.
  3. In the “Control Panel” search box, type “Credential” and select the search result “Credential Manager” (This one is the feature formerly known as Windows Vault).
  4. Select the “Windows Credentials” button.
  5. Now, select “Add a Windows Credential.”
  6. In the view that opens, type in the hostname of your NAS or its network address
  7. Provide the user name and password that you want to use to connect on the NAS instead of your Windows Live ID.

  Et voilà!

   

  

  Synology, Tips

• From WordPress 3.3 to 3.4 on Synology: Almost YAUN !!

  4 November 2012

  No! I don’t mean “Yet Another Unix Nerd”!!!

  But upgrading WordPress from 3.3 to 3.4 on my DS209+ was almost “Yet Another Upgrade Nightmare” 🙂

  Click to Read MoreClick to Close

  Upgrading a package for Synology is usually really a piece of cake. Unfortunately, the upgrade package for WordPress caused me difficulties.

  First issue: MySQL password

  The setup failed quite immediately after downloading, complaining that there was possibly an issue with the MySQL password. After some investigation, it appeared to me that :

  • the DSM Package Center is running as Synology’s “root” user and
  • the setup of WordPress was trying to access MySql with that account but without any password.

  I found on Synology’s Forum that “Current wordpress package requires an default mysql account root with empty password to create database successfully. If you have set mysql root password before, please install phpMyAdmin to reset the password first.“

  And unfortunately (although quite normal), I did set a password for the MySql “root” user in the past… So, as suggested in the message above, I did reset MySql root password to blank.

  • Go to phpMyAdmin, opened the “Users” tab and clicked “Edit Privileges” for the user “root” with Host=localhost.
  • In the “Edit Privileges” dialog box, scroll down to the “Change Password” area and select “No Password” before clicking “Go”.
  • Finally, back to the “Users” page, click “Create PHP code” to apply the change. At that moment, phpMyAdmin could prompt you to re-enter your credentials (root with a blank password).

  I did next restart the update of the WordPress which finally completed fine. But…

  Next issue: Page Not Found

  My Blog was not reachable anymore after the upgrade ? Damned… WordPress was imply disabled… I had to click “Start” next to the WordPress Package in the DSM Package Center 😆

  And finally, my home page appeared… I went immediately to the administration dashboard where I discovered that the setup was actually not yet complete. In this dashboard, I found a message asking me to click a button to upgrade the database. Fortunately, nothing wrong occurred during this upgrade 🙂

  Last issue: This is somewhat embarrassing, isn’t it?

  Although the home page appeared correctly, I was not able to open anything else: no post, no “custom” pages, no categories, … For each of them, I got the WordPress’ “Page Not Found”… All the permalinks appeared somewhat “corrupted”… No idea why.

  Fortunately (bis ter et repetita), fixing this issue was not difficult. I simply had to re-enforce the right Permalinks structure.

  • Go back to the administration dashboard and select the menu “Permalinks” under “Settings”.
  • Check that “your” structure of Permalinks is still selected and did click “Save Changes” (Even if you didn’t change the structure).

  And miracle! Everything went back to normal. I didn’t lose any customization or plugins except my custom smilies from \web\wordpress\wp-includes\images\smilies (fortunately backuped),…

  YASU!!

  No! I Don’t mean “Yet Another System Utility”!!! But “Yet Another Successful Update” 😆

  

  Synology, Wordpress

• Schedule a Backup of all your MySQL databases on Synology

  29 September 2012

  It would be a good idea to schedule a daily backup of all the MySQL databases on your Synology. Those will indeed be wiped out if by accident, you have to reset your NAS (reinstall the firmware), ex.: if you lose a disk in your RAID 0.

  That can be done using a shell script and a cron job as described here after.

  How to BackupClick to close

  First, create a user with a local-read-only access on the databases. We will indeed have to let its password in the script, endangering the security. Using a local-read-only user will mitigate the risks.

  1. Go to the web administration interface (DSM) of your NAS.
  2. Install phpMYAdmin via the “Package Center” if not yet done.
  3. Open phpMyAdmin via the “Start Menu” (“Main Menu”).
     1. I am using the login ‘root’ with the password of Syno’s ‘admin’ user
  4. Open the “Users” tab in phpMyAdmin
  5. Click “Add User” (bellow the list of existing users)
  6. Enter the User Name. Ex.: backup
  7. Select “localhost” as an Host.
  8. Enter a password. Ex.: mysql
  9. Keep “none” as “Database for user”
  10. Grant the user with Global privileges: Select (in Data) and Reload, Show Databases and Lock Tables (in Administration)
  11. Click “Add User” at the botton of the page

  Next, create a shell scripts in a Shared Folder of the NAS (Ex.: \volume1\backup\backupMySql.sh). Working in a Shared Folder will make it easier for you to copy/open later the backups from your PC). Don’t forget to create a “Unix” file, either using the touch command in a Console or saving a file As a “Unix shell script” within Notepad++. Notice that a script created with NotePad++ and saved on the Shared Folder will belong to the user account accessing that Shared Folder (Most probably your Windows Account if like me you simply created a user on your NAS with the same login and password). A script created with “touch” in a Console will belong to the user accessing the NAS via telnet/SSH (Most probably the “root” account).

  [shell]#!/bin/sh
  #
  DIR=/volume1/backup/sqlbackup/
  DATESTAMP=$(date +%Y%m%d%H%M%S)
  DB_USER=backup
  DB_PASS=mysql
  
  # create backup dir if it does not exist
  mkdir -p ${DIR}
  
  # remove backups older than $DAYS_KEEP
  #DAYS_KEEP=30
  #find ${DIR}* -mtime +$DAYS_KEEP -exec rm -f {} \; 2> /dev/null
  
  # remove all backups except the $KEEP latest
  KEEP=5
  BACKUPS=`find ${DIR} -name 'mysqldump-*.gz' | wc -l | sed 's/\ //g'`
  while [ $BACKUPS -ge $KEEP ]
  do
    ls -tr1 ${DIR}mysqldump-*.gz | head -n 1 | xargs rm -f
    BACKUPS=`expr $BACKUPS - 1`
  done
  
  #
  # create backups securely
  #umask 006
  
  # dump all the databases in a gzip file
  FILENAME=${DIR}mysqldump-${DATESTAMP}.gz
  /usr/syno/mysql/bin/mysqldump --user=$DB_USER --password=$DB_PASS --opt --all-databases --flush-logs | gzip >> $FILENAME
  [/shell]
  

  NB: Since DSM 6.0, “/usr/syno/mysql/bin/mysqldump” has been moved to “/bin/mysqldump” !!!

  Possibly, type the following command in a Console (telnet/SSH) to set the user ‘root’ as owner of the script:

  [shell]chown root /volume1/backup/backupMySql.sh[/shell]

  IMPORTANT notice: I used to have “-u DB_USER” (with a blank space in between) in my script above and -“p$DB_USER” (without a blank) instead of –user and –password. But a reader (Fredy) reported that the script was not running fine for him unless removing the blank. As per documentation of mysqldump’s user parameter and password parameter, there should be a blank after -u but not after -p. However, samples on the web usually illustrate the use of mysqldump with “-uroot”. So, I decided to use the more explicit notation “–user=” and “–password=”. I did test this notation with a wrong username or password and the resulting dump is indeed empty. With the correct username and password, it works fine.

  Since DSM 4.2, the Task Scheduler can be used to run the script on a daily basis.

  1. Go to the Start Menu
  2. Open the Control Panel
  3. In the “Application Settings”, open the Task Scheduler
  4. Select “Create a User-Defined Script”
  5. Type a name for that “Task:”
  6. Keep the “User:” root
  7. In the “Run Command” pane, type:

     sh /volume1/backup/backupMySql.sh

  Don’t forget the “sh” in front of your command, otherwise, it does not work (although the sample provided by Synology is missing it ?!)

  If you don’t use the Task Scheduler, you can add a Cron Job to execute the script, e.g. every day at 0:01. Open a Console (Telnet/SSH) and type:

  [shell]echo "1       0       *       *       *       root    sh /volume1/backup/backupMySql.sh" >> /etc/crontab[/shell]

  FYI, a cron line syntax is “mm hh dd MMM DDD user task” where:

  • mm is the minute (0..59)
  • hh is the hour (0..23)
  • dd is the day in the month (1..31)
  • MMM is the month (jan, feb, … or 1..12)
  • DDD is the day in the week (sun, mon, … or 0..7 where 0 and 7 beeing both sunday)

  The following values can also be used:

  • * : a every unit (0, 1, 2, 3, 4…)
  • 5,8 : at unit 5 et 8
  • 2-5 : units 2 to 5 (2, 3, 4, 5)
  • */3 : every 3 units (0, 3, 6, 9…)
  • 10-20/3 : every 3 units, from 10th to 20th (10, 13, 16, 19)

  So, the script will start every day at 0:01h

  Finally, you must restart the cron daemon to activate the new job. To find the process id and send a SIGHUP signal to this one, type the following command line in a Console (Telnet/SSH):

  [shell]ps | grep crond | grep -v grep | awk '{print$1}' | xargs -t kill -HUP[/shell]

  It should display “Kill -HUP xxxx” where xxx is the pid of the cron daemon.
  

  Added on 03/01/2013Click to Close

  Attention: if you copy paste the command to restart the cron daemon from this page into the telnet console, some symbols will be wiped out: the ‘{ and ‘ around print$1… you have to type them manually…

  Attention: if you upgrade the version of DSM, the changes made in the cron script are lost (at least, it’s what I have noticed after updating last month…). Reason why I recommend to use the new “Task Scheduler” feature available since DSM 4.2.

  Tip to edit the cron script: you can use the package “Config File Editor” available here. Once installed, you can access it via the Main Menu. Then, you have to edit the file named “Config File Editor” and add the following line:

  /etc/crontab,crontab

  Once this line is added and saved, … I don’t remember how to force the change to be taken into account :/. But restarting the DiskStation is enough 😀

  Finally, back into the Config File Editor, select the ‘crontab’ entry and modify this script, save your changes and restart the cron daemon.

  Tip to restart the cron daemon: you can use the package “MODS Web Console” available here. To install it, go to the Package Center and add the following url via the Settings > Package Sources : https://www.beatificabytes.be/sspks. Once this url added, go to the tab “Community” and click Install on the “MODS Web Console” icon.

  Run the Web Console via the Main Menu, log in with “admin”/”admin” (The defaults values if not changed) and type:

  synoservice --restart crond

  Added on 01/12/2013Click to Close

  If you want a lazy solution to notify the Administrator about the success or failure of the backup, you can use the ‘synonotify’ command (See details here). A more advanced solution would be to configure the “Mail Server” and use its ‘sendmail’ command:  /volume1/@appstore/MailServer/sbin/sendmail…

  Added on 08/01/2017Click to Close

  mysqldump has moved

  • DSM 6.0 : /usr/syno/mysql/bin/mysqldump
  • MariaDB 5: /volume1/@appstore/MariaDB/usr/bin/mysqldump
    MariaDB 10: /volume1/@appstore/MariaDB10/usr/local/mariadb10/bin/mysqldump

How to RestoreClick to Close

Download the script here.