<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title><![CDATA[Linux, Unix and Netware Clients]]></title><link>http://forums.dantz.com/showforum.php?fid/31/</link><description>For general discussions on Linux/Unix/Netware Clients. Including Red Hat and Solaris</description><language>none</language><pubDate>Thu, 03 Jul 2008 13:01:59 GMT</pubDate><lastBuildDate>Thu, 03 Jul 2008 13:01:59 GMT</lastBuildDate><docs>http://blogs.law.harvard.edu/tech/rss</docs><generator>FusionBB 2.2 (www.fusionbb.com)</generator><item><title><![CDATA[Different modify time/date errors]]></title><link>http://forums.dantz.com/showtopic.php?tid/27584/</link><guid isPermaLink="false">http://forums.dantz.com/showtopic.php?tid/27584/</guid><description><![CDATA[ Hello, <br />
<br />
At my work, we run Retrospect SMB for Windows, 7.5.x. We added a "client" that uses Red Hat Linux and is installed on 5 servers for them I believe. I have jobs written to tape once a week. The jobs always successfully write to tape but I always notice errors relating to different modify/date time. Is their a way to get rid of this or is it a matter of those files being modified while the job is running? Some of the examples of the error I copied and pasted below.<br />
<br />
		File "/opt/local/logs/iostat_logs/bsgsql02.noc.iscgnet.com.iostat.080702": different modify date/time (set: 7/2/2008 6:37:14 PM, vol: 7/2/2008 6:37:44 PM)<br />
		File "/opt/local/logs/mpstat/bsgsql02.noc.iscgnet.com.mpstat.data.080702": different modify date/time (set: 7/2/2008 6:37:19 PM, vol: 7/2/2008 6:37:49 PM)<br />
		File "/opt/local/logs/vmstat_logs/bsgsql02.noc.iscgnet.com.vmstat.data.080702": different modify date/time (set: 7/2/2008 6:37:21 PM, vol: 7/2/2008 6:37:51 PM)<br />
		File "/opt/local/mysql/data/ib_logfile0": different modify date/time (set: 7/2/2008 6:37:26 PM, vol: 7/2/2008 6:37:55 PM)<br />
		File "/opt/local/mysql/data/ib_logfile1": different modify date/time (set: 7/2/2008 6:37:16 PM, vol: 7/2/2008 6:37:52 PM)<br />
		File "/opt/local/mysql/data/ibdata1": different modify date/time (set: 7/2/2008 6:37:26 PM, vol: 7/2/2008 6:37:55 PM)<br />
		File "/opt/local/mysql/data/master.info": different modify date/time (set: 7/2/2008 6:37:45 PM, vol: 7/2/2008 6:37:52 PM)<br />
		File "/opt/local/mysql/data/relay-log.info": different modify date/time (set: 7/2/2008 6:37:45 PM, vol: 7/2/2008 6:37:52 PM)<br />
	7/2/2008 6:38:01 PM: 8 execution errors<br />
<br />
<br />
This isn't that big of a deal since all the data is being written to the tape.<br />
<br />
Thanks, <br />
<br />
Nick ]]></description><pubDate>Thu, 03 Jul 2008 12:50:55 GMT</pubDate></item><item><title><![CDATA[7.6 Linux client broken]]></title><link>http://forums.dantz.com/showtopic.php?tid/27545/</link><guid isPermaLink="false">http://forums.dantz.com/showtopic.php?tid/27545/</guid><description><![CDATA[ I was pleased to see that error -540 is supposed to finally be fixed in version 7.6 - we have been running a separate 7.0 install to back up our Linux systems.<br />
<br />
However, the 7.6 Linux client is completely broken (at least on Centos 5.x); I get a bunch of messages like this:<br />
<br />
pmcTrans: requested 158: expected code 216 and 218 bytes, got 202 and 4 bytes<br />
connTcpConnection: invalid code found: 158<br />
<br />
Fortunately, the 7.5 Linux client seems to continue to work correctly.<br />
 ]]></description><pubDate>Mon, 30 Jun 2008 19:35:00 GMT</pubDate></item><item><title><![CDATA[Backing up Boot Camp partition while in OS X]]></title><link>http://forums.dantz.com/showtopic.php?tid/27448/</link><guid isPermaLink="false">http://forums.dantz.com/showtopic.php?tid/27448/</guid><description><![CDATA[ [While the title of the forum is "Linux, Unix &amp; Netware Clients,"  I will make the assumption that this includes OS X clients as well.  If so, it would be good to include that in the Forum name.]<br />
