avamar server 便携版本是一个vmware的虚拟机，rhel4操作系统作为avamar server的载体，可能定制化了一些EMC自己的东西 .
测试安装环境：
1. Server : DELL R610 至强 2.0Ghz 8核,8GB MEM,500GB硬盘，开启CPU虚拟化.
2. OS : Windows 2008 R2 64位
3. VMWARE ISO ： avamar-kickstart-rhel4.8-64-0031
4. 安装包 : v5.0.4.30-customer_unified-v5.0.106.28
5. 手册 : Avamar 5.0 Lab Guide 1.2-Final
安装完虚拟机之后，需要根据手册安装avamar server , 配置avamar server的主机名，域名，IP，等信息。
之后avamar server服务器上会多出一个WEB SERVICE，可以用来管理avamar server.
默认 :
USER : MCUser
PWD : MCUser1
在备份之前，首先要注册备份机，方法是在备份机上安装agent，并且修改/etc/hosts，执行注册（将客户机的信息注册到avamar server）。
管理客户机需要登录avamar server web service ，需要在/etc/hosts或windows里面增加一个条目，用于解析avamar server的地址
管理客户机可以选择安装avamar GUI , 以便管理.
管理可以通过
1. http://avamar_server_host
2. http://avamar_server_host/em
3. 客户机avamar GUI
进行管理.
avamar server后台使用的是postgresql数据库。一共起了两个集群，端口分别是5555和5556， emdb和mcdb.
mcdb=# \dt
List of relations
Schema | Name | Type | Owner
--------+-------------------------+-------+-------
public | activities | table | admin
public | activity_errors | table | admin
public | activity_types | table | admin
public | audits | table | admin
public | axion_systems | table | admin
public | change_id | table | admin
public | cl_msg_cache | table | admin
public | cl_plugins | table | admin
public | clients | table | admin
public | compatibility | table | admin
public | datasets | table | admin
public | ds_commands | table | admin
public | ds_excludes | table | admin
public | ds_includes | table | admin
public | ds_targets | table | admin
public | ev_catalog | table | admin
public | ev_catalog_ext | table | admin
public | ev_counter | table | admin
public | ev_cus_body | table | admin
public | ev_cus_cc_list | table | admin
public | ev_cus_codes | table | admin
public | ev_cus_prof | table | admin
public | ev_cus_prof_params | table | admin
public | ev_cus_rpt | table | admin
public | ev_cus_snmp_contact | table | admin
public | ev_cus_syslog_contact | table | admin
public | ev_cus_to_list | table | admin
public | ev_data_entry_type | table | admin
public | ev_pending | table | admin
public | ev_sys_prof | table | admin
public | ev_unack | table | admin
public | events | table | admin
public | gcstatus | table | admin
public | gr_members | table | admin
public | group_proxy_mapping | table | admin
public | groups | table | admin
public | hfscheck_failures | table | admin
public | log_parse_info | table | admin
public | mgmt_client | table | admin
public | plugin_can_restore | table | admin
public | plugin_catalog | table | admin
public | plugin_depends_upon | table | admin
public | plugin_flag_groups | table | admin
public | plugin_flag_pulldown | table | admin
public | plugin_flags | table | admin
public | plugin_options | table | admin
public | plugin_state | table | admin
public | property_value | table | admin
public | proxy_client | table | admin
public | proxy_datastore_mapping | table | admin
public | repl_activities | table | admin
public | repl_backups | table | admin
public | report_filter | table | admin
public | reports | table | admin
public | retention_policies | table | admin
public | sc_recur | table | admin
public | schedules | table | admin
public | snapshot | table | admin
public | snapup_history | table | admin
public | sv_dpn_stats | table | admin
public | sv_elog_cache | table | admin
public | sv_node_space | table | admin
public | sv_node_util | table | admin
public | vm_client | table | admin
public | vm_datastore | table | admin
(65 rows)
emdb=# \dt
List of relations
Schema | Name | Type | Owner
--------+---------------------+-------+-------
public | activities | table | admin
public | activity_errors | table | admin
public | axion_server | table | admin
public | checkpoints | table | admin
public | compatibility | table | admin
public | dpn_info | table | admin
public | emaxion_system | table | admin
public | ev_catalog | table | admin
public | ev_catalog_ext | table | admin
public | ev_unack | table | admin
public | ev_unack_count | table | admin
public | hfscheck_failures | table | admin
public | replication_info | table | admin
public | status_descriptions | table | admin
(14 rows)
下面是通过DBvisualizer产生的ER视图:
由于avamar 采用的是源端去重技术，因此在效率上非常高。
avamar 带 DB2 ORACLE的备份插件，所以备份起来比较方便。但是对于PostgreSQL,需要自己写脚本，然后调用mccli来备份。
下面是一些简单的测试:
还原的时候出了点小问题，还原的SIZE与原始目录有差异。EMC的回复：
This is because of sparse file. For sure the data backup & restored is identical.
du commands will report the block size used for the object but not the actual file size.
A sparse file is a file with empty space, or gaps, left open for future addition of data.
If the empty spaces are filled with the ASCII null character and the spaces are large enough, the file will be sparse, and disk blocks will not be allocated to it.
http://bugs.avamar.com/show_bug.cgi?id=5971
By default --restore-sparse-threshold=128 meaning that only regions larger than 128K bytes will be considered sparse. Smaller regions will be written as sequences of zeros.