default dumptype DUMP

Hi, Does DUMP dumptype have any properties that can be redefined ? I need to follwing task: stop the application, dettach the mirror, ufsdump attach the mirror This can be done with gtar but can this be done with native backup tools as well ? I Thanks Gunnar Gunnarsson

ZWC template not applying as expected

I have a template setup in ZWC which contains the single entry: "C:\Documents and Settings". The corresponding DLE is: foo.bar.com "c:" zwc-compress The problem is that Amanda then backs up the entire C drive rather than just the "Documents and Settings" folder. What is it I'm missing? Kind Reg

Re: ZWC template not applying as expected

Chris, I'd puzzeled over that too. I believe that the templates are for amanda servers, you are only running the client and the tempate is never used for anything. My (unix based) dislist files contain dle's that look like foo c:/database-backups zwc-compress foo c:/users-data1 zwc-c

Re: ZWC template not applying as expected

Hi Brian, On Tue, Jun 8, 2010 at 11:06 AM, Brian Cuttler wrote: > Chris, > > I'd puzzeled over that too. > > I believe that the templates are for amanda servers, you > are only running the client and the tempate is never used > for anything. A look at a tcpdump does show that the diskdevice in t

Re: default dumptype DUMP

Gunnarsson, Gunnar wrote: Does DUMP dumptype have any properties that can be redefined ? I need to follwing task: stop the application, dettach the mirror, ufsdump attach the mirror This can be done with gtar but can this be done with native backup tools as well ? I Haven't seen an ans

Re: ZWC template not applying as expected

Well, Google turned up this: http://forums.zmanda.com/showthread.php?t=2588 But trying to apply it to my DLE results in an "Invalid disk list entry. For taking backup of a single file use templates." Sort of ironic considering I *am* trying to use a template. ;-) On Tue, Jun 8, 2010 at 1:17 PM,

amanda-backup_client conflicts with amanda-backup_server-3.1.0-1.rhel5.i386

I just did a brand new installation of CentOS 5.5 (an RHEL 5.5 clone), updated it ("yum update") and pulled in amanda-backup_server-3.1.0-1.rhel5.i386.rpm. I installed like so: [r...@quartz ~]# yum --nogpgcheck install amanda-backup_server-3.1.0-1.rhel5.i386.rpm Loaded plugins: fastestmirror ...

large level 1 dumps

Our server is Solaris 10/sparc and is running amanda 2.4.4 and tar (GNU tar) 1.17. We have a fairly large partition [clep/tmp/amanda] df -hl /export/zone Filesystem size used avail capacity Mounted on /dev/dsk/c3t0d0s6 1.1T 411G 746G36%/export/zone that is givi

Re: ZWC template not applying as expected

On Tue, Jun 8, 2010 at 7:53 AM, Chris Nighswonger wrote: > I have a template setup in ZWC which contains the single entry: > "C:\Documents and Settings". The corresponding DLE is: > > foo.bar.com "c:" zwc-compress > The disklist entry should be foo.bar.com zwc-compress The template should be

Re: amanda-backup_client conflicts with amanda-backup_server-3.1.0-1.rhel5.i386

I *think* this is the same issue being addressed here: http://forums.zmanda.com/showthread.php?t=2800 Dustin -- Open Source Storage Engineer http://www.zmanda.com

Re: ZWC template not applying as expected

On Tue, Jun 8, 2010 at 2:58 PM, Paddy Sreenivasan wrote: > On Tue, Jun 8, 2010 at 7:53 AM, Chris Nighswonger > wrote: >> I have a template setup in ZWC which contains the single entry: >> "C:\Documents and Settings". The corresponding DLE is: >> >> foo.bar.com "c:" zwc-compress >> > > The disklis

After upgrading to 3.1.0: ETIMEOUT must be positive

Hello, I upgraded my 2.6.1p2 installation to 3.1.0, but now I receive on all am* commands: > ETIMEOUT must be positive But the manpage says: etimeout int . A negative value will be interpreted as a total amount of time to wait per client instead of per disk. Who's wrong? Manpage or progr

Can't recover with 2.6.1p2 client from 3.1.0 server

Hello, I upgraded our server to 3.1.0 (before 2.6.1p2). But now I can't recover files on my 2.6.1p2 client that were backuped before I switched the server version: > Specified file list matches multiple dumps; cannot continue recovery Got no header and data from server, check in amidxtaped.*.deb

Re: After upgrading to 3.1.0: ETIMEOUT must be positive

On Tue, Jun 8, 2010 at 3:58 PM, Marc Muehlfeld wrote: >  > ETIMEOUT must be positive > > But the manpage says: > > etimeout int > . A negative value will be interpreted as a total amount of time to wait > per client instead of per disk. > > Who's wrong? Manpage or program code? Well, it was c

Re: Can't recover with 2.6.1p2 client from 3.1.0 server

On Tue, Jun 8, 2010 at 3:58 PM, Marc Muehlfeld wrote: >  > Tue Jun  8 16:39:14 2010: amidxtaped: CTL << LABEL=KDD174:29 .. >  > Tue Jun  8 16:39:18 2010: amidxtaped: CTL >> MESSAGE Specified file list > matches multiple dumps; cannot continue recovery So what's happening here is that amidxtaped

Cleanup vtape space Amanda-2.6.1

Good time of the day, users. After long long holliday I'm returning in company and see this message: FAILURE DUMP SUMMARY: www.site.org /var/www/htdocs/ISU lev 1 FAILED [Not enough holding disk space] www.site.org /var/www/htdocs/ISU lev 1 FAILED [out of holding space in degraded mode] P

Re: Cleanup vtape space Amanda-2.6.1

Is it possible to use: /*amadmin DailySet1 holding list -l -d | amadmin DailySet1 holding delete -*/ to delete all unnecessary dumps ? Dimiter Maznekov wrote: Good time of the day, users. After long long holliday I'm returning in company and see this message: FAILURE DUMP SUMMARY: www.site