Best Practices
- The source and target nodes should be the same version,
- Information about the Avamar server's LAN IP address range should be provided to avoid address conflicts,
- The time-out setting should be high (Default time-out setting: 20 hours). Hfscheck and maintenance must not be triggered when a replication process is in progress,
- Launch the replication process when all backups are complete on the source node,
- To replicate an Avamar node, you first need to copy the client backups, domains, Groups, datasets, programmes and storage policies onto the target node.
Comparison between Avamar server replication (in Replicate mode) and server backup using Avamar agents
| Remote backup | Local backup + replication | |
| Deduplication / load balancing |
No difference. |
|
| Integrity | The daily integrity checking mechanism is the same | |
| Telecoms connections | Identical volume (total
deduplication) but during the backup window only |
Identical volume but during the predetermined replication window |
| Restoration | Limited by the connection to the Telehouse/KDDI platform | Unlimited |
| Storage | Limited by the connection to the Telehouse/KDDI platform | Unlimited |
Avamar offers revolutionary backup and restore solutions
- Total data deduplication limits the exponential growth of backup data,
- Reduces disk drive-based backup storage by up to 50 times,
- Quick, full, daily backups using existing networks,
- Reduced disk drive-based backup costs compared with tape backups,
Accelerated migration to disk drives as the main backup medium.
Avamar-compatible applications and operating systems
