cancel
Showing results for 
Search instead for 
Did you mean: 

Converting entirely from LTO3 to LTO4

sclind
Moderator
Moderator
   VIP   

I have a Windows 2008 R2 server running Netbackup 7.5.0.7 with a Storagetek L700e attached.  Its 10 LTO3 drives are going to be replaced with 20 LTO4 drives.  After the upgrade I will no longer need to write on the LTO3 tapes but I may need to read them until they expire (two weeks after the upgrade).   I plan to remove the LTO3 media from the silo and only put them back in if a mount request comes up.

I have a few questions about the upgrade:

Q1) The current media – the LTO3 tapes - are all ‘hcart3’.  I want all newly inserted media – the LTO4 tapes – to go in as ‘hcart’.  How do I tell Netbackup how new media should be designated?

Q2) When the LTO3 drives are removed and the LTO4 drives are put in their place I would expect they should configure as ‘hcart’.  Is that correct?

Q3) The Storage Unit in the policies is called ‘L700e’.  It uses the ‘hcart3’ density/media type.   I think all I need to do here is change the ‘L700e’ Storage Unit to ‘hcart’. Is that correct?

Is there anything I have missed to have all the policies start using the new LTO4 media in the new LTO4 drives?  The old LTO3 media would only be mounted if I submitted a restore request.

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

My 2c:

Media Type Mappings is greyed out because this is for ACSLS robots only.

So, these are the steps that I would follow:

On the day of the tape drive replacement, do the following:

  • Delete all hcart3 Storage Units
  • Delete all hcart3 tape drives (no need to delete the robot if same robot will still be used)
  • In Media GUI, select all media that are in the robot, right-click and select 'Move' to logically move all tapes in the robot to non-robotic.
  • Deactivate all media servers
  • Shut down master and media servers
  • Wait till after hardware changes have completed.
  • Check that all LTO3 media is removed from the robot and that LTO4 media (with L4 suffix on barcodes) is loaded in the robot. 
  • Boot master and media servers. (Because all media servers are deactivated, no backups will kick in)
  • Check that zoning is done for new tape drives. Do Persistent Binding using the HBA tools on media server(s).
  • Check devices at OS level on all media servers - ensure LTO4 drives are seen and drivers are loaded. (The assumption here is that you will have multiple media servers as no single server will be able to stream that many drives)
  • Run 'scan' (...\veritas\volmgr\bin) on all media servers to ensure that tape drives repond to scsi-commands
  • Activate all media servers
  • Use Device Config Wizard an firstly select the media server that is the robot control host. Complete device config and Storage Unit Creation.
  • Use Device Config Wizard again, select rest of media servers. Complete device config and Storage Unit Creation.
  • You will see that tape drives and STU(s) are automatically added as hcart (because of NBU Device Mapping).
  • Inventory the robot. The L4 suffix on the barcode will ensure that media is added as hcart.
  • Update Storage Unit(s) in all backup policies.
  • You are now ready to test/run some backups.

To restore from old LTO3 media:
add tape to the robot, Inventory, then change one of the tape drives in NBU config to hcart3.
Run the restore.
Change tape drive back to hcart.

 

Hope this helps.
 


 

View solution in original post

15 REPLIES 15

Genericus
Moderator
Moderator
   VIP   

Bad news / Good news -

You should build a whole new set of HCART, groups, pools, etc

It is not that hard.

 

On my solaris master server, I have in /usr/openv/volmgr a file called vm.conf

vm.conf :

# cat vm.conf
ACS_UNKNOWN=HCART
ACS_LTO_1_5T=HCART
ACS_LTO_800G=HCART2

Essentially you tell NB what will be HCART, HCART2, HCART3 - they are user definable.

These values match what you see in the "Inventory Robot, Advanced Options, Media Type Mappings" Listing

HOWEVER!

1. You will want to keep a drive & storage unit as HCART3 because when you load an old tape it needs to match.

2. LTO drives tapes can read from earlier tapes, if you want you can waste an LTO4 and define as an LTO3. (I do not recommend this, because it cannot be both at once.)

3. You should end up with volume pools/volume groups/storage units/drives for your old HCART, as well as a new set for your new HCART.

 

NetBackup 9.1.0.1 on Solaris 11, writing to Data Domain 9800 7.7.4.0
duplicating via SLP to LTO5 & LTO8 in SL8500 via ACSLS

RonCaplinger
Level 6

Just out of curiosity, are you encrypting tapes now?  When we switched from LTO3 to LTO4 drives, we started using encryption at the drive level using our tape library vendor's solution, which encrypts all tape data on LTO4 tapes.  But this produced a problem for catalog backups, which should not be encrypted.  There was no way to create an unencrypted tape, EXCEPT by using an LTO3 tape in the LTO4 drives.

Just something else to keep in mind as you switch tape technology.

sclind
Moderator
Moderator
   VIP   

No encryption for us.

sclind
Moderator
Moderator
   VIP   

>These values match what you see in the "Inventory Robot, Advanced Options, Media Type Mappings" Listing

This tab is greyed out on the system.  Why would that be?

sclind
Moderator
Moderator
   VIP   

>1. You will want to keep a drive & storage unit as HCART3 because when you load an old tape it needs to match.

Based on this it sounds like I want to change the old LTO3 tapes to 'HCART' (and still remove them from the silo).

I dont want to burn a whole drive for a restore that may never happen.

sclind
Moderator
Moderator
   VIP   

Now that I've read this old thread it sounds like perhaps I should keep *everyhting* as HCART3:

