I don't think it is good idea. Because synxproxy to Japan trans pacific network connection bandwidth is narrow (~ 5Mbps).
If you want to setup some kind of redundancy of push primary in Japan, we should build some kind of pushproxy and management system of primary pusy mirror backend. >>>>> In <20130303075058.c44c71f5a6785883bddec...@debian.or.jp> >>>>> Hideki Yamane <henr...@debian.or.jp> wrote: >> Package: mirrors >> Severity: normal >> X-debbugs-CC: debian-mirr...@lists.debian.org, bo...@debian.or.jp >> >> Hi, >> >> Some of you may know, I've started debian-mirror.sakura.ne.jp. >> >> http://henrich-on-debian.blogspot.com/2013/02/introducing-debian-mirrorsakuranejp.html >> >> Now it is pushed-mirror under hanzubon.jp, and I think it's better to be >> pushed >> from upstream syncproxy if we can. >> >> The reason is, sakura mirror and other mirrors pushed from hanzubon.jp is >> providing >> ftp.jp.debian.org. ftp.jp.d.o has some robustness mechanism that if primary >> one goes >> down or not sync some days and be obsolete, then DNS entry will switch to >> point >> another mirror. However, if hanzubon.jp archive will stop or be corrupted, >> then >> **all** of those mirrors are same state. If sakura mirror can get updated >> archives >> from syncproxy, ftp.jp.d.o get more robustness IMO. >> >> Could you consider to add sakura mirror as syncproxy leaf, please? >> >> -- >> Regards, >> >> Hideki Yamane henrich @ debian.or.jp/org >> http://wiki.debian.org/HidekiYamane -- ISHIKAWA Mutsumi <ishik...@hanzubon.jp>, <ishik...@debian.org> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org