<br />
Running Retrospect Single Server 7.0.344, update 7.0.12.105 on Windows Server 2003 Std Ed, SP2.<br />
<br />
Just installed Vista via Boot Camp to my MacBook Pro, and am planning on backing up the BC partition (partition is NTFS, read-only in OS X) while the Mac is booted in OS X.  A few questions:<br />
<br />
- Should this method of backing up my Vista partition work correctly?<br />
- I also use VMware Fusion to access the Vista install.  Is there any "official" recommendation about if that shouldn't be running while backing up?<br />
- Has anyone done a successful whole-partition restore in this setup?<br />
<br />
Thanks for any feedback. ]]></description><pubDate>Mon, 16 Jun 2008 14:36:17 GMT</pubDate></item><item><title><![CDATA[Problem with a Linux client on a dual network card system]]></title><link>http://forums.dantz.com/showtopic.php?tid/27375/</link><guid isPermaLink="false">http://forums.dantz.com/showtopic.php?tid/27375/</guid><description><![CDATA[ Hi,<br />
I have Retrospect 7.5 Single Server on a Windows Server 2003 and two Red Hat Enterprise Linux 5 machines with clients. Both are on the same subnet. One of them works with no problems (it's a 32-bit system). However, the other client cannot be connected to from the backup server. It doesn't show up in the "Add client" list when multicast is used. When I add it using subnet broadcast, it appears, but then can't be connected to with error -530 (client not found). <br />
<br />
The daemon is running on the problem machine (x64), and I'm guessing it has to do with two network cards the system has. <br />
Is there a way to point the client to the correct network adapter? <br />
<br />
Thank you for any suggestions<br />
<br />
Sasha<br />
 ]]></description><pubDate>Thu, 29 May 2008 20:50:39 GMT</pubDate></item><item><title><![CDATA[Example LVM Backup Script (external scripting)]]></title><link>http://forums.dantz.com/showtopic.php?tid/27274/</link><guid isPermaLink="false">http://forums.dantz.com/showtopic.php?tid/27274/</guid><description><![CDATA[ So now that we got it all  <a href="http://forums.dantz.com/showtopic.php?tid/27153/" title="forums.dantz.com/showtopic.php?tid/27153/">sorted out</a> as to how to set up external scripting for a Linux client, I wanted to make sure to post the script that I needed to create. <br />
