Forum Discussion

nevetslee's avatar
nevetslee
Level 2
13 years ago
Solved

Backup Exec 2012 - Backing up to removable drives

We've always backed up to removable drives. With v. 12.5 we never had a problem. We told BE to backup to Z:\B2D and it never gave us any issues. With BE 2010 R3 we had problems with the dirves going offline, but customer training took care of that. As long as the client went in a put the drive online (should it go offline) we were still able to backup to USB/ eSATA drives using Z:\B2D.

 

With BE 2012 I can configure storage on a drive, but once Drive A is unplugged and drive B is plugged in Drive A goes offline. When Drive A is plugged in the path is shown as Z:\BEData\. Once Drive B is plugged in the path is shown as \\?\Volume{f3e905be-6fe8-11de-9395-0024e857504d}\BEData\ (which varies depending on the drive).

My work-around was to configure storage on all 5 drives, which works for this client. If Drive C is plugged in the other 4 show as offline, but it is picked up and shows as online. If you lug Drive A back in the path again shows as Z:\BEData.

My question: Is there a way to fix it so that BE 2012 will not look to volumes, and will instead look to drive letters? This is ok if a client has 5 drives, but I have one client who has 50 drives (and a very complex environment).

Or do I have to configure storage on all 50 drives and really clutter up the device tab?

Thanks,

Steve

  • Steve:

    Back in the release time of 12.x we (Backup Exec) would track removable media by drive letters.  This was a bit inconsistant because what we expected as Drive Z: may not always appear mountable as drive Z:\.  A change was made to the product in the 2010 release that would track the drive GUID as opposed to the logical drive letter assigned by windows.  this is more reliable as each time the drive is mounted we will regonize the GUID and have it avalialbe to us. 

    With the 2012 product we have introduced the idea of "Unpluggable fixed disks" like a WD My Book or Seagate FreeAgent GoFlex and “Devices with Removable Storage”, drives where cartridges can be removed from the drive like RDX but the drive is still attached to computer.  Backup Exec 2012 handles unpluggable fixed disks and “devices with removable storage.”  Fixed disks, whether unpluggable or not, are only configurable as Disk Storage (ordinary B2D) not Disk Cartridge (removable B2D).  “Devices with removable storage” are only configurable as Disk Cartridge.

    Backup Exec 2012 each configured unpluggable hard disk is tracked uniquely. 

    Disk Cartridge devices are not managed by our Data Lifecyle Manament (DLM), this was by design in the BE 2012 product.  They still use the same media set retention that Backup Exec has always used. 

    For the most part a Disk Cartridge in BE 2012 is handled like tape. 

    If what you are dealing with are drives, For instance SATA Drives.  There are some SATA drives that support removing disks but don’t register with BE as removed/swapped… there is speculation that this could be a hardware/driver issue.  I personally have an eSATA card from Dynex in one of my systems but it doesn’t show external hard disks attached to it in the “Safely Remove” menu in the system tray even though they should.  On the other hand, the internal SATA C: hard disk in my personal computer at home shows up in “Safely Remove” even though you couldn’t possibly remove your C: safely?.  The point is that the adapter hardware and/or driver can affect the OS’s knowledge of the “unpluggability” of hard disks.

    However, if the OS knows that the disk has been changed when the “cartridges” are swapped, then BE should know as well.  And if the OS does not know, they have bigger problems that BE; they could get data corruption.  If the disk does show up in “Safely Remove”, then you should be issuing a safe removal though that menu before swapping cartridges or they could possibly be corrupting their disks.

    Now that the long winded explination is out of the way, you asked about the possibility of a workaround for your issue.  There is another thread (https://www-secure.symantec.com/connect/forums/sata-drives-usb-dock-be2012-whats-best-method-setup)  where Mark Russinovich  (ex Sysinternals/Microsoft guy) provides a utility that may help you out.

    http://blogs.technet.com/b/markrussinovich/archive/2011/11/08/3463572.aspx.

    Work-around:

    1. Attach first disk to your server and use DISKPART to find the signature
      SELECT DISK #, where # is the disk number in you system (use Disk Management to find disk number).
      UNIQUEID DISK
      This will give you a 4 byte disk ID e.g. "e9eb3aa5"
    2. Now attach the second (or third, etc) and do the same, find the UNIQUE ID, which will show as the same ID as the first. With the same DISKPART tool you can overwrite the ID with a new ID, try incrementing the number with 1 (that is what I did) for each new disk.
      Use the command in DISKPART: UNIQUEID DISK ID=e9eb3aa6, where the ID is the id you choose, this is just an example (see also the article above).
    3. After the ID is changed, I deleted all BE folders from that disk (/BEControl and /BEdata), disconnect the USB drive and reconnected it.
    4. This time BE Storage does not find the disk in the list and you can Add a new disk.

     

    Let me know if this helps,

    Joshua

     

     

  • Steve:

    Back in the release time of 12.x we (Backup Exec) would track removable media by drive letters.  This was a bit inconsistant because what we expected as Drive Z: may not always appear mountable as drive Z:\.  A change was made to the product in the 2010 release that would track the drive GUID as opposed to the logical drive letter assigned by windows.  this is more reliable as each time the drive is mounted we will regonize the GUID and have it avalialbe to us. 

    With the 2012 product we have introduced the idea of "Unpluggable fixed disks" like a WD My Book or Seagate FreeAgent GoFlex and “Devices with Removable Storage”, drives where cartridges can be removed from the drive like RDX but the drive is still attached to computer.  Backup Exec 2012 handles unpluggable fixed disks and “devices with removable storage.”  Fixed disks, whether unpluggable or not, are only configurable as Disk Storage (ordinary B2D) not Disk Cartridge (removable B2D).  “Devices with removable storage” are only configurable as Disk Cartridge.

    Backup Exec 2012 each configured unpluggable hard disk is tracked uniquely. 

    Disk Cartridge devices are not managed by our Data Lifecyle Manament (DLM), this was by design in the BE 2012 product.  They still use the same media set retention that Backup Exec has always used. 

    For the most part a Disk Cartridge in BE 2012 is handled like tape. 

    If what you are dealing with are drives, For instance SATA Drives.  There are some SATA drives that support removing disks but don’t register with BE as removed/swapped… there is speculation that this could be a hardware/driver issue.  I personally have an eSATA card from Dynex in one of my systems but it doesn’t show external hard disks attached to it in the “Safely Remove” menu in the system tray even though they should.  On the other hand, the internal SATA C: hard disk in my personal computer at home shows up in “Safely Remove” even though you couldn’t possibly remove your C: safely?.  The point is that the adapter hardware and/or driver can affect the OS’s knowledge of the “unpluggability” of hard disks.

    However, if the OS knows that the disk has been changed when the “cartridges” are swapped, then BE should know as well.  And if the OS does not know, they have bigger problems that BE; they could get data corruption.  If the disk does show up in “Safely Remove”, then you should be issuing a safe removal though that menu before swapping cartridges or they could possibly be corrupting their disks.

    Now that the long winded explination is out of the way, you asked about the possibility of a workaround for your issue.  There is another thread (https://www-secure.symantec.com/connect/forums/sata-drives-usb-dock-be2012-whats-best-method-setup)  where Mark Russinovich  (ex Sysinternals/Microsoft guy) provides a utility that may help you out.

    http://blogs.technet.com/b/markrussinovich/archive/2011/11/08/3463572.aspx.

    Work-around:

    1. Attach first disk to your server and use DISKPART to find the signature
      SELECT DISK #, where # is the disk number in you system (use Disk Management to find disk number).
      UNIQUEID DISK
      This will give you a 4 byte disk ID e.g. "e9eb3aa5"
    2. Now attach the second (or third, etc) and do the same, find the UNIQUE ID, which will show as the same ID as the first. With the same DISKPART tool you can overwrite the ID with a new ID, try incrementing the number with 1 (that is what I did) for each new disk.
      Use the command in DISKPART: UNIQUEID DISK ID=e9eb3aa6, where the ID is the id you choose, this is just an example (see also the article above).
    3. After the ID is changed, I deleted all BE folders from that disk (/BEControl and /BEdata), disconnect the USB drive and reconnected it.
    4. This time BE Storage does not find the disk in the list and you can Add a new disk.

     

    Let me know if this helps,

    Joshua

     

     

  • Joshua,

    Thank you very much for the long winded reply. It actually helps my understanding. I can see how having BE recognize the GUID is going to make a more stable environment.

    I did follow the link you provided and it looks like it's more of solution to disks having the same ID. I was sort of hoping I could get away with having all 5 drives usable as Z:, without having to actually have 5 drives listed under the media tab. Am I looking at it wrong? :)

    I'm guessing the correct way to setup the backup jobs is to use pools. For instance at one client we have both a Y: and a Z: drive. Z: gets Nightly Backups, Y: gets a weekend job. So I'd make a drive pool of 40 or so drives for the Nightly, and a Drive pool of 10 or so drives for the weekend job. Then just point the Backup Job to the drive Pool, rather than to a disk.

    Or am I totally missing what you were saying? :)

  • You should always use device pools so that you do not need to change your jobs when you change yuor drives.  When you target your jobs to a device pool, it will use the first available device in the pool.  Assuming that you only have one of your removable disks plugged in at a time, this should work fine.

    You don't have to worry about which drive letter is used by the drive when it get plugged in.  BE will take care of that.  You can have a disk showing up as Z: at one time and Y: at another time and it does not matter.  It is the disk id that does.

  • Thanks PKH. I appreciate the response.

    So two sets of Backups going to two different drives (A Y and  a Z) should actually be two drive pools.

    Correct?

  • No, that would defeat the purpose of a pool

    Creat a Pool   "Daily Backups" for example.  then place any devices you write daily backups to into that pool, and point the Daily job to that pool
     

    When the job runs, it will look for any device from that pool that is online, and use the first one it finds (see pkh's response earlier)

  • I didn't explain well. We have a client who has one set of drive they use for Nightly Backups (M-F). Presently that is the Z: drive but when we upgrade them it will become a Nightly Pool. They then have a second set of drives, presently all mapped to Y:, that they use for a weekend VHD Backup (Saturday). That will become the VHD Pool.

    So when we upgrade them I'll have to configure their drives to point to one pool or the other, which is going to be a chore, but it sounds like it will fix the continual problem we've had of drives going Offline when they swap them out.

    Does that make more sense? :)

    I really appreciate the guidance. You guys are making me the company expert.

    Steve

  • if for example, the daily backups are written to Drives 1-5 and the weekly backups are written to drives 6-12,  then place  the devices/folders for the first 5 drives in the daily pool and the other seven in the weekly pool

    Then edit the Daily job and point it to the Daily pool rather than All Pools.  Do the same with the Weekly job