avtar --create --id=MaryAdmin@/NorthAmerica/USA --path=/NorthAmericaa/USA/win01.

avamar.edu C:\Abackup --label="Marybkup"

avtar --create --id=MaryAdmin@/NorthAmerica/USA --path=/NorthAmericaa/USA/win01.
avamar.edu "C:\Documents and Settings" --label="Marybkup"
1. From 6.0 Avamar runs on 64-bit SUSE Linux Enterprise Serevr 11 OS.
2. There are 3 logins:
1. Root: required for instyalling rpms.
2. admin: for support operations.
3. dpn: maintenance user ID. Avamar own cron jobs.
3. BASH is the OS standard CLI.
4. Avamar internal user accounts are different such as root, MCUser, repluser.
5. Avamar directory structure;
/usr/local/avamar:
bin: binaries and scripts
src: customer tar files and web download files
etc: configuration files
var: cron and administrator logs
>symlinked to /data01/avamar/var
6. Data, checkpoints and logs are located in one or more /data0n directories.
cp.* are checkpoint directories.
cur directories contains data and log files.
> *.inx: index stripes
> *.dat: data stripes
> *.chd: chunk header lists
> *.par: local parity stripes
> *.usd: user accounting data
> *.wlg: write log file
> stripidA.stripedidB
7. Nodes are designated in MODULE.NODE format.
8. Avamar refers top the storage nodes in two ways:
physical node number: are based on ten node's IP address position in the
probe.xml file.
Logical node number: when node is added to the system. A node's logical
number do not change even if the node's IP address or position in the probe.xml
file changes.
9. probe.xml file is located at /sur/local/avamar/var
10. Use nodedb program commands to add, delete, update and display objects in th
e probe.xml file.
11. nodenumbers utility: compares the contents of probe.xml to the output of the
avamaint nodelist command and denotes any out of sequential order conditions.
12. mapall utility: use to perform operations on all nodes in an Avamar server.
> mapall --all '/bin/hostname'