White Papers

Best practices for setting up Dell VTL Container or NetVault Backup native virtual tape library (nVTL)

Technical setup and conﬁguration nVTL -- best practices

This section highlights key conﬁguration and setup best practices to add the DR Series

appliance for the use with NetVault Backup nVTL instance(s).

General setup and conﬁguration -- best practices

For additional details on the following prerequisites, refer to the manufacturer’s

documentation.

• Ensure that cabling is conﬁgured correctly.

• Conﬁgure interfaces, protocol, and addressing.

- Conﬁgure the networking infrastructure to support jumbo frames (MTU=9000).

• Make sure that you have a preconﬁgured system to run as the NetVault Backup Server and

respective nVTLs.

• Make sure that you have a DR Series appliance preconﬁgured for use with the following

attributes established:

- Proper network connectivity with IP address or DNS name of DR Series appliance.

- DR Series appliance(s) conﬁgured with the appropriate containers needed to host the

NetVault Backup nVTL instance.

- For each container deﬁned, a network share exported via CIFS or NFS of appropriate

permission and size.

- All authentication requirements fulﬁlled such as domain name, user name, and

password for users set up on the DR Series appliance to provide full access to the

predeﬁned containers and network share(s) for use as backup repositories. In the case

of the NetVault Backup nVTL solution, this should include full access to the NetVault

Backup Server and to all NetVault Backup SmartClients intended for use.

DR Series appliance setup and conﬁguration -- best practices

• Create and conﬁgure each NetVault Backup nVTL instance to run within the domain of a

single DR Series appliance storage container. This enables easier management of storage

consumption.

• Create NetVault Backup Server users who have full read/write access to the container. This

is a requirement for NetVault Backup to be able to manage the conﬁguration items and

respective objects created within the applicable container during backup, provide access

during recovery, and perform deletion upon retirement.