Translation

(itstool) path: sect2/para
The following examples assume that the users already exist in the system. Before adding a user to the system, make sure to create their home dataset first and set the <option>mountpoint</option> to <literal>/home/<replaceable>bob</replaceable></literal>. Then, create the user and make the home directory point to the dataset's <option>mountpoint</option> location. This will properly set owner and group permissions without shadowing any pre-existing home directory paths that might exist.
3/4900
Context English Portuguese (Brazil) State
Sending Encrypted Backups over <application>SSH</application> Envio de backups criptografados pelo <application>SSH</application>
Sending streams over the network is a good way to keep a remote backup, but it does come with a drawback. Data sent over the network link is not encrypted, allowing anyone to intercept and transform the streams back into data without the knowledge of the sending user. This is undesirable, especially when sending the streams over the internet to a remote host. <application>SSH</application> can be used to securely encrypt data send over a network connection. Since <acronym>ZFS</acronym> only requires the stream to be redirected from standard output, it is relatively easy to pipe it through <application>SSH</application>. To keep the contents of the file system encrypted in transit and on the remote system, consider using <link xlink:href="https://wiki.freebsd.org/PEFS">PEFS</link>. O envio de fluxos pela rede é uma boa maneira de manter um backup remoto, mas apresenta uma desvantagem. Os dados enviados pelo link de rede não são criptografados, permitindo que qualquer pessoa intercepte e transforme os fluxos de volta em dados sem o conhecimento do usuário remetente. Isso é indesejável, especialmente ao enviar os fluxos pela Internet para um host remoto. O <application>SSH</application> pode ser usado para criptografar com segurança os dados enviados por uma conexão de rede. Como o <acronym>ZFS</acronym> requer apenas que o fluxo seja redirecionado da saída padrão, é relativamente fácil transmiti-lo através do <application>SSH</application>. Para manter o conteúdo do sistema de arquivos criptografado em trânsito e no sistema remoto, considere o uso do <link xlink:href="https://wiki.freebsd.org/PEFS">PEFS</link>.
A few settings and security precautions must be completed first. Only the necessary steps required for the <command>zfs send</command> operation are shown here. For more information on <application>SSH</application>, see <xref linkend="openssh"/>. Algumas configurações e precauções de segurança devem ser concluídas primeiro. Apenas as etapas necessárias para a operação do <command>zfs send</command> são mostradas aqui. Para mais informações sobre o <application>SSH</application>, consulte <xref linkend="openssh"/>.
This configuration is required: Essa configuração é necessária:
Passwordless <application>SSH</application> access between sending and receiving host using <application>SSH</application> keys Acesso <application>SSH</application> sem senha entre o host de envio e recebimento usando chaves <application>SSH</application>
Normally, the privileges of the <systemitem class="username">root</systemitem> user are needed to send and receive streams. This requires logging in to the receiving system as <systemitem class="username">root</systemitem>. However, logging in as <systemitem class="username">root</systemitem> is disabled by default for security reasons. The <link linkend="zfs-zfs-allow">ZFS Delegation</link> system can be used to allow a non-<systemitem class="username">root</systemitem> user on each system to perform the respective send and receive operations. Normalmente, os privilégios do usuário <systemitem class="username">root</systemitem> são necessários para enviar e receber fluxos. Isso requer o login no sistema de recebimento como <systemitem class="username">root</systemitem>. No entanto, o login como <systemitem class="username">root</systemitem> vem desabilitado por padrão por motivos de segurança. O sistema <link linkend="zfs-zfs-allow">ZFS Delegation</link> pode ser usado para permitir que um usuário não <systemitem class="username">root</systemitem> em cada sistema execute as respectivas operações de envio e recebimento.
On the sending system: No sistema de envio:
<prompt>#</prompt> <userinput>zfs allow -u someuser send,snapshot <replaceable>mypool</replaceable></userinput> <prompt>#</prompt> <userinput>zfs allow -u someuser send,snapshot <replaceable>mypool</replaceable></userinput>
To mount the pool, the unprivileged user must own the directory, and regular users must be allowed to mount file systems. On the receiving system: Para montar o pool, o usuário não privilegiado deve ser o dono do diretório e os usuários regulares devem poder montar sistemas de arquivos. No sistema de recebimento:
<prompt>#</prompt> <userinput>sysctl vfs.usermount=1</userinput>
vfs.usermount: 0 -&gt; 1
<prompt>#</prompt> <userinput>echo vfs.usermount=1 &gt;&gt; /etc/sysctl.conf</userinput>
<prompt>#</prompt> <userinput>zfs create <replaceable>recvpool/backup</replaceable></userinput>
<prompt>#</prompt> <userinput>zfs allow -u <replaceable>someuser</replaceable> create,mount,receive <replaceable>recvpool/backup</replaceable></userinput>
<prompt>#</prompt> <userinput>chown <replaceable>someuser</replaceable> <replaceable>/recvpool/backup</replaceable></userinput>
<prompt>#</prompt> <userinput>sysctl vfs.usermount=1</userinput>
vfs.usermount: 0 -&gt; 1
<prompt>#</prompt> <userinput>sysrc -f /etc/sysctl.conf vfs.usermount=1</userinput>
<prompt>#</prompt> <userinput>zfs create <replaceable>recvpool/backup</replaceable></userinput>
<prompt>#</prompt> <userinput>zfs allow -u <replaceable>someuser</replaceable> create,mount,receive <replaceable>recvpool/backup</replaceable></userinput>
<prompt>#</prompt> <userinput>chown <replaceable>someuser</replaceable> <replaceable>/recvpool/backup</replaceable></userinput>
The unprivileged user now has the ability to receive and mount datasets, and the <replaceable>home</replaceable> dataset can be replicated to the remote system: O usuário sem privilégios agora tem a capacidade de receber e montar conjuntos de dados, e o conjunto de dados <replaceable>home</replaceable> pode ser replicado para o sistema remoto:
<prompt>%</prompt> <userinput>zfs snapshot -r <replaceable>mypool/home</replaceable>@<replaceable>monday</replaceable></userinput>
<prompt>%</prompt> <userinput>zfs send -R <replaceable>mypool/home</replaceable>@<replaceable>monday</replaceable> | ssh <replaceable>someuser@backuphost</replaceable> zfs recv -dvu <replaceable>recvpool/backup</replaceable></userinput>
<prompt>%</prompt> <userinput>zfs snapshot -r <replaceable>mypool/home</replaceable>@<replaceable>monday</replaceable></userinput>
<prompt>%</prompt> <userinput>zfs send -R <replaceable>mypool/home</replaceable>@<replaceable>monday</replaceable> | ssh <replaceable>someuser@backuphost</replaceable> zfs recv -dvu <replaceable>recvpool/backup</replaceable></userinput>
A recursive snapshot called <replaceable>monday</replaceable> is made of the file system dataset <replaceable>home</replaceable> that resides on the pool <replaceable>mypool</replaceable>. Then it is sent with <command>zfs send -R</command> to include the dataset, all child datasets, snapshots, clones, and settings in the stream. The output is piped to the waiting <command>zfs receive</command> on the remote host <replaceable>backuphost</replaceable> through <application>SSH</application>. Using a fully qualified domain name or IP address is recommended. The receiving machine writes the data to the <replaceable>backup</replaceable> dataset on the <replaceable>recvpool</replaceable> pool. Adding <option>-d</option> to <command>zfs recv</command> overwrites the name of the pool on the receiving side with the name of the snapshot. <option>-u</option> causes the file systems to not be mounted on the receiving side. When <option>-v</option> is included, more detail about the transfer is shown, including elapsed time and the amount of data transferred. Um snapshot recursivo chamado <replaceable>monday</replaceable> é composto do conjunto de dados do sistema de arquivos <replaceable>home</replaceable> que reside no pool <replaceable>mypool</replaceable>. Em seguida, ele é enviado com o <command>zfs send -R</command> para incluir o conjunto de dados, todos os conjuntos de dados filho, snapshots, clones e configurações no fluxo. A saída é canalizada para o <command>zfs receive</command> em espera no host remoto <replaceable>backuphost</replaceable> através do <application>SSH</application>. Recomenda-se a utilização de um nome de domínio totalmente qualificado ou do endereço IP. A máquina receptora grava os dados no conjunto de dados <replaceable>backup</replaceable> no pool <replaceable>recvpool</replaceable>. Adicionar <option>-d</option> ao <command>zfs recv</command> sobrescreve o nome do pool no lado de recebimento com o nome do snapshot. A opção <option> -u </option> faz com que os sistemas de arquivos não sejam montados no lado do recebimento. Quando <option> -v </option> é incluído, mais detalhes sobre a transferência são mostrados, incluindo o tempo decorrido e a quantidade de dados transferidos.
Dataset, User, and Group Quotas Cotas para Datasets, Usuários e Grupos
<link linkend="zfs-term-quota">Dataset quotas</link> are used to restrict the amount of space that can be consumed by a particular dataset. <link linkend="zfs-term-refquota">Reference Quotas</link> work in very much the same way, but only count the space used by the dataset itself, excluding snapshots and child datasets. Similarly, <link linkend="zfs-term-userquota">user</link> and <link linkend="zfs-term-groupquota">group</link> quotas can be used to prevent users or groups from using all of the space in the pool or dataset. <link linkend="zfs-term-quota">As cotas para dataset</link> são usadas para restringir a quantidade de espaço que pode ser consumida por um determinado conjunto de dados. As <link linkend="zfs-term-refquota">cotas de referência</link> funcionam basicamente da mesma maneira, mas contam apenas o espaço usado pelo próprio conjunto de dados, excluindo snapshots e conjuntos de dados filho. Da mesma forma, as cotas para <link linkend="zfs-term-userquota">usuário</link> e para <link linkend="zfs-term-groupquota">grupo</link> podem ser usadas para impedir que usuários ou grupos usem todo o espaço do pool ou do conjunto de dados.
The following examples assume that the users already exist in the system. Before adding a user to the system, make sure to create their home dataset first and set the <option>mountpoint</option> to <literal>/home/<replaceable>bob</replaceable></literal>. Then, create the user and make the home directory point to the dataset's <option>mountpoint</option> location. This will properly set owner and group permissions without shadowing any pre-existing home directory paths that might exist. <op
To enforce a dataset quota of 10 GB for <filename>storage/home/bob</filename>: Para impor uma cota de dataser de 10 GB para o <filename>storage/home/bob</filename>:
<prompt>#</prompt> <userinput>zfs set quota=10G storage/home/bob</userinput> <prompt>#</prompt> <userinput>zfs set quota=10G storage/home/bob</userinput>
To enforce a reference quota of 10 GB for <filename>storage/home/bob</filename>: Para impor uma cota de referência de 10 GB para <filename>storage/home/bob</filename>:
<prompt>#</prompt> <userinput>zfs set refquota=10G storage/home/bob</userinput> <prompt>#</prompt> <userinput>zfs set refquota=10G storage/home/bob</userinput>
To remove a quota of 10 GB for <filename>storage/home/bob</filename>: Para remover uma cota de 10 GB do <filename>storage/home/bob</filename>:
<prompt>#</prompt> <userinput>zfs set quota=none storage/home/bob</userinput> <prompt>#</prompt> <userinput>zfs set quota=none storage/home/bob</userinput>
The general format is <literal>userquota@<replaceable>user</replaceable>=<replaceable>size</replaceable></literal>, and the user's name must be in one of these formats: O formato geral é <literal>userquota@<replaceable>user</replaceable>=<replaceable>size</replaceable></literal> e o nome do usuário deve estar em um destes formatos:
<acronym>POSIX</acronym> compatible name such as <replaceable>joe</replaceable>. nome compatível com o <acronym>POSIX</acronym>, como <replaceable>joe</replaceable>.
<acronym>POSIX</acronym> numeric ID such as <replaceable>789</replaceable>. ID numérico <acronym>POSIX</acronym>, como <replaceable>789</replaceable>.
<acronym>SID</acronym> name such as <replaceable>joe.bloggs@example.com</replaceable>. nome <acronym>SID</acronym>, como <replaceable>joe.bloggs@example.com</replaceable>.
<acronym>SID</acronym> numeric ID such as <replaceable>S-1-123-456-789</replaceable>. ID numérico <acronym>SID</acronym> , como <replaceable>S-1-123-456-789</replaceable>.
For example, to enforce a user quota of 50 GB for the user named <replaceable>joe</replaceable>: Por exemplo, para impor uma cota de usuário de 50 GB para o usuário chamado <replaceable>joe</replaceable>:
<prompt>#</prompt> <userinput>zfs set userquota@joe=50G</userinput> <prompt>#</prompt> <userinput>zfs set userquota@joe=50G</userinput>
To remove any quota: Para remover qualquer cota:
<prompt>#</prompt> <userinput>zfs set userquota@joe=none</userinput> <prompt>#</prompt> <userinput>zfs set userquota@joe=none</userinput>

