Multi volume tar archive

tar archive spanning multiple volumes backupDir=/backups backupFile=pseudo-tape.tar backupVolume=pseudo-tape.volno # tar # -c create new archive # --gzip gzip archive # -M create/list/extract multi-volume # --tape-length change tape after writing x * 1024 bytes. 1048576 gives 1GB output files # --file archive file # --new-volume-script run script at end of each volume # --volno-file use/update volume number in file tar -c -M --tape-length=1048576 --file=${backupDir}/${backupFile} --new-volume-script=${backupDir}/pseudo-tape-new-volume.sh --volno-file=${backupDir}/${backupVolume} ${backupDir}/software-20151102 dir="${backupDir}" base_name="${backupFile}" next_volume_name=`echo -n "archive.
Read On →

vsftpd

We have installed vsftpd on a few of our servers to allow users to securely connect to upload or retrieve files. The users are all chroot’d - they cannot cd out of their home directory. Our procedure for configuring the server, vsftpd and the users to allow this follows. Install vsftpd Simple as: yum install vsftpd (or apt-get if you are using a different Linux flavour). Create user account
Read On →

Adding space to PRIMARY filegroup

It’s always the simple things that catch you out on occasion. Adding space to SQL Server database primary filegroup returned this error: Msg 1105, Level 17, State 2, Server WG0140, Line 1 Could not allocate space for object 'sys.sysfiles1'.'sysfiles1' in database 'SITE' because the 'PRIMARY' filegroup is full. To add space to the primary filegroup requires some free space in the first MDF file. Adding just 1MB to the MDF file allowed the addition of another (NDF) file without error.
Read On →

SAP connect to database fails

Curious problem this morning. SAP instance was failing to start because R3trans could not connect to the database. Checking trans.log revealed the following error: 4 ETW000 R3trans version 6.25 (release 741 - 29.01.15 - 20:15:01). 4 ETW000 unicode enabled version 4 ETW000 =============================================== 4 ETW000 4 ETW000 date&time : 21.09.2015 - 06:01:56 4 ETW000 control file: <no ctrlfile> 4 ETW000 R3trans was called as follows: R3trans -d 4 ETW000 trace at level 2 opened for a given file pointer 4 ETW000 [ dev trc,00000] Mon Sep 21 06:01:56 2015 82 0.
Read On →

DB2 Fix Pack blues

SAP reported a while back that they were withdrawing support for DB2 9.7 FP10 due to a defect reported by IBM, see Defect in DB2 BINSORT might cause misordered index in 9.7 FP10 or 10.5 FP5SAP. We have installed the replacement 9.7.10SAP fix pack on some instances but not production. Having just refreshed a QA instance from production I needed to verify if the post upgrade steps had been completed, which included applying the 9.
Read On →