http://mailman.eng.auburn.edu/pipermail/veritas-bu/2009-July/104883.html

http://mailman.eng.auburn.edu/pipermail/veritas-bu/2009-July/104884.html

 

The following steps should be taken to implement this type of migration
with NetBackup software. A typical example of this would be migrating
from LTO2 to LTO3.

1) Replace all of the old drives with new drives. Depending on how the
NetBackup device configuration wizard automatically configures the new
drives, or how they may have been manually configured, the drives may
need to be reconfigured to match the drive type of the old drives. This
is necessary so that the new drives can read the existing media.
I totally agree with what Don is saying, it makes much more sense to
change the density of the new drives to match the old drives and change
any new LTO4 media that's been put in to match as well.

 

Not only is there probably more to change if you're changing all of the
old media to the new media type, but each and every fragment in the
image catalog lists the media type that the fragment is on

Nicolai
Moderator
Moderator
Partner    VIP   

The plan for keeping everything as HCART3 will work if you do not mix LTO3 and LTO4 for writing operations.

 

sclind
Moderator
Moderator
   VIP   

Sounds like this is the way to go.  I'll just have to make sure I change the LTO4 drives from HCART  to HCART3 after they are discovered.

Greek-God
Level 3
Employee Accredited

Please refer to the technote - http://www.symantec.com/docs/TECH155814 

It might help to configure both LTO 3 and LTO 4 tapes in netbackup. 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

My 2c:

Media Type Mappings is greyed out because this is for ACSLS robots only.

So, these are the steps that I would follow:

On the day of the tape drive replacement, do the following:

  • Delete all hcart3 Storage Units
  • Delete all hcart3 tape drives (no need to delete the robot if same robot will still be used)
  • In Media GUI, select all media that are in the robot, right-click and select 'Move' to logically move all tapes in the robot to non-robotic.
  • Deactivate all media servers
  • Shut down master and media servers
  • Wait till after hardware changes have completed.
  • Check that all LTO3 media is removed from the robot and that LTO4 media (with L4 suffix on barcodes) is loaded in the robot. 
  • Boot master and media servers. (Because all media servers are deactivated, no backups will kick in)
  • Check that zoning is done for new tape drives. Do Persistent Binding using the HBA tools on media server(s).
  • Check devices at OS level on all media servers - ensure LTO4 drives are seen and drivers are loaded. (The assumption here is that you will have multiple media servers as no single server will be able to stream that many drives)
  • Run 'scan' (...\veritas\volmgr\bin) on all media servers to ensure that tape drives repond to scsi-commands
  • Activate all media servers
  • Use Device Config Wizard an firstly select the media server that is the robot control host. Complete device config and Storage Unit Creation.
  • Use Device Config Wizard again, select rest of media servers. Complete device config and Storage Unit Creation.
  • You will see that tape drives and STU(s) are automatically added as hcart (because of NBU Device Mapping).
  • Inventory the robot. The L4 suffix on the barcode will ensure that media is added as hcart.
  • Update Storage Unit(s) in all backup policies.
  • You are now ready to test/run some backups.

To restore from old LTO3 media:
add tape to the robot, Inventory, then change one of the tape drives in NBU config to hcart3.
Run the restore.
Change tape drive back to hcart.

 

Hope this helps.
 


 

sclind
Moderator
Moderator
   VIP   

Marianne - I think this is exactly what I am going to do.

My backups all expire within 15 days so the chances of me having to restore from an LTO3 is slim.  So your method is perfect.

You mention:

In Media GUI, select all media that are in the robot, right-click and select 'Move' to logically move all tapes in the robot to non-robotic.

Out of curiosity why does this matter since I am removing all the LTO3 media anyways?

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

I feel it is a good idea to let NBU know that the media is taken out.

You will probably not do an inventory after the LTO3 tapes have been removed with empty robot or use NBU to eject all the tapes?
Only do inventory when new tapes are in the robot after the drive change?

sclind
Moderator
Moderator
   VIP   

There are a lot of LTO3 tapes so I was planning on removing them manually from the L700.  Likewise inserting the new LTO4 tapes. So I was planning on a "Inventory Robot" before we started the backups.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

If memory serves me right, NBU has a problem when there is not a 'move out of the robot' for tapes and media is manually replaced.

Remember, if you do not eject from NBU or do a 'logical move' to Standalone of the LTO3's, the NBU config will still show them in robot slots but those slots are now occupied by totally different tapes.

The 'logical move' will take a few seconds and ensure all goes well when you Inventory with new tapes in the robot.

sclind
Moderator
Moderator
   VIP   

I did this conversion yesterday and I wanted to let everyone know it was successful using Marianne's method:

Before the HW tech arrived I removed all the LTO3 tapes and inventoried the silo (so Netbackup knows they are no longer there).

I then deleted the LTO3 drives. The robot's were left as is.

The HW tech then removed the 10 LTO3 drives and replaced with 20 LTO4 drives.

The new drives where then zoned, etc.

I rebooted the windows master and media servers.

I checked that the new drives were found in the device manager and via 'scan'.

I then discovered the 20 new 'hcart' devices.

I inserted 100 new LTO4 tapes and inventoried the silo. They came up as 'hcart'.

The storage unit we use that used to reference 'hcart3' was deleted and recreated using 'hcart'.

I ran some test backups and all was good.

 

This morning a fellow sysadmin needed a restore from an LTO3 tape.  I changed one of the drives from 'hcart' to 'hcart3'. I inserted the restore tapes and inventoried the silo.

When I submitted the restore it ran perfect!