UNSOLVED
L
larrywalters
1 Rookie
•
12 Posts
0
2592
April 25th, 2016 07:00
I don't want to clone to the Default pool
NetWorker v8.2.1.5.Build.793
EBR VBA v1.1.1.50
I created a new backup group that is just the physical backup server and the EBR VBA. I have them backing up to our Data Domain using DDBoost. I have the group set to clone at the start of each save set completion to a pool named Lex-EMC-Clone (LTO Ultrium-3 media pool). There is media available in the designated pool.
The problem is that it's trying to clone to the default pool instead of the pool I want it to. Any idea why?
Console Log Message:
1. Media Waiting event: Waiting for 1 writable volume(s) to backup pool 'Default' disk(s) or tape(s) on lexbkup01
2. Suggest manually labeling a new writable volume for pool 'Default'
If really no other backup runs at that point in time, I expect this to be a bug.
"Default" is a backup pool, not a backup clone pool.
If your pool is not a backup clone pool as mentioned, I expect NW to select the "Default Clone" pool but the not "Default" backup pool. Pools never mix data types.
You can verify the correct setup for your pool by running the clone command manually:
1. Verify one of the save sets you created during the backup. Get the save set id (ssid)
2. Run "nsrclone -v -b Lex-EMC-Clone -S ssid#"
Shubhadip_Datta
26 Posts
1259
0
Posted April 26th, 2016 00:00
Hi,
Its better first we need to ensure that the waiting for volume in Default pool is coming due to clone operation only not due to some other operation. You can better label a volume in default pool and see what actually happening on that volume. It can be due to some other operation also.
larrywalters
1 Rookie
•
12 Posts
1259
0
Posted April 26th, 2016 08:00
Thanks for your answer. After I discovered this problem, I setup a separate clone job of this data to the pool. It works fine as does the manually executed command line clone that you recommended.
larrywalters
1 Rookie
•
12 Posts
1259
0
Posted April 26th, 2016 08:00
Thanks for your answer but I checked the media pool type and it is in fact "Backup Clone".
larrywalters
1 Rookie
•
12 Posts
1259
0
Posted April 26th, 2016 09:00
Thanks for your answer. The backup portion does run correctly. It's just the clone operation that is the problem. I added media to the "Default" pool (which is a backup pool and not a backup clone pool). I restarted the job and the job completed "successfully" but not correctly.
The clone operation only cloned the save set for the boostrap and index of the backup server. It cloned it to both the Default media pool and the desired pool, Lex-EMC-Clone. None of the other save sets were cloned.
larrywalters
1 Rookie
•
12 Posts
1259
0
Posted April 26th, 2016 11:00
Thanks for your answers. I created another test pool and the same problem occurs. I don't think the problem is with the media pool. I can clone to it using a separate clone job.
gautamgp
1 Rookie
•
226 Posts
1259
0
Posted April 25th, 2016 20:00
Hi Larry,
The pool configuration does not look right to me. Please check if the pool "Lex-EMC-Clone" has the pool type set to "backup clone". If not, then delete the pool and recreate it with type "backup clone".