Server down? - Page 5

mreynert · #1 03-13-2012, 08:34 AM

That picture doesn't look good...

Spiney · #2 03-13-2012, 08:38 AM

Start donating.

**Rogean** · #3 03-13-2012, 08:35 AM

It's fine, just for some reason the backup database lost sync with the replication, which triggered a failsafe preventing the primary database from purging binary logs, and it ran out of hard drive space on the binary log partition.

So now I'm resetting replication and doing a fresh copy of the database from primary to backup.

HappyTr33z · #4 03-13-2012, 08:37 AM

Quote:

Originally Posted by Rogean [You must be logged in to view images. Log in or Register.]

It's fine, just for some reason the backup database lost sync with the replication, which triggered a failsafe preventing the primary database from purging binary logs, and it ran out of hard drive space on the binary log partition.

So now I'm resetting replication and doing a fresh copy of the database from primary to backup.

Well hell yeah.

Hmotzart · #5 03-13-2012, 08:37 AM

^^^^^^^^^^^^^^

CHEER!

melkezidek · #6 03-13-2012, 08:39 AM

Quote:

Originally Posted by Rogean [You must be logged in to view images. Log in or Register.]

It's fine, just for some reason the backup database lost sync with the replication, which triggered a failsafe preventing the primary database from purging binary logs, and it ran out of hard drive space on the binary log partition.

So now I'm resetting replication and doing a fresh copy of the database from primary to backup.

SOOOO the picture pretty much summed that up nicely then [You must be logged in to view images. Log in or Register.]

gwapojosh · #7 03-13-2012, 08:40 AM

Quote:

Originally Posted by Rogean [You must be logged in to view images. Log in or Register.]

It's fine, just for some reason the backup database lost sync with the replication, which triggered a failsafe preventing the primary database from purging binary logs, and it ran out of hard drive space on the binary log partition.

So now I'm resetting replication and doing a fresh copy of the database from primary to backup.

"Did you try turning off and then on again?" hehe

**Rogean** · #8 03-13-2012, 08:41 AM

Quote:

Originally Posted by gwapojosh [You must be logged in to view images. Log in or Register.]

"Did you try turning off and then on again?" hehe

3 Times man, just like you said!

gwapojosh · #9 03-13-2012, 08:43 AM

Quote:

Originally Posted by Rogean [You must be logged in to view images. Log in or Register.]

3 Times man, just like you said!

Lol For me it would be that or hitting it with a stick.. It's a good thing that I'm not running the show [You must be logged in to view images. Log in or Register.]

Xadion · #10 03-13-2012, 08:44 AM

Quote:

Originally Posted by Rogean [You must be logged in to view images. Log in or Register.]

It's fine, just for some reason the backup database lost sync with the replication, which triggered a failsafe preventing the primary database from purging binary logs, and it ran out of hard drive space on the binary log partition.

So now I'm resetting replication and doing a fresh copy of the database from primary to backup.

Thats exactly what I thought the problem was!