Below questions would help in providing easy solution.

What is the bandwidth between your remote site to DC? What is the size of servers in your remote site?  Are those servers hosted in ESX?

Consider the following :

1. Timezone difference between DC and Remote site.

2. Off -Businesss hour backup window

3. Amount of Data for initial seeding and type of data(FS/DB/Exchange/other application data)

4. Rate of change in the data (Daily Incr  backups data size)

5.Bandwidth and latency between the sites.

Hope this will help for your planning.

Also you can try running manual backup with allow overtime option, if you are using Avmr 7.x that would help to run the backup duing maintenance window.

Regards

Maganti

Also consider 'seeding' the data if there is a large amount of it and the bandwidth between sites is limited

This KB is a little old but it describes the principle of seeding

108535 - Best practices when backing up remote clients via a WAN

Best way... USB Drive seeding - send the data on External drive to the DC and run incremental backup for the remote site All set !

Thank you all for the detailed information in the very short time.

I have already got all the above mentioned information, I am looking for the best practices for backing up the remote site clients.

It's not very clear what your configuration is, and what you are trying to achieve. How many remote sites are we talking about?

The only general tips I can give are:

- Don't run backups when the WAN bandwidth is used by important applications (so usually that means backup time is evening/night)

- Only backup the data you really need

- Perform test restores (no point in having a backup if you can't restore it)

There's not much to do on the clients themselves. Just install the Avamar client and activate it to the Avamar server in the appropriate domain. Everything else is done in the Avamar Administrator console.

If backups are consuming too much bandwidth you can throttle it (either for the client or a dataset)

The good part is the de-dup is done at that client side.

so after you get your first backup done, after that there is less data that has to be transmitted.

Consider you time zones.  7 pm EST (when most everybody is gone on the EAST coast, the WEST coast is still working so not a good time to backup their server).

A small pipe would make it slower, but it still works great.

If you're looking for the best practices for backing up the remote site then choose remote backup solution. I am familiar with one of the finest remote backup solution i.e CloudBacko. I recommend because I had used it in the past .