Tips Expand storage by migrating disks from Synology DS713+ to DS1815+

The 2x3TB disks of my DS713+ were full. Being lazy, I decided to expand the storage by migrating the disk to a new DS1815+ with more bays (instead of doing a full backup and restore on larger disks). It was a piece of cake!

Click to Read More

  1. Do first a backup of the configuration of your current Synology via Control Panel > Update & Restore menu > Configuration Backup tab > Back up configuration button
  2. Move the disks to the new Synology, keeping the very same order (disk in bay n must go into the bay n of the new Synology).
  3. Add a few other disks in the new Synology and create new Volumes
  4. Boot the new Synology and wait for the beep.
  5. Start the Synology Assistant, find your new Synology and click "Connect" on it.
  6. Use the Migration mode, keeping all your files. NB.: you should download the latest DSM for your new Synology and use that local copy during the installation process instead of letting the installation process download that file itself.
  7. Restore the Configuration backup on the new Synology
  8. If you were using the web station and php, enable it. This settings was lost in my case: Control Panel > Web Services menu > Web Services tab > Enable Web Station option
  9. Repair the packages one by one. Wait for each repair to be successful before repairing the next package otherwise you could be in troubles. Pay attention also that the behaviour of the UI can be weird when auto-refreshing after a repair. If clicking repair on a package, you see that the package repaired is not the one you clicked on (but one that was already repaired), close and reopen the Package Center. All my packages where successfully repaired (sometimes I had to skip one and retry later, IMO due to the dependencies...). Here are the packages I had to repair
    1. Audio Station. everything kept as-is, including the user-defined radio
      1. if music does not appear, go to Control Panel > Media Indexing and re-index the media files.
    2. Download Station: didn't lose anything from its download queue
    3. Plex Media Server. I simply had to reenter my credentials which were expired
    4. DNS Server: all settings/zones still defined. Access to all services from intranet and internet working fine
    5. Maria DB: nothing lost. In particular my Worpress blog.
    6. Media Server: ok
    7. Video Station: all video and metadata accessible
    8. Photo Station: all albums still there and ok
    9. Python 3: I had to retry the repair but works fine
    10. Java Manager: ok (used to install Java 7)
    11. Surveillance Station: Licenses, settings, camera, recordings are all kept
    12. Time Backup: I had to retry the repair but backup tasks are ok, as wel as the timeline itself.
    13. Node.js
  10. Other Packages:
    1. My Custom packages were still there: iPKGui, AcpiOnLan, Mods (My Own Dsm Shorcuts), Unofficial Java Installer (Java 8)
    2. Custom Package Sources are still defined too
    3. Jdownloader was still installed and configured and I only had to restart it.
    4. Settings were lost for FileBot Node. After reconfiguring FileBot Node, it was not working (unable to access its onw port) I had to uninstall it and reinstall (including FileBot). Reconfigured settings were however not lost...
    5. WordPress was stopped. My blog was however well still accessible as I did reenable the Web Station
  11. Synology's DDNS Service
    1. DDNS Service being linked to the old Synology, I had to go to https://account.synology.com/fr-fr/overview and unlink my DDNS name
    2. Next, I went to  Control Panel > External Access and did Edit my provider (Synology) to re-enabled the DDNS and re-introduced my login/password.
    3. It took a few minutes before being again connected.
  12. I finally moved a few Shared Folders to the new volumes by editing them via Control Panel > Shared Folder menu > Edit. I simply changed the location, picking the new Volume as a target. Attention, during the move, the Control Panel is not accessible anymore. If you need to access it, simply open a new browser ;) (The only thing that cannot be done, is moving two Shared Folders simultaneously). Notice that the move can take ages as the new volume is probably still under validation (depends if you checked that option when you created the volume).

Et voilà.

Synology Expand a Synology RAID 0 Volume with bigger disks using VMWare...