Loading…

The following examples assume that the users already exist in the system. Before adding a user to the system, make sure to create their home dataset first and set the <option>mountpoint</option> to <literal>/home/<replaceable>bob</replaceable></literal>. Then, create the user and make the home directory point to the dataset's <option>mountpoint</option> location. This will properly set owner and group permissions without shadowing any pre-existing home directory paths that might exist.
<op
6 days ago
The following examples assume that the users already exist in the system. Before adding a user to the system, make sure to create their home dataset first and set the <option>mountpoint</option> to <literal>/home/<replaceable>bob</replaceable></literal>. Then, create the user and make the home directory point to the dataset's <option>mountpoint</option> location. This will properly set owner and group permissions without shadowing any pre-existing home directory paths that might exist.
<op
6 days ago
The following examples assume that the users already exist in the system. Before adding a user to the system, make sure to create their home dataset first and set the <option>mountpoint</option> to <literal>/home/<replaceable>bob</replaceable></literal>. Then, create the user and make the home directory point to the dataset's <option>mountpoint</option> location. This will properly set owner and group permissions without shadowing any pre-existing home directory paths that might exist.
<option><option>
a week ago
The following examples assume that the users already exist in the system. Before adding a user to the system, make sure to create their home dataset first and set the <option>mountpoint</option> to <literal>/home/<replaceable>bob</replaceable></literal>. Then, create the user and make the home directory point to the dataset's <option>mountpoint</option> location. This will properly set owner and group permissions without shadowing any pre-existing home directory paths that might exist.
<option><option>
a week ago
The following examples assume that the users already exist in the system. Before adding a user to the system, make sure to create their home dataset first and set the <option>mountpoint</option> to <literal>/home/<replaceable>bob</replaceable></literal>. Then, create the user and make the home directory point to the dataset's <option>mountpoint</option> location. This will properly set owner and group permissions without shadowing any pre-existing home directory paths that might exist.
<option>
a week ago
The following examples assume that the users already exist in the system. Before adding a user to the system, make sure to create their home dataset first and set the <option>mountpoint</option> to <literal>/home/<replaceable>bob</replaceable></literal>. Then, create the user and make the home directory point to the dataset's <option>mountpoint</option> location. This will properly set owner and group permissions without shadowing any pre-existing home directory paths that might exist.
<option><option><option><option>
a week ago
The following examples assume that the users already exist in the system. Before adding a user to the system, make sure to create their home dataset first and set the <option>mountpoint</option> to <literal>/home/<replaceable>bob</replaceable></literal>. Then, create the user and make the home directory point to the dataset's <option>mountpoint</option> location. This will properly set owner and group permissions without shadowing any pre-existing home directory paths that might exist.
<option><option><option><option>
a week ago
The following examples assume that the users already exist in the system. Before adding a user to the system, make sure to create their home dataset first and set the <option>mountpoint</option> to <literal>/home/<replaceable>bob</replaceable></literal>. Then, create the user and make the home directory point to the dataset's <option>mountpoint</option> location. This will properly set owner and group permissions without shadowing any pre-existing home directory paths that might exist.
<option><option><option>
a week ago
The following examples assume that the users already exist in the system. Before adding a user to the system, make sure to create their home dataset first and set the <option>mountpoint</option> to <literal>/home/<replaceable>bob</replaceable></literal>. Then, create the user and make the home directory point to the dataset's <option>mountpoint</option> location. This will properly set owner and group permissions without shadowing any pre-existing home directory paths that might exist.
<option><option>
a week ago
The following examples assume that the users already exist in the system. Before adding a user to the system, make sure to create their home dataset first and set the <option>mountpoint</option> to <literal>/home/<replaceable>bob</replaceable></literal>. Then, create the user and make the home directory point to the dataset's <option>mountpoint</option> location. This will properly set owner and group permissions without shadowing any pre-existing home directory paths that might exist.
<option>
a week ago
Browse all component changes

Things to check

XML syntax

The translation is not valid XML

Reset

Mismatched full stop

Source and translation do not both end with a full stop

Reset

Has been translated

Last translation was "<op".

Fix string

Reset

Glossary

English Portuguese (Brazil)
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: sect2/para
Source string location
book.translate.xml:40209
String age
5 months ago
Source string age
5 months ago
Translation file
books/pt_BR/handbook.po, string 6587