cancel
Showing results for 
Search instead for 
Did you mean: 

DSSU status 83

Will_Restore
Level 6

Somehow our Disk Staging Storage Unit (DSSU) mountpoints got mixed up.  Basic disk1, disk2, disk3 normally mount on /stage1, /stage2, /stage3 respectively.  Now disk1 is mounted on /stage2 and vice versa and Duplication jobs are failing for some older backups with Error 2060013 and Status 83. 

We can remount the disks so they are back in proper order, though other Duplication jobs will start failing because recent backups will then be mixed up. 

So to recap, older backups went to /stage1 but the images are actually on /stage2.  We can correct that by remounting the disks.  Meanwhile newer backups to /stage2 will be on /stage1 after the remount causing newer Duplications to fail. 

Is there an easy way to fix this other than move a bunch of images around?

 

2 ACCEPTED SOLUTIONS

Accepted Solutions

Nicolai
Moderator
Moderator
Partner    VIP   

Don't think so. Alternative give up and expire the backup images on DSSU in the time frame.

Or to be really safe suspend all relocation - run a new backup and then expire the mixed up backup images.

Best Regards

Nicolai

View solution in original post

RiaanBadenhorst
Level 6
Partner    VIP    Accredited Certified
You could create links for all files in /stage1 to /stage2 and vice versa Then later delete the links.

View solution in original post

3 REPLIES 3

Nicolai
Moderator
Moderator
Partner    VIP   

Don't think so. Alternative give up and expire the backup images on DSSU in the time frame.

Or to be really safe suspend all relocation - run a new backup and then expire the mixed up backup images.

Best Regards

Nicolai

RiaanBadenhorst
Level 6
Partner    VIP    Accredited Certified
You could create links for all files in /stage1 to /stage2 and vice versa Then later delete the links.

Will_Restore
Level 6

Thanks, thought about links but that takes almost as much time as moving the files, which we are now doing.  The larger, more important backups (email, database, etc.) are being relocated as they would take a few days to redo.  The smaller stuff we can remove and rerun when convenient.

Odd this media server has been rebooted many times after OS patch and this is the first time I recall the disk mounts getting messed up (and the patches that should not have caused that; another matching environment did not experience the disk mix-up)