Using trickle and Bacula in a multi-homed environment
patvdv — Mon, 05/09/2011 - 13:45
Here is a brief tutorial on how I have set up the powerful Bacula backup tool on a server supporting a split-backup environment:
- Daily backups are made on NIC 1 to a local network storage facility (hosted by a Bacula backup server)
- On-demand backups are pulled via NIC 2 across a public network channel - e.g. VPN link - to a complete off-site storage facility (hosted by another Bacula backup server)
An extra limitation exists in the fact that the on-demand backups suffer a metering charge, one that based on a maximum allowed throughput per time unit, say 10 mbits/s. It is therefore important that any Bacula backup run stays well below that traffic threshold.
Shutting down Oracle databases quickly in parallel
patvdv — Mon, 27/07/2009 - 19:08
Most folks running a larger(r) amount of Oracle instances on the one and same server use a sequential method for shutting down their databases at for example backup time or during system shutdown. This can pose some inconveniences and at worst a real problem if it takes a long while before these SHUTDOWN IMMEDIATE commands complete. A concrete example may be the requirement to quickly shutdown your system during a power failure whilst still running on UPS batteries.
To work around this issue I have made a small script that can be used to shutdown a whole bunch of databases in a much faster but yet still tidy fashion. This is archieved by running all database shutdown in parallel and in the background using a helper script and the nohup facility.
Using multiple SSH daemons on one host
patvdv — Fri, 20/06/2008 - 22:01
Recently I ran into the situation where I needed to hook up 2 CentOS GNU/Linux servers to allow the transfer of a large data volume between the both of them. Both servers are internet facing systems and the obvious choice would have been to haul the data across via SCP (secure copy) using the public network interface. Unfortunately, all traffic originating from the public interface was being billed and the entire data transfer would have resulted in a rather hefty bill if I would have used the public internet as transport medium. An additional requirement stipulated that this kind of data transfer would need to happen on a regular basis which would make the use of CD/DVD's rather cumbersome. Since both boxes had a second NIC, the obvious choice was to connect them via a simple cross cable and to use a non-routable IP range for these NICs. Here is a simplified picture of the network setup:
HP Proliant HW monitor
patvdv — Fri, 20/06/2008 - 20:54
About
The hppro_hwmon Perl script will query the HP Linux hpasmcli and hpacucli command-line tools to check or show the health of your Proliant hardware. It will check following components:
-
Fans
-
Memory DIMMs
-
Power Supplies
-
Server
-
Temperature Controls
-
RAID Controller
-
Physical Drives
-
Logical Drives
The default script comes with a standard set of components to check but can be easily customized to fit your needs.
Recent comments
4 weeks 1 day ago
22 weeks 2 days ago
1 year 16 weeks ago
1 year 16 weeks ago
1 year 35 weeks ago
1 year 39 weeks ago
1 year 43 weeks ago
1 year 43 weeks ago
1 year 43 weeks ago
1 year 45 weeks ago