Automatic clonig fails for two Groups

Could someone to help me in this question?

another information about the Network

NetWorker Server:

Windows 2003 Enterprise Edition
NetWorker 7.2.1

Library:

Storagetek SL500
2xHP LTO3

Clients of Groups that fails

Solaris 8.0
NetWorker 7.2.1

Thanks a lot

The problem is that when Networker makes the automatic cloning only reads save set from one of the volumes an cloning that volume only (and the backup has used two volumes):
05/21/06 02:15:01 nsrd: savegroup info: starting TECNODESA (with 5 client(s))
05/21/06 02:15:05 nsrd: media info: suggest mounting 320113M_000 on tireaw2k10 for writing to pool '320113M'
05/21/06 02:15:05 nsrd: media waiting event: Waiting for 1 writable volumes to backup pool '320113M' tape(s) on tireaw2k10
05/21/06 02:15:07 nsrd: media info: loading volume 320113M_000 into \\.\Tape1
05/21/06 02:15:07 nsrmmd #31: Start nsrmmd #31, with PID 7112, at HOST tireaw2k10
05/21/06 02:15:33 nsrd: media info: suggest mounting 320113M_001 on tireaw2k10 for writing to pool '320113M'
05/21/06 02:15:33 nsrd: media event cleared: Waiting for 1 writable volumes to backup pool '320113M' tape(s) on tireaw2k10
05/21/06 02:15:33 nsrd: media waiting event: Waiting for 2 writable volumes to backup pool '320113M' tape(s) on tireaw2k10
05/21/06 02:15:35 nsrmmd #32: Start nsrmmd #32, with PID 6780, at HOST tireaw2k10
05/21/06 02:15:37 nsrd: media info: loading volume 320113M_001 into \\.\Tape0
05/21/06 02:15:42 nsrd: \\.\Tape1 2:Verify label operation in progress
05/21/06 02:15:46 nsrd: \\.\Tape1 2:Mount operation in progress
05/21/06 02:15:53 nsrd: media waiting event: Waiting for 1 writable volumes to backup pool '320113M' tape(s) on tireaw2k10
05/21/06 02:16:04 nsrd: media event cleared: Waiting for 1 writable volumes to backup pool '320113M' tape(s) on tireaw2k10
05/21/06 02:16:04 nsrd: media waiting event: Waiting for 2 writable volumes to backup pool '320113M' tape(s) on tireaw2k10
05/21/06 02:16:12 nsrd: \\.\Tape0 1:Verify label operation in progress
05/21/06 02:16:16 nsrd: \\.\Tape0 1:Mount operation in progress
05/21/06 02:16:55 nsrd: media waiting event: Waiting for 1 writable volumes to backup pool '320113M' tape(s) on tireaw2k10
05/21/06 02:16:55 nsrd: tireasol25.backup.tirea.es:/var/home saving to pool '320113M' (320113M_000)
05/21/06 02:16:55 nsrd: tireasol25.backup.tirea.es:/opt saving to pool '320113M' (320113M_000)
05/21/06 02:16:55 nsrd: tireasol25.backup.tirea.es:/etc saving to pool '320113M' (320113M_000)
05/21/06 02:16:55 nsrd: tireasol25.backup.tirea.es:/var/opt saving to pool '320113M' (320113M_000)
05/21/06 02:16:55 nsrd: tireasol13:/opt/sterling saving to pool '320113M' (320113M_000)
05/21/06 02:16:55 nsrd: tireasol23:/var/home saving to pool '320113M' (320113M_000)
05/21/06 02:16:55 nsrd: tireasol3:/opt/iPlanet saving to pool '320113M' (320113M_000)
05/21/06 02:16:55 nsrd: tireasol23:/usr/local saving to pool '320113M' (320113M_000)
05/21/06 02:17:17 nsrd: tireasol25.backup.tirea.es:/etc done saving to pool '320113M' (320113M_000) 14 MB
05/21/06 02:17:19 nsrd: tireasol3:/var/opt saving to pool '320113M' (320113M_000)
05/21/06 02:17:47 nsrd: media event cleared: Waiting for 1 writable volumes to backup pool '320113M' tape(s) on tireaw2k10
05/21/06 02:17:47 nsrd: tireasol23:/var/desa saving to pool '320113M' (320113M_001)
05/21/06 02:17:47 nsrd: tireasol23:/datos/BD_STERLING saving to pool '320113M' (320113M_001)
05/21/06 02:17:47 nsrd: tireasol3:/datos/BD_CONTA saving to pool '320113M' (320113M_001)
05/21/06 02:17:47 nsrd: tireasol15:/var/opt saving to pool '320113M' (320113M_000)
05/21/06 02:17:47 nsrd: tireasol3:/var/home saving to pool '320113M' (320113M_001)
05/21/06 02:17:47 nsrd: tireasol15:/var/home saving to pool '320113M' (320113M_001)
05/21/06 02:17:47 nsrd: tireasol15:/usr/local saving to pool '320113M' (320113M_001)
----------

