Beruflich Dokumente
Kultur Dokumente
Scripts Repository:
ftp://ftp.avamar.com/software/scripts/
Software Repository:
ftp://ftp.avamar.com/software/
CommandLine
Dpnctl status
Add key -
ssh-agent bash
ssh-add ~dpn/.ssh/dpnid
su - admin
ssh-agent bash
dstpassword=8RttoTriz
HEALTHCHECK / ANALYSIS
healthcheck.pl to gather most of the data and avmaint license ava to get the licensed
amount.
Login to the utility node as admin
su - admin
Capacity.sh - Check to see if grid is running steady state and top client users
i.e. --days=365
REPORTS
DPNSummary try and get as far back as possible on dates
MISC Stats 1
Client Plugins
CAPACITY
SIZING
The configurator has implemented a very conservative algorithm with respect to initial
commonality, i.e. it sums up all primary storage and treats this as a SINGLE host
However, when you run the initial scan, then the first box will add about 70% new data
and all subsequent boxes will add only another 0,3% ( or 1 3 % worst case) new data.
This will reduce your config significantly ..
INGEST
MultiNode 3to5 GB / HR/ NODE
BACKUP / SCANNING
RESTORE
The numbers we use are 50 GB/hour per storage node. Max is 16 nodes. All storage
nodes can be selected to participate in a restore, which would then be 800GB/hr for a full
Avamar grid.
REPLICATION
Plan Replication to be in 8 hour windows
Desktop / Laptop
Full Avamar Grid can support 5,000 clients. Consider using smaller nodes for
additional connections when sizing out. 17 concurrent connections per node
AVALANCHE
The utility and spare are not in the node list. In this case, you have 6 active storage nodes. You
cannot determine retention settings via Avalanche. The only way to determine the size of the
nodes is to look at the nodelist*utc.xml file. Its a bit convoluted, but heres the instructions.