Intel DN2820FYKH NUC Update

Thought I’d do a follow up post on our Intel NUC (Model: DN2820FYKH).

The little machine is running fine and has only had one software crash since we started to use it. It is turned on 24/7 and gets used everyday. At the moment it has an uptime of 44days or so.

Still very impressed by the machine in day to day use. It does exactly what we need it to do with minimal  footprint on a desktop.

Would certainly buy one of them again. Really do want an i3 or i5 based model some day.

Linux bash vulnerable on most modern Linux distributions

Came across an interesting post today from VentraIP which outlines that Linux bash is vulnerable on most modern Linux distributions. You can read more about it directly from them here.

I ran the command on a Raspbian install I have on a Raspberry Pi that hasn’t been updated for a few weeks and surprise surprise. It was vulnerable.

Before upgrade:

root@zulu:~# env x='() { :;}; echo vulnerable' bash -c "echo this is a test"
vulnerable
this is a test

After upgrade:

root@zulu:~# env x='() { :;}; echo vulnerable' bash -c "echo this is a test"
bash: warning: x: ignoring function definition attempt
bash: error importing function definition for `x'
this is a test

Best we all go do a sweep of our systems and upgrade those all that would be impacted by this. Best to close the problem now before it gets exploited.

Linode continues to be a powerhouse VPS provider

I’ve used Linode in the past and continue to hold them in high regard. If you need a bullet proof VPS provider who continues to listen to customers and provide exceptional value, I highly recommend them.

I’ve still got my account with them, just don’t have any active services at the moment, but I am sure I will again in the near future.

Be sure to sign up via the link here.

NUC_01

Intel DN2820FYKH NUC

The talk of the past year in hardware has been the Intel NUC, and I’ve been wanting to get my hand on one for the last few months, since the Third Generation module was released.

In the end I decided to purchase an Intel Celeron based one (Model: DN2820FYKH) and to load it up to run Windows 8.1 Pro.

For more detailed information about the specification, hint up the link here.

The Celeron model has some notiable differences (lacking features) between the i3 and i5 based models.

  • Only one memory socket (max 8GB ram) (vs i3/5 16GB max in 2 sockets).
  • Ships with wireless (vs i3/5 not shipping with it).
  • No MSATA support, as the socket for it don’t exist.

Despite this lack of feature between it’s more powerful siblings, I figured that Windows 8.1 Pro on a machine where you can install 8GB ram and a 2.5″ Laptop SSD drive would be adequate for the footprint.

Sure enough, it runs very well. Reasonable and capable little computer. I paired mine with a powered USB hub and a 19″ monitor I had spare.

Pictures;

NUC_01NUC_02NUC_03

 

Simpana 10 – Commserve DR Backup

A demo I put together that shows how to perform a Commserve DR Backup in Simpana 10. It talks about the process of how to do it manually and where you can find the files associated with the process. Sometimes this might need to be performed manually and collected manually so that you can upload it via some manual process due to lack of connectivity in an environment to the outside world. i.e. internet.

It’s a follow on from a previous post that talks about the same process in Simpana 9. Which you can find here.

Hope you enjoy the demo. If this post helps you, please leave a comment.

Simpana 10 – Specifying the media parameters for RMAN command line operations – Example

An recent addition to Simpana 10 Oracle iDA over Simpana 9 was the ability to specify Media Parameters for RMAN Command Line Operations, which wasn’t possible in Simpana 9.

Below is an example on its use, and the documentation links from Commvault are 1, 2 an 3.

The client in this example is “jwora1″ running Windows 2008 R2 x64 and an Oracle 11gR2 64bit release. Simpana 10 with a SP4 is installed on client and Commserve – “jwcs”.

RMAN Script:

run {
allocate channel ch1 type 'sbt_tape' PARMS="BLKSIZE=262144,ENV=(CVOraSbtParams=C:\p.txt,CvClientName=jwora1,CvInstanceName=Instance001)" trace 2;
backup current controlfile;
}

Contents of p.txt file below;

[sp]
SP_Main-jwma1

[mediaagent]
jwma1

Below is a look at the GUI configuration for the Oracle instance “orcl” on client “jwora1″ which shows that third party command line backups should use Storage Policy (SP) – “SP_Main-jwcs”. However as you will not by the running of the job using the Media Parameters it will use a different SP and MediaAgent, as defined by the p.txt file I passed.

subclient not configured with any SP
subclient not configured with any SP
orcl properties showing command line backup should use SP - SP_Main-jwcs by default.
orcl properties showing command line backup should use SP – SP_Main-jwcs by default.
orcl properties showing log backups would use SP - SP_Main_jwcs by default
orcl properties showing log backups would use SP – SP_Main_jwcs by default.
sample execution of my rman backup script - current control file backup
sample execution of my rman backup script – current control file backup
Commserve Job Controller showing the running job. Note which MediaAgent is used and SP.
Commserve Job Controller showing the running job. Note which MediaAgent is used and SP.

If you find my posts of value, please send me some feedback. Especially if you find this post and it helps you in your travels.

UPDATE: And to follow on from the example above, the following is also possible too. If you don’t pass the CvClientName and CvInstanceName on the channel allocation, you can pull those too from the parameters file. Sample below of alternative backup script syntax and parameters file contents. All documented on the documentation link provided top of post.

RMAN Script:

run {
allocate channel ch1 type 'sbt_tape' PARMS="BLKSIZE=262144,ENV=(CVOraSbtParams=C:\p2.txt)" trace 2;
backup current controlfile;
}

Contents of p2.txt file:

[sp]
SP_Main-jwma1
[mediaagent]
jwma1
[CvClientName]
jwora1
[CvInstanceName]
Instance001

The parameter file can have spaces between the definitions like in the top example, which I prefer, as it makes the file easier to read. Where as the p2.txt file has no extra spaces, which also works but makes it harder to read personally.

Enjoy.

New Voice Services Provider – Telecube

Totally missed it, but a friend alerted me to the fact we have a new voice services provider in play.

Telecube seem to be a new provider and seem to be making a name for themselves.

I signed up on the weekend, and the immediate thing I noticed was the very nice portal for configuration of the services and the fact you can configure up to 10 extensions which is very handy.

You can also check out the Whirlpool thread for them here. If you’d like to sign up, click here.