The disk library has 4 mountpaths connected via fiber channel.
Unfortunately, one of these has hit a snag and is beyond repair, which might cause issue when browse/recover backup data.
While we could consider running a full backup for all servers tied to this lib, but it's not exactly our top choice.
Question:
How to pinpoint the affected clients on the faulty mount path and find the oldest backup history for these clients? (do need open a support case and upload CS DB ?)
Once I've got that info, I can kick off fresh full backups just for those clients and also manually age data based on the backup history findings.
i think i will have to start manual full backup for clients tied to the library coz full schedule which typically runs on a monthly basis. Or Upon successful completion of the DDB verification, jobs with failed data blocks will automatically convert to full jobs when daily backup kick off ?
Once the jobs that failed verification are deleted and data aging has been run there is no need to run Full backups. We will just add new DDB records for things that were pruned due to the deletion.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.