<br />
This script is for backing up Zimbra Collaboration Suite on a Logical Volume, though I am sure it can be adapted to other apps that need to be backed up with minimal downtime. In my case the /opt folder is a unique logical volume and contains my Zimbra install that I need to backup (as well as some other apps). Since Zimbra is fairly self contained, all I need to do is backup this folder to get a backup of the app and data. But before I back it up, I need to make sure that the database has flushed all tables to disk and nothing is changing during that time (i.e. maintain state). I do this by having retrospect stop Zimbra before taking the snapshot and then restarting it. Then retrospect backs up the snapshot. Downtime is about 3 min (which is ostensibly the time it takes to restart zimbra).<br />
<br />
To do this, you need to make sure you have some unused partition space on your volume group (in my case 3GB), usually about 10% of the size of the volume to be backed up (I'm backing up ~40GB currently). Then put the code below in a file called /etc/retroeventhandler and make it executable and tweak the variables to suite you. <br />
<br />
This code is pretty much the verbatim code for lvm backup from the Zimbra wiki, but split up to execute the relevant parts before and after the backup.<br />
<br />
<pre><font class="code">Code:</font><br />

#!/bin/bash
#
# Retrospect Client retroeventhandler script
# 
# Contact Information 
# 
# EMC Corporation 
# 3003 Oak Road, 3rd Floor 
# Walnut Creek, CA 94597 
# 800.225.4880 or 925.948.9000
# customer_service@dantz.com
# 
# Copyright 2000-2005 EMC Corporation 
#
#
# How to use this script
# 
# Any executable with pathname /etc/retroeventhandler will be run 
# at the beginning and end of each source in a scripted backup. 
# The executable is passed one of the following parameter arrays:
#
#  StartSource, Script name(string), Source path(string),
#  Source name(string), Client name(string), Err file(empty)
#
#  EndSource, Script name(string), Source path(string),
#  Source name(string), Client name(string), KB stored(int),
#  Files stored(int), Duration in seconds(int), Source
#  start(date string), Source end(date string), 
#  Script start(date string), Backup set(string), 
#  Backup type(string), Source parent(string),
#  Errors(int), Fatal errors(int), Result(string)
#
# If a non-zero exit code is encountered for an execution trig-
# gered by the StartSource event, that backup source will 
# be skipped.
#
# Notes
# 1. The Source path is non-intuitive for mount points; it shows 
#    the Retrospect object path rather than the Linux or Unix path. For 
#    example, on client Bongo Fury  with an external drive mounted 
#    to /mnt/ext, the source path is "Backup Clients/Bongo Fury/ext", 
#    while the source name is "/mnt/ext".
#
# 2. Parameters 2 through 17 are passed double-quoted, so you
#    have to include the double quotes in your string for exact
#    pattern matching in tests (e.g. $X = [ "\"ScriptName\"" ])
#
# This sample script appends a timestamp and the arguments it 
# receives to a log file.
LOGFILE=/var/log/retro-events.log
date &gt;&gt;$LOGFILE
for X in "$@"; do
    echo $X &gt;&gt;$LOGFILE
done
# This sample script prevents a script named Invasive from
# backing up the /mnt/ext mountpoint.
#if [ $2 = "\"Invasive\"" ] &amp;&amp; [ $4 = "\"/mnt/ext\"" ]; then
#	exit 1
#fi





###################################################################################
# 
#    Script to backup a Zimbra installation (open source version)
#    by installing the Zimbra on a separate LVM Logical Volume,
#    taking a snapshot of that partition after stopping Zimbra,
#    restarting Zimbra services, , then using retrospect to backup the snapshot.
#
#    This script was originally based on a script found on the Zimbra wiki
#    http://wiki.zimbra.com/index.php?title=Open_Source_Edition_Backup_Procedure
#    and totally rewritten since then.
#
#    Copyright (C) 2007 Serge van Ginderachter &lt;svg@ginsys.be&gt;
#
#    This program is free software; you can redistribute it and/or modify
#    it under the terms of the GNU General Public License version 2 as 
#    published by the Free Software Foundation.
#
#    This program is distributed in the hope that it will be useful,
#    but WITHOUT ANY WARRANTY; without even the implied warranty of
#    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
#    GNU General Public License for more details.
#
#    You should have received a copy of the GNU General Public License
#    along with this program; if not, write to the Free Software
#    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
#    Or download it from http://www.gnu.org/licenses/old-licenses/gpl-2.0.html
#
####################################################################################

#### Modify the following variables according to your installation

# backup_dir - directory to backup to 
zm_backup_path=/home/zbackup

# zm_lv - the Logical Volume that contains /opt/zimbra - /opt mount point expected
zm_lv=LogVol00

# vol_group - the Volume Group that contains $zm_lv
zm_vg=VolGroup01

# zimbra_path - the path beneath the Logical Volume $zm_lv that needs to be synced
zm_path=zimbra

# zm_lv_fs - the file system type (ext3, xfs, ...) in /opt/zimbra
zm_lv_fs=ext3

# lvcreate lvremove - path and command for the lvm logical volume creation and deletion command
LVCREATE=/usr/sbin/lvcreate
LVREMOVE=/usr/sbin/lvremove

#### Modify the following variables according to your taste and needs

# zmsnapshot - the snapshot volume name for $zm_lv
zm_snapshot=zbackup

# zmsnapshot_size - size avalable for growing the snapshot
zm_snapshot_size=3GB

# zm_snapshot_mnt - zimbra snapshot mount point
zm_snapshot_path=/mnt/zbackup


#### Following parameters probably shouldn't need to be changed

log_facility=daemon
log_facility_mail=mail
log_level=notice
log_level_err=error
log_tag="$0"


say() { 
	MESSAGE_PREFIX="zimbra backup:"
	MESSAGE="$1"
	TIMESTAMP=$(date +"%F %T")
	echo -e "$TIMESTAMP $MESSAGE_PREFIX $MESSAGE"
	logger -t $log_tag -p $log_facility.$log_level "$MESSAGE" 
	logger -t $log_tag -p $log_facility_mail.$log_level "$MESSAGE"
	}

error ()  {
	MESSAGE_PREFIX="zimbra backup:"
        MESSAGE="$1"
	TIMESTAMP=$(date +"%F %T")
	echo -e $TIMESTAMP $MESSAGE &gt;&amp;2
	logger -t $log_tag -p $log_facility.$log_level_err "$MESSAGE"
	logger -t $log_tag -p $log_facility_mail.$log_level_err "$MESSAGE"
	exit
	}


##########################################
# Create and mount snapshot prior to retrospect backup
##########################################

if [ $1 = "StartSource" ] &amp;&amp; [ $4 = "\"/mnt/zbackup/\"" ]; then

	# load kernel module to enable LVM snapshots
	/sbin/modprobe dm-snapshot || error "Error loading dm-snapshot module"
	
	# Output date
	say "$2 backup started"
	
	# Stop the Zimbra services
	say "stopping the Zimbra services, this may take some time"
	/etc/init.d/zimbra stop || error "error stopping Zimbra" 
	kill -9 $(ps -u zimbra -o "pid=") #|| error "Error stopping Zimbra" #added as a workaround to zimbra bug 18653
	
	# Create a logical volume called ZimbraBackup
	say "creating a LV called $zm_snapshot"
	$LVCREATE -L $zm_snapshot_size -s -n $zm_snapshot /dev/$zm_vg/$zm_lv  || error "error creating snapshot, exiting" 
	
	# Start the Zimbra services
	say "starting the Zimbra services in the background....."
	(/etc/init.d/zimbra start &amp;&amp; say "services background startup completed") || error "services background startup FAILED" &amp;
	
	# Mount the logical volume snapshot to the mountpoint
	say "mounting the snapshot $zm_snapshot"
	mount -t $zm_lv_fs -o ro /dev/$zm_vg/$zm_snapshot $zm_snapshot_path
	
	# Create the current backup
	say "snapshot ready for retrospect backup"
	
fi



##########################################
# Unmount and remove snapshot after retrospect backup
##########################################

if [ $1 = "EndSource" ] &amp;&amp; [ $4 = "\"/mnt/zbackup/\"" ]; then

	# Unmount $zm_snapshot from $zm_snapshot_mnt
	say "unmounting the snapshot"
	umount $zm_snapshot_path || error "error unmounting snapshot"
	
	# Remove the snapshot volume
	# https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/71567
	say "pausing 1s and syncing before removing the snapshot from LVM"
	sleep 1 ; sync                 
	say "removing the snapshot"
	$LVREMOVE --force /dev/$zm_vg/$zm_snapshot  || say "error removing the snapshot"
	
	# Done!
	say "$2 backup ended: ${17} ($6 KB - $7 Files - $8 Folders)"

fi


<br />
</pre><br />
<br />
<br />
Automating the backup with this code has worked out well, although I have yet to do a test restore. I will post more about restore upon completing it.<br />
<br />
Enjoy ]]></description><pubDate>Mon, 12 May 2008 16:50:51 GMT</pubDate></item><item><title><![CDATA[external scripts won't execute]]></title><link>http://forums.dantz.com/showtopic.php?tid/27153/</link><guid isPermaLink="false">http://forums.dantz.com/showtopic.php?tid/27153/</guid><description><![CDATA[ I can perform backups via the 7.5.112 linux client of volumes on my RHEL4 server. But when I enable external scripting (by creating the /etc/retroeventhandler folder), all backups fail and the server gives the error: Source volume skipped (external script intervened: ). This happens when there is no script in the folder and when the folder contains the default retroeventhandler script, copied over from the /usr/local/dantz/client folder. The script will run just fine when called directly from the command line.<br />
<br />
One clue to the problem might be in the retropds.log file. When I enable the external scripting I get this error when a backup is executed and fails: volScriptFork[1]: execv() failed with error 13<br />
<br />
This implies to me that the retrospect client cannot run the execv() function which executes the script. Does this mean that I am missing some dependencies? Like maybe some compat C libraries or maybe GCC or Xorg packages? <br />
<br />
Has anyone else had this problem and/or have a solution?<br />
<br />
Thanks.<br />
 ]]></description><pubDate>Tue, 22 Apr 2008 23:19:34 GMT</pubDate></item><item><title><![CDATA[error 206 - duplicate activator code]]></title><link>http://forums.dantz.com/showtopic.php?tid/26925/</link><guid isPermaLink="false">http://forums.dantz.com/showtopic.php?tid/26925/</guid><description><![CDATA[ Had Linux client installed in RH Enterprise 5.1 and it was working fine. Recently had to do a fresh install of the RH system because of some problems with update patches. After the RH reinstall,  I installed the Retrospect client using retroclient-70.rpm.  Am using Retro server for Mac 6.1.<br />
Trying to do the first login for the linux client and keep getting the 206 - duplicate activator code error.  Have de and reinstalled the linux client a couple of times.  The retro server sees the linux boc fine in the network pane but can't get it logged in.<br />
Ideas?<br />
philmc ]]></description><pubDate>Wed, 26 Mar 2008 02:29:34 GMT</pubDate></item></channel></rss>