if you care, planned UF outage this weekend

[fly]

Moving servers, so it may take a few for DNS to get updated...

 

[Valve1138]

Okies.

Don't forget to flush your DNS cache boys and girls.

 

[b_sinning]

It was nice knowing you guys.

 

[Jonny_B]

It been a hell of a ride. Catch you on the flip side.

 

[shawndavid]

It's a good thing I have a life on the weekends.

 

[Valve1138]

DON'T CROSS THE STREAMS!

 

[Floptical]

A real admin would have a live replication copy of the site on the new server and have zero downtime.....and you wonder why you can't get a job sitting around eating berries and watching King of the Hill.

 

[Syrup Beaver]

Very well then.

Make sure you give the software it's massage.

 

[Syrup Beaver]

A real admin would have a live replication copy of the site on the new server and have zero downtime.....and you wonder why you can't get a job sitting around eating berries and watching King of the Hill.

A REAL admin would them in separate data centers in case of a disaster.

 

[fly]

A real admin would have a live replication copy of the site on the new server and have zero downtime.....and you wonder why you can't get a job sitting around eating berries and watching King of the Hill.

Fuck mysql replication over a WAN. and fuck you too.

 

[Syrup Beaver]

You need a hardware-based replication technology, forget database replication.

 

[Floptical]

I hear Netapp has some good hardware replication products as well as Snap Manager for SQL...

 

[Shalimar]

you guys could all go over to the huffington post all weekend!!!

 

[Duke]

Maybe this will give us a reason to go to gators.

 

[Floptical]

Maybe this will give us a reason to go to gators.

Now only if they had a Gators in Brandon.

 

[Shalimar]

hahahahaha..



sunday should be big.. big finale and all.

 

[Coqui]

Change Control requires two weeks notification. Why wasn't I notified?

 

[OzSTEEZ]

you guys could all go over to the huffington post all weekend!!!

Or maybe some other site? *nudge nudge*

 

[Josh]

Set the TTL in your dns zone file to something low, like 500 seconds. Thus the changes would be propegated more quickly across the internet. Then once the new server is up and running, put the TTL back to a normal setting so as not to flood your server with unnecessary dns traffic.

 

[fly]

Set the TTL in your dns zone file to something low, like 500 seconds. Thus the changes would be propegated more quickly across the internet. Then once the new server is up and running, put the TTL back to a normal setting so as not to flood your server with unnecessary dns traffic.

(my dns-fu is VERY weak)

the DNS servers will be changing as well, so will that still matter?