Video Screencast Help

Error 2106 after expanding DD database volume

Created: 20 Aug 2013 • Updated: 23 Aug 2013 | 3 comments
This issue has been solved. See solution.

Hello Everyone,

As the title says, we expanded the dedupe database volume without stopping the services. A big no-no...yes I know :(   but we realized this after we did this.

Now we get an error 2106 for all backups using the DD volume.

Any ideas how to fix this?

Many thanx,

Operating Systems:

Comments 3 CommentsJump to latest comment

Marianne's picture

Have you restarted NBU services followed by Inventory of the disk pool?

If you have already done so, probably best to log a support call.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

BTLOMS's picture

Restarted Services, restarted server - no luck

also ran nbdevconfig command with -UP and then with RESET key

no luck.

going to try one more reboot.

BTLOMS's picture

ok so this was the issue:

the disks was online, but volume was down: because netbackup was rebuilding a corrupted CRDB. After this it started processing all pending tlogs. it took about 12 hours to complete this. We understood it was processing old logs by monitoring the spoold logs CR process queue. After this we just UP'd the volume and it came back.