![]() ![]() However, when I plug the HD into my Mac OSX, the name comes up as “Elements”, which is the WD brand. Is it possible to rename the HD? This seems to be the simplest solution. Either edit the backup task to point towards the new directory name, or rename the HD back to its original “usbshare1”. I figure there’s 2 possible solutions to “trick” Hyper Backup to relink to the task. From reading other forum posts, I think what happened is the HD was renamed when the photos HD with the same name was present. Eventually, I noticed the discrepancy was Hyper Backup expects to see “usbshare1” and the videos HD appears as “usbshare2”. I checked permissions and the Hyper Backup settings. In DSM, the USB drive was connected and the files appeared in File Station. However, when it was time to back up the video drive, Hyper Backup indicated there was no disk to backup to. Anyway, the photos backup completed with no issue. I thought this would save me the few extra seconds it would have taken to unplug the first drive after it completed its back up and plug in the second. Seeing there’s 2 USB ports in my Synology NAS, I plugged both drives in. For the past 6-8 months, I’ve had no problems and the backups are pretty quick, just updating changes. Right-click on each of the users home folder in the folder-tree on the left and select Permissions. I manually run the backup on the 2 HDs monthly and store them in a safe. This is a secondary backup to my C2 cloud backup of my whole drive. I even converted the 'photo' share to Windows ACL as Synology suggested but cannot still find a sensible way to give / deny permission like in the good old DSM 6.2.4 days. To make this post easier to follow, let’s say one HD backs up photos and the other one backs up videos. Hello, In old Photo Station I could very easily give/deny access to folders with photographs. I have a media folder that I’m backing up between 2 external USB drives on Hyper Backup. However, I’m hoping there’s a quick fix, instead of having to start over with a brand new backup. Otherwise, I would probably reinstall DSM to avoid any problems.First of all, I realize there is a “user-error” component to my problem. ![]() Right now, my NAS seems to run stable and I did not notice any changes but I want to avoid problems in the future, so I was wondering if someone could tell me, if these are the correct ownership and permission settings for this directory. Running ls -al as the root user (after running cd) gives me the following ownership and permissions: ls -alĭrwx- 4 root root 4096 Jul 8 20:20. However, I don't know, if this ownership and permission setting is correct now. which I supposed to be the correct ownership. I realized this mistake immediately and ran chown -R root:root. not on the directory for the repos but instead in the root directory itself, changing the ownership of the root directory to the gituser account. While setting up the folder to contain the repos, I unfortunately ran chown -R gituser:administrators. But to accelerate speeds and bandwidth even more, the tech industry wants to. I was trying to setup the Git server for Synology DSM 6.2 and to do so, I logged in via SSH using the root user (switching from the admin account during the SSH session). (Credit: Getty Images) New generations of PCI Express techthe interface used across PC partsare already on the way. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |