Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revisionLast revisionBoth sides next revision | ||
remote_mount_plugin_for_omv5 [2021/02/12 22:30] – [Use Cases] crashtest | remote_mount_plugin_for_omv5 [2022/07/28 17:24] – crashtest | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | < | + | < |
{{ : | {{ : | ||
Line 6: | Line 7: | ||
\\ | \\ | ||
\\ | \\ | ||
- | If preferred, this document | + | This document |
\\ | \\ | ||
- | {{ :underconstruction.jpg? | + | \\ |
+ | [[https://translate.google.com/ | ||
+ | [[https:// | ||
+ | [[https:// | ||
+ | [[https:// | ||
\\ | \\ | ||
===== The Remote Mount Plugin ===== | ===== The Remote Mount Plugin ===== | ||
Line 24: | Line 29: | ||
===== Uses for Remote Mount ===== | ===== Uses for Remote Mount ===== | ||
- | Remote Mount is useful for mounting, accessing and replicating network shares, located on another LAN server or a LAN client. | + | * Remote Mount is useful for mounting, accessing and replicating network shares, located on another LAN server or a LAN client. |
- | \\ | + | |
- | \\ | + | * **Remote Mount makes the creation of a full Backup Server relatively easy**, with no command line operations required. |
- | Along with setting up Remote Mount, this document will provide a practical example where Remote Mount and Rsync are used for replicating a network share. | + | |
- | \\ | + | |
- | \\ | + | |
===== Install the Remote Mount Plugin ===== | ===== Install the Remote Mount Plugin ===== | ||
Line 56: | Line 58: | ||
---- | ---- | ||
- | On the Primary server; under **Access Rights Management**, | + | **On the Primary server**:\\ |
+ | \\ | ||
+ | Under **Access Rights Management**, | ||
\\ | \\ | ||
\\ | \\ | ||
Line 144: | Line 148: | ||
\\ | \\ | ||
\\ | \\ | ||
- | For users who are interested only in mounting a remote share, this concludes the installation, configuration, of the Remote Mount plugin. | + | For users who are interested only in mounting a remote share, this concludes the installation |
\\ | \\ | ||
{{ : | {{ : | ||
Line 181: | Line 185: | ||
---- | ---- | ||
\\ | \\ | ||
- | Now we have two shared folders. | + | Now we have two shared folders. |
\\ | \\ | ||
Line 190: | Line 194: | ||
- | ===== Setting up an Rsycn Job ===== | + | ===== Setting up an Rsync Job ===== |
\\ | \\ | ||
- | First note that the job type is **Local**. | + | First note that the job type is **Local**. |
\\ | \\ | ||
\\ | \\ | ||
Line 222: | Line 226: | ||
\\ | \\ | ||
\\ | \\ | ||
- | It's necessary to change ownership (**chown**) to the local root account and the local users group, and to modify access permissions (**chmod**). In this case **--chmod=0775** and **--chown=root: | + | It's necessary to change ownership (**chown**) to the local root account and the local users group, and to modify access permissions (**chmod**). In this case '' |
\\ | \\ | ||
\\ | \\ | ||
Line 279: | Line 283: | ||
\\ | \\ | ||
- | * After the first replication event is complete, in subsequent jobs, rsync will only transfer new and changed files. | + | * After the first replication event is complete, in subsequent jobs, rsync will only transfer new and changed files. |
* In the Rsync Job's options, with the “**Keep Partially Transferred Files**” switch **ON**, even if a job is interrupted with a reboot or for some another reason, transferred files are not lost. | * In the Rsync Job's options, with the “**Keep Partially Transferred Files**” switch **ON**, even if a job is interrupted with a reboot or for some another reason, transferred files are not lost. | ||
* Turning the **Delete** switch **OFF**, may provide some degree of protection against accidentally deleted files. | * Turning the **Delete** switch **OFF**, may provide some degree of protection against accidentally deleted files. | ||
Line 392: | Line 396: | ||
\\ | \\ | ||
\\ | \\ | ||
- | While not for beginners, setting up automated and self purging snapshots is within the capability of a Computer or Linux enthusiast. | + | While not for beginners, setting up automated and self purging snapshots is within the capability of a Computer or Linux enthusiast. |
---- | ---- | ||
Line 400: | Line 404: | ||
\\ | \\ | ||
* Log into OMV's GUI, on the **Backup Server**. | * Log into OMV's GUI, on the **Backup Server**. | ||
- | * Under **Services**, | + | * Under **Services**, |
* Under **Services**, | * Under **Services**, | ||
* Notify users to use the Backup Server until further notice. | * Notify users to use the Backup Server until further notice. | ||
+ | * On the **Primary Server**, under **Services**, | ||
\\ | \\ | ||
===== The Bottom Line ===== | ===== The Bottom Line ===== | ||
\\ | \\ | ||
- | The Remote Mount Plugin and Openmediavault' | + | The Remote Mount Plugin and Openmediavault' |
{{ : | {{ : | ||
Line 425: | Line 430: | ||
**chown** is used to reset ownership and group access on incoming foreign files.\\ | **chown** is used to reset ownership and group access on incoming foreign files.\\ | ||
In the following, the left hand side of the colon is the “Owner” (**root**). | In the following, the left hand side of the colon is the “Owner” (**root**). | ||
- | '' | + | '' |
\\ | \\ | ||
**Others**, not part of the command, is any username that is NOT specifically called out as the “owner” or any member of the group “users”.\\ | **Others**, not part of the command, is any username that is NOT specifically called out as the “owner” or any member of the group “users”.\\ | ||
Line 431: | Line 436: | ||
**chmod** is used to define the permissions applied to the Owner, the Group, and others.\\ | **chmod** is used to define the permissions applied to the Owner, the Group, and others.\\ | ||
\\ | \\ | ||
- | '' | + | '' |
On the Primary (remote) server, [[https:// | On the Primary (remote) server, [[https:// | ||
Line 439: | Line 444: | ||
(OMV's standard Linux permissions)\\ | (OMV's standard Linux permissions)\\ | ||
- | **Owner: | + | **Owner: |
- | **Group: | + | **Group: |
- | **Others: | + | **Others: |
\\ | \\ | ||
{{ :: | {{ :: |