Professional Documents
Culture Documents
Release 7.1
21159731
Legal Notice
Copyright 2011 Symantec Corporation. All rights reserved. Symantec, the Symantec Logo, Veritas, and NetBackup are trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. This Symantec product may contain third party software for which Symantec is required to provide attribution to the third party (Third Party Programs). Some of the Third Party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. Please see the Third Party Legal Notice Appendix to this Documentation or TPIP ReadMe File accompanying this Symantec product for more information on the Third Party Programs. The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Symantec Corporation and its licensors, if any. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19 "Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in Commercial Computer Software or Commercial Computer Software Documentation", as applicable, and any successor regulations. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement.
Symantec Corporation 350 Ellis Street Mountain View, CA 94043 http://www.symantec.com Printed in the United States of America. 10 9 8 7 6 5 4 3 2 1
Technical Support
Symantec Technical Support maintains support centers globally. Technical Supports primary role is to respond to specific queries about product features and functionality. The Technical Support group also creates content for our online Knowledge Base. The Technical Support group works collaboratively with the other functional areas within Symantec to answer your questions in a timely fashion. For example, the Technical Support group works with Product Engineering and Symantec Security Response to provide alerting services and virus definition updates. Symantecs support offerings include the following:
A range of support options that give you the flexibility to select the right amount of service for any size organization Telephone and/or Web-based support that provides rapid response and up-to-the-minute information Upgrade assurance that delivers software upgrades Global support purchased on a regional business hours or 24 hours a day, 7 days a week basis Premium service offerings that include Account Management Services
For information about Symantecs support offerings, you can visit our Web site at the following URL: www.symantec.com/business/support/ All support services will be delivered in accordance with your support agreement and the then-current enterprise technical support policy.
Hardware information Available memory, disk space, and NIC information Operating system Version and patch level Network topology Router, gateway, and IP address information Problem description:
Error messages and log files Troubleshooting that was performed before contacting Symantec Recent software configuration changes and network changes
Customer service
Customer service information is available at the following URL: www.symantec.com/business/support/ Customer Service is available to assist with non-technical questions, such as the following types of issues:
Questions regarding product licensing or serialization Product registration updates, such as address or name changes General product information (features, language availability, local dealers) Latest information about product updates and upgrades Information about upgrade assurance and support contracts Information about the Symantec Buying Programs Advice about Symantec's technical support options Nontechnical presales questions Issues that are related to CD-ROMs or manuals
Contents
Section 1
Chapter 2 Chapter 3
Chapter 4
Contents
Chapter 5
Managing AdvancedDisk
................................................... 37 37 37 38 38 39 40 40 40 41 41 42 43 43 44 44 45 45 46 46 47 48
Managing AdvancedDisk storage servers .......................................... Deleting an AdvancedDisk storage server ................................... Determining AdvancedDisk storage server state .......................... Removing AdvancedDisk storage server attributes ....................... Removing an AdvancedDisk storage server from disk pool access ............................................................................ Viewing AdvancedDisk storage servers ...................................... Viewing AdvancedDisk storage server attributes .......................... Managing AdvancedDisk disk pools ................................................. Adding volumes to an AdvancedDisk disk pool ............................ Changing AdvancedDisk disk pool properties .............................. Changing AdvancedDisk disk pool state ..................................... Changing AdvancedDisk disk volume state ................................. Deleting an AdvancedDisk disk pool .......................................... Determining AdvancedDisk disk pool state ................................. Determining AdvancedDisk disk volume state ............................. Merging AdvancedDisk disk pools ............................................. Removing a volume from an AdvancedDisk disk pool .................... Viewing AdvancedDisk disk pools ............................................. Monitoring AdvancedDisk storage capacity and usage ........................ Monitoring NetBackup disk activity ................................................. Viewing disk reports .....................................................................
Chapter 6
Section 2
Chapter 7
Chapter 8
Contents
About the OpenStorage plug-in ....................................................... About OpenStorage disk pools ........................................................ About spanning volumes on OpenStorage disk pools ..................... About OpenStorage optimized duplication methods ........................... About optimized duplication within the same domain ................... About duplicating images to a remote NetBackup master server ............................................................................ About OpenStorage optimized synthetic backups ............................... About OpenStorage direct to tape .................................................... About NDMP requirements for OpenStorage direct to tape ............ About media server requirements for OpenStorage direct to tape ............................................................................... About media server recommendations for OpenStorage direct to tape ........................................................................... About OpenStorage direct to tape limitations .............................. About the OpenStorage direct to tape process .............................. About Nirvanix cloud storage ......................................................... About the Nirvanix storage pool ............................................... About Nirvanix child accounts .................................................. About backup image representation in the Nirvanix cloud ............. About data encryption for cloud storage ..................................... About Nirvanix storage requirements and limitations ...................
62 63 63 64 64 65 66 67 68 70 71 71 71 72 73 73 74 74 75
Chapter 9
Chapter 10
Chapter 11
10
Contents
OpenStorage disk pool properties .............................................. 90 Configuring an OpenStorage storage unit ......................................... 91 OpenStorage storage unit properties ......................................... 92 About OpenStorage storage unit recommendations ...................... 94 Configuring OpenStorage optimized duplication behavior ................... 96 Configuring OpenStorage optimized duplication within the same domain ................................................................................. 98 Configuring OpenStorage direct to tape .......................................... 100 Configuring OpenStorage optimized synthetic backups ..................... 102 Adding OpenStorage functionality to an existing environment ........... 102 Setting NetBackup configuration options by using bpsetconfig ........... 103
Chapter 12
Contents
11
Monitoring OpenStorage storage capacity and usage ........................ Viewing OpenStorage disk reports ................................................. About catalog backups to OpenStorage devices ................................ About restoring from backup copies ...............................................
Chapter 13
Section 3
Chapter 14
Section 4
Chapter 15
Chapter 16
Chapter 17
12
Contents
Verifying the connectivity ............................................................ About configuring the Shared Storage Option in NetBackup ............... About configuring SSO in NetBackup ....................................... Configuring Shared Storage Option devices in NetBackup ............ About adding Shared Storage Option configuration options ......... About configuring NetBackup storage units and backup policies ......................................................................... Verifying your Shared Storage Option configuration .........................
Chapter 18
Chapter 19
Chapter
About this guide About NetBackup SAN Client and Fibre Transport
The AdvancedDisk option allows multiple NetBackup media servers to share the disk storage that is attached to a NetBackup media server. (Attached means a file system mount on the storage.) See About the AdvancedDisk option on page 17. The OpenStorage option allows multiple NetBackup media servers to share intelligent disk appliance storage or cloud-based storage. See About the NetBackup OpenStorage option on page 57. The SharedDisk option allows multiple NetBackup media servers to share disk array storage. See About SharedDisk support in NetBackup 7.0 and later on page 133. The Shared Storage Option allows multiple NetBackup media servers to share individual tape drives (standalone drives or drives in a robotic library). See About the Shared Storage Option on page 137.
14
Introducing shared storage About NetBackup SAN Client and Fibre Transport
Section
AdvancedDisk option
Chapter 2. Introducing AdvancedDisk Chapter 3. Licensing AdvancedDisk Chapter 4. Configuring AdvancedDisk Chapter 5. Managing AdvancedDisk Chapter 6. Toubleshooting AdvancedDisk
16
Chapter
Introducing AdvancedDisk
This chapter includes the following topics:
Disk volumes
Network file system mounts NetBackup media servers function as both storage servers and data movers
Is easy to deploy and use. NetBackup discovers the storage and uses familiar NetBackup storage units and backup policies to use the storage.
18
Allows multiple file systems to be used in a single storage unit. Allows user to increase storage unit capacity by adding disks. Only add the capacity required, then update the NetBackup disk pools. Logical units of storage span physical boundaries, so you do not have to create new NetBackup storage units or change the backup policies. Reduces the level of administrator attention. Automatic policies distribute job load and intelligently manage capacity so that jobs do not fail because of out of space conditions.
Chapter
Licensing AdvancedDisk
This chapter includes the following topics:
You cannot create the disk pools or the storage units that reference AdvancedDisk disk pools. NetBackup jobs that attempt to use the disk pools or the storage units that are based on disk pools fail. The error message indicates that the feature is not licensed.
NetBackup does not delete the disk pools or the storage units that reference the disk pools. You can use them again if you enter a valid license key.
20
Licensing AdvancedDisk
No special installation is required for the NetBackup components of AdvancedDisk. However, you must enter a license key. If you installed the license key when you installed or upgraded NetBackup, you do not need to perform this procedure. Enter the license key on the NetBackup master server. The following procedure describes how to use the NetBackup Administration Console to enter the license key. To license AdvancedDisk
1 2 3 4 5
To add a license to a specific server, select File > Change Server and then select the server. In the NetBackup License Keys dialog box, click New. In the Add a New License Key dialog box, enter the license key and click Add or OK. Click Close. Restart all the NetBackup services and daemons.
Chapter
Configuring AdvancedDisk
This chapter includes the following topics:
Configuring the AdvancedDisk option About AdvancedDisk file system requirements About AdvancedDisk storage servers About AdvancedDisk data movers About AdvancedDisk shared storage access About AdvancedDisk preferred or required read servers Configuring an AdvancedDisk storage server About AdvancedDisk disk pools Configuring an AdvancedDisk disk pool Configuring an AdvancedDisk storage unit
The NetBackup Administrator's Guide for Windows, Volume I. The NetBackup Administrator's Guide for UNIX and Linux, Volume I.
22
Section
See About AdvancedDisk file system requirements on page 22.
Step 2
Learn about storage servers See About AdvancedDisk storage servers and data movers on page 23. See About AdvancedDisk data movers on page 23.
Step 3
Learn about what can affect See About AdvancedDisk shared storage access how you configure storage on page 24. servers See About AdvancedDisk preferred or required read servers on page 24. Configure a storage server See Configuring an AdvancedDisk storage server on page 26. See About AdvancedDisk disk pools on page 29. See Configuring an AdvancedDisk disk pool on page 29. See Configuring an AdvancedDisk storage unit on page 32.
Step 4
Step 5 Step 6
Step 7
Step 8
Configure a policy that uses See the NetBackup Administrator's Guide for an AdvancedDisk storage Windows, Volume I. unit See the NetBackup Administrator's Guide for UNIX and Linux, Volume I.
23
See Configuring an AdvancedDisk disk pool on page 29. Additional requirements and limitations are as follows:
You must use manual mount points. Automatic mount and unmount can change mount points, which may cause disk resources to be unavailable. The NFS server that exports the mount points must be configured to allow root access to the file systems.
Note: Symantec recommends that you do not span backup images across NFS volumes in an AdvancedDisk disk pool. File system full conditions cannot be detected adequately. Therefore, a disk pool based on NFS volumes should be comprised of only one volume. Windows CIFS not supported On Windows, networked mapped devices are not visible to Windows services, and AdvancedDisk cannot discover Common Internet File System disk volumes. Therefore, AdvancedDisk does not support the Common Internet File System.
24
Each media server must mount the file systems of all the disk volumes within a disk pool. The mount points must be the same on each media server. NetBackup does not validate mount points, so you must ensure that the mount points are the same for each media server. You also must ensure that the mount points are valid. To obtain a consolidated list of disk volumes, NetBackup queries every media server. For large sets of servers, queries may affect performance. Disk volume status is monitored on a single media server. Which server monitors the status can change. Therefore, a change in disk volume availability on one media server may not be reflected in the disk volume status NetBackup reports.
To enable AdvancedDisk shared storage access by more than one media server: upgrade the NetBackup master server and the EMM server to NetBackup 6.5.2 or later. (Normally, the master server and the EMM server are on the same computer.) You do not have to upgrade 6.5 media servers. NetBackup 6.5 and later commands support multiple AdvancedDisk media server access to the storage. You can configure disk pools by using the NetBackup Administration Console on the master server or NetBackup commands. To configure shared access, configure multiple media servers as storage servers. See Configuring an AdvancedDisk storage server on page 26.
25
ReqRestore
The server is required for the read side of restore operations. You can configure more than one server as required for restore. If you configure required servers for restore but not preferred servers, jobs queue until a required server is available to execute the job. Other servers are never considered for restore jobs. Normal NetBackup rules for job retry apply. If you configure both preferred and required storage servers and a required server is not available, NetBackup considers preferred servers for jobs. If none are available, jobs queue until a required or preferred server is available. Other servers are never considered for restore jobs. Normal NetBackup load balancing occurs for all required servers. Load balancing does not occur between the required and preferred servers.
ReqDuplicate
The server is required for the read side of duplication operations. You can configure more than one server as required for duplication. If any server is configured as required for duplication, NetBackup considers only required for duplication servers for jobs. If a required server is unavailable, jobs queue until a required server is available to execute the job. Normal NetBackup rules for job retry apply. Required for duplication also applies to storage server allocation for synthetic backup operations.
Only the media servers that are configured in the storage unit are considered for jobs. Therefore, if you configure a subset of the disk pool media servers in a storage unit, NetBackup selects from those servers only. If you use the preferred or required restore or duplication attributes for a storage server, the following may occur:
A restore operation uses a storage server that does not have a PrefRestore or ReqRestore attribute. Reasons may be as follows:
26
The destination disk pool does not include a storage server with a restore or a duplication attribute. A preferred or required storage server cannot be used because it is unavailable (NetBackup considers it DOWN).
A restore or a duplication operation is queued. The reason may be that a preferred or required storage server cannot be used because it is unavailable (NetBackup considers it DOWN).
If you do not configure preferred or required restore servers, NetBackup uses normal criteria to select a media server for restore or duplication. (That is, if you configure more than one storage server.) Information about how NetBackup balances storage unit and media server load is available. See Maximum concurrent jobs in the following guides:
NetBackup Administrators Guide for UNIX and Linux, Volume I NetBackup Administrators Guide for Windows, Volume I
You can use preferred or required restore servers rather than the Media host override host property. Information about the Media host override property is available. See the following guides:
NetBackup Administrators Guide for UNIX and Linux, Volume I NetBackup Administrators Guide for Windows, Volume I
Upgrade the NetBackup master server and the NetBackup EMM server to NetBackup 6.5.2 or later. (Normally, the master server and the EMM server are on the same computer.) Optionally, to enable command-line support on media servers, upgrade the media servers that are used for AdvancedDisk operations to NetBackup 6.5.2 or later. You do not have to upgrade the media servers. You can configure and manage the restore and the duplication storage servers by invoking the commands on the master server.
27
Use the Storage Server Configuration Wizard to configure a storage server. However, if you want to configure preferred or required attributes, use the nbdevconfig command. You can configure multiple storage servers. If you do, you must run the wizard for each storage server you want to configure. You must configure as storage servers the NetBackup media servers that have read and write access to the storage. See About AdvancedDisk storage servers on page 23. When you configure a storage server, it also is configured as a data mover. See About AdvancedDisk data movers on page 23. See About AdvancedDisk preferred or required read servers on page 24. To configure an AdvancedDisk storage server by using the wizard
Determine if the storage server is configured already. See Viewing AdvancedDisk storage servers on page 40.
2 3
In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Configure Disk Storage Servers. Follow the wizard screens to configure a storage server.
Determine if the storage server is configured already. See Viewing AdvancedDisk storage servers on page 40.
Run the following command on the NetBackup master server or the media server:
nbdevconfig -creatests -storage_server hostname -stype AdvancedDisk [-st storage_type] -media_server hostname [-setattribute attribute]
28
-storage_server The name of the NetBackup media server that has a file system mount on the storage. storage_server -stype hostname -st storage_type Use AdvancedDisk. A numeric value that specifies the storage server properties. For AdvancedDisk, the default is 5 (direct attached, formatted disk). Required only if you want to use a value other than the default. Determine the value by adding together the numeric values of the following properties: 1 - formatted disk. The disk is formatted as part of the vendor-specific preparation; NetBackup does not format the disk. 2 - raw disk. The disk is not formatted; NetBackup formats the disk. 4 - direct attached. Direct-attached means that the storage server and media server are the same NetBackup host. 8 - network attached. Network-attached means that the storage server is physically distinct from the NetBackup media server. It does not imply LAN data movement nor does it preclude Fibre Channel as the transport for data movement.
Whether the disk is formatted and how it is attached are mutually exclusive and complementary. -media_server hostname -setattribute attribute Use the same name as the storage server name.
An attribute to apply to the storage server for the read side of restore or duplication operations. The following are the attributes:
PrefRestore. The storage server is preferred for the read side of restore operations. More than one storage server can have the PrefRestore attribute.
ReqRestore. The storage server is required for the read side of restore operations. More than one storage server can have the ReqRestore attribute. ReqDuplicate. The storage server is required for the read side of duplication operations. More than one storage server can have the ReqDuplicate attribute.
29
The NetBackup media servers that share the storage. The media servers must be configured as storage servers. They also function as data movers. When you specify the storage servers, you associate them with the disk pool. Only those storage servers can access the disk pool. See About AdvancedDisk storage servers on page 23. The disk volumes to include in the pool. The disk pool properties. See AdvancedDisk disk pool properties on page 30.
Symantec recommends that disk volume and disk pool names be unique across your enterprise. You must first configure storage servers. See Configuring an AdvancedDisk storage server on page 26. Once you've configured storage servers, proceed to creating a disk pool.
30
1 2
In the NetBackup Administration Console, in the left pane, select Media and Device Management. From the list of wizards in the right pane, click Configure Disk Pool and follow the wizard instructions. NetBackup does not filter out common file system mount points, such as / and /usr. Therefore, carefully choose the volumes to include in a disk pool. For help, see the wizard help.
31
The default is 98%. Low water mark The Low water mark is a threshold at which NetBackup stops image cleanup. TheLow water mark setting cannot be greater than or equal to the High water mark setting. The default is 80%.
32
per volume
Select or enter the number of read and write streams to allow per volume. Many factors affect the optimal number of streams. Factors include but are not limited to disk speed, CPU speed, and the amount of memory.
33
1 2
In the NetBackup Administration Console, in the left pane, select NetBackup Management > Storage > Storage Units. Click Actions > New > Storage Unit.
Complete the fields and set the options in the New Storage Unit dialog box. See AdvancedDisk storage unit properties on page 33.
Click OK.
34
Storage unit name Enter a unique name for the new storage unit. The name can describe the type of storage. The storage unit name is the name used to specify a storage unit for policies and schedules. The storage unit name cannot be changed after creation. Storage unit type Select Disk as the storage unit type. Disk type Disk pool Select AdvancedDisk for the disk type. Select the disk pool that contains the storage for this storage unit. All disk pools of the specified Disk type appear in the Disk pool list. If no disk pools are configured, no disk pools appear in the list. Media server Specify the NetBackup media servers that can move data to and from the disk pool for this storage unit. Only the media servers that are configured as storage servers appear in the media servers list. Specify the media server or servers as follows: To allow any server in the media server list to access the disk storage (default), select Use any available media server. To restrict the media servers that can access the disk storage, select Only use the following media servers. Then, select the media servers to allow. The selection list includes only the media servers that are configured as storage servers for the disk pool.
NetBackup selects the media server to use when the policy runs. Maximum fragment size Specify the largest fragment size that NetBackup can create to store backups. The default maximum fragment size for a disk storage unit is 524,288 megabytes. To specify a maximum fragment size other than the default, enter a value from 20 megabytes to 524,288 megabytes. Backups to disk are usually fragmented to ensure that the backup does not exceed the maximum size that the file system allows. If an error occurs in a backup, the entire backup is discarded. The backup restarts from the beginning, not from the fragment where the error occurred. (An exception is for backups for which checkpoint and restart are enabled. In that case, fragments before and including the last checkpoint are retained; the fragments after the last checkpoint are discarded.)
35
36
For example, assume that you have 100 important clients, 500 regular clients, and four media servers. You can use two media servers to back up your most important clients and two media servers to back up your regular clients. The following example describes how to configure a favorable client-to-server ratio:
Configure the media servers for AdvancedDisk and configure the storage. Configure a disk pool. Configure a storage unit for your most important clients (such as STU-GOLD). Select the disk pool. Select Only use the following media servers. Select two media servers to use for your important backups. Create a backup policy for the 100 important clients and select the STU-GOLD storage unit. The media servers that are specified in the storage unit move the client data to the storage server. Configure another storage unit (such as STU-SILVER). Select the same disk pool. Select Only use the following media servers. Select the other two media servers. Configure a backup policy for the 500 regular clients and select the STU-SILVER storage unit. The media servers that are specified in the storage unit move the client data to the storage server.
Backup traffic is routed to the wanted data movers by the storage unit settings. Note: NetBackup uses storage units for media server selection for write activity (backups and duplications) only. For restores, NetBackup chooses among all media servers that can access the disk pool.
Chapter
Managing AdvancedDisk
This chapter includes the following topics:
Managing AdvancedDisk storage servers Managing AdvancedDisk disk pools Monitoring AdvancedDisk storage capacity and usage Monitoring NetBackup disk activity Viewing disk reports
38
If a disk pool is configured from the disk volumes that the storage server manages, you cannot delete the storage server. Warning: Do not delete a storage server if its storage contains unexpired NetBackup images. If you do, data loss may occur. To delete an AdvancedDisk storage server
1 2 3
In the NetBackup Administration Console, expand Media and Device Management > Credentials > Storage Server. On the Edit menu, select Delete. Click Yes in the confirmation dialog box.
Preferred restore server (PrefRestore) Required restore server (ReqRestore) Required duplication server (ReqDuplicate)
See About AdvancedDisk preferred or required read servers on page 24. Attributes are added when you use the nbdevconfig command to configure a storage server. See Configuring an AdvancedDisk storage server on page 26.
39
Run the following command on the NetBackup master server or on a storage server:
nbdevconfig -changests -storage_server storage_server -stype AdvancedDisk -clearattribute attribute
For every storage unit that specifies the storage server (media server) in Use one of the following media servers, clear the check box that specifies the media server. This step is not required if the storage unit is configured to use any available media server.
If only one storage server exists, change the state of all disk pools on the array to DOWN. To do so, use the following command:
nbdevconfig -changestate -stype AdvancedDisk -dp disk_pool_name -state DOWN
40
In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Credentials > Storage Server. The right pane, labeled All Storage Servers , shows all configured storage servers. AdvancedDisk storage servers show AdvancedDisk in the Disk Type column.
Run the following command on the NetBackup master server or a storage server:
nbdevquery -liststs -storage_server storage_server -stype AdvancedDisk U
This example output is shortened; more flags may appear in actual output.
41
See Changing AdvancedDisk disk pool state on page 42. See Changing AdvancedDisk disk volume state on page 43. See Deleting an AdvancedDisk disk pool on page 43. See Determining AdvancedDisk disk pool state on page 44. See Determining AdvancedDisk disk volume state on page 44. See Merging AdvancedDisk disk pools on page 45. See Removing a volume from an AdvancedDisk disk pool on page 45. See Viewing AdvancedDisk disk pools on page 46.
When you merge the disk pools, specify the original disk pool as the primary one. NetBackup deletes the secondary disk pool after the merge. See Merging AdvancedDisk disk pools on page 45.
42
1 2 3
In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Devices > Disk Pools. In the right pane, select the disk pool you want to change. Click Edit > Change.
In the Change Disk Pool dialog box, change properties. See AdvancedDisk disk pool properties on page 30.
Click OK.
43
1 2 3 4
In the NetBackup Administration Console, in the left pane, select Media and Device Management > Device Monitor. Select the Disk Pools tab. Select the disk pool. Select either Actions > Up or Actions > Down.
Determine the name of the disk volume. The following command lists all volumes in the specified disk pool:
nbdevquery -listdv -stype AdvancedDisk -dp disk_pool_name
To display the disk volumes in all disk pools, omit the -dp option.
Change the disk volume state. The following is the command syntax:
nbdevconfig -changestate -stype AdvancedDisk -dp disk_pool_name dv vol_name -state state
44
If a disk pool is the storage destination of a storage unit, you must first delete the storage unit. Warning: Do not delete a disk pool that contains unexpired NetBackup images; if you do, data loss may occur. To delete an AdvancedDisk disk pool
1 2 3 4
In the NetBackup Administration Console, in the left pane, select Media and Device Management > Devices > Disk Pools. Select a disk pool Click Edit > Delete. In the Delete Disk Pool dialog box, verify that the disk pool is the one you want to delete and then click OK.
1 2 3
In the NetBackup Administration Console, in the left pane, select Media and Device Management > Device Monitor. Select the Disk Pools tab. The state is displayed in the Status column.
Determine the name of the disk volume. The following command lists the volumes in the specified disk pool:
nbdevquery -listdv -stype AdvancedDisk -dp disk_pool_name
45
To display the disk volumes in all AdvancedDisk disk pools, omit the -dp option.
Change the state of each disk pool to DOWN. See Changing AdvancedDisk disk pool state on page 42. If backup jobs are assigned to a disk pool, the state change fails. Cancel the backup jobs or wait until the jobs complete.
Merge the disk pools. The following is the command syntax. The primary disk pool is the one you want to retain; nbdevconfig deletes the secondary disk pool after the merge.
nbdevconfig mergedps stype AdvancedDisk -primarydp disk_pool_name -secondarydp disk_pool_name
Change the state of the primary disk pool to UP. See Changing AdvancedDisk disk pool state on page 42.
NetBackup image fragments cannot exist on the disk volume. NetBackup jobs cannot be active on the disk volume.
46
By default, NetBackup automatically decreases disk pool capacity if you remove a disk volume. The following is the path to the nbdevconfig command:
Change the disk volume state to DOWN. See Changing AdvancedDisk disk volume state on page 43.
Change the disk pool state to DOWN. See Changing AdvancedDisk disk pool state on page 42.
Remove the volume by using the nbdevconfig command. The following is the command syntax:
nbdevconfig -deletedv -stype AdvancedDisk -dp disk_pool_name dv vol_name
Change the disk pool state to UP. See Changing AdvancedDisk disk pool state on page 42.
In the NetBackup Administration Console tree, in the left pane, select Media and Device Management > Devices > Disk Pools. The list appears in the right pane.
47
The NetBackup Disk Pool status report. NetBackup Administration Console Storage Server window
The storage server view displays real-time values. To display the window, select Media and Device Management > Credentials > Storage Servers.
The NetBackupLicenseKeys The summary of active capacity-based license features in dialog box. the NetBackup License Keys dialog box. The summary displays the storage capacity for which you are licensed and the capacity used. It does not display the amount of physical storage space. To open the dialog box, select Help > License Keys in the NetBackup Administration Console.
The NetBackup OpsCenter also provides information about storage capacity and usage. See the NetBackup OpsCenter Administrator's Guide.
48
The bpbrm backup and restore manager The bpdbm database manager The bpdm disk manager The bptm tape manager for I/O operations
117
111
178
The Disk Service Manager process that runs in the Enterprise Media Manager (EMM) process. The Storage Server Interface process that runs in the Remote Manager and Monitor Service. RMMS runs on media servers. The Remote Disk Service Manager interface (RDSM) that runs in the Remote Manager and Monitor Service. RMMS runs on media servers.
202
Device configuration
230
To view and manage VxUL log files, you must use NetBackup log commands. Information about how to use and manage logs on NetBackup servers is available. See the NetBackup Troubleshooting Guide.
49
Disk Logs
The Disk Logs report displays the media errors or the informational messages that are recorded in the NetBackup error catalog. The report is a subset of the Media Logs report; it shows only disk-specific columns. The Disk Storage Unit Status report displays the state of disk storage units in the current NetBackup configuration. For disk pool capacity, see the disk pools window in Media and Device Management > Devices > Disk Pools. Multiple storage units can point to the same disk pool. When the report query is by storage unit, the report counts the capacity of disk pool storage multiple times.
The Disk Pool Status report displays the state of disk pool storage units. This report displays only when an Enterprise Disk Option license is installed.
1 2 3 4
In the NetBackup Administration Console, in the left pane, expand NetBackup Management > Reports > Disk Reports. Select the name of a disk report. In the right pane, select the report settings. Click Run Report.
50
Chapter
Toubleshooting AdvancedDisk
This chapter includes the following topics:
AdvancedDisk troubleshooting
The following may help you troubleshoot AdvancedDisk: Table 6-1 Problem
Unable to access storage
AdvancedDisk does not support Common Internet File System (CIFS). If you try to configure multiple storage servers, NetBackup returns the following message:
DSM does not support to use multiple Windows Storage server type: AdvancedDisk.
52
Disk failure - AdvancedDisk If recovery mechanisms do not protect a disk that fails, the backup images on that disk are lost. Operating system read and write errors may occur for the volume that represents the disk. NetBackup cannot use that volume because of the errors, and NetBackup jobs may fail. To prevent NetBackup from trying to read from or write to the disk, you must change the volume state to DOWN in NetBackup. If the volume represents other disks that still function, those disks are not available because the volume state is DOWN. You may be able to read from the volume by mounting it manually. If so, you may be able to recover image fragments from any disks that did not fail. If you replace a failed disk, you can use the same mount point for the replacement disk. Change the volume state to UP, and NetBackup uses that volume again. Any valid backup images on that volume are available for restores.
Invoke the following command on the master server or a media server that functions as a storage server: The following output shows an incorrect value for AdvancedDisk:
Storage Server : halo Storage Server Type : AdvancedDisk Storage Type : Formatted Disk, Network Attached
53
1 2 3 4 5
Delete all disk pools that use the storage server. Delete the storage server. Reconfigure the storage server. Recreate the disk pools. If necessary, specify the new disk pools in the storage units. If you recreated the disk pools with the same names as the ones you deleted, this step is not necessary.
54
Section
OpenStorage option
Chapter 7. Introducing OpenStorage Chapter 8. Planning your deployment Chapter 9. Provisioning the storage Chapter 10. Licensing OpenStorage Chapter 11. Configuring OpenStorage Chapter 12. Managing OpenStorage Chapter 13. Troubleshooting OpenStorage
56
Chapter
Introducing OpenStorage
This chapter includes the following topics:
Disk appliances that include a host computer and the storage. Nirvanix cloud-based storage.
Storage vendors participate in the Symantec OpenStorage Partner Program. Symantec qualifies their storage solutions for the OpenStorage API. Depending on the storage implementation, OpenStorage may provide the following capabilities:
Share disks. Multiple heterogeneous media servers can access the same disk volume concurrently. Balance load and performance. NetBackup balances backup jobs and storage usage among the media servers and disk pools. For each backup job, NetBackup chooses the least full disk volume and least busy media server. Use of disk appliance capabilities, which may include optimized off-host duplication and deduplicated storage capabilities. Fast storage provisioning. Almost unlimited storage. Alternative to off-site vaulting.
58
Simplified disaster recovery. Access your data from anywhere over the Internet.
Figure 7-1 shows an OpenStorage configuration that uses a disk appliance. Figure 7-1 OpenStorage appliance configuration
Load-balanced NetBackup media servers are data movers. They have the vendor plug-in installed.
Network
Chapter
Planning your OpenStorage deployment About OpenStorage requirements and limitations About OpenStorage storage servers About OpenStorage server credentials About OpenStorage data movers About the OpenStorage plug-in About OpenStorage disk pools About OpenStorage optimized duplication methods About OpenStorage optimized synthetic backups About OpenStorage direct to tape About Nirvanix cloud storage
Task
Read about requirements and See About OpenStorage requirements and limitations on page 60. limitations
60
Task
Learn about storage servers, See About OpenStorage storage servers on page 61. data movers, and credentials See About OpenStorage data movers on page 62. See About OpenStorage server credentials on page 61.
Step 3
See About OpenStorage disk pools on page 63. See About spanning volumes on OpenStorage disk pools on page 63.
Step 4
Learn about optimized duplication Learn about optimized synthetic backups Learn about copy to tape Learn about Nirvanix cloud storage
Step 5
Step 6 Step 7
See About OpenStorage direct to tape on page 67. See About Nirvanix cloud storage on page 72.
Step 8
Learn about provisioning the See About provisioning the disk storage appliance on page 77. storage See About installing the disk appliance plug-in on page 78. See the configuration overview topics See Configuring OpenStorage disk appliance storage on page 81. See Configuring OpenStorage Nirvanix cloud storage on page 83.
Step 9
A NetBackup OpenStorage Option license key. Storage that is exposed to NetBackup through a software plug-in that conforms to the Symantec OpenStorage API.
Information about supported systems is available. See the NetBackup Release Notes.
61
For OpenStorage solutions that use a disk appliance, the disk appliance host is the storage server. For Nirvanix Storage Delivery Network cloud-based storage, nirvanix.com is the storage server.
For each OpenStorage environment, only one storage server exists. When you configure the storage server, you enter the storage server host name. You also must enter the storage server type, as follows:
For disk appliance storage, your storage vendor provides the name of the storage type. For Nirvanix cloud storage, enter one of the following:
nirvanix for data that is not encrypted. nirvanix_e to use encryption for the data you send to the cloud.
Saves the credentials so the media servers can log into the storage server. If the storage server is also an NDMP FSE host for direct to tape operations, they both must have the same logon credentials. See About OpenStorage direct to tape on page 67. Configures each media server you select as a data mover. NetBackup does not monitor connectivity between data movers and the storage server. However, when you configure the credentials, NetBackup configures and maintains an access path between the media server and the storage server. See About OpenStorage data movers on page 62.
62
If the storage server does not require logon credentials, you must enter dummy credentials so that NetBackup configures the media servers as data movers.
For appliance storage, the appliance vendor provides the plug-in. The vendor should provide information about how to install the plug-in. To determine a disk appliances capabilities, NetBackup uses the plug-in to query the storage appliance. Capabilities can include deduplicated storage, optimized off-host duplication, and so on. See About installing the disk appliance plug-in on page 78. For Nirvanix cloud storage, the plug-in is installed with NetBackup; no separate installation is required.
63
For disk appliance storage, the vendor may expose the storage as one or more units of storage (that is, disk volumes). For Nirvanix cloud storage, a child account is exposed as a single volume. If the Nirvanix application (that is, storage pool) has more than one child account, each is exposed as a volume. See About Nirvanix child accounts on page 73.
A disk pool can represent one or more volumes. If a disk pool represents more than one volume, NetBackup selects a volume for a backup based on: available capacity and predicted size of the backup. NetBackup tries to write backup data to a single volume. If necessary, backup images span volumes in a disk pool unless the storage implementation does not support volume spanning. Backup images do not span across multiple disk pools. A disk pool is the storage destination of a NetBackup storage unit. Figure 8-1 shows a disk pool configuration in a disk appliance. Figure 8-1 OpenStorage disk appliance disk pools
Disk appliance
DP_Gold_OpenStorage
DP_Silver_OpenStorage
64
In NetBackup, the SpanImages attribute specifies that backup images can span across volumes in a disk pool. The SpanImages attribute applies to both storage servers and disk pools. Two reasons exist that may require you to update NetBackup to use the volume spanning functionality, as follows:
Your OpenStorage vendor plug-in supports volume spanning functionality. Volume spanning is not a trait that the vendor plug-in advertises. Therefore, you must configure the storage server to use it explicitly. You upgrade to a NetBackup release that supports OpenStorage volume spanning from a release that does not support it. NetBackup 6.5.4 and later support OpenStorage volume spanning. If your vendor plug-in supports spanning and you upgrade to 7.0 from a 6.5 to 6.5.3 release, you can configure NetBackup to use volume spanning.
In both cases, set the SpanImages attribute on both the storage server and the disk pool. See Setting OpenStorage storage server attributes on page 107. See Updating an OpenStorage disk pool on page 119.
65
Reduced workload on the NetBackup media servers. More backups can be performed. Faster duplication. Duplication can occur in the background, simultaneously with ongoing backup jobs. Reduced bandwidth. If the appliance supports deduplication, the copy process may send only changed blocks.
The requirements and limitations of optimized duplication with the same domain are as follows:
Optimized duplication requirements The vendor must expose the off-host data movement capability in their plug-in. Both the source and the destination disk pools must be the same OpenStorage vendor type. One or more NetBackup media servers must connect to the source appliance and the destination appliance.
If the optimized duplication fails, the job is not retried. To configure NetBackup to do normal duplication if the optimized job fails, add the following entry to the bp.conf file on the NetBackup master server: RESUME_ORIG_DUP_ON_OPT_DUP_FAIL = TRUE
The copy operation uses the maximum fragment size of the source storage unit, not the setting for the destination storage unit. The optimized duplication copies the image fragments as is. For greater efficiency, the duplication does not resize and reshuffle the images into a different set of fragments on the destination storage unit. To confirm the image copy, a media server must have connectivity to the destination appliance. A storage unit group cannot be a destination for optimized duplication. The destination must be a storage unit that represents an OpenStorage appliance of the same type as the source appliance.
See Configuring OpenStorage optimized duplication within the same domain on page 98.
66
The ability to duplicate backups to storage in other NetBackup domains, often across various geographical sites, helps facilitate disaster recovery. Both domains must have OpenStorage configured and working in their domains. The OpenStorage devices must support replication. You must use a storage lifecycle policy to copy the backup images to another NetBackup domain. For information about how to configure duplication to a remote master server, see NetBackup Administrator's Guide, Volume I. For OpenStorage duplication to a remote master server, the source NetBackup domain has no knowledge of the remote domain or its storage server. The relationship between the source and the target domains is configured using the disk appliance vendor's tools. When the appliances are configured properly, NetBackup images on the source disk appliance are replicated automatically to the target disk appliance. That disk appliance uses the OpenStorage API to notify NetBackup that a replication event occurred. NetBackup then imports those images. Caution: If you also use optimized duplication within the same domain, correct configuration is critical. For duplication to a remote master server, a target storage server must not also be a storage server for the source domain. Therefore, choose the target storage server or servers carefully. The following are the requirements for optimized duplication to a remote NetBackup domain:
The vendor must expose the off-host data movement capability in their plug-in. Both the source and the destination disk pools must be the same OpenStorage vendor type.
67
Faster than a synthetic backup. Regular synthetic backups are constructed on the media server. They are moved across the network from the storage server to the media server and synthesized into one image. The synthetic image is then moved back to the storage server. Requires no data movement across the network. Regular synthetic backups use network traffic. Uses fewer disk resources, depending on the vendor implementation. The storage vendor determines the storage implementation. If the disk appliance uses data deduplication, duplicate data is not created and stored.
In NetBackup, the Optimizedlmage attribute enables optimized synthetic backup. It applies to both storage servers and disk pools. If the original vendor plug-in exposed optimized synthetic backup functionality, the storage server and disk pools inherited that functionality. However, if your OpenStorage vendor updates their plug-in to add optimized synthetic backup functionality, you have to update NetBackup. See Adding OpenStorage functionality to an existing environment on page 102. The following are the requirements for optimized synthetic backups:
The master and the media servers are at NetBackup version 6.5.4 or later. The Enterprise Disk license key is installed on the NetBackup master server. The plug-in from the disk appliance vendor supports the OpenStorage OptimizedImage attribute. The vendor plug-in is installed on each media server that connects to the storage appliance. The target storage unit's disk pool is the same disk pool on which the source images reside.
68
NetBackup media servers manage the operations. The media servers require the NetBackup for NDMP software and specific NetBackup release levels. See About media server requirements for OpenStorage direct to tape on page 70. How to configure OpenStorage direct to tape is described elsewhere. See Configuring OpenStorage direct to tape on page 100.
A separate host that interacts with the disk appliance. The host must be directly connected to the disk appliance.
Direct to tape requires an NDMP tape server for the destination tape library. The NDMP tape server must support NDMP v4 or later. The host that provides the NDMP tape server functionality can be one of the following entities: The same host that provides the NDMP FSE functionality. If one host provides the NDMP FSE and NDMP tape server functionality, the tape library must be attached directly to that host. Data does not travel over the network. See Figure 8-2 on page 69. A host that is embedded in the tape library. Data travels over the network. See Figure 8-3 on page 69. A separate host to which the tape server is directly attached. Data travels over the network. See Figure 8-4 on page 70.
69
The NDMP FSE server must use the same credentials as the OpenStorage storage server. If you use the NDMP FSE server for other purposes, do not configure the credentials differently for that purpose. For example, if you also use the NDMP FSE server as a VTL with NetBackup, use the same credentials when you configure it with NetBackup.
Figure 8-2
Network
The disk appliance provides both the NDMP FSE and NDMP tape server functionality
Figure 8-3
Network
70
Figure 8-4
NDMP tape server host Tape library directly attached to the NDMP host
Description
In this context, the read side media server does not read or move the backup images. It manages the read side of the NDMP copy operation. The read side media server requires the following:
NetBackup 6.5.4 or later. The NetBackup for NDMP software. Logon credentials for the disk appliance storage server and the NDMP FSE host. If the NDMP FSE host and the storage server host have the same name, NetBackup uses the storage server credentials to logon to the NDMP host. Therefore, you do not have to configure NDMP credentials in NetBackup. This NetBackup behavior means that the credentials you create for the disk appliance storage server and the NDMP FSE host must be the same. If the NDMP FSE hostname is different than the storage server hostname, you must configure logon credentials in NetBackup for that NDMP host.
In this context, the write side media server does not move or write the backup images. It manages the write side of the NDMP copy operation. The write side media server requires the following:
NetBackup 6.5 or later. The NetBackup for NDMP software. Logon credentials for the NDMP tape server host.
71
If one host provides both NDMP FSE and NDMP tape server functionality, one media server functions as both the read and write server.
Configure logon credentials to the OpenStorage storage server. Install the NetBackup for NDMP software. Configure logon credentials for the NDMP FSE host (if required). Configure logon credentials for the NDMP tape server host.
The destination storage unit must be NDMP. You cannot use a storage unit group. You cannot make multiple copies with one copy operation. Backup images are not multiplexed when written to tape.
NetBackup verifies that the image to be duplicated resides on an OpenStorage device. NetBackup verifies that the disk appliance NDMP host supports the OpenStorage direct to tape specification. NetBackup selects the write side media server, a destination tape drive, and a tape volume. NetBackup selects a media server that has credentials to the NDMP tape server host. The media servers NetBackup considers are listed in the destination storage unit. The write side media server does the following:
72
Establishes an NDMP session with the NDMP tape server and confirms that it supports the NDMP v4 protocol. Mounts, opens, and positions the tape and then uses NDMP to write a header to the tape. Sets up the NDMP mover interface on the NDMP tape server. It also monitors the progress of the write operation by waiting for any NDMP notifications.
NetBackup selects the read side media server. If the write side media server has credentials for the NDMP FSE host, NetBackup selects it as the read side server. If it does not have credentials, NetBackup selects a media server with credentials to the NDMP FSE host. The read side media server does the following:
Establishes an NDMP session with the NDMP FSE host. Opens the files to be copied. Sets up the NDMP mover interface on the NDMP FSE host. It also monitors the progress of the read operation by waiting for any NDMP notifications.
By means of the NDMP protocol, the backup images on the disk appliance are copied to the tape storage. After the images are copied, the read and write media servers close their connections to their respective NDMP hosts. NetBackup validates the image copies; if valid, NetBackup ends the duplication job with status 0 (success).
73
Note: Nirvanix uses the terms application and storage pool interchangeably in their documentation.
74
Backup images appear as folders under the Storage Pool/Child Account view. Every write operation for a new image creates a folder under the backup image folder. The folder names use a block image sequence number; for example, 0, 1, 2, and so on. Each backup image folder contains a block_map file. The file maps the block images to individual files. Backup image properties are added as metadata to the folders.
75
See the NetBackup Release Notes. Information about how to configure KMS is available. See the NetBackup Security and Encryption Guide. Follow the procedures in that guide to install KMS. Note the following:
KMS requires a Host Master Key passphrase and ID when you create the key management database. The Key Management Service can create a random passphrase for you. KMS requires a Key Protection Key passphrase and ID when you create the key management database. The Key Management Service can create a random passphrase for you. Each Nirvanix child account you use for NetBackup storage requires a key group. KMS requires a name for each key group. Use the following format for the key group name:
nirvanix.com:child_account_name
The first child account name is the same as the name you used for the child account when you set the storage server properties. See Nirvanix storage server properties on page 86. Unlike other storage types, the key group name does not require the ENCR_ prefix.
Each key group you create requires a key record. KMS requires a passphrase when you create the key record. A key record name is optional. If you use a key record name, you can use any name for the key record name. Symantec recommends that you use a descriptive name.
A NetBackup OpenStorage Option license key. A Nirvanix Storage Delivery Network master account user name and password. Default node-replication policy settings for your Nirvanix account. New storage pools inherit the default policies, but you can adjust them for each storage pool to fit your business needs. For more information or to verify that your account has the proper settings, contact Nirvanix customer support using the Nirvanix Management Portal. Use NetBackup to create the Nirvanix storage pool that is used for your NetBackup backups. The storage pools that NetBackup creates contain a required Symantec Partner Key. If you use the Nirvanix Management Portal
76
to create the storage pool, it does not contain the partner key. Consequently, that storage pool cannot accept data from NetBackup.
Unique storage pool names. Storage pool names must be unique among all users of the Nirvanix Storage Delivery Network.
The following OpenStorage capabilities are not supported for Nirvanix storage:
Optimized duplication Optimized synthetics Direct to tape (by NDMP) Disk volume spanning of backup images
Information about supported systems is available. See the NetBackup Release Notes.
Chapter
About provisioning the disk storage appliance About installing the disk appliance plug-in About provisioning the Nirvanix storage space
Add the appliance to your environment. Install the vendor software packages on all NetBackup media servers that connect to the appliance. See About installing the disk appliance plug-in on page 78. Perform vendor-specific steps to configure the appliance. Use the vendors processes and procedures to configure the appliance so that it works with your environment. To configure the storage, you may be required to do the following:
Assign the appliance a name. NetBackup uses the name to identify the appliance. Divide the appliance into one or more logical units of space. NetBackup refers to these logical units as disk volumes. NetBackup aggregates the disk volumes into disk pools.
78
Instructions for how to install and configure the appliance are beyond the scope of the NetBackup documentation. For instructions, refer to the vendor documentation.
Chapter
10
Licensing OpenStorage
This chapter includes the following topics:
You cannot create the disk pools or the storage units that use the disk pools.
80
NetBackup jobs fail that attempt to use the disk pools or the storage units that are based on the disk pools. The error message indicates that the feature is not licensed.
NetBackup does not delete the disk pools or the storage units that are based on the disk pools. You can use them again if you enter a valid license key.
Licensing OpenStorage
No special installation is required for the NetBackup components of OpenStorage. However, you must enter a license key. The following procedure describes how to use the NetBackup Administration Console to enter the license key. Note: Enter the license key on the NetBackup master server and on each media server that connects to the disk appliance. If you use the direct to tape feature, also enter the license key on each NetBackup media server that you use for direct to tape. Those media servers also must have the NetBackup for NDMP software installed. The license key that activates OpenStorage also activates the NDMP software on the media servers. See About OpenStorage direct to tape on page 67. To license OpenStorage
1 2 3 4 5
To add a license to a specific server, select File > Change Server and then select the server. In the NetBackup License Keys dialog box, click New. In the Add a New License Key dialog box, enter the license key and click Add or OK. Click Close. Restart all the NetBackup services and daemons.
Chapter
11
Configuring OpenStorage
This chapter includes the following topics:
Configuring OpenStorage disk appliance storage Configuring OpenStorage Nirvanix cloud storage Creating NetBackup log file directories Configuring an OpenStorage storage server Setting the Nirvanix storage server properties Configuring Nirvanix data mover preferences Configuring an OpenStorage disk pool Configuring an OpenStorage storage unit Configuring OpenStorage optimized duplication behavior Configuring OpenStorage optimized duplication within the same domain Configuring OpenStorage direct to tape Configuring OpenStorage optimized synthetic backups Adding OpenStorage functionality to an existing environment Setting NetBackup configuration options by using bpsetconfig
82
The configuration tasks for Nirvanix cloud storage are described in a different topic. See Configuring OpenStorage Nirvanix cloud storage on page 83. The NetBackup administrator's guides describe how to configure a base NetBackup environment. See the NetBackup Administrator's Guide for Windows, Volume I. See the NetBackup Administrator's Guide for UNIX and Linux, Volume I. Table 11-1 Step
Step 1
Task
Learn about planning your deployment Enable legacy logging Provision the storage and install the plug-in Configure a storage server Configure a disk pool Configure a storage unit Configure optimized duplication
Step 2 Step 3
See Creating NetBackup log file directories on page 84. See About provisioning the disk storage appliance on page 77. See About installing the disk appliance plug-in on page 78. See Configuring an OpenStorage storage server on page 85. See Configuring an OpenStorage disk pool on page 89. See Configuring an OpenStorage storage unit on page 91. Optimized duplication is optional. See Configuring OpenStorage optimized duplication within the same domain on page 98. See Configuring OpenStorage optimized duplication behavior on page 96.
Step 8
Copy to tape is optional. See About OpenStorage direct to tape on page 67. See Configuring OpenStorage direct to tape on page 100.
Step 9
Optimized synthetic backups are optional. See Configuring OpenStorage optimized synthetic backups on page 102.
Step 10
Configure a policy that uses See the NetBackup Administrator's Guide for Windows, Volume I. an OpenStorage storage unit See the NetBackup Administrator's Guide for UNIX and Linux, Volume I.
83
Task
Learn about planning your deployment Enable legacy logging Provision the storage Optionally, configure encryption
See Creating NetBackup log file directories on page 84. See About provisioning the Nirvanix storage space on page 78. The NetBackup Key Management Service provides data at rest encryption for your backups. See About data encryption for cloud storage on page 74.
Step 5
The Storage server type determines whether or not you use encryption for your data, as follows:
Use nirvanix for data that is not encrypted. Use nirvanix_e to use encryption for the data you send to the cloud. Encryption is optional. See About data encryption for cloud storage on page 74.
Use nirvanix.com for the Storage server name. If your Nirvanix account uses a name other than services.nirvanix.com, enter the fully qualified domain name Nirvanix provided. For example, the server name may be similar to services.storage.nirvanix.com.
Caution: After you configure the storage server, do not continue with the
Disk Pool Configuration Wizard. Before you configure the disk pool, you must set the storage server properties. See Configuring an OpenStorage storage server on page 85. Step 6 Set the storage server properties Configure data mover preferences See Setting the Nirvanix storage server properties on page 85. See Nirvanix storage server properties on page 86. See Configuring Nirvanix data mover preferences on page 89.
Step 7
84
Task
Optionally, configure additional child accounts
See Configuring an OpenStorage disk pool on page 89. See Configuring an OpenStorage storage unit on page 91.
Configure a policy that uses See the NetBackup Administrator's Guide for Windows, Volume I. the storage unit you See the NetBackup Administrator's Guide for UNIX and Linux, Volume I. configured
Depending on the operating system, run one of the following scripts: UNIX: /usr/openv/netbackup/logs/mklogdir Windows:install_path\NetBackup\logs\mklogdir.bat
85
Depending on the operating system, create the debug directory and the tpcommand directory (by default, the debug directory and the tpcommand directory do not exist). After you create the directories, the pathnames are as follows: UNIX: /usr/openv/volmgr/debug/tpcommand Windows: install_path\Volmgr\debug\tpcommand
1 2 3
In the NetBackup Administration Console, in the left pane, click Media and Device Management. In the right pane, select Configure Disk Storage Servers. Follow the wizard screens to configure a storage server.
1 2 3
In the NetBackup Administration Console, expand Media and Device Management > Credentials > Storage Server Select the storage server. On the Edit menu, select Change.
86
In the Change Storage Server dialog box, select the Properties tab.
5 6
To change a value, select it in the Value column and then change the value. When finished changing values, click OK. NetBackup creates the Nirvanix application (that is, storage pool). NetBackup creates the child account when you configure a disk pool.
87
STORAGE_POOL_NAME
The name of the Nirvanix storage pool. When you set the Nirvanix storage server properties, enter the name to use for the storage pool. NetBackup uses this name when it creates the storage pool in the Nirvanix cloud. You determine the name of the storage pool. Storage pool names must be unique among all users of Nirvanix Storage Directory Network not only unique within your organizations storage in the Nirvanix SDN. Symantec recommends that you use a naming convention that is recognizable. The storage pool name must be 50 or fewer characters. The following are invalid characters for the storage pool nbu_name: "\\/:?|*\"<>[] ";
Caution: Never change the name of your Nirvanix storage pool after you configure
Nirvanix storage in NetBackup. See About the Nirvanix storage pool on page 73. CHILD_ACCOUNT_NAME The name of Nirvanix of child account. When you set the Nirvanix storage server properties, enter the name to use for the child account of the storage pool. NetBackup uses this name when it creates the child account. You determine the name of the child account. Symantec recommends that you use a naming convention that is recognizable. NetBackup uses the child account name for the password for the account. The child account name must be 100 or fewer characters. The following are invalid characters for the child account name: "\\/:?|*\"<>[]~`'!@%^&()+={};' " See About Nirvanix child accounts on page 73. CHILD_ACCOUNT_SIZE The capacity of the storage of your child account. You can enter the size in MB, GB, or TB; for example, 50TB. 0 (zero) means the size is limited only by the amount of storage Nirvanix has available. USE_SSL Whether to use Secure Sockets Layer encryption for the control APIs. The default is YES, use SSL. Whether to use Secure Sockets Layer encryption for read and write operations to the Nirvanix storage. The default is YES, use SSL. The size of the buffer to use for write operations. The default is 10 MBs. To disable the use of the buffer, set this value to 0 (zero). BUFFER_NUM The number of buffers to use for write operations. The default is 1, fixed.
USE_SSL_RW
BUFFER_SIZE
88
LOG_CURL
Whether to log cURL activity. The default is 0, do not log activity. NetBackup uses the cURL library to manage data transfer to the Nirvanix cloud.
CURL_CONNECT_TIMEOUT The maximum time in seconds that the media server tries to connect to the Nirvanix storage server. This only limits the connection phase, not the session time. The default is 300 seconds (five minutes). The media server attempts to connect up to three times. To disable this timeout, set the value to 0 (zero). NetBackup uses the cURL library to manage data transfer to the Nirvanix cloud. CURL_TIMEOUT The maximum time in seconds to allow for the completion of a data operation. If the operation does not complete in the specified time, the operation fails. The default is 900 seconds (15 minutes). The media server attempts the operation up to three times. To disable this timeout, set the value to 0 (zero). NetBackup uses the cURL library to manage data transfer to the Nirvanix cloud. RESTRICT_IP Determines if multiple hosts can upload and download using the same upload-download token, as follows:
If RESTRICT_IP is set to YES, only one host can use an upload-download token.
By default, RESTRICT_IP is set to YES. This setting prevents any intrusions into the session by any other host. If RESTRICT_IP is set to NO, multiple host addresses can upload and download using the same token. If the host's IP address changes, this setting allows the host to continue with the session. A host IP address my change because of network address translation (NAT) or proxies. Therefore, set RESTRICT_IP to NO for such environments. PROXY_TYPE If firewalls prevent access to the nirvanix.comdomain on ports 80 (HTTP) or 443 (HTTPS), you can use a proxy server. Valid values are either HTTP or SOCKS. If you do not use a proxy server, leave this field blank. The IP address of the proxy server. If you do not use a proxy server, leave this field blank. If you use a proxy server, the port number to use to connect to the proxy server. If you do not use a proxy server, leave this field blank. The NetBackup server that hosts the KMS service. When you set the Nirvanix storage server properties, enter the name of the KMS server host. By default, this field contains the NetBackup master server name. KMS_VERSION The version of the NetBackup Key Management Service.
PROXY_IP
PROXY_PORT
KMS_SERVER
89
CRYPT_VERSION CRYPT_LOG_VERBOSE
The encryption version. A switch to set the logging level of the encryption activities. The value is either YES for logging or NO for no logging.
You must copy these files to any additional media servers that you configured as data movers. To configure Nirvanix data mover preferences
For each data mover media server, copy the aforementioned files to the following directory (depending on operating system): UNIX: /usr/openv/lib/ost-plugins Windows: install_path/NetBackup/bin/ost-plugins
The storage server. For OpenStorage, the disk appliance is the storage server. The disk volume or volumess to include in the pool. The disk pool properties. See OpenStorage disk pool properties on page 90.
Symantec recommends that disk volume and disk pool names be unique across your enterprise. See Configuring an OpenStorage storage server on page 85.
90
1 2
In the NetBackup Administration Console, in the left pane, select Media and Device Management. From the list of wizards in the right pane, click Configure Disk Pool and follow the wizard instructions.
Description
The disk pool name. The storage server name. For disk appliance storage, the storage server is the disk appliance host. For Nirvanix cloud storage, the storage server is nirvanix.com.
For disk appliance storage, the disk volumes that comprise the disk pool. The total amount of space available in the disk pool. The total raw, unformatted size of the storage in the disk pool. The storage host may or may not expose the raw size of the storage.
A comment that is associated with the disk pool. The High water mark setting is a threshold that triggers the following actions: When an individual volume in the disk pool reaches the High water mark, NetBackup considers the volume full. NetBackupchooses a different volume in the disk pool to write backup images to. When all volumes in the disk pool reach the High water mark, the disk pool is considered full. NetBackup fails any backup jobs that are assigned to a storage unit in which the disk pool is full. NetBackup also does not assign new jobs to a storage unit in which the disk pool is full. NetBackup begins image cleanup when a volume reaches the High water mark; image cleanup expires the images that are no longer valid. For a disk pool that is full, NetBackup again assigns jobs to the storage unit when image cleanup reduces any disk volume's capacity to less than the High water mark.
91
Description
The Low water mark is a threshold at which NetBackup stops image cleanup. TheLow water mark setting cannot be greater than or equal to the High water mark setting. The default is 80%.
Select to limit the number of read and write streams (that is, jobs) for each volume in the disk pool. A job may read backup images or write backup images. By default, there is no limit. When the limit is reached, NetBackup chooses another volume for write operations, if available. If not available, NetBackup queues jobs until a volume is available. Too many streams may degrade performance because of disk thrashing. Disk thrashing is excessive swapping of data between RAM and a hard disk drive. Fewer streams can improve throughput, which may increase the number of jobs that complete in a specific time period.
per volume
Select or enter the number of read and write streams to allow per volume. Many factors affect the optimal number of streams. Factors include but are not limited to disk speed, CPU speed, and the amount of memory.
92
1 2
In the NetBackup Administration Console, in the left pane, select NetBackup Management > Storage > Storage Units. Click Actions > New > Storage Unit.
3 4
Complete the fields in the New Storage Unit dialog box. Click OK.
93
Storage unit name Provide a unique name for the new storage unit. The name can describe the type of storage. The storage unit name is the name used to specify a storage unit for policies and schedules. The storage unit name cannot be changed after creation. Storage unit type Select Disk as the storage unit type. Disk type Select OpenStorage (VendorName) for the disk type. VendorName is a string provided by the storage vendor that identifies the vendor or storage. Select the disk pool that contains the storage for this storage unit. All disk pools of the specified Disk type appear in the Disk pool list. If no disk pools are configured, no disk pools appear in the list. Media server Specify the NetBackup media servers that can move data to the storage server for this storage unit. (For OpenStorage, NetBackup media servers function as data movers.) Only the media servers that are configured as data movers for the OpenStorage implementation appear in the media server list. If a media server does not appear in the list, verify that the software plug-in is installed and that logon credentials are created. Specify the media server or servers as follows: To allow any media server in the media server list to move data to the storage server, check Use Any Available Media Server. If you configure more media server data movers in the future, you do not have to update the storage unit. After you install the plug-in and configure the credentials, NetBackup automatically uses the media servers for the backups that are sent to the storage unit. To restrict the media servers that can move data to the storage server, check Only Use The Following Media Servers. Then select the media servers that are allowed to move the data.
Disk pool
Any media server in the list can receive data from the storage server; it does not have to be selected. A media server receives data for restore jobs and for storage monitoring purposes. NetBackup selects the media server to use when the policy runs. Maximum fragment size Specify the largest fragment size that NetBackup can create to store backups. The default maximum fragment size for a disk storage unit is 524,288 megabytes. To specify a maximum fragment size other than the default, enter a value from 20 megabytes to 524,288 megabytes. Backups to disk are usually fragmented to ensure that the backup does not exceed the maximum size that the file system allows. If an error occurs in a backup, the entire backup is discarded. The backup restarts from the beginning, not from the fragment where the error occurred. (An exception is for backups for which checkpoint and restart are enabled. In that case, fragments before and up to the last checkpoint are retained; the fragments after the last checkpoint are discarded.)
94
Description
Specify the maximum number of jobs that NetBackup can send to a disk storage unit at one time. (Default: one job. The job count can range from 0 to 256.) NetBackup queues jobs until the storage unit is available. If three backup jobs are ready to be sent to the storage unit and Maximum concurrent jobs is set to two, NetBackup starts the first two jobs. NetBackup queues the third job. If a job contains multiple copies, each copy applies toward the Maximum concurrent jobs count. Maximum concurrent jobs controls the traffic for backup and duplication jobs but not restore jobs. The count applies to all servers in the storage unit, not per server. If you select multiple media servers in the storage unit and 1 for Maximum concurrent jobs, only one job runs at a time. The number to enter depends on the available disk space and the server's ability to run multiple backup processes.
Configure a favorable client-to-server ratio for important clients. See About configuring a favorable client-to-server ratio with OpenStorage on page 94. Separate SAN client traffic from other traffic. See About separating OpenStorage SAN client traffic on page 95.
You also can use the storage unit Maximum concurrent jobs setting to control the backup or the duplication traffic that is sent to the media servers. See About throttling OpenStorage traffic to the media servers on page 96.
95
For example, assume that you have 100 important clients, 500 regular clients, and four media servers. You can use two media servers to back up your most important clients and two media servers to back up your regular clients. The following example describes how to configure a favorable client-to-server ratio:
Configure the media servers for OpenStorage and configure the storage. Configure a disk pool. Configure a storage unit for your most important clients (such as STU-GOLD). Select the disk pool. Select Only use the following media servers. Select two media servers to use for your important backups. Configure a backup policy for the 100 important clients and select the STU-GOLD storage unit. The media servers that are specified in the storage unit move the client data to the storage server. Configure another storage unit (such as STU-SILVER). Select the same disk pool. Select Only use the following media servers. Select the other two media servers. Configure a backup policy for the 500 regular clients and select the STU-SILVER storage unit. The media servers that are specified in the storage unit move the client data to the storage server.
Backup traffic is routed to the wanted data movers by the storage unit settings. Note: NetBackup uses storage units for media server selection for write activity (backups and duplications) only. For restores, NetBackup chooses among all media servers that have logon credentials to the storage server.
Configure the FT media servers and the regular media servers for OpenStorage and configure the storage. Configure a disk pool.
96
Define a storage unit (such as STU-FT). Select the disk pool. Select Only use the following media servers. Select the FT media servers that connect to the SAN clients. Create a backup policy for the SAN clients and select the STU-FT storage unit. Define another storage unit (such as STU-LAN). Select the same disk pool. Select Only use the following media servers. Select the media servers with LAN connectivity to the regular clients. Create a backup policy for the regular clients and select the STU-LAN storage unit.
Backup traffic is routed to the wanted data movers by the storage unit settings. This scenario assumes that the SAN clients are a subset of your client base. It also assumes that the media servers with LAN connectivity to the regular clients also have SAN connectivity to the storage. Note: NetBackup uses storage units for media server selection for write activity (backups and duplications) only. For restores, NetBackup chooses among all media servers that have logon credentials to the storage server.
97
The default NetBackup behavior is to use optimized duplication between the source and the target storage systems that support optimized duplication. If an optimized duplication job fails, NetBackup does not run the job again. You can configure NetBackup to use normal duplication if optimized duplication fails. The default is three attempts. You can specify the number of times NetBackup retries an optimized deduplication job before it fails the jobs. If the optimized deduplication job is configured in a storage lifecycle policy and the job fails, NetBackup retries the job three times. If the job is unsuccessful after three tries, NetBackup waits two hours and then retries the job. You can change the wait period.
Caution: These settings affect all optimized duplication jobs; they are not limited to optimized duplication to a Media Server Deduplication Pool or a PureDisk Deduplication Pool. You can configure several optimized duplication copy behaviors, as follows:
Optimized duplication failover. By default, if an optimized duplication job fails, NetBackup does not run the job again. Number of optimized duplication attempts. You can specify the number of times NetBackup retries an optimized duplication job before it fails the jobs. Storage lifecycle policy retries. If the optimized duplication job is configured in a storage lifecycle policy, NetBackup retries the job three times.
Caution: These settings affect all optimized duplication jobs, not only OpenStorage optimized duplication jobs.
98
Configuring OpenStorage Configuring OpenStorage optimized duplication within the same domain
See Setting NetBackup configuration options by using bpsetconfig on page 103. Alternatively on UNIX systems, add the entry to the bp.conf file on the NetBackup master server. To configure the number of duplication attempts
On the master server, create a file named OPT_DUP_BUSY_RETRY_LIMIT that contains an integer the specifies the number of times to retry the job before NetBackup fails the job. The file must reside in the following directory (depending on the operating system):
Change the wait period for retries by adding an IMAGE_EXTENDED_RETRY_PERIOD_IN_HOURS entry to the NetBackup LIFECYCLE_PARAMETERS file. The default for this value is two hours. For example, the following entry configures NetBackup to wait four hours before NetBackup tries the job again:
IMAGE_EXTENDED_RETRY_PERIOD_IN_HOURS 4
Configuring OpenStorage Configuring OpenStorage optimized duplication within the same domain
99
See About optimized duplication within the same domain on page 64. To configure optimized duplication
Ensure that all requirements are met. See About optimized duplication within the same domain on page 64.
Configure optimized duplication behaviors. See Configuring OpenStorage optimized duplication behavior on page 96. See About throttling OpenStorage traffic to the media servers on page 96.
Select the media server in common. In the storage unit for the destination disk pool, select Only use the following media servers. Then, select the media server or media servers that are common to both the source storage server and the destination storage server. If you select more than one, NetBackup balances the optimized copy job load among them.
A storage lifecycle policy. The storage lifecycle policy manages both the backup jobs and the duplication jobs. When you configure the storage lifecycle policy, do the following:
For the Backup destination, select the Storage unit that is the target of your backups. The disk appliance for the storage unit contains the primary backup copies; they are the source images for the duplication operation.
For the Duplication destination, select the Storage unit for the disk pool on another appliance. See the NetBackup Administrators Guide, Volume I.
A Vault policy. For Vault, you must configure a Vault profile and a Vault policy.
On the Vault Profile dialog box Choose Backups tab, choose the backup images in the source disk pool. On the Vault Profile dialog box Duplication tab, select the destination storage unit in the Destination Storage unit field. Configure a Vault policy to schedule the duplication jobs. A Vault policy is a NetBackup policy that is configured to run Vault jobs. Select the profile you created for the OpenStorage duplication job.
100
The bpduplicate command. Use the NetBackup bpduplicate command to copy images manually. Duplicate from the source storage to the destination storage. See NetBackup Commands Reference Guide.
You can apply separate retention periods to each copy. For example, you can retain the source image for three weeks and the destination copy for a longer period of time. If you delete the source image, the copy is not deleted.
Action
Install and configure the See the NetBackup for NDMP Administrators Guide. NDMP tape server hosts and storage devices Reconfigure the storage server If you upgraded a disk appliance so it supports the Symantec OpenStorage copy to tape specification, you must reconfigure the storage server in NetBackup. See Configuring an OpenStorage storage server on page 85.
Step 2
Step 3
Install the NetBackup for NDMP software on each media server you use for direct to tape. See About media server requirements for OpenStorage direct to tape on page 70. See About media server recommendations for OpenStorage direct to tape on page 71. See the NetBackup for NDMP Administrators Guide. You must enter a license key that activates NDMP on those media servers. The license key that activates OpenStorage also activates NetBackup for NDMP.
Step 4
Configure logon credentials in NetBackup for the NDMP hosts. See About NDMP requirements for OpenStorage direct to tape on page 68. See the NetBackup for NDMP Administrators Guide.
101
Action
Configure the NetBackup storage units
Step 6
First ensure that all requirements are met. See About NDMP requirements for OpenStorage direct to tape on page 68. Then, use one of the following methods for direct to tape: Create a storage lifecycle policy to create the backup and to duplicate the backup images automatically. For the Backup destination Storage unit, select the storage unit for the disk pool on one appliance. For the Duplication destination Storage unit, select the NDMP storage unit. See the NetBackup Administrators Guide for UNIX and Linux, Volume I or the NetBackup Administrator's Guide for Windows, Volume I. Create a Vault policy to copy images automatically. On the Profile dialog box Choose Backups tab, choose the backup images in the source disk pool on one appliance. For the Destination Storage unit on the Duplication tab, select the NDMP storage unit. See the NetBackup Vault Administrators Guide. Use the Duplicate option in the Catalog node of the NetBackup Administration Console. Select the NDMP storage unit as the destination for the duplication. Use the Storage unit field in the Setup Duplication Variables dialog box. See the NetBackup Administrators Guide for UNIX and Linux, Volume I or the NetBackup Administrator's Guide for Windows, Volume I. Use the NetBackup bpduplicate command to duplicate images on the disk appliance to an NDMP storage unit. See NetBackup Commands Reference Guide..
102
1 2
Configure a Standard or MS-Windows backup policy. Select the Synthetic backup attribute on the Schedule Attribute tab.
Install the updated plug-in See About installing the disk appliance plug-in on page 78. Update the storage server You must update the storage server so NetBackup can use the new functionality. See Updating an OpenStorage storage server on page 108. Update existing disk pools You also must update existing disk pools so they recognize the new functionality. See Updating an OpenStorage disk pool on page 119. Any disk pools that you create after you update the vendor plug-in and storage server inherit the new functionality.
103
On the host on which you want to set configuration options, write the current configuration to a file by running the following command: UNIX: /usr/openv/netbackup/bin/admincmd/bpgetconfig h hostname
> file.txt
Windows: install_path\NetBackup\bin\admincmd\bpgetconfig h
hostname > file.txt
Edit and save the file. You can change the values of the options that are in the file. You can add option and value pairs. Ensure that you understand the values that are allowed and the format of any new options that you add.
Upload the configuration by running the following command: UNIX: /usr/openv/netbackup/bin/admincmd/bpsetconfig h hostname
file.txt
Windows: install_path\NetBackup\bin\admincmd\bpsetconfig h
hostname file.txt
104
Chapter
12
Managing OpenStorage
This chapter includes the following topics:
Managing OpenStorage storage servers Managing OpenStorage server credentials Managing OpenStorage data movers Managing OpenStorage disk pools Monitoring OpenStorage storage capacity and usage Viewing OpenStorage disk reports About catalog backups to OpenStorage devices About restoring from backup copies
106
1 2 3 4 5 6 7
In the NetBackup Administration Console, expand Media and Device Management > Credentials > Storage Server Select the storage server. On the Edit menu, select Change. In the Change Storage Server dialog box, select the Properties tab. To change a value, select it in the Value column and then change the value. When finished changing values, click OK. Click OK.
1 2 3
In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Credentials > Storage On the Edit menu, select Delete. Click Yes in the confirmation dialog box.
107
For the server_type, the storage vendor provides the string that identifies the server type. The State field shows either UP or DOWN.
Run the following command on the NetBackup master server or on a storage server:
nbdevconfig -changests -storage_server hostname -stype server_type -setattribute attribute
For hostname, use the name of the disk appliance host. For server_type, the OpenStorage vendor provides the string that identifies their storage type. For attribute, use the name of the attribute you want to set. The following is the path to the nbdevconfig command:
108
Run the following command on the NetBackup master server or on a storage server:
nbdevconfig -changests -storage_server hostname -stype server_type -clearattribute attribute
For hostname, use the name of the disk appliance host. For server_type, the OpenStorage vendor provides the string that identifies their storage type. For attribute, use the name of the attribute you want to clear. The following is the path to the nbdevconfig command:
Run the following command on the master server or on one of the media servers:
nbdevconfig -updatests -storage_server storage_server -stypeserver_type -media_server media_server
109
-stype server_type The storage vendor provides the string that identifies the server type. -media_server media_server A NetBackup media server that connects to the storage server. The media server queries the storage server for its capabilities. The vendor plug-in must be installed on the media server. If the plug-in resides on more than one media server, you can specify any one of them.
In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Credentials > Storage Server. The right All Storage Servers pane shows all configured storage servers. OpenStorage storage servers show the vendor string that identifies the storage type in the Disk Type column.
110
1 2 3 4 5 6
In the NetBackup Administration Console, expand Media and Device Management > Credentials > Storage Server. Select the storage server, then select Edit > Change. Select the Media Servers tab. Select the media server you want to add. Also select the media servers that are configured as data movers already. Enter the credentials. Click Set and then click OK.
1 2 3 4 5 6
In the NetBackup Administration Console, expand Media and Device Management > Credentials > Storage Server. Select the storage server, then select Edit > Change. Select the Media Servers tab. Select the media servers that function as data movers. Change the credentials. Click Set and then click OK.
111
1 2 3 4 5
In the NetBackup Administration Console, expand Media and Device Management > Credentials > Storage Server. Select the storage server, then select Edit > Change. Select the Media Servers tab. Select the media server for which you want to delete the credentials. Click Remove and then click OK.
1 2 3
In the NetBackup Administration Console, expand Media and Device Management > Credentials > Storage Server. Select the storage server, then select Edit > Change. Select the Media Servers tab. The media servers for which credentials are configured are identified in the Media Servers Status column.
Add a media server as a data mover. See Adding an OpenStorage data mover on page 111. To add an OpenStorage data mover, see the procedure later in this section. Retire a media server as a data mover. See Retiring an OpenStorage data mover on page 112.
112
Task
Install and configure the NetBackup media server software.
Step 2
For disk appliance storage, install the OpenStorage See About installing the disk appliance plug-in vendor software plug-in on the media server on page 78. For disk appliance storage, connect the NetBackup Beyond the scope of the NetBackup documentation. media server to the OpenStorage appliance. Add the storage server logon credentials for the media server. See Adding OpenStorage server credentials on page 109.
Step 3
Step 4
Step 5
For every storage unit that points to a disk pool of In the NetBackup Administration Console, in the that storage server, verify that the new media server left pane, select NetBackup Management > Storage appears. The storage unit dialog box includes a > Storage Units. media servers list. For every storage unit that is configured to use any available media server, the new data mover is allowed access to the storage server automatically.
Step 6
For every storage unit that specifies Use one of the In the NetBackup Administration Console, in the following media servers, update the storage unit so left pane, select NetBackup Management > Storage it uses the correct data movers. > Storage Units. This step is not required if the storage unit is configured to use any available media server.
For every NetBackup storage unit that See the NetBackup Installation Guide for specifies that data mover (that is, media UNIX and Linux or the NetBackup server), clear the checkbox that specifies the Installation Guide for Windows. media server. This step is not required if the storage unit is configured to use any available media server.
113
On the media server to be retired, delete the See Deleting the OpenStorage server credentials for the storage server. credentials of a data mover on page 110.
114
Configure a disk pool from the new disk volumes on the storage server. Merge the disk pools. When you merge the disk pools, specify the original disk pool as the primary one. NetBackup deletes the secondary disk pool after the merge.
1 2
In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Devices > Disk Pools. In the right pane, select the disk pool you want to change.
115
In the Change Disk Pool dialog box, change properties. See OpenStorage disk pool properties on page 90.
Click OK.
1 2 3 4
In the NetBackup Administration Console, in the left pane, select Media and Device Management > Device Monitor. At the bottom of the right pane, select the Disk Pools tab. Select the disk pool. Select either Actions > Up or Actions > Down.
116
Determine the name of the disk volume. The following command lists all volumes in the specified disk pool:
nbdevquery -listdv -stype server_type -dp disk_pool_name
For the server_type, the storage vendor provides the string that identifies the server type.
Change the disk volume state using the following command syntax:
nbdevconfig -changestate -stype server_type -dp disk_pool_name dv vol_name -state state
For the server_type, the storage vendor provides the string that identifies the server type. The state is either UP or DOWN.
117
Warning: Do not delete a disk pool that contains unexpired NetBackup images; if you do, data loss may occur. To delete an OpenStorage disk pool
1 2 3 4
In the NetBackup Administration Console, in the left pane, select Media and Device Management > Devices > Disk Pools. Select a disk pool. Click Edit > Delete. In the Delete Disk Pool dialog box, verify that the disk pool is the one you want to delete and then click OK.
1 2 3 4
In the NetBackup Administration Console, in the left pane, select Media and Device Management > Device Monitor. At the bottom of the right pane, select the Disk Pools tab. Select the disk pool. The state is displayed in the Status column.
Determine the name of the disk volume. The following command lists the volumes in the specified disk pool:
nbdevquery -listdv -stype server_type -dp disk_pool_name
For the server_type, the storage vendor provides the string that identifies the server type.
118
To display the disk volumes in all OpenStorage disk pools on that vendor's storage, omit the -dp option.
The volumes in the two disk pools must have unique names. OpenStorage requires that vendors use unique names for disk volumes in a disk appliance. All volumes must be from the same storage server. If the secondary disk pool is referenced by storage units, you must delete those storage units.
Change the state of each disk pool to DOWN. See Changing OpenStorage disk pool state on page 115. If backup jobs are assigned to a disk pool, the state change fails. Cancel the backup jobs or wait until the jobs complete.
Merge the disk pools. The following is the command syntax. The primary disk pool is the one you want to retain; nbdevconfig deletes the secondary disk pool after the merge.
nbdevconfig mergedps stype server_type -primarydp disk_pool_name -secondarydp disk_pool_name
Change the state of the primary disk pool to UP. See Changing OpenStorage disk pool state on page 115.
119
NetBackup image fragments cannot exist on the disk volume. NetBackup jobs cannot be active on the disk volume.
By default, NetBackup automatically decreases disk pool capacity if you remove a disk volume. To remove a volume from an OpenStorage disk pool
Change the disk volume state to DOWN. See Changing OpenStorage disk volume state on page 116.
Change the disk pool state to DOWN. See Changing OpenStorage disk pool state on page 115.
Remove the volume by using the nbdevconfig command. The following is the command syntax:
nbdevconfig -deletedv -stype server_type -dp disk_pool_name -dv vol_name
For the server_type, the storage vendor provides the string that identifies the server type.
Change the disk pool state to UP. See Changing OpenStorage disk pool state on page 115.
120
The storage vendor provides the string that identifies the server type. The attribute is the name of the argument that represents the new functionality. For example, OptimizedImage specifies that the environment supports the optimized synthetic backup. SpanImages specifies that backup images can span across volumes on the disk appliance.
-setattribute attribute
In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Devices > Disk Pools.
121
The NetBackup Disk Pool See Viewing OpenStorage disk reports on page 121. status report. NetBackup The storage server view displays real-time values. Administration Console To display the window, in the NetBackup Administration Console, in the left pane, select Storage Server window Media and Device Management > Credentials > Storage Servers. The NetBackup License The summary of active capacity-based license features in the NetBackup License Keys Keys dialog box. dialog box. The summary displays the storage capacity for which you are licensed and the capacity used. It does not display the amount of physical storage space. To open the dialog box, in the NetBackup Administration Console, select Help > License Keys.
The NetBackup OpsCenter also provides information about storage capacity and usage. See the NetBackup OpsCenter Administrator's Guide.
Disk Logs
The Disk Logs report displays the media errors or the informational messages that are recorded in the NetBackup error catalog. The report is a subset of the Media Logs report; it shows only disk-specific columns.
122
The Disk Pool Status report displays the state of disk pool storage units. This report displays only when an Enterprise Disk Option license is installed.
1 2 3 4
In the NetBackup Administration Console, in the left pane, expand NetBackup Management > Reports > Disk Reports. Select the name of a disk report. In the right pane, select the report settings. Click Run Report.
123
124
Chapter
13
Troubleshooting OpenStorage
This chapter includes the following topics:
About OpenStorage log files Troubleshooting OpenStorage credentials creation Troubleshooting Nirvanix storage pool creation Troubleshooting the encryption plug-in Troubleshooting Nirvanix backups and restores
An sts_ prefix relates to the interaction with the storage vendor software plug-in. A nirvanix.com prefix relates to interaction with the Nirvanix Storage Delivery Network. An encrypt prefix relates to interaction with the encryption plug-in. An KMSCLIB prefix relates to interaction with the NetBackup Key Management System.
126
Most interaction occurs on the NetBackup media servers. Table 13-2 shows the NetBackup legacy logs for OpenStorage activity. For legacy logging, the log directories must exist so that the utility can write log messages. See Creating NetBackup log file directories on page 84. Table 13-1 Activity
Backups and restores
The bpbrm backup and restore manager. The bpdbm database manager. The bpdm disk manager. The bptm tape manager for I/O operations.
Connection operations
The bpstsinfo utility writes information about connections to the Nirvanix storage server in its log files. The tpconfig utility. The tpconfig command writes log files to the tpcommand directory.
Credentials configuration
Table 13-2 shows the NetBackup VxUL originator IDs (OIDs) for the processes that write VxUL log messages. VxUL uses a standardized name and file format for log files. To view VxUL log files, you must use the NetBackup vxlogview command. The following is an example of how to view the most recent 20 minutes of log entries for the NetBackup Remote Manager and Monitor Service:
vxlogview -o 222 -t 00:20:00
Information about how to view and manage VxUL log files is available. See the NetBackup Troubleshooting Guide. Table 13-2 Activity
Backups and restores Nirvanix SDN account configuration Device configuration
222
The the Remote Manager and Monitor Service is the process that creates the Nirvanix storage pool and child accounts. RMMS runs on media servers. The nbemm process.
111
127
202
Device configuration
230
Examine the log files for the tpconfig command See About OpenStorage log files on page 125. See Creating NetBackup log file directories on page 84.
128
Examine the log files for the tpconfig command See About OpenStorage log files on page 125. See Creating NetBackup log file directories on page 84.
<Respones> <ResonseCode>50002</ResponseCode> <ErrorMessage>Unauthorized storage pool creation due to node access.</ </Response>
To use the Nirvanix Storage Delivery Network, you must have default node-replication policy settings for your Nirvanix account. New storage pools inherit the default policies, but you can adjust them for each storage pool to fit your business needs. For more information or to verify that your account has the proper settings, please contact Nirvanix Customer Support using the Nirvanix Management Portal. See About Nirvanix storage requirements and limitations on page 75.
Run the following command on the media server from which you want to verify the connectivity:
bpstsinfo si storage_server nirvanix.com stype nirvanix_e
UNIX: /usr/openv/netbackup/bin/admincmd
129
Windows: install_path\NetBackup\bin\admincmd
If the command fails to show connectivity, examine the bpstsinfo command log files to determine why connectivity was not made with nirvanix.com. Examine the log files on the media server on which you want to verify the connectivity. See About OpenStorage log files on page 125. See Creating NetBackup log file directories on page 84.
That the key group exists. That the encryption keys exist in that key group. That the current state of the keys key is ACTIVE.
Determine if backups exist on Nirvanix storage. See To determine if backup images exist on Nirvanix storage on page 130. If backups do not exist, examine the bptm command log files. Examine the bptm log files for failure information. See To find backup and restore failure information on page 130. Look for the following:
If backup jobs fail with error 84 or 87 in the NetBackup Activity monitor, examine the job details in the Activity Monitor or the bptm logs. The write_image call or the close_image call should show an out of space message.
130
The error indicate that you reached your CHILD_ACCOUNT_SIZE setting. The CHILD_ACCOUNT_SIZE setting is a storage server value. See Nirvanix storage server properties on page 86.
If you find an 80006 reponse code, the buffer size may be too large. The following is an example:
Reduce the buffer size and try the backup again. See To determine if backup images exist on Nirvanix storage on page 130. To determine if backup images exist on Nirvanix storage
Run the following command on the media server that was assigned the backup job:
bpstsinfo ii storage_server nirvanix.com stype storage_type
For storage_type, use either nirvanix for nonencrypted backups or nirvanix_e for encrypted backups. The following is the path to the bpstsinfo command:
Examine the bptm command log files on the media server that was assigned the backup job. See About OpenStorage log files on page 125. See Creating NetBackup log file directories on page 84.
Section
SharedDisk option
132
Chapter
14
Introducing SharedDisk
This chapter includes the following topics:
All configuration attempts to a SharedDisk storage server on a 7.0 or later media server fail with a storage server not found error. All read or write requests to a SharedDisk disk pool use 6.5 media servers only. If no 6.5 media servers are available, the requests fail. If you upgrade a 6.5 SharedDisk media server to 7.0 or later, NetBackup marks the storage servers as DOWN. It no longer functions as a SharedDisk storage server. To ensure that the media server is not considered for SharedDisk jobs, do one of the following: Restart the Enterprise Media Manager service after the upgrade or remove the storage server from all disk pools and then delete it. You can delete the SharedDisk disk pools and the SharedDisk storage servers that reside on 7.0 and later media servers. However, all delete operations on images fail. To delete images, do the following:
Expire the images and delete them from the catalog by using one of the following bpexpdate commands:
134
With this command, NetBackup does not run an image cleanup job. You can use NetBackup Management > Catalog to determine the backupid.
bpexpdate -backupid backupid -d 0 -force
With this command, NetBackup attempts an image cleanup job. It fails with error 174; you can ignore the error. You can use NetBackup Management > Catalog to determine the backupid.
bpexpdate -stype SharedDisk
With this command, NetBackup attempts an image cleanup job. It fails with error 174; you can ignore the error.
Delete the fragments of the expired images by using the following command:
nbdelete -allvolumes -force
Note: Symantec recommends that you use solutions other that SharedDisk. The AdvancedDisk storage option is another solution.
Section
Chapter 15. Introducing the Shared Storage Option Chapter 16. Licensing the Shared Storage Option Chapter 17. Configuring the Shared Storage Option Chapter 18. Using the Shared Storage Option Chapter 19. Troubleshooting the Shared Storage Option
136
Chapter
15
About the Shared Storage Option About Shared Storage Option components About reserving or releasing shared devices How to share robotic libraries without using the Shared Storage Option Shared Storage Option terms and concepts
138
Introducing the Shared Storage Option About Shared Storage Option components
Environments that do not use Fibre Channel, such as SCSI switches or multi-initiator configurations
See Frequently asked questions about Shared Storage Option on page 165.
Data path
Hardware connection
It is connected to drives DRV1 and DRV2 through SAN hardware. Host A is the first host in the environment to come online with a non-zero scan ability factor. Therefore, it is the initial scan host for its drives. See About scan hosts on page 139.
Introducing the Shared Storage Option About Shared Storage Option components
139
It is connected to drives DRV1 and DRV2 through SAN hardware. It is configured to be the EMM server, which is also the device allocation host See About the device allocation host on page 141. It controls the robotics. Except for ACS or TLM robot types, only one robot control host exists for each robot. It can be configured (optionally) as a highly available (HA) server.
For a process flow diagram of Shared Storage Option components, see the NetBackup Troubleshooting Guide.
140
Introducing the Shared Storage Option About Shared Storage Option components
Each shared drive has a host that is identified as the scan host. A scan host is the host from which the automatic volume recognition process (avrd) scans unassigned drives. (The robotic daemons scan assigned drives.) A scan host must have data path access to the drive. The EMM database contains the shared drive information; that information includes the scan host. Media servers receive drive status information from the EMM server.
How the scan host is determined EMM determines scan hosts; a scan host may be different for each shared drive. The first host in the environment to come online with a non-zero scan ability factor is the initial scan host for its drives. To configure the scan ability factor of media servers, use the nbemmcmd command. For more information, see NetBackup Commands Reference Guide.) The scan host can change A scan host is assigned for a shared drive until some interruption occurs. For example, if one of the following occurs, EMM chooses a new scan host: The socket connection, the host, the drive, the drive path, or the network goes down. The drive is logically placed in the Down mode.
The scan host temporarily changes to hosts that request tape mounts while the mount is in progress. Scan host changes occur so only one host at a time has access to the drive path. Drive paths for the scan host If a drive has multiple paths that are configured on the selected scan host, EMM selects a scan path as follows: The first local device path it finds in its database in the UP state. The first NDMP-attached drive path it finds in its database in the UP state.
Introducing the Shared Storage Option About reserving or releasing shared devices
141
For shared tape drives, only the scan host polls drives until a mount request is received from NetBackup. During a mount request, NetBackup uses the host that requests the mount to poll the shared drive. This design enables NetBackup to support Dynamic Loop Switching or SAN zones. Each tape drive needs to be detected only from a single host. Each tape drive can potentially have its own scan host that switches dynamically to process errors and continue availability. A central device arbitrating component manages scan host assignments for shared drives. The arbitrating component also provides a network drive reservation system so that multiple NetBackup media servers can share a drive. Polling a shared tape drive allows dynamic loop switching and reduces the number of device accesses and reduces CPU time. However, it cannot detect connectivity breaks (for example, discontinuity in the Fibre Channel fabric) until I/O occurs.
The name of the shared drive. The name of the current scan host. The operation, which is one of the following:
RESERVED The host on which the script is executed needs SCSI access to the drive until it is released.
142
Introducing the Shared Storage Option How to share robotic libraries without using the Shared Storage Option
ASSIGNED
Informational only. It does not change the fact that the host that reserved the drive needs SCSI access. Only the scan host needs SCSI access to the drive. The host that executes the script has become the scan host. A host should not become a scan host while the drive is RESERVED. The scan host may change between a RESERVED operation and a RELEASED operation.
RELEASED SCANHOST
The script resides in one of the following directories: Windows: Install_path\VERITAS\Volmgr\bin UNIX: /usr/openv/volmgr/bin/shared_drive_notify Note: The script must be executable by the root user. The script exits with status 0 upon successful completion.
How to share robotic libraries without using the Shared Storage Option
You can share robotic tape libraries among multiple NetBackup media servers by using any of the following methods:
Shared library support NetBackup allows different drives within the same robotic library to be configured on different media servers. This capability is termed shared library support. Robot types that support shared library are ACS, TL8, TLD, TLH, TLM. Partitioned libraries Some robot vendors also let you partition libraries. One partitioned view of the robotic library includes one set of drives, while the other view has a different set of drives in the library. Partitions let two robotic control daemons on different control hosts manage the robotic library possibly each for a different NetBackup master and media server environment. Multiple master servers Use multiple NetBackup master servers that share a common media and device management domain. This means that the master servers use the same EMM server.
Introducing the Shared Storage Option Shared Storage Option terms and concepts
143
These capabilities are not related to Shared Storage Option and should not be confused with Shared Storage Option.
Shared drive
144
Introducing the Shared Storage Option Shared Storage Option terms and concepts
Chapter
16
About the Shared Storage Option license key Licensing the Shared Storage Option
146
Licensing the Shared Storage Option Licensing the Shared Storage Option
To license SharedDisk
1 2 3 4 5
To add a license to a specific server, on the File menu, click Change Server and then select the server. In the NetBackup License Keys dialog box, click New. In the Add a New License Key dialog box, enter the license key and click Add or OK. Click Close. Restart all the NetBackup services and daemons.
See About the Shared Storage Option license key on page 145.
Chapter
17
About Shared Storage Option prerequisites About hardware configuration guidelines About installing and configuring drivers Verifying the connectivity About configuring the Shared Storage Option in NetBackup Verifying your Shared Storage Option configuration
Configure your SAN environment. Attach robots and drives. Ensure that all of the servers recognize the shared devices. Device recognition may depend on operating system configuration, as follows:
On UNIX or Linux servers, you may have to modify configuration files, such as the sg driver on Solaris systems. On Windows servers, Windows recognizes devices automatically. However, in some instances you may have to install device drivers.
148
Configuring the Shared Storage Option About Shared Storage Option prerequisites
Determine the physical location of each drive within the robot. Location usually is shown on the connectors to the drives or in the vendor documentation. This task may not be required if NetBackup device discovery accurately determines drive location within the robot. Connect all drives and all robots. Install SAN connecting hardware (for example, bridges, switches, or hubs). If fiber is part of your configuration and you use a SCSI-to-fiber bridge, determine the SCSI-to-Fibre Channel mapping for your tape devices. Hard-wired SCSI IDs are converted to Fibre Channel logical unit numbers (LUNs) that the hosts read. To ensure correct drive assignments, you should know which LUNs map to which physical SCSI IDs. Use persistent LUN mapping if possible. Familiarity with the hardware and various vendor configuration tools help you accomplish this task. See the vendor documentation for your bridge. Record the physical configuration. When you set up a Shared Storage Option configuration, record your hardware information. Record the adapter, SCSI addresses, World Wide Names (WWNs), and Fibre Channel LUNs to which you connected each drive. Also, record the version levels of firmware and drivers. Install and configure the appropriate drivers. See your vendor documentation for instructions. On UNIX or Linux servers, create any device files that are needed. Depending on the operating system, a reconfiguration system start (boot -r) may create these files automatically. Create the device files for each drive; use the Fibre Channel LUNs of the drives and adapters in the device file names. Add the names of the device files to your notes to complete the correlation between device files and physical drive location. Use the NetBackup Device Configuration Guide and the man pages that are available with the operating system. On UNIX servers, customize the operating system by modifying the appropriate system configuration files. This task requires knowledge of the system files that use the Shared Storage Option environment and their formats. For example, on Sun Solaris systems you may need to modify the sg, st, and HBA driver files. Modify the HBA driver files to bind Fibre Channel devices (WWN) to a specific target ID. For procedures, see the operating system documentation. For instructions on how to configure the HBA on Windows servers, see the HBA documentation from the vendor.
149
Use any available hardware configuration interface to configure and ensure that the configuration is what you expect. For example, on Windows servers you can use the Hyperterminal interface to configure SCSI-to-fibre bridges. Use the following order when you configure and verify the hardware:
If errors occur and you suspect the operating system, refer to the operating system logs as described in your operating system documentation.
If you use SAN hardware from multiple vendors, problems may occur. Always use a SAN configuration and use firmware levels that the hardware vendor supports. Consult SAN device, HBA, and operating system documentation to determine how to configure operating system tape drivers and pass-through drivers to detect your SAN devices. Check your hub timer settings. Use hard arbitrated loop physical addresses rather than soft addresses. Consult with hardware suppliers to verify the recommended usage of their products. Check the firmware levels of all your Fibre Channel hardware (for example, bridges). Use the most recent firmware level that is known to operate with other SAN hardware devices. Try to duplicate SAN issues and problems using commands and utilities on the host operating system. Test both backup and restore capabilities. Backup jobs may complete successfully, but the data may be corrupted. For example, incorrect switch settings may cause problems. Ensure that your hardware and SAN configuration are operational and stable before adding Shared Storage Option software. Test backup and restore capabilities with dedicated tape drives before you configure them as shared drives.
150
Configuring the Shared Storage Option About installing and configuring drivers
For large configurations, begin drive sharing with a few tape drives and two or three media servers (or NetBackup SAN media servers). Configuration and troubleshooting processes are easier on smaller configurations. If possible, create multiple and independent Shared Storage Option configurations with subsets of servers sharing subsets of SAN-attached drives. Use the correct start order for your Fibre Channel hardware, as follows:
The start sequence is longer for some devices than others. To verify that the hardware starts completely, examine indicator lights. A green light often indicates a completed start sequence.
Verify that all of your servers (master and media) can communicate with one another. To do so, use the ping command from each server to every other server. Be sure to ping by host name to verify that the name resolution methods function properly. Use the NetBackup bpclntcmd utility to resolve IP addresses into host names. For more information, see the NetBackup Troubleshooting Guide and the NetBackup Commands Reference Guide. Use operating system and NetBackup commands and tools to verify that the devices are configured correctly. Make sure that the operating system detects
Configuring the Shared Storage Option About configuring the Shared Storage Option in NetBackup
151
the devices on the SAN before you configure the Shared Storage Option. If the configuration does not work in the operating system, it does not work for the Shared Storage Option. For example, on Solaris systems you can use the mt -f tapename status command to determine tape drive status.
For more information and examples, see the appropriate operating system chapter in the NetBackup Device Configuration Guide.
Configuring Shared Storage Option devices See Configuring Shared Storage Option in NetBackup devices in NetBackup on page 151. About adding Shared Storage Option configuration options See About adding Shared Storage Option configuration options on page 152.
About configuring NetBackup storage units See About configuring NetBackup storage and backup policies units and backup policies on page 152.
152
Configuring the Shared Storage Option About configuring the Shared Storage Option in NetBackup
Be sure to review the limitations of the wizard in the wizard help. To start the Device Configuration Wizard
1 2
In the NetBackup Administration Console, expand Media and Device Management. Click Configure Storage Devices.
NetBackup Administrators Guide for UNIX and Linux, Volume II NetBackup Administrators Guide for Windows, Volume II.
NetBackup Administrators Guide for UNIX and Linux, Volume I NetBackup Administrators Guide for Windows, Volume I.
Configuring the Shared Storage Option Verifying your Shared Storage Option configuration
153
Configuring a backup policy How you define a policy for a media server depends on your for each media server media server license, as follows: For a media server that is licensed for Shared Storage Option, the policy can back up the media server and any other NetBackup clients. For a NetBackup SAN media server, only the SAN media server can be backed up.
A license for a regular media server provides the greatest flexibility; a license for a NetBackup SAN media server is more restrictive. For a policy for the clients that you want to back up anywhere in your configuration, you can choose any available storage unit. Alternatively, you can use storage unit groups (prioritized storage units).
If you have serialized devices, Symantec recommends that you use the Device Configuration Wizard. The wizard verifies your configuration. If you have non-serialized devices, see the Symantec support site for a tech note with instructions about how to verify your configuration. The tech note title is "Verifying a Shared Storage Option (SSO) Configuration with Non-Serialized Devices." If you have serialized devices but you did not use the Device Configuration Wizard , use the following procedure to verify your configuration.
The verification procedures use the NetBackup scan and tpconfig commands. These commands are located in the following directory:
In the following example the ADIC robotic library has six drives, but only drives 5 and 6 are configured on this particular host.
154
Configuring the Shared Storage Option Verifying your Shared Storage Option configuration
Perform the verification on all of the NetBackup servers in your configuration. Ensure that each shared drive has the same logical drive name and same drive number ID on each media server that shares the drive.
Configuring the Shared Storage Option Verifying your Shared Storage Option configuration
155
Execute tpconfig -d or tpconfig -dl. For NDMP devices, use tpautoconf -probe -ndmp_host_name host_list. The output from tpconfig shows the logical names NetBackup assigns to tape drives. The following example shows drive number 5 is named QUANTUM.DLT7000.000 and drive number 6 is named QUANTUM.DLT7000.001:
Id DriveName Type Residence Drive Path Status *************************************************************** 0 QUANTUM.DLT7000.000 dlt TLD(0) DRIVE=5 /dev/st/nh3c0t5l0 UP 1 QUANTUM.DLT.7000.001 dlt TLD(0) DRIVE=6 /dev/st/nh3c0t1l0 UP Currently defined robotics are: TLD(0) robotic path = /dev/sg/h3c0t0l0 EMM server = norway
156
Configuring the Shared Storage Option Verifying your Shared Storage Option configuration
Execute the scan command. The scan output shows the robot and the drive properties. The following is example output:
************************************************************* ********************** SDT_TAPE ************************** ********************** SDT_CHANGER ************************** ************************************************************* Device Name : "/dev/sg/h3c0t0l0" Passthru Name: "/dev/sg/h3c0t0l0" Volume Header: "" Port: -1; Bus: -1; Target: -1; LUN: -1 Inquiry : "ADIC Scalar 100 3.10" Vendor ID : "ADIC " Product ID : "Scalar 100 " Product Rev: "3.10" Serial Number: "ADIC009K0340314" WWN : "" WWN Id Type : 0 Device Identifier: "" Device Type : SDT_CHANGER NetBackup Robot Type: 6 Removable : Yes Device Supports: SCSI-2 Number of Drives : 6 Number of Slots : 50 Number of Media Access Ports: 10 Drive 1 Serial Number : "PXB03S0979" Drive 2 Serial Number : "PXB03S0913" Drive 3 Serial Number : "CXA04S2051" Drive 4 Serial Number : "PXA31S1787" Drive 5 Serial Number : "PXA37S3261" Drive 6 Serial Number : "PXA50S2276" Flags : 0x0 Reason: 0x0 -----------------------------------------------------------Device Name : "/dev/st/nh3c0t5l0" Passthru Name: "/dev/sg/h3c0t5l0" Volume Header: "" Port: -1; Bus: -1; Target: -1; LUN: -1 Inquiry : "QUANTUM DLT7000 2561" Vendor ID : "QUANTUM " Product ID : "DLT7000 "
Configuring the Shared Storage Option Verifying your Shared Storage Option configuration
157
Product Rev: "2561" Serial Number: "PXA37S3261" WWN : "" WWN Id Type : 0 Device Identifier: "" Device Type : SDT_TAPE NetBackup Drive Type: 9 Removable : Yes Device Supports: SCSI-2 Flags : 0x4 Reason: 0x0 -----------------------------------------------------------Device Name : "/dev/st/nh3c0t1l0" Passthru Name: "/dev/sg/h3c0t1l0" Volume Header: "" Port: -1; Bus: -1; Target: -1; LUN: -1 Inquiry : "QUANTUM DLT7000 296B" Vendor ID : "QUANTUM " Product ID : "DLT7000 " Product Rev: "296B" Serial Number: "PXA50S2276" WWN : "" WWN Id Type : 0 Device Identifier: "" Device Type : SDT_TAPE NetBackup Drive Type: 9 Removable : Yes Device Supports: SCSI-2 Flags : 0x4 Reason: 0x0
Use the device file name from the tpconfig output to locate the tape drive in the scan output. Step 1 shows device file pathnames /dev/st/nh3c0t5l0 and /dev/st/nh3c0t1l0.
Determine the serial number of the drive in the scan output. "Tape" in the device type field identifies a tape drive. Step 2 shows example scan output shows the following: The drive /dev/st/nh3c0t5l0 serial number is PXA37S3261. The drive /dev/st/nh3c0t1l0 serial number is PXA50S2276.
158
Configuring the Shared Storage Option Verifying your Shared Storage Option configuration
Verify that the serial number for the drive matches the serial number in the output from the robot section of scan. "Changer" in the device type field identifies a robot. In the previous examples, the serial numbers match.
Chapter
18
Device Monitor and Shared Storage Option Viewing SSO summary reports About adding SSO configuration options
Changing the operating mode For a shared drive, the Change Mode dialog contains a list for a shared drive of all paths to the selected drive. You can choose any number of paths to which the mode change applies.
160
A list of all paths to the selected drive The current drive comment for each combination.
You can choose any number of paths to which the changes apply. Performing drive cleaning The three available drive cleaning functions are used with functions for a shared drive shared drives are as follows: Clean Now In the list of hosts that share the drive, you can choose only one host on which the function applies. Reset Mount Time In the list of hosts that share the drive, you can choose any number of hosts on which the function applies. Set Cleaning Frequency Supported for shared drives.
1 2 3 4 5
In the NetBackup Administration Console, in the left pane, expand Media and Device Management > Device Monitor. On the Actions menu, select View Status of Shared Drives. In the Status of Shared Drives dialog box, select a device allocation host (or hosts) from the list. Use Add to move the host to the list of hosts to scan. Click OK. The Shared Drive Summary and Device Allocation Host Summary appear in the two lower panes of the dialog.
Using the Shared Storage Option About adding SSO configuration options
161
Drive name Device allocation host Number of registered hosts Drive reservation status Hosts that reserve the drive Current scan host
Device allocation host Host name of the registered host Number of registered and reserved drives Availability status Scan ability factor Scan status (if the host is scan host for at least one SSO drive)
NetBackup Administrators Guide for UNIX and Linux, Volume II NetBackup Administrators Guide for Windows, Volume II.
162
Using the Shared Storage Option About adding SSO configuration options
Chapter
19
Operating system assistance Common configuration issues with Shared Storage Option Frequently asked questions about Shared Storage Option
Operating system logs, as described in the operating system documents. NetBackup logs. Operating system man pages (UNIX or Linux servers only). The NetBackup Device Configuration Guide.
Verify that the SAN hardware uses current firmware or drivers. Hardware includes hubs, switches, HBAs, and bridges.
164
Troubleshooting the Shared Storage Option Common configuration issues with Shared Storage Option
Verify that the JNI HBA failover value was set to zero to avoid I/O hangs. This value applies to bridges and HBAs. Verify that the HBAs with the SCSI-3 protocols are compatible with the operating system drivers. Verify that your cluster configuration is supported. For more information about cluster configuration, see the NetBackup Release Notes Verify that all of your Fibre Channel devices support your Fibre Channel topology. For example, in a switched fabric topology, ensure that all devices supported switched fabric. Verify that Shared Storage Option is licensed on each server. To do so, select Help > License keys from the NetBackup Administration Console on each server. To enable Shared Storage Option, enter the Shared Storage Option license key on each server. Verify that you configured Shared Storage Option from the master server. You must configure SSO from the master server not from a media server (or SAN media server). Verify that you configured the same robot control host on every host. Remember that except for ACS and TLM robot types, only one host controls the robot. Verify that you used the Device Configuration Wizard rather than the tpconfig utility to configure Shared Storage Option. The wizard coordinates configuration with all hosts that share the drives. The tpconfig utility may create inconsistent configurations. Verify that you selected the appropriate device hosts in the Device Configuration Wizard , including the host with robotic control. Fibre Channel connections to the drives and the robots cause increased complexity in a NetBackup device configuration. On some operating systems, SCSI-to-fibre bridges may result in inconsistencies in the device paths when you restart a host. After a restart of the host, the device configuration should be verified. Verify that names across all systems that share the drives are consistent. Test the drive paths on every media server. Define NetBackup storage units for each media server. Do not select any available media server in the storage units.
Troubleshooting the Shared Storage Option Frequently asked questions about Shared Storage Option
165
Verify that you did not interrupt a data path during a backup. If you do, the NetBackup job fails. It can fail with media write errors or it may hang and have to be terminated manually. Verify that you do not use Berkeley-style close on the tape path (UNIX or Linux servers only). On Solaris systems, verify the following:
That you added tape configuration list entries in /kernel/drv/st.conf (if needed). That you defined configuration entries for expanded targets and LUNs in sg.links and sg.conf files. If you see problems with the entries in the /etc/devlink.tab file (created from sg.links), verify the following: The first entry uses hexadecimal notation for the target and LUN. The second entry uses decimal notation for the target and LUN. Use a single tab character between the entries; do not use a space or a space and a tab character.
That you configured the operating system to force load the sg/st/fcaw drivers.
For more information, see the Solaris chapter of the NetBackup Device Configuration Guide.
166
Troubleshooting the Shared Storage Option Frequently asked questions about Shared Storage Option
Q. Does NetBackup Shared Storage Option use the IP protocol or the SCSI protocol? A. Both. IP protocol is used to provide coordination between servers. Shared Storage Option uses SCSI protocol (SCSI reserve) as an added layer of protection.
Index
A
ACS or TLM robot types 139 AdvancedDisk and CIFS 23 and NFS 23 license key for 20 Arbitrated Loop Physical Address (ALPA) 149
I
installing the OpenStorage vendor plug-in 78
L
license key for AdvancedDisk 20 for Shared Storage Option 145 license keys 137
B
Backup Exec 143 bpclntcmd utility 150
M
maximum concurrent drives for backup 152 Media server storage unit setting 34, 93
C
Cloud storage 72 configuring devices 147 configuring OpenStorage optimized synthetic backups 102
N
nbemm 138 nbemm/DA definition 138 Nirvanix 72 changing storage server properties 85 the Nirvanix vendor plug-in 62
D
device configuration wizard 151 drivers 147148 files 148 device allocation host 139, 141 disk appliance plug-in 62 duplicating images to another NetBackup domain about 64, 66
O
OpenStorage installing the vendor plug-in 78 Nirvanix 72 plug-in 62 OpenStorage disk pool updating 119 OpenStorage optimized synthetic backups about 66 configuring 102 OpenStorage storage server updating 108 OpenStorage volume spanning about 63 optimized duplication configuring behavior for OpenStorage 97 OpenStorage 64
E
examples SSO components configuration 138
F
firmware levels 148149
H
HyperTerminal 149
168
Index
optimized synthetic backups configuring OpenStorage 102 OpenStorage 66 overview of shared drives 137
P
plug-in for a disk appliance 62 for Nirvanix storage 62
R
replication about duplicating images to another NetBackup domain 64, 66 robot sharing without SSO 142
SSO (continued) Shared Drive Summary 161 supported SAN hardware 165 terminology 143 Storage area network (SAN) 137, 143, 147, 149 storage server about OpenSorage 61 changing properties for Nirvanix 85 storage unit properties OpenStorage 92 storage unit recommendations OpenStorage 94 supported SAN hardware 165 Symantec Backup Exec 143
T
tested SAN components 165 troubleshooting AdvancedDisk disk failure 52 AdvancedDisk volume state changes to DOWN when volume is unmounted 52 multiple AdvancedDisk storage servers on Windows 51 unable to access AdvancedDisk storage 51
S
SAN media server 139, 143 SAN Shared Storage Option (see SSO) 137 scan host 138, 140 scripts shared_drive_notify 141 SCSI-to-fibre bridges 149 Servers SAN media server 139 shared drives definition 143 shared drives (see SSO) 137 shared library support 142 shared robots without SSO 142 Shared Storage Option. See SSO license key for 145 shared storage option key 137 shared_drive_notify script 141 SharedDisk storage units 133 spanning volumes OpenStorage 63 SSO definition 137 device allocation host 139, 141 Device Allocation Host Summary 161 hardware requirements 137 scan host 138, 140
U
updating an OpenStorage disk pool 119 updating an OpenStorage storage server 108
V
volume spanning OpenStorage 63
W
wizard device configuration 151 shared drive configuration 151