Continuing to work through #GCP training – having gotten my #ACE, I now need to get my #PCA.
At any rate, one of the training-modules was talking about data transfer times and popped up a size/rate table to show transfer-times. It instantly transported me back to when I was doing DR-related delivery-consulting.
I still remember one customer being pissed when I'd finished setting up their storage-replication and declared, "well, I'll see you in about 21 days to verify that we're actually finished and functional". They were incredulous, sputtering about "how can you possibly say 21 days". I'd reminded them that I'd noted that their replication-bandwidth was objectively too small (while they had a T3, their data set was large and they couldn't get their networking people to remove the session-limits that were constraining the replication to a fraction of that T3's capability). We'd spent a couple days benchmarking and working with their networking people to try to address the discrepancy between their theoretical bandwidth and the observed bandwidth. In fairness, they probably would have been ill-advised to dedicate the entirety of the T3's bandwidth to replications — since they presumably had other projects that needed some of its bandwidth — but the amount they were able to allocate to the storage replication was way too low. I'd given them an initial transfer-time estimate, the day prior, based on my benchmarking and the first couple hours of the replication's sync-up. My return the next day was mostly to confirm that things were moving along as expected — so that I didn't have to revise my estimate (fortunately, over the intervening 16 hours, my numbers had stayed dead-on).
Just to add some gas to the fire:
• I reminded them that they had had the option to speed up the initial sync by seeing it with a tape-based restore – which would have required them to ship tapes from NJ to AZ, import the tapes into their DR site's tape library system, then do a restore to the DR site's storage array
• I pointed out to them that, with such a low transfer-rate, if they ever had link-loss, it could take them hours to days to get back in sync. I further pointed out and that, worst case (i.e., on a long-enough link-outage), the replication-software might declare the sync "stale" and they'd have to re-initialize and re-do the transfer.
This was probably 2005 or 2006. So, it's not that they had a ton of data to transfer, it's just that cross-country private circuits weren't available with nearly as high of transfer speeds and what options were available were silly-expensive.
Am Samstag, dem 5. April trafen wir uns zum Gruppentreffen in der mobilen Jugendarbeit Backnang.
In kleiner und gemütlicher Runde bemalten wir Plastik-Ostereier und sprachen über kommende Events, wie CSD's im Sommer und Aktionen anderer LGBTQIA+ Gruppen.
Die aktuelle Situation für uns Queers, sowohl gesamtpolitisch, als auch im Alltag, wurde ebenfalls besprochen. Wir teilten unseren Frust und überlegten Strategien, wie wir unsere Wut verarbeiten und sogar nutzen könnten. Teilnehmende erzählten von ihren Erfahrungen und welche Formen der Selbstfürsorge für sie funktionieren.
Dazu gab es Snacks und Brezeln.
. 
Komm zum nächsten Rems-Queer-Kreis Orga Treffen am Mittwoch, den 16.04.2025 ab 17:35 Uhr. Wir treffen uns in der Backnanger Innenstadt (Adresse auf Anfrage). Zusammen diskutieren wir unter anderem über unsere Gruppentreffen im Frühjahr und Ausflüge wie einen Besuch beim CSD Schwäbisch Hall und der trans Pride Stuttgart.
rk T