Why take the replicant offline? Just create a snapshot of the disk and copy the files from that. The replicant will continue to replicate all the updates as fast as it can while you copy off the snapshot. If something should happen to the primary box while you're making the backup, you'll be better off.
Mirroring IS a backup solution, but not a complete one. The whole point to having the replication is to have a live backup, should a machine failure occur, as well as making backups painless and easy to do -- meaning a backup won't seriously degrade performance (copying large amounts of data will kill database I/O performance) because the backup is happening on the slave machine. The backups made on the second machine can be stored on it, offsite, or on any appropriate media.
Snapshots with a replication point set are important. Why? For synchronizing between servers. In the case something catastrophic happened, such as a "delete * from important_table", a restore from backup will be necessary. Unless a snapshot is taken with a replication point, the individual servers have no way of knowing their restored copies are synchronized. Without the replication point saved, a new one will be set and an entire database copy from master to slave may have to happen before the slave begins committing any updates. The reason snapshots should be used is because the journal containing the snapshot point could easily be played through and over-written by the time all the data has been copied to backup.
Not quite. Backing up a live database can be a bit tricky. By the time you finish copying part of the database, the first bit can change again. So you have to create a snapshot of some kind. And that has to be supported in the database setup (at the application or server level) in order for the backup to be in a consistent state. And you don't want your backup process to degrade site performance, either. So a simple file copy is totally inadequate.
A common solution is replication. Backup is then performed by creating a replication point on the slave database machine then taking a snapshot and copying that while while master database machine continues serving at full speed. Replication can then catch up when the backup is complete. Another advantage to having replication is duplication on the machine level -- if the master fails, go live to the slave with minimal to no downtime. Set both machines up in a master-master configuration and you can swap back and forth as needed, allowing live maintenance and backup with no performance degredation.
As well as in most parts of Canada. Driving with studded tires is a world of difference, even compared to excellent winter tires. If it's legal to drive with them in a snowy climate, they're the number one safety improvement to have. They have saved me from collisions more than once.
That's it! The ultimate terrorist! Just breed Aluminum and Ted Bundy. What do you get? Al Bundy! Impervious to mind control rays (not much mind to begin with) and an excellent football player, too.
It was a bit before cell phones became really popular, but it would even fry digital watches according to the guide. They had everyone leave their electronics in the tour office. That's probably why they had a bus from the seventies, too, before vehicles had lots of electronics in them.
Which is somewhat ironic, because the usual way of smelting aluminum generates incredibly big magnetic fields as part of the electrolysis process. I took a tour through a facility once, and there was no limit to the number of paper clips you could stack end-to-end on the tour bus while in the plant. Pretty neat.
I beg to differ! We have airborne water tankers for putting out forest fires. Just fill them up with the slime from Hamilton Harbour, and they'll kill anything!
Because you can dump that heat into the surrounding ground. Think geothermal energy reversed. The only time you can't do that is when the ground is too unstable for piping (which would mean it's a bad place for a bunker anyway), or when the ground is permafrost.
The real question is what is Canada doing with nuclear bunkers? Like anyone's going to bother bombing them.:P
You're catching on. These buildings actually have a different primary purpose. They're designed like bunkers so no one could devine their real reason for existence: they're some of the few places in Canada where one can seek refuge from Céline Dion.
And get picked up by all the underwater listening stations?
I know of at least a couple on the BC coast, but I won't say where they are, as the drug smugglers don't need that knowledge. They've been known to damage them in the past.
I must say I'm rather impressed by the secrets the Forces have been able to maintain. There is a lot of stuff that isn't public knowledge.
Redlined? Cracking? Debian? I'm sorry to burst your bubble but by the last numbers I have, when Debian releases the internet does not strain under the load. When Fedora releases (currently the largest / most popular Linux distribution at release time) the internet does not load, and it's not uncommon for the Fedora mirroring system to move 100's if not thousands Terabytes in a week. The internet doesn't redline or strain under this load, in reality most people don't even know it's going on. This isn't 1998 anymore, and there are a lot of mirrors out there with 100mbps, 1000mbps and even a few now with 10gbps uplinks to the internet.
I run a medium sized forum (25k users) that does 1 TB a month. That's about 4 Mbps, which is not even %0.01 of the available bandwidth into the hosting facility. Even if a Debian upgrade moves PBs, it's not all that much in the grand scheme of things. For what's it's worth, the facility currently moves about 6 Gbps.
Slashdot Mirror
Whether it's Windows 7 or not, there's one thing that's guaranteed: it's going to be a pane.
Why take the replicant offline? Just create a snapshot of the disk and copy the files from that. The replicant will continue to replicate all the updates as fast as it can while you copy off the snapshot. If something should happen to the primary box while you're making the backup, you'll be better off.
Mirroring IS a backup solution, but not a complete one. The whole point to having the replication is to have a live backup, should a machine failure occur, as well as making backups painless and easy to do -- meaning a backup won't seriously degrade performance (copying large amounts of data will kill database I/O performance) because the backup is happening on the slave machine. The backups made on the second machine can be stored on it, offsite, or on any appropriate media.
Snapshots with a replication point set are important. Why? For synchronizing between servers. In the case something catastrophic happened, such as a "delete * from important_table", a restore from backup will be necessary. Unless a snapshot is taken with a replication point, the individual servers have no way of knowing their restored copies are synchronized. Without the replication point saved, a new one will be set and an entire database copy from master to slave may have to happen before the slave begins committing any updates. The reason snapshots should be used is because the journal containing the snapshot point could easily be played through and over-written by the time all the data has been copied to backup.
Not quite. Backing up a live database can be a bit tricky. By the time you finish copying part of the database, the first bit can change again. So you have to create a snapshot of some kind. And that has to be supported in the database setup (at the application or server level) in order for the backup to be in a consistent state. And you don't want your backup process to degrade site performance, either. So a simple file copy is totally inadequate.
A common solution is replication. Backup is then performed by creating a replication point on the slave database machine then taking a snapshot and copying that while while master database machine continues serving at full speed. Replication can then catch up when the backup is complete. Another advantage to having replication is duplication on the machine level -- if the master fails, go live to the slave with minimal to no downtime. Set both machines up in a master-master configuration and you can swap back and forth as needed, allowing live maintenance and backup with no performance degredation.
As well as in most parts of Canada. Driving with studded tires is a world of difference, even compared to excellent winter tires. If it's legal to drive with them in a snowy climate, they're the number one safety improvement to have. They have saved me from collisions more than once.
That's it! The ultimate terrorist! Just breed Aluminum and Ted Bundy. What do you get? Al Bundy! Impervious to mind control rays (not much mind to begin with) and an excellent football player, too.
It was a bit before cell phones became really popular, but it would even fry digital watches according to the guide. They had everyone leave their electronics in the tour office. That's probably why they had a bus from the seventies, too, before vehicles had lots of electronics in them.
Which is somewhat ironic, because the usual way of smelting aluminum generates incredibly big magnetic fields as part of the electrolysis process. I took a tour through a facility once, and there was no limit to the number of paper clips you could stack end-to-end on the tour bus while in the plant. Pretty neat.
I sure hope so! We don't need another Balrog in a hoolahoop roaming the world! :D
Remember kids, when you have the opportunity to make a funny about SCSI, you have to LUNge at it.
Was that all you had left? Did someone raid all your funny hard drive jokes? ;-)
I'd like one for myself. It would spruce my apartment up.
I only posted that an hour ago, that's why.
So he had Parliament prorogued two weeks early for the holidays. Whoop-dee-do.
I beg to differ! We have airborne water tankers for putting out forest fires. Just fill them up with the slime from Hamilton Harbour, and they'll kill anything!
Because you can dump that heat into the surrounding ground. Think geothermal energy reversed. The only time you can't do that is when the ground is too unstable for piping (which would mean it's a bad place for a bunker anyway), or when the ground is permafrost.
The real question is what is Canada doing with nuclear bunkers? Like anyone's going to bother bombing them. :P
You're catching on. These buildings actually have a different primary purpose. They're designed like bunkers so no one could devine their real reason for existence: they're some of the few places in Canada where one can seek refuge from Céline Dion.
And get picked up by all the underwater listening stations?
I know of at least a couple on the BC coast, but I won't say where they are, as the drug smugglers don't need that knowledge. They've been known to damage them in the past.
I must say I'm rather impressed by the secrets the Forces have been able to maintain. There is a lot of stuff that isn't public knowledge.
[citation needed]
What? Do you think this site is part the Wikimeteor Foundation?
You wouldn't happen to be from the Terrace area, would you?
Yes, there is a blood test for it. Chances are it will show positive. Most adults have it.
You coded in brainfuck without a condom and got cerebral herpes, obviously.
I run a medium sized forum (25k users) that does 1 TB a month. That's about 4 Mbps, which is not even %0.01 of the available bandwidth into the hosting facility. Even if a Debian upgrade moves PBs, it's not all that much in the grand scheme of things. For what's it's worth, the facility currently moves about 6 Gbps.
Check out KTorrent. I used to use Azureus because of the advanced features, but got tired of the bloat.
>>I work for the Department of Redundancy Department.
>Which one?
Both. :-)