06-05-2014 03:43 AM
06-05-2014 05:20 AM
1) If you have GRT enabled backup sets (especially if using Incremental backups involving GRT) then changing the drive letter of the disk storage after the backup may give a problem restoring from those sets and you might hjave ot oput the original drive letter back (tempoirarily) to do GRT restroes. Possibly OK for just temp cover for a week but somethign you do need to be aware of.
2) Make sure you restart all incremental and differential jobs with a new sequence starting tiwth a full backup (especially if GRT is enabled) when you start using the new drive so that nothing tries to link itself to the original sets on the original drive letter.
3) You will probably have to create a new b2d device on the new disk and then retarget your backup jobs as we don't just store the drive letter of the B2D volumes, we also store GUID type identifiers and adjust the drive letter should we find that the identifier is linked with a different letter.
06-05-2014 05:49 AM
06-05-2014 07:33 AM
For 3:
You can test this. With your B2D still set to H: sto[p all the Backup Exec services.
Use Windows Disk Manager to change teh drive letter to say J:
Start the BE services and open the BE console
You will probably find that after a few minutes the B2D devcie comes onlien and if you look at teh peroperties you wil see that teh drive letter has changed. Obviously oput this back after you have done this test.
What this shows is that if you change the drive ltter BE will know it is the same B2D and if you do not edit the jobs that will just write to the new drive letter and that tro use the new drive you would have to cerate a new B2d and retarget the jobs.
The only way I know of to retarget the jobs in a block is to setup the new B2d and then in the beconsole delete the old B2D which will then prompt for what you want to do with the jobs that use it, although it is possible you could do something with BEMCLI scripting.
-----------
For 2: I kind of have to give miore info against 1 first
What I am saying is that if you do you full backup of a GRT enabled set to H:\B2DGRT
That it will create something like
H:\B2DGRT\IMG0005\<a number of files>
and if an incremental of the same source data is then also run it might create
H:\B2DGRT\IMG0008\<a number of files>
As part of the content of the files created within IMG0008 there are config records that link directly back to IMG0005 and these config recoreds use the full path including the drive letter
If you then change the drive letter these config records will point to the wrong drive letter causing problems for the GRT restore from the incremental (although you wil probably still be able to restore from the full.
This does not affect none GRT (bkf file) content as this is purely handled by catalogs and the media inventory and not linked to drive letters
Now to explain 2 - If your full is still on the old drive and your incremental is on the new one there will be a link as defined above. Hence the recommendation to run full jobs to start this change of drives.
06-09-2014 03:09 AM