Ok, here NetWorker uses te volumes 320113M_000 and 320113M_000 to make the backup of the group, then when makes the automatic clonig you can see:

05/21/06 04:49:46 nsrd: media event cleared: Waiting for 1 writable volumes to backup pool '666112D' tape(s) on tireaw2k10
05/21/06 04:49:59 nsrd: tireaw2k10:cloning session saving to pool '666112D' (666112D_002)
05/21/06 04:50:05 nsrd: cloning session:1 of 21 save set(s) reading from 320113M_001 18 MB of 45 GB
05/21/06 05:03:52 nsrd: tireaw2k10:cloning session done saving to pool '666112D' (666112D_002)
05/21/06 05:03:52 nsrd: cloning session:save sets done reading 45 GB
05/21/06 05:03:56 nsrd: write completion notice: Writing to volume 666112D_002 complete
05/21/06 05:04:11 nsrd: tireaw2k10:bootstrap saving to pool '320113M' (320113M_001)
05/21/06 05:04:13 nsrmmdbd: media db is saving its data. This may take a while.
05/21/06 05:04:13 nsrmmdbd: media db is open for business.
05/21/06 05:04:31 nsrd: tireaw2k10:bootstrap done saving to pool '320113M' (320113M_001) 1428 KB
05/21/06 05:05:06 nsrd: write completion notice: Writing to volume 320113M_001 complete
05/21/06 05:05:55 nsrd: tireaw2k10:cloning session saving to pool '666112D' (666112D_002)
05/21/06 05:06:15 nsrd: cloning session:1 of 1 save set(s) reading from 320113M_001 1428 KB of 1428 KB
05/21/06 05:06:16 nsrd: tireaw2k10:cloning session done saving to pool '666112D' (666112D_002)
05/21/06 05:06:16 nsrd: cloning session:save sets done reading 1428 KB
05/21/06 05:06:16 nsrd: savegroup info: Added 'tireaw2k10' to the group 'TECNODESA' for bootstrap backup.
05/21/06 05:06:16 savegrp: Automatic cloning of saveset /var/home for client tireasol25.backup.tirea.es during savegroup operation has failed!
05/21/06 05:06:16 savegrp: Automatic cloning of saveset /opt for client tireasol25.backup.tirea.es during savegroup operation has failed!
05/21/06 05:06:16 savegrp: Automatic cloning of saveset /etc for client tireasol25.backup.tirea.es during savegroup operation has failed!
05/21/06 05:06:16 savegrp: Automatic cloning of saveset /var/opt for client tireasol25.backup.tirea.es during savegroup operation has failed!
05/21/06 05:06:16 savegrp: Automatic cloning of saveset /opt/sterling for client tireasol13 during savegroup operation has failed!
05/21/06 05:06:16 savegrp: Automatic cloning of saveset /var/home for client tireasol23 during savegroup operation has failed!
05/21/06 05:06:16 savegrp: Automatic cloning of saveset /opt/iPlanet for client tireasol3 during savegroup operation has failed!
05/21/06 05:06:16 savegrp: Automatic cloning of saveset /usr/local for client tireasol23 during savegroup operation has failed!
05/21/06 05:06:16 savegrp: Automatic cloning of saveset /var/opt for client tireasol3 during savegroup operation has failed!
05/21/06 05:06:16 savegrp: Automatic cloning of saveset /datos for client tireasol13 during savegroup operation has failed!
05/21/06 05:06:16 savegrp: Automatic cloning of saveset /var/opt for client tireasol23 during savegroup operation has failed!
05/21/06 05:06:16 savegrp: Automatic cloning of saveset /opt for client tireasol3 during savegroup operation has failed!
05/21/06 05:06:16 savegrp: Automatic cloning of saveset /opt for client tireasol23 during savegroup operation has failed!
05/21/06 05:06:16 savegrp: Automatic cloning of saveset /etc for client tireasol13 during savegroup operation has failed!
05/21/06 05:06:16 savegrp: Automatic cloning of saveset /etc for client tireasol3 during savegroup operation has failed

------------

Only read from the volume 320113M_001 and ignore the savesets in the volume 320113M_000, then the automatic clone fails for this save set, but it is only happens in the backups that requires two volumes for make the backup of the group.

Thanks a lot!!!!

You will need to inspect savesets and their state first. Do something like:

mminfo -avot -q group=TECNODESA -t yesteday -r "ssid,name,client,volume,ssflags,sumflags,savetime(20),clonetime(20),clflags"

I don't remember anymore automatic cloning and how it goes, but I know it was pretty basic and not very good - scripting did give much better results. And it was much more verbose. From log you sent you can't see why did it fail. However, if mminfo won't show a thing and if you can reproduce this every day I would suggest to disable automatic staging and try manual one just to verify if you will get the same error or not.

Usually this should not be a problem - as one cloning process should wait for volume until it becomes available. It would rather interesting to see what is the actual error you get for failure (that may give us more clue).

Ok, a lot of thanks i,m going to try it XD

I,ve find another message in the yesterday's daemon.log:

05/23/06 02:56:14 nsrd: media event cleared: Waiting for 1 writable volumes to backup pool '666112D' tape(s) on tireaw2k10
05/23/06 02:57:32 nsrd: tireaw2k10:cloning session saving to pool '666112D' (666112D_000)
05/23/06 02:57:33 nsrd: cloning session:1 of 21 save set(s) reading from 320113M_000 33 KB of 15 GB
05/23/06 03:02:25 nsrd: tireaw2k10:cloning session done saving to pool '666112D' (666112D_000)
05/23/06 03:02:25 nsrd: cloning session:save sets done reading 15 GB
05/23/06 03:02:29 nsrd: write completion notice: Writing to volume 666112D_000 complete
05/23/06 03:02:56 nsrd: media notice: each clone host needs at least two enabled devices for save of client `tireaw2k10'
05/23/06 03:02:57 savegrp: command 'nsrclone -s tireaw2k10 -b 666112D -S -f - ' exited with return code 1.
05/23/06 03:04:50 nsrd: tireaw2k10:bootstrap saving to pool '320113M' (320113M_000)
05/23/06 03:04:52 nsrmmdbd: media db is saving its data. This may take a while.
05/23/06 03:04:52 nsrmmdbd: media db is open for business.
05/23/06 03:05:09 nsrd: tireaw2k10:bootstrap done saving to pool '320113M' (320113M_000) 1553 KB
05/23/06 03:05:42 nsrd: write completion notice: Writing to volume 320113M_000 complete
05/23/06 03:06:40 nsrd: tireaw2k10:cloning session saving to pool '666112D' (666112D_000)
05/23/06 03:06:50 nsrd: cloning session:1 of 1 save set(s) reading from 320113M_000 1553 KB of 1553 KB
05/23/06 03:06:50 nsrd: tireaw2k10:cloning session done saving to pool '666112D' (666112D_000)
05/23/06 03:06:50 nsrd: cloning session:save sets done reading 1553 KB
05/23/06 03:06:55 nsrd: savegroup info: Added 'tireaw2k10' to the group 'TECNODESA' for bootstrap backup.
05/23/06 03:06:55 savegrp: Automatic cloning of saveset /var/home for client tireasol3 during savegroup operation has failed!
05/23/06 03:06:55 savegrp: Automatic cloning of saveset /var/home for client tireasol23 during savegroup operation has failed!
05/23/06 03:06:55 savegrp: Automatic cloning of saveset /var/desa for client tireasol23 during savegroup operation has failed!


I refer to the line: 05/23/06 03:02:56 nsrd: media notice: each clone host needs at least two enabled devices for save of client `tireaw2k10'

To what this mistake refers?

Very thanks

I never saw that message before even there is a reference to it in the savegrp manual (between the lines). I believe I saw from your first log that you use DDS so I'm thinking this could be an issue either with read hostname (see SN 60803) or/and how storage node has cloning storage node set (what you wish is that your storage node client has in clone storage node client listed itself - meaning you will need at least two devices for that - however when cloning starts you will need read hostname set to the name of that storage node too).

As I noted earlier, automatic cloning is not very smart and scripting offers much more (and you could avoid read hostname issues too).

To confirm above you should open the case with support.

I believe that you have reason, the two dds of the storage node were disabled, and the readhostname value was the storage node, i'm going to change the readhostname with the server name value to seeing what happens.
Already I tell you.
Thank you very much for your help.

Ok I believe tha t the problem is solved already, I have thrown the nsrclone from line of commands and has done it correctly, thank you very much for everything and for your help.