We have noticed the folowing "problems" with this design: But all have the same backup stratigy:īackup => to Pri site local (14 restore points, most jobs on Inremental, some due to size set to reversed incremental)Ĭopy 1 => to Sec site local (7 restore points)Ĭopy 2 => to Sec site dedupe (week,month,year schedule in place) We have 5 jobs, all with particular guest settings. The accelerator eliminates traffic, but increases copy times by 5x. No WAN accalerator used as the bandwith is to big. Repository set to decompress and align data.Ħ00mbit/s connection between sites. For DR/Instant recovery if primairy site fails.Ĭopy 2: Data Domain via CIFS. For single file, application restore and instant reovery.Ĭopy 1: Proxy + Repository on fysical server with enough fast local storage for 7 restore points. 7.8TB of used storage.īackup: Proxy + Repository on fysical server with enough fast local storage for 14 restore points. ![]() ![]() VMware production cluster with 7x ESXi 5.1 on EMC FC VNX5300 storage. I would like to discuss the best setup for our situating regaring the use of multiple sites and a EMC Data Domain unit D640.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |