SYNOLOGY NAS snapshot replication使用注意事項

去年(2017)七月購入1817 + 兩台, 既供NFS及SMB使用,當然也會使用其備份軟体!!SYNOLOGY提供了許多備份軟体可供使用,如SYNOLOGY SNAPSHOT REPLICATION, HYPER BACKUP, ACTIVE BACKUP系統, CLOUD SYNC等,可說相當多元!

DSM 6.0 後所新增的功能,最吸引我的便是快照技術,及遠程快照複寫的功能!!

只是使用這個功能時,可能需注意,它的CPU LOADING很重!!尤其是新建的replication job. 它會起3-4個processes, 可能佔用的CPU LOADING達到50-70%之間,愈大的資料夾就會佔用愈久,即便平日的同步,也至少佔用20-30%左右!!

後來才得知原廠說明,目前的版本,並非原生的BTRFS,必須等到2018年4月份,SYNOLOGY會出DSM 6.2版,屆時它才是原生的BTRFS,根據原廠告知,它的效能問題才能得到解決,且讓我們拭目以待吧!!

若想觀察其效能,除了WEB管理界面上的資源監控,也可登入SSH CONSOLE,使用HTOP指令去看…



AD Disaster Recovery on VM environment

Virtualization should be a very mature skill for years. Today I tried one thing and got a successful result, hope it’s also helpful for you.

Environment introduction as below:

(1) production AD domain controller ran on VLAN 1

(2) a clone VM which made by 3 months ago ran on VLAN 50

(3) using WSB, backup production AD DC’s C Drive on local D drive.

so, is it possible to copy production’s backup material to vlan 50 DC to sync domain information between each other?

the answer is yes!! of course.

below is what i was doing today.

(1) NAS sync the backup folder from production DC.

(2) VLAN 50 which be cloned DC got the backup from NAS.

(3) in VLAN 50 DC, ran a command as below:
wbadmin restore catalog, for detailed, you could review it at

(4) above will let your system think it’s backup by itself.

(5) and then restart vlan 50 dc to be under Directory Services Restore Mode.

(6) after it’s rebooted, execute the command as below

weadmin get versions

to find out if it’s the newest backup just done by production DC.

(7) and then execute the restore command as below

wbadmin start systemstaterecovery -version:<VersionIdentifier>

version identifier, please refer to the get version result as step 6.

(8) and then you will sync two DCs’s data completely.

enjoy it.