UNIX notes

Há mais de uma maneira para restaurar um arquivo que tenha sido copiado com o software de backup da IBM, TSM.

Eu gosto de usar a linha de comando. A partir da shell do Unix pode-se executar o comando:

dsmc restore ‘[arquivo a ser restaurado]‘ ‘[destino do arquivo]‘ <opções>

Ex:

dsmc restore ‘/home/usuario/teste.txt’ ‘/tmp/’ -subdir=yes -pick -inactive

O exemplo acima vai restaurar o arquivo /home/usuario/teste.txt no /tmp. As opções utilizadas acima não são obrigatórias:

-subdir: Com subdir igual a yes, no caso de restaurar um diretório, ele irá restaurar toda estrutura de subdiretórios abaixo dele. Muito útil para restore de diretórios.

-inactive: Vai listar as versões não ativas do backup que ainda não expiraram.

-pick: Esta opção vai listar os arquivos ao invés de já efetuar o restore. É muito útil para primeiro visualizar o arquivo e então selecioná-lo para o restore.

É possível também, ao invés de usar o “dsmc restore” direto na shell do Unix, chamar a linha de comando do TSM com o comando “dsmc” e então, usar a opção restore ou outros comandos do TSM:

# dsmc

tsm> restore ‘/home/arquivo.xxx’ ‘/tmp/’ -subdir=yes -pick -inactive

Mais informações no Manual da IBM de TSM para Unix, “Backup-Archive Clients Installation and User’s Guide”:

http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/topic/com.ibm.itsmc.doc_5.3.3/ans50000.pdf

As informações a seguir foram escritas num Forum do “LinusQuestions.org” pelo usuário “Harry Seldon“.

Achei um resumo útil e decidi salvar aqui no “meu” bloco de notas.

Fonte: http://www.linuxquestions.org/questions/aix-43/aix-default-user-list-612651/

“I work at a company that gets audited all the time. The ones we’re most commonly asked to remove are guest, lpd, uucp, nuucp (if it’s there) and imnadmin. Here’s a list of accounts I put together about a year ago; most of it is relevant, I think:

daemon - The daemon user account exists only to own and run system server processes and their associated files. This account guarantees that such processes run with the appropriate file access permissions.

bin - The bin user account typically owns the executable files for most user commands. This account’s primary purpose is to help distribute the ownership of important system directories and files so that everything is not owned solely by the root and sys user accounts.

sys - The sys user owns the default mounting point for the Distributed File Service (DFS) cache, which must exist before you can install or configure DFS on a client.

adm - The adm user account owns the following basic system functions:
* Diagnostics, the tools for which are stored in the /usr/sbin/perf/diag_tool directory.
* Accounting, the tools for which are stored in the following directories:
o /usr/sbin/acct
o /usr/lib/acct
o /var/adm
o /var/adm/acct/fiscal
o /var/adm/acct/nite
o /var/adm/acct/sum

uucp - Owner of hidden files used by uucp protocol. The uucp user account is used for the UNIX-to-UNIX Copy Program, which is a group of commands, programs, and files, present on most AIX systems, that allows the user to communicate with another AIX system over a dedicated line or a telephone line.

guest - Allows access to users who do not have access to accounts.

nobody - The nobody user account is used by the Network File System (NFS) to enable remote printing. This account exists so that a program can permit temporary root access to root users

lpd - Owner of files used by printing subsystem. This account has been disabled.

imnadm - IMN search engine used for Documentation Library Search.

lp - Possibly something to do with printing.

invscout - Surveys the host system for currently installed microcode or Vital Product Data (VPD).

snapp - The account that manages Snapp, an extensible, XML-based application that provides a menu-driven interface for UNIX system administration tasks on a handheld PDA.

sshd - The user account for managing the sshd service.”