I had 2 x 2TB disks in a RAID 0 Volume on my DS713+ and wanted to replace them with 2 x 3TB... My first idea was quite simple: move the 2TB disks from the DS713+ into my PC, next to the 3TB disks, clone those 2TB onto the 3TB disks and resize the data partition... Unfortunately, googling for users' feedback on such an operation, I finally felt that it could possibly be no such a real piece of cake... So, I used my second idea: "Backup" the DS713+ into a Virtual Synology, replace the 2TB with the 3TB in the DS713+ and "Restore".

Click to Read More

I decided to not try the "partition resizing" approach because it seems that expanding next the Volume to use the free space on the partition could be difficult (if possible at all). I will for sure try that idea later with dummy data. But for now, I wanted a peace-of-mind-solution. So, I did:

  1. Create a Virtual Synology (a DS3612xs with DSM 5.0-4528) with enough space,
  2. Enable the Network Backup Service on that DS3612xs
  3. Clean-up as much as possible on the DS713+ (DSM 5.0-4528 update 1)
    1. Disabled the camera in Surveillance Station and  deleting all the recordings
    2. Stopping Plex, Video Station, Audio Station and Photo Station
    3. Deleting all the movies from \\<DiskStation>\video (As those are anyway backuped on my main server)
    4. Deleting all the musics from \\<DiskStation>\music (As those are anyway backuped on my main server)
    5. Keeping however the photos to not loose albums' settings and thumbnails (as those would require days to be recreated!)
  4. Backup as much as possibly from the DS713+
    1. Using the native "Backup & Replication" feature, but also
    2. "Exporting" the Configuration of the "Surveillance Station" and Copying the extra licences (not the default one)
    3. "Exporting" all the complete zones' settings from the "DNS Server"
    4. Taking note of the information not backuped:
      1. "QuickConnect"
      2. "External Access"
      3. "Network"
      4. "Security"
      5. "Notification"
      6. "Application Portal alias"
    5. Taking note of:
      1. All the Packages installed:
      2. The custom "Package sources" configured in the settings of the Package Center
    6. Backuping Wordpress
      1. Stopping first WordPress
      2. Taking a Backup of the database wordpressblog via a full "Export" with phpMyAdmin
    7. In addition, to be 100% safe,I also took a full copy of
      1. the Plex's configuration & settings: \\<DiskStation>\Plex\Library\Application Support\Plex Media Server
      2. the WordPress installtion: \\<DiskStation>\web\wordpress
      3. All my "customized" stuff
  5. Replace the 2 x 2TB with the 2 x 3TB in the DS713+
  6. Reinstall DSM 5.0 on the DS713+ with the same name and admin's password as previously
  7. I reinstalled WordPress, Plex, DNS Server and PhotoStation, but I did not configure them and stopped them! (Actually, I don't know yet if installing them before the restore was required... -- to be checked).
  8. Enable the Telnet Service in "Terminal & SNMP"
  9. Restore manually the information for
    1. "QuickConnect"
    2. "External Access"
    3. "Network"
    4. "Security"
    5. "Notification"
  10. Restore the Backup made on the DS3612xs. It included:
    1. All the Shared Folders selected to be backuped
      1. Shared Folders recreated when installing a Packages are renamed!
    2. The "File Services" settings
    3. The "Users"
    4. The "Groups"
    5. (I don't use the Directory Services)
    6. The "Regional Options"
    7. The "Task Scheduler"
    8. The "Application Portal" alias
  11. Reinstall the other Packages.
  12. Import manually the DNS zones exported previously (via "Create" > "Import zone").
  13. Fix issues with "Surveillance Station" if any.
    1. I had to delete the camera restored with the Backup in "Surveillance Station" (weird as I successfully restored such backups in the past...)
    2. Add manually my extra licences
    3. Import manually the Configuration settings I exported previously.
  14. Restore manually the database of WordPress via phpMyAdmin and start next WordPress. It should not prompt you anymore to configure it.
  15. Check that the expected content has been restore in the various Shared Folders: photo, Plex (music and video if not cleaned-up), etc...
  16. Delete all Plex's plugins (hidden folder \\<DiskStation>\Plex\Library\Application Support\Plex Media Server\Plug-ins). They will be reinstalled automatically when you will start Plex. I have indeed noticed that various features do not run fine anymore in the Administration site otherwise. Ex.: choose language when editing libraries or fixing incorrect match, choosing providers, etc...
  17. Start all Packages currently stopped.

Here after, the steps to create a Virtual Synology:

Click to Read More

  1. Take the latest Boot Image iso available to start a "DSM" in a VMWare (Nanoboot-5.0.3.2 DSM 5.0-4528 x64) here.
  2. Take next the latest DSM pat Image (DSM 5.0-4528) here.
  3. Get the Synology Assistant from here and install it.
  4. Use VMWare Workstation 10 to create a new VM (You may create a Shared one to be able to run it remotely if you want):
    1. Create a "Custom (Advanced)" virtual machine
    2. Linux, version "Other Linux 2.6.x kernel 64-bit"
    3. With 1 processor, 2 cores
    4. 1024MB Memory
    5. Using a Bridged network
    6. LSI Logic Controller
    7. SCSI Disk Type
    8. And a large new virtual disk fully allocated (for performance reason)
  5. Instead of starting the new machine immediately, edit the settings: the CD/DVD must be changed to use the Iso Boot Image donwloaded at step 1.
  6. Next, edit the ".vmx" file created by VMWare next to the VM: Add this line just after the first one: bios.bootOrder = "cdrom"
  7. Now start the VM. It shows a menu with various entries named "Nanoboot-5.0-4528 xxx". Pick the one to "Install/Upgrade".
  8. Run next the Synology Assistant. It will find a "DiskStation" not yet installed. Select that one and right-click to "Install" it.
  9. When prompted for the Installation File, pick the pat file downloaded at step 2.
  10. Proceed until the installation is completed (Give a name to you new Synology. No need however to setup a QuickConnect ID).
  11. Enable the Backup https://www.synology.com/en-us/support/downloadService via the Start Menu > Backup & Replication > Backup Service > Enable Backup Network Service.

You are now ready to backup your actual Synology.

And icing on the cake, here is how to access the DSM and data still available in the old RAID 0 Volume (I.e.: on the two old 2TB):

Click to Read More

I did create a second Virtual Synology with the RAID 0 volume still available on the two old 2TB! Doing so, I will still be able to access all my data and settings if by any chance some have not been correctly restored.

  1. Take the latest Boot Image iso available to start a "DSM" in a VMWare (Nanoboot-5.0.3.2 DSM 5.0-4528 x64) here.
  2. Get the Synology Assistant from here and install it.
  3. Use VMWare Workstation 10 to create a new VM (You may NOT create a Shared as those do not support physical disks. Also you better have to run VMWare as Administrator otherwise adding physical disks could be disabled):
    1. Create a "Custom (Advanced)" virtual machine
    2. Linux, version "Other Linux 2.6.x kernel 64-bit"
    3. With 1 processor, 2 cores
    4. 1024MB Memory
    5. Using a Bridged network
    6. LSI Logic Controller
    7. SCSI Disk Type
    8. And add the two old physical disks. Notice: the order is important. If they are not in the correct order, the DSM won't start and report a disk access failure. No panic: simply swap the disks and retry ;)
  4. Instead of starting the new machine immediately, edit the settings: the CD/DVD must be changed to use the Iso Boot Image donwloaded at step 1.
  5. Next, edit the ".vmx" file created by VMWare next to the VM: Add this line just after the first one: bios.bootOrder = "cdrom"
  6. Now start the VM. It shows a menu with various entries named "Nanoboot-5.0-4528 xxx". Pick the one to "Install/Upgrade".
  7. Run next the Synology Assistant. It will find your old Synology "Migratable". Select that one and right-click to "Migrate". The RAID 0 Volume is detected automatically and the DSM should load. If it fails around 50%, swap the physical disks and restart the VM. They are probably not in inserted in the correct order (I did swap them physically in my PC - as using bays- but I could have removed them from the VM configuration and re-added them in the right order).
  8. NB: installing with the option to download the latest DSM version failed. I had to download and use the pat file DSM 5.0-4528 available here.
  9. Give this new Synology a unique name and disable any service that would conflict with one already running somewhere else.

Synology Upgrade from DSM 4.3 to DSM 5.0

Wow, what a fancy look & feel !!! That's my first impression  :-D

But what I really care about, is that all the services I was using on DSM 4.3 are still running fine... And it seems to be the case once a few issues fixed...

Click to Read More

After the upgrade, various packages had to be updated. Unfortunately, the updates did not all passed successfully. I got errors like "failed to download" (notice: I did an update of all my packages before upgrading from DSM 4.3 to 5.0 as recommended by users on Synology's forum)

I discovered soon that I was actually unable to download and install any other packages. And looking into Control Panel > Update & Restore, I saw the Status "Connection failed. Please check your Internet connection".

I  was unable to play Internet radio within the Audio Station and trying to "Update Now" the DDNS service (Control Panel > External Access > Update Now), I was receiving a message like "Network error occurred. Please check your DNS and network settings."

As Download Station was still able to download, the internet connection was not the issue. So, based on the hypothesis that it should be a DNS issue, I did force a DNS address manually in Control Panel > Network > General > Manually configure DNS Server. I did set the IP of my Adsm Modem as it's configured to forward DNS request to my provider. But I could have tried with Google's DNS: 8.8.8.8 or 8.8.8.4

And it solved all the issues above ?!

As a reminder, my DHCP server is configured on my Buffalo Router to provide the IP of my NAS as a DNS Server (I run the "DNS Server" package of Synology) and the IP of my ADSL model as a fallback. It used to work fine before the upgrade and as I didn't change anything else in my infra, I thought that some behavior could have change in some Syno's services. I did try various changes and found one that was solving the issues without manual configuration of a DNS IP on my Syno:

I had to "Enable resolution services" in my Synology's "Control Panel > DNS Server > Resolution" settings. Simple, no ?

But I discovered then another issue: my Plex Server was not accessible anymore (when opened from DSM's start menu). It was trying to start on the IP address of an unused Ethernet port - There are two Ethernet ports on the DS713+ and only the second one of mine was plugged on my Switch. The IP used by Plex Server was therefore a default one: 169.254.x.x. So, I did connect the first Ethernet ports on my Switch and did a reboot. I was next able to access the Web UI on the IP assigned now to my NAS's first Ethernet port.

But it was not solving everything. Indeed, plex.tv was still not able to reach my NAS since my ADSL Modem was forwarding the default port of Plex (32400) onto the IP of the second Ethernet port and not on the first one (I.e.: on the IP Plex Server was actually listening on). As my NAS is only connected to one LAN, I decided to enable the Link Aggregation to merge the two ports into a "virtual single one". Doing so, I would have only one IP assigned to my NAS and both Ethernet port used together to increase a bit the bandwidth: Control Panel > Network > Network Interface > Create > Create Bond > IEEE 802 Dynamic Link Aggregation. I did complete the Wizard (using DHCP the get an IP) and went to reconfigure my DHCP server (on my Buffalo Router): I.e.: I did update the static leases and assigned the static IP wanted for my NAS on the MAC address currently used by the Dynamic Link Aggregation (It's available in the Control Panel > Info Center > Network > Bond 1).

Once the DHCP server and the Synology reconfigured, I did reboot both (to avoid caching effect). Unfortunately, when accessing my server via plex.tv, it was still not displayed as "online" :( Also, in the "Plex Media Server"'s settings "myPlex", I was unable to connect with my login/password and worst, I was unable to change any settings in my Plex Server: Saving changes was always failing... I found a note about a known issue on the Synology website:

DSM 5.0: Known Issue - Plex Media Server
Users need to manually set read permission for the “plex” user at the User page in Control Panel to allow Plex Media Server to read the shared media folder content.

But trying this fix didn't solve my issues.

I thought then that there could be a more recent version of the Plex Server on plex.tv than on Synology... And indeed. The version I had was 9.8 and there was a 9.9 on Plex.tv. I did download the spk for my processor (DS713+ = Intel) and did install it manually. And Bingo, my Plex Media Server was now able to connect to myPlex and it appeared as "Online" in plex.tv !!!

So, to conclude, the following services are now running fine:

    • Download Station (it resumes the download of your the torrent without any issue)
    • Surveillance Station (the time line is not broken)
    • DNS Server (once the "Resolution Service" enabled as mentioned above)
    • Video Station (has been updated)
    • Photo Station (has been updated)
    • Webalizer (has been updated)
    • Plex  (After a manual update as mentioned above and some reconfiguration of the IP/Ethernet port used)
    • WordPress (has been updated)
    • phpMyAdmin

Changes I noticed:

  • As usually, after the upgrade of WordPress (If you do so), you will have to reset the permalinks' format (via Dashboard > Settings > Permalinks > Common Settings > re-select your structure and "Save Changes"). Otherwise, links to your posts (E.g.: found via google or kept as favorites by readers) won't work anymore..
  • The DDNS service is now named "External Access". Nothing has changed and nothing needs to be reconfigured.
  • MySQL has been replaced by MariaDB (a fork of the original project). Start it once to finalize the update (you will have to provide your password). phpMyAdmin still runs fine and connects automatically to MariaDB with your current root login and password.
  • You will now get a monthly report by email with the status of the disks. Ex.:

Dear user,

The following is your monthly report regarding the health of disks on <serverName>. You can also check the health of individual disks at Storage Manager > HDD/SSD > Health Info.

Disk 1:

Disk Reconnection Count 0

Bad Sector Count 0

Disk Re-identification Count 0

Disk 2:

Disk Reconnection Count 0

Bad Sector Count 0

Disk Re-identification Count 0

Synology Plex Server on Synology DS713+: Cannot load M3U8: 404 not found

When trying to watch a movie streamed by the Plex Server of my DS713+, I used to get an error "Cannot load M3U8: 404 not found" (only on mobile devices or within a browser). This was due to a wrong "temp" directory configured (out-of-the-box) for transcoding purpose.

Click to Read More

Watching movies was working fine with the Plex Theater on my PC.

I had the error message "Cannot load M3U8: 404 not found" only when trying to play movies within Chrome (on a PC or on a tablet).

I read on the web that this error could be due to the NAS struggling with transcoding the movie (which is done or not depending on the client's spec). Plex clearly states that one needs a dual-core NAS to be able to do transcoding. But I have a DS713+. So it should have been fine

I also read that Plex Theater (on Windows) does not need any transcoding. As it was working fine, I definitively though there should be something wrong with the configuration  of the transcoding...

I did look at the logs of Plex Server (in \\<MyNas>\plex\Library\Application Support\Plex Media Server\Logs) and found that error:

ERROR - Exception handled: boost::filesystem::temp_directory_path: Not a directory: "/volume1/Plex/tmp_transcoding"

Checking directly on the NAS via telnet, I found that the right path should have been /volume1/Plex/Library/tmp_transcoding (Notice: "Plex" starts here with a upper case although the related shared folder accessible via SMB starts with lower case!!!)

So, I did force that correct value via the Plex server web interface > Settings > Transcoder > Show Advanced Settings > Transcoder temporary directory.

And BINGO !!!

Synology Migration from my DS209+ to my DS713+

I have just moved my blog from my Synology DS209+ to my new DS713+.

If you see this, it means that the migration is successful ;)

Click to Read More

The setup of the new DS713+ was straightforward and really easy using the setup Wizard of Synology. It took more time to screw the two drives (WD SE 2TB WD2000F9YZ) in the trays. Those trays look cheap (plastic) and fragile, but they are really easy to use, plug and unplug.

1/ I did use http://find.synology.com to search for my new DS. It worked fine and found both the 209+ and the 713+. From there I did start the setup on the 713+. It automatically download the latest version of DSM and install it.

2/ Once installed, a wizard opens within DSM to configured the most important features:

  1. Create a volume with the disks (I didn't create the default "Hybrid RAID (SHR)" as already suggested during the setup. I did a RAID 0 using the wizard instead).
  2. Users and Shared Folders
  3. File Station
  4. Other Packages (I did re-install all my favorite packages): Audio Station, Cloud Station, CouchPotato Custom*, DNS Server, Download Station, Git, Mail Server, Mail Station, Media Server, Photo Station, phpMyAdmin, Plex Media Server, Python, Python 3, Surveillance Station Time Backup, Video Station, Web Console*, Config File Editor*, Webalizer, WordPress
  5. ...

3/ In the Package Center, I did reconfigure the custom "Package Sources" (required for * above):

  1. http://packages.missilehugger.com : 'Config File Editor' and 'Web Console'
  2. http://packages.synocommunity.com : 'Couch Potato Server'
  3. http://www.cphub.net : 'Advanced Power Manager'
  4. http://packages.quadrat4.de : IPKG 'Bootstrap installer', ...

4/ Via the Control Panel  > Terminal, I did enable "telnet"

5/ I did next set a fix IP for the DS713+ on my DD-WRT router (under "static leases" in the "Service" tab) and did connect on the DS713+ via telnet to force it to renew its IP with the command "/etc/rc.network restart"

6/ I did also reinstall the package Perl, BootStrap Installer (Install Ipkg) and iPKGui  (manage ipkg packages) - both from packages.quadrat.de -  and configured the following package source: http://ipkg.nslu2-linux.org/feeds/optware/syno-e500/cross/unstable (name 'cross', type 'scr/gz', file 'cross-feed.Conf')

7/ I did install the "web-Console" package and logged in with admin/admin. Then I did restart the web-console after changing the password via the command (typing also the #) : #users modify admin

Notice: I didn't use Synlogy's migration wizard to backup and restore the full "configuration settings" as I wanted to clean a bit my NAS and restore/reconfigure only what I really still need. More details on migration methods are provided on Synology's wiki.

Click to Read 'Wordpress' Part

1/ Regarding WordPress, once the package installed, I did:

  1. Export the 'wordpressblog' database from my DS209+
  2. I did copy the following folders from the DS209+ on the DS713+
    1. \wordpress\wp-content\icons
    2. \wordpress\wp-content\themes
    3. \wordpress\wp-content\uploads
    4. \wordpress\wp-content\plugins
  3. I did restore that backup on the DS713+
  4. I had to reset the "Header Image" via Appearance>Themes>Customize.
  5. I did check that all the plugin's where enabled. All settings where correctly recovered from the backup restored previously.

I didn't re-install the plugin MultiDomain as I am now using the DNS package of Synology to solve the issue I had in the past when accessing my blog from my intranet or from internet.

2/ I did copy the other webpages in /web from the DS209+ onto the DS713+

3/ I did reconfigure the port-forwarding on my DD-WRT (via the tab "NAT/QoS") to forward the traffic on port 80 to the DS713+ instead of DS209+. I also configured "Wake on Lan" on the DD-WRT (via the "Administration" > "WOL") to be able to wake-up my new NAS although it should run 24/7.

Et voilà... the "web part" of the DS713+ is up and running :P

Click to Read 'Photo Station' Part

1/ To move the Photo albums, I did use Synology's "Main menu" > "Backup and Restore" feature on the DS209+.

  1. On the DS713+, enable the "Network Backup" service (without rsync) via "Main Menu" > "Network Backup". This is going to create a Shared Folder 'NetBackup'.
  2. Back to the DS209+, In the "Backup" tab of the "Backup and Restore" wizard, click create and select "Data Backup type".
  3. In the wizard, type a name for the backup and select "Network Backup (Synology Server)". Let the DS209+ find the DS713+ (clicking into the "server name" combo-box) and use this one as server name for the backup destination (fill manually the password for the username and pick "NetBackup" as shared folder. Keep in mind the name of the "folder" to be created in "NetBackup" to store the backup).
  4. In the tab where you can select application data, configuration, etc... pick
    1. In the "Application" part, select "Photo Station"
    2. In the "Shared folder" part, select "photo"
  5. And finally "Back up immediately after the wizard finished"

2/ Next, on the DS713+, using the same  "Main menu" > "Backup and Restore" feature, I did the restore

  1. In the "Restore" tab, click on "Restore" and select "data".
  2. In the wizard, select "Local Restoration" and keep next "NetBackup" and select the name of the "folder" where the DS209+ stored its backup.
  3. Do not select any "configuration settings to restore"
  4. Select however all "items to restore" in the next screen. You will see that there is a "conflict" for the Shared Folder "photo". No matter, the existing folder on the target will be overwritten.

Et voilà. It's magic: all the photo and thumbnails are restored, including the albums, smart albums, covers, etc...

One thing is however not restored via this process: the users' privileges... I presume that this is because I didn't restore the users table. I had to grant access to the users to each album manually via the "Parameters" > "User accounts" menu of Photo Station.

Click to Read 'Surveillance Station' Part

1/ To move the Surveillance Station settings, I did use also Synology's "Main menu" > "Backup and Restore" feature on the DS209+.

  1. First, I did disable all my camera in the Surveillance Station of the DS209+ via the "Main Menu" > "Surveillance Station" > "IP Camera"
  2. Next, I did delete all the records as I wanted to only migrate the "settings"
  3. Finally, I did a backup of 'surveillance' as I did for the Photo Station here above. I only had to provide another folder-name under 'NetBackup' than for the photo

2/ Next, on the DS713+, I did

  1. "Stop" the Surveillance Station, via "Package Center" > "Surveillance Station" > Action "Stop".
  2. Restore the 'surveillance' following the same procedure as for the Photo Station.
  3. Once the restore completed, "Run" the Surveillance Station, via "Package Center" > "Surveillance Station" > Action "Run".
  4. Go to the "Main Menu" > "Surveillance Station"  > "IP Camera" and re-enable the camera. You can see that not only the camera are restored, but also the patrol settings, etc...

Notice: the paid licences have been transferred !!! What is weird: I was able to re-enable the camera also on the DS209+. Both NAS were then consuming stream from all the camera... I was not expecting the licenses to be usable on several devices ?!

Click to Read 'Audio and Video Station' Part

1/ Simply copy the content of the Shared Folders "music" and "video" from DS209+ to DS713+. Audio Station and Video Station will re-index the files.

2/ Reconfigure Video Station (Collections and Custom Libraries must be redefined)

3/ Recreate your favorite Web Radio Station in the Audio Station

This is a bit of work but I didn't find a backup/restore similar to the one available for the 'photo' and the 'surveillance'. And I didn't want to restore the full configuration of my DS209+ as-is.

Click to Read 'Other' Part

1/ Reconfigure the other port-forwarding rules on the DD-WRT to transfer all required traffic to the DS713+:

  1. Admin: 5000
  2. WebDav and WebDav https: 8000 and 8443
    1. Enable WebDav via "Main Menu" > "Control Panel" > "WebDAV"
    2. Configure the port 8000 and 8443 resp. for http
  3. CouchPotato: 5050

2/ Reconfigure the WorkGroup via "Main Menu" > " Configuration Panel" > "Win/Mac/NFS" > "Windows File Service"

3/ Enable "Recycle Bin", "Windows ACL" and "File Indexing" on required shared folders via "Main Menu" > " Configuration Panel" > "Shared Folder" > (select a folder) "Edit".

4/ Reconfigured the "DNS server" as made on DS209+. Or, use the "Export Zone" > "Complete Zone settings" menu of the "DNS Server" on DS209+ and then "Create" > "Import Zone" menu of the "DNS Server" on the new DS.

5/ Recreate the MySQL Backup Task and the reconfigure Time Backup's tasks.

Click to Read 'DDNS' Part

I also had to register my DDNS' domain name olympe.diskstation.me for my new DS713+ instead of for my DS209+.

1/ Log in https://myds.synology.com

2/ Click on the "Unlink" icon on the row of your old DS.

3/ Select the old DS and click on "Delete" on the right side of the "DDNS status" header.

4/ Go now to the "Control Panel" of the new DS and click on "DDNS".

5/ Click on "Add" and re-register the DS with the domain name that used to be linked to the old DS.