I believe that the save group will only automatically clone the save sets written to tape during this backup session. It will not clone the entire volume which was used for backups, only pick out the save sets written as part of the save group.
It looks like it has tried to clone the saveset and not given an error. Gustavo, can you add the parameter copies to the parameters after the -r and we will see what that is reporting - I expect it to say 1 but let's see what comes up.
Have you tried manually cloning the saveset that was not automatically cloned and if so was it successful?
mminfo -q "group=Pampa-Sql-Mensual, savetime>=96 hours ago " -o n -r "ssid, cloneid, copies, name, level, savetime, group, volume"
ssid clone id copies name lvl date group volume 400381794 1289574002 1 MSSQL:Intranet full 11/12/10 Pampa-Sql-Mensual PMPM58L4 383604581 1289574131 2 MSSQL:Intranet incr 11/12/10 Pampa-Sql-Mensual PMPM58L4 383604581 1289575086 2 MSSQL:Intranet incr 11/12/10 Pampa-Sql-Mensual F02247L4 366827366 1289574246 2 index:pmpcc10 full 11/12/10 Pampa-Sql-Mensual PMPM58L4 366827366 1289575086 2 index:pmpcc10 full 11/12/10 Pampa-Sql-Mensual F02247L4
I couldn´t understand the mistake about it , so I decided to start cloning manually. At the manual way it's it working correctly, may be my next step will be to make a script, it's strange but this problem it's affecting my sql auto cloning jobs.
You say you manually cloned it, I assume the mminfo output you posted was taken before that? Can you run it again just to verify that the full saveset was cloned?
Was this a one-off occurence or has it happened for all SQL clones? Do you run incrementals and if so are they cloning okay?
david_reniers
1 Message
0
November 11th, 2010 08:00
Hi,
I believe that the save group will only automatically clone the save sets written to tape during this backup session. It will not clone the entire volume which was used for backups, only pick out the save sets written as part of the save group.
David Reniers
DavidHampson-rY
294 Posts
0
November 12th, 2010 01:00
Gustavo
Could you post some mminfo output for this so we can see what has been cloned and what hasn't:
mminfo -q "client=clientname,savetime>1 day ago" -r name,savetime,ssid,cloneid,level,totalsize
Have you checked the logs for any errors relating to the cloning?
GustavoUehara
10 Posts
0
November 12th, 2010 07:00
Davids (both), Thank you for your response
here are the outputs:
Note: Automatic cloning finish Ok but it's not cloning the full "DB: MSSQL:Intranet SSID: 400381794".
Thank's
Email that notify me about the backup and clone job
--------------------------------------------------------------------------------------------------
Start time: Fri Nov 12 12:01:51 2010
Clone Start: Fri Nov 12 12:04:12 2010
End time: Fri Nov 12 12:06:21 2010
Automatic cloning of save sets to pool Pampa Clone LTO4 succeeded.
--- Successful Save Sets ---
* pmpcc10:MSSQL:Intranet 43708:nsrsqlsv:Start time: Fri Nov 12 12:00:00 2010
* pmpcc10:MSSQL:Intranet 43621:nsrsqlsv:Computer Name: PMPCC10 User Name: SYSTEM
* pmpcc10:MSSQL:Intranet NSR_BACKUP_LEVEL: full;
* pmpcc10:MSSQL:Intranet NSR_GROUP: Pampa-Sql-Mensual;
* pmpcc10:MSSQL:Intranet NSR_SAVESET_NAME: "MSSQL:Intranet";
* pmpcc10:MSSQL:Intranet NSR_SERVER: cubenw;
* pmpcc10:MSSQL:Intranet 53085:nsrsqlsv:Backing up of Intranet succeeded.
pmpcc10: MSSQL:Intranet level=full, 102 MB 00:02:08 1 file(s)
cubenw: index:pmpcc10 level=full, 100 MB 00:00:06 1263 files
--- Cloned Save Sets ---
Automatic cloning of save sets to pool Pampa Clone LTO4 succeeded.
----------------------------------------------------------------------------------------------------
mminfo output
-----------------------------------------------------------------------------------------------------
name ssid clone id lvl date total group volume
MSSQL:Intranet 383604581 1289575086 incr 11/12/10 1572 Pampa-Sql-Mensual F02247L4
MSSQL:Intranet 400381794 1289574002 full 11/12/10 105346964 Pampa-Sql-Mensual PMPM58L4
MSSQL:Intranet 383604581 1289574131 incr 11/12/10 1572 Pampa-Sql-Mensual PMPM58L4
----------------------------------------------------------------------------------------------------
daemon.raw
-----------------------------------------------------------------------------------------------------
42506 11/12/10 12:01:52 2 0 0 1 24852 0 cubenw nsrd savegroup info: starting Pampa-Sql-Mensual (with 1 client(s))
0 11/12/10 12:01:56 2 0 0 1 24852 0 cubenw nsrd Operation 473 started : Load volume `PMPM58L4', volume id `2258419222'..
42502 11/12/10 12:01:56 2 0 0 1 24852 0 cubenw nsrd media waiting event: Waiting for 1 writable volumes to backup pool 'Pampa Mensual LTO4' tape(s) on cubenw
33526 11/12/10 12:01:58 2 0 0 1 2269 0 cubenw nsrmmd#26 Start nsrmmd #26, with PID 2269, at HOST cubenw
38752 11/12/10 12:02:11 2 0 0 1 24852 0 cubenw nsrd /dev/rmt/12cbn Verify label operation in progress
38752 11/12/10 12:02:18 2 0 0 1 24852 0 cubenw nsrd /dev/rmt/12cbn Mount operation in progress
42504 11/12/10 12:04:02 2 0 0 1 24852 0 cubenw nsrd media event cleared: Waiting for 1 writable volumes to backup pool 'Pampa Mensual LTO4' tape(s) on cubenw
38718 11/12/10 12:04:02 0 0 2 1 24852 0 cubenw nsrd pmpcc10:MSSQL:Intranet saving to pool 'Pampa Mensual LTO4' (PMPM58L4)
0 11/12/10 12:04:05 2 0 0 1 24866 0 cubenw nsrmmdbd pools supported: Pampa Mensual LTO4;
38714 11/12/10 12:04:05 0 0 2 1 24852 0 cubenw nsrd pmpcc10:MSSQL:Intranet done saving to pool 'Pampa Mensual LTO4' (PMPM58L4) 102 MB
38718 11/12/10 12:04:05 0 0 2 1 24852 0 cubenw nsrd pmpcc10:MSSQL:Intranet saving to pool 'Pampa Mensual LTO4' (PMPM58L4)
38714 11/12/10 12:04:05 0 0 2 1 24852 0 cubenw nsrd pmpcc10:MSSQL:Intranet done saving to pool 'Pampa Mensual LTO4' (PMPM58L4) 2 KB
38718 11/12/10 12:04:06 0 0 2 1 24852 0 cubenw nsrd cubenw:index:pmpcc10 saving to pool 'Pampa Mensual LTO4' (PMPM58L4)
12361 11/12/10 12:04:06 2 0 0 1 24852 0 cubenw nsrd [Jukebox `IBM@2.6.1', operation # 473]. Finished with status: succeeded
38714 11/12/10 12:04:12 0 0 2 1 24852 0 cubenw nsrd cubenw:index:pmpcc10 done saving to pool 'Pampa Mensual LTO4' (PMPM58L4) 100 MB
0 11/12/10 12:04:13 2 0 0 1 24852 0 cubenw nsrd Operation 474 started : Load volume `F02247L4', volume id `1356334262'..
42502 11/12/10 12:04:13 2 0 0 1 24852 0 cubenw nsrd media waiting event: Waiting for 1 writable volumes to backup pool 'Pampa Clone LTO4' tape(s) on cubenw
42502 11/12/10 12:04:13 2 0 0 1 24852 0 cubenw nsrd media waiting event: waiting for LTO Ultrium-4 tape PMPM58L4 on cubenw
33526 11/12/10 12:04:15 2 0 0 1 2329 0 cubenw nsrmmd#26 Start nsrmmd #26, with PID 2329, at HOST cubenw
38752 11/12/10 12:04:26 2 0 0 1 24852 0 cubenw nsrd /dev/rmt/14cbn Verify label operation in progress
0 11/12/10 12:04:29 2 0 0 1 24866 0 cubenw nsrmmdbd pools supported: Pampa Mensual LTO4;
38752 11/12/10 12:04:33 2 0 0 1 24852 0 cubenw nsrd /dev/rmt/14cbn Mount operation in progress
42506 11/12/10 12:04:46 2 0 0 1 24852 0 cubenw nsrd write completion notice: Writing to volume PMPM58L4 complete
42504 11/12/10 12:04:53 2 0 0 1 24852 0 cubenw nsrd media event cleared: confirmed mount of PMPM58L4 on /dev/rmt/12cbn
42504 11/12/10 12:06:19 2 0 0 1 24852 0 cubenw nsrd media event cleared: Waiting for 1 writable volumes to backup pool 'Pampa Clone LTO4' tape(s) on cubenw
38718 11/12/10 12:06:19 0 0 2 1 24852 0 cubenw nsrd cubenw:cloning session saving to pool 'Pampa Clone LTO4' (F02247L4)
38730 11/12/10 12:06:19 0 0 2 1 24852 0 cubenw nsrd cloning session: 2 save set(s) reading from PMPM58L4 2 KB of 100 MB
38714 11/12/10 12:06:21 0 0 2 1 24852 0 cubenw nsrd cubenw:cloning session done saving to pool 'Pampa Clone LTO4' (F02247L4)
38732 11/12/10 12:06:21 0 0 2 1 24852 0 cubenw nsrd cloning session:save sets done reading 100 MB
38758 11/12/10 12:06:21 2 0 0 1 24852 0 cubenw nsrd savegroup notice: Pampa-Sql-Mensual completed, Total 2 client(s), 1 Clients Disabled, 1 Succeeded. Please see group completion details for more information.
12361 11/12/10 12:06:22 2 0 0 1 24852 0 cubenw nsrd [Jukebox `IBM@2.6.1', operation # 474]. Finished with status: succeeded
0 11/12/10 12:06:24 2 0 0 1 24866 0 cubenw nsrmmdbd pools supported: Pampa Clone LTO4;
42506 11/12/10 12:06:24 2 0 0 1 24852 0 cubenw nsrd write completion notice: Writing to volume F02247L4 complete
ble1
4 Operator
•
14.4K Posts
0
November 12th, 2010 18:00
daemon log seems to suggest this has been cloned. Not sure what you used for query in your mminfo command, but try following:
- query saveset and list volumes and number of copies
- query clone tape and list al ssids
DavidHampson-rY
294 Posts
0
November 14th, 2010 03:00
It looks like it has tried to clone the saveset and not given an error. Gustavo, can you add the parameter copies to the parameters after the -r and we will see what that is reporting - I expect it to say 1 but let's see what comes up.
Have you tried manually cloning the saveset that was not automatically cloned and if so was it successful?
GustavoUehara
10 Posts
0
November 15th, 2010 09:00
People, Actually this is the mminfo query :
mminfo -q "group=Pampa-Sql-Mensual, savetime>=96 hours ago " -o n -r "ssid, cloneid, copies, name, level, savetime, group, volume"
ssid clone id copies name lvl date group volume
400381794 1289574002 1 MSSQL:Intranet full 11/12/10 Pampa-Sql-Mensual PMPM58L4
383604581 1289574131 2 MSSQL:Intranet incr 11/12/10 Pampa-Sql-Mensual PMPM58L4
383604581 1289575086 2 MSSQL:Intranet incr 11/12/10 Pampa-Sql-Mensual F02247L4
366827366 1289574246 2 index:pmpcc10 full 11/12/10 Pampa-Sql-Mensual PMPM58L4
366827366 1289575086 2 index:pmpcc10 full 11/12/10 Pampa-Sql-Mensual F02247L4
I couldn´t understand the mistake about it , so I decided to start cloning manually. At the manual way it's it working correctly, may be my next step will be to make a script, it's strange but this problem it's affecting my sql auto cloning jobs.
Filesystem and Exchange cloning are working OK.
Thank you
DavidHampson-rY
294 Posts
0
November 15th, 2010 10:00
Gustavo
You say you manually cloned it, I assume the mminfo output you posted was taken before that? Can you run it again just to verify that the full saveset was cloned?
Was this a one-off occurence or has it happened for all SQL clones? Do you run incrementals and if so are they cloning okay?
regards
David
GustavoUehara
10 Posts
0
November 23rd, 2010 06:00
Answers
You say you manually cloned it, I assume the mminfo output you posted was taken before that?
Yes it's true, the mminfo posted was taken before the manual cloning
Can you run it again just to verify that the full saveset was cloned?
All the saveset was correctly cloned
Was this a one-off occurence or has it happened for all SQL clones?
We made somo tests with other groups, mssql clientes and they are cloning automatically withouth any problems.
I think that the problems it's because the backup job (save) it's not sending the parameters to nsrclone.
Up to now it's a strange error, If I found the error I will post the resolution.
thanks!