DDBoost ,CIFS , NFS , VTL Implementation & NAS BEST PRACTICES

Data Domain Implementation:

To successfully integrate the Data Domain system into a backup environment:

1. Perform the basic installation and configuration tasks.(make certain that all installations have occurred, including installation of all application software as necessary throughout the environment, and installation and initial configuration of the Data Domain system for proper network access by client systems and backup servers.

2. configure the Data Domain system with the correct networking, and create a backup user
(performed by Implementation Engineers).

3. Configure the backup server with the necessary credentials or other settings as necessary, and create a share on the Data Domain system.
(performed by Implementation Engineers).

Verifying Data Domain functionality with Backup system:

1. Perform administrative tasks on the backup systems administrative console in order to create a backup job.

2. Run and monitor the backup job in the backup systems administrative console.

3. Perform operations to perform backup and validate recovery for a client system.

4. Validate and analyze the backups within the Data Domain System Manager, where you can view statistics and reports.

DDBoost Implementation:

1. Prepare Data Domain systems (A and B) for DD Boost

Enable DD Boost and Set User.

Create Storage Unit and CIFS Share.

2. Backup application Console Configure Data Domain systems as Devices for Boost

Configure system A for Backup.

Configure system B for Backup Clone.

3. Backup application Console

Configure Backup / Clone Operations

4. Console: Monitor Activity for Backup / Clone

5. Verity Files on Data Domain systems A and B

6. Backup application Console:

Restore files from Backup Clone

Implement VTL:

1. Install Configure HBA Cards.

2. Configure FC zoning.

3. Configure VTL on Data Domain System.

4. On Backup application administrative management perform the device discovery and configuration.

5. On Backup application administrative management Run and monitor backup jobs and validate backup.

Implement CIFS:

1. Install Backup software Management and Media (Storage Node) servers and clients components .

2. On Data Domain System Configure Networking and CIFS parameters, Create a Backup user and CIFS share.

o Create a new user and Choose Admin from the Privilege drop down menu.

o Choose the Admin option. note of these new user credentials. They will be added to the services logon credentials on the NetWorker Server.

o map a CIFS share on the Data Domain system, to be used in NetWorker backup administration. This directory will be the target for backups.

o Map a network drive to the ClFSshare created.

3. Additional Configuration on Backup Application AKA Networker (configure a CIFS AFTD NetWorker device on NetWorker server or storage node)

4. Verify CIFS access from Backup system.

5. From Backup application Create a backup Job , Run and monitor it , then Validate that backup job.

6. From Backup application Recover backup and validate it.

7. On Data Domain Analyze system statistics.

Implement NFS:

1. Install Backup software Management and Media (Storage Node) servers and clients components .

2. On Data Domain System Configure Networking and NFS parameters.

3. Backup Application additional Configuration :

o Mount Points.

o Mount Data Domain Directory.

o Modify /etc/fstab.

o Create Backup directory.

4. Validate functionality for NFS by creating and copying files from the Server to the Data Domain backup directory.

Tivoli Storage Manager work Flow:

Tivoli Storage Manager policies are rules that determine how the client data is stored and managed. The rules include where the data s initially stored, how many backup versions are kept, how long archive copies are kept, and so on.

The steps in the process are as follows:

1. A client initiates a backup, archive, or migration operation. The file involved in the operation is bound to a management class. The management class is either the default or one specified for the file in client options (the clients include-exclude list).
If the file is a candidate for backup, archive, or migration based on information in the management class,

2. The client sends the file and file information to the server.

3. The server checks the management class that is bound to the file to determine the destination, the name of the Tivoli Storage Manager storage pool where the server initially stores the file. For backed-up and archived files, destinations are assigned in the backup and archive copy groups, which are within management classes. For space-managed files, destinations are assigned in the management class itself.

4. The server stores the file in the storage pool that is identified as the storage destination.

Preparing Data Domain for integration with RMAN:

Prior to integration with Oracle Recovery Manager (RMAN) enabled for DD Boost. Every Data Domain system that Is enabled for Data Domain Boost must have a unique name. You can use the Data Domain systems DNS name, which is always unique.

1. Verify that the file system is enabled and running by entering:# filesys status

2. Add the DD Boost license type:# license add ABCD-DCBA-AABB-CCDD

3. add a user. enter:# user add boostadmin password abcl23

4. Now type:# ddboost set user-name boostadmin

5. Enable DD Boost by entering:# ddboost enable

6. Create one or more storage units on each Data Domain system that will be used with RMAN.(Each storage unit name on a single Data Domain system must be unique.)

7. when performing file replication, the storage unit name on the two Data Domain systems used In the replication must be the same.

On the Data Domain system, enter:# ddboost storage-unit create storage_unit_examplel

8. You repeat the last step for each Boost-enabled Data Domain system.

9. Now you configuring Advanced Load Balancing and Link Failover. Add existing interfaces to the group and register

the Data Domain system with RMAN. Note that the interfaces must already have been created with the net command, and only one Interface group can be created and this group cannot be named.

12. Begin adding the interfaces into the group by entering #ddboost ifgroup add interface 192.168.1.1

Continue creating the group by entering: # ddboost ifgroup add interface 192.168.1.2

Continue creating the group by entering: # ddboost ifgroup add interface 192.168.1.3

Finish creating the group by entering: # ddboost ifgroup add interface 192.168.1.4

Select one interface on the Data Domain system to register with RMAN. Note that an Interface that is not part of the ifgroup can also be used to register with RMAN. It is recommended that the interface be registered with a resolvable name using DNS or any other name resolution mechanism.

13. Enable the feature on the Data Domain system by entering:# ddboost ifgroup enable

14. Enable low-bandwidth optimization. To do this, enter:# ddboost file-replication option set low-bw-optim

15. After low-bandwidth optimization is enabled, a full cleaning cycle on the Data Domain system is required. Use this option only when there is replication over low-bandwidth networks with less than 6 Mbps aggregate bandwidth.

16. Now you enable Encrypted File Replication. To do this, enter# ddboost file-replication option set encryption enabled

17. RMAN, In the Oracle System Manager (OEM), you configure a channel by entering a command that is specific to the environment (Linux/Solaris, or Windows with Oracle Database hg/log).

18. Next, you register Each Data Domain System with a script

19. The servemame is the name of the Data Domain system exactly as specified by the BACKUP_HOST value In the CONFIGURE CHANNEL command.

20. Now We are ready to perform backups and restores to and from your Data Domain system using device type sbt_tape. If you want all your backups to go to the Data Domain system,

21. Configure SBT_TAPE as your default device.

CommVault Simpana#

Data Domain system is used here as one or more Static Shared Magnetic Libraries that utilize the CIFS protocol.

1. Create a CommVault administrative user account with proper privileges. The account should be the same as the service account used for CommVault administration and have administrative rights.

2. Enter the following:# user add svc_simpana role admin password abcl23

3. Set the tape marker setting for Simpana and restart the file system.

4. If the Data Domain system will only be a target for Simpana backups, use the cvi marker setting instead, reset the marker setting by entering:# filesys option reset marker-type

5. Verify that the marker setting was reset to the default. Note that the auto marker setting is available with DD OS 5.0 and onward.

6. The filesystem must be restarted to effect this change.Restart the filesystem
by entering:# filesys disable

Re-enable the files system
by entering:# filesys enable

7. Now set the CIFS client access permissions for Simpana media agents. A share called ClFSbackup was previously createde. To provide client access to all clients,
enter:# cifs share
modify ClFSbackup clients *

You create folder(s) under /backup for Shared Disk Device backup target(s) and base folders for mount paths. You can optionally define these folders as separate CIFS shares within the CLI.Congratulations, you successfully prepared a Data Domain system for integration into a CommVault Simpana backup environment. View the implementation documentation for CommVault for additional integration procedures within Simpana.

**

Note

Create a separate folder for each TSM device class (FILE TYPE) Perform capacity planning and measurement to ensure the Data Domain Restorer capacity is adequate for each folder If subdirectories are created, export the subdirectories via NFS to ensure TSM calculates accurate space for volumes. For multiple TSM servers using a single Data Domain Restorer instance create a separate file system mount point or folder for each TSM

**

NAS BEST PRACTICES:

CIFS/NFS File system#

Advertisements

About Ahmad Sabry ElGendi

https://www.linkedin.com/pub/ahmad-elgendi/94/223/559
This entry was posted in Data Domain, E20-385, EMC. Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s