[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[cobalt-users] raqbackup 3.1 bug
- Subject: [cobalt-users] raqbackup 3.1 bug
- From: Brett Wright <brett@xxxxxxxxxxxxx>
- Date: Tue Apr 1 13:23:03 2003
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
Hi Team
Not sure if this is been reported, i couldn't find it in the achieves. Ive
also posted this to developers list.
When backing up with raqbackup3.1 it has some sort of size limit each tar
file can be , proberly for FTP transfers
eg
Scanout: INFO: exporting group clients
Scanout: INFO: building archive for clients
Scanout: creating tar: /home/raqbackup/data/groups-clients-public.tar.gz
Scanout: creating tar: /home/raqbackup/data/groups-clients-private.tar.gz.1
Scanout: creating tar: /home/raqbackup/data/groups-clients-private.tar.gz.2
Scanout: creating tar: /home/raqbackup/data/groups-clients-private.tar.gz.3
Scanout: creating tar: /home/raqbackup/data/groups-clients-private.tar.gz.4
Scanout: creating tar: /home/raqbackup/data/groups-clients-private.tar.gz.5
Scanout: creating tar: /home/raqbackup/data/groups-clients-private.tar.gz
when it goes to FTP the files it does NOT send the .gz.1 .gz.2 etc , code
in raqbackup3.1.sh looks like
mkdir $SOURCE
cd $SOURCE
binary
mput *.gz
ascii
mput *.txt
There just need to be another .* on the end
eg
mput *.gz.*
Something to double check if you have large directories/sites you are
backing up, otherwise you might find not all your files are been backed up
as we did ;o)
Sorry if this is already been pointed out
Brett