Sunday, December 8, 2013

Hi,

I would like to show how to test clone restore.

First select the which data backup you want to restore.

recover -c "Source host name" -R "Destination host name" -iR

check version of all save set. i.e you select the C:\ drive save set.(12/04/2013)

Note the C:\ drive backup date from version command.

add the files and check volume. It will show the local AFTD volume.

Note the volume name

Then check clone data with mminfo command

go to >>>> backup server NMC >>>Media >>>>Disk Volume >>> select the noted volume name.

Right click and select show save set.

Select that particular C:\ drive save set and change it mode to normal to Suspect.

Then run again recover command same as above.

check version again

Your selected C:\ drive version Showing different AFTD and it will cloned AFTD for (12/04/2013).

change time

add that particular files.


check volumes and you will get different AFTD volumes.


then try to restore data from clone AFTD

Sunday, December 1, 2013

Tech Tip : NMC view save

Often we face trouble while setting the layout, positions and sizes of sub-windows inside a particular window in NetWorker Management Console (NMC) as, sometimes, they tend to revert back to the default layout the next time that particular window is opened. Following is a quick tip to help save your view settings so that you don’t need to change it as per your preference each time you open an NMC window:

1. Open only one instance of NMC and then open the window you wish to set your layout on.
2. Arrange the sub-windows inside it as you prefer. The below is a sample screenshot which shows the positions and sizes of the Groups, Alerts and Sessions sub-windows.
3. Often, after the layout is set, merely closing the window using the X button on the top right corner 
    of the window saves the view settings. In case it doesn’t, set the layouts again and close the 
    window by double-clicking on the program icon on the top left corner of the window’s title bar.

4. Try opening the same or any similar window again, you will see that your view settings have been 
     saved.

5. This trick is also applicable while saving the layout of NetWorker’s console window.

Networker installation on Windows OS:


Networker installation on Windows OS:

 

You must install the Console server software on one computer in your datazone to

manage the NetWorker server. Only one installation of the Console server is required

to manage multiple NetWorker servers.

 

To install the Console:

 

Ø  In the Welcome to NetWorker Management Console Installation page, click

Next.

 

Ø  In the Customer Information page, fill in the appropriate information and click next

 

Ø  In the Installation Required JRE page, if you have not installed the JRE version

or 1.5.0 software, install it now and then click Next. The JRE is required to

run the Console reporting function:

 

Ø  Select Install Java 2 Runtime Environment, SE v1.5.0_11 to install the JRE

version 1.5 software.

 

Ø  Select Skip JRE installation to continue the installation without installing the

             JRE. You are prompted to install the JRE when you first access the Console

            interface. This disables the command line reporting feature.

 

Ø  In the Product Setup page:

 

a.       To install the software in the default directory, click Next.

b.      To install the software in a different directory, click Change and navigate to or  type a new destination.

 

Note: The estimated disk space required for the Console components is 270 MB.

If the Setup wizard detects that there is insufficient disk space to install the software, another dialog box appears listing the system’s local drives, and highlighting the drive with insufficient disk space. The list also displays disk size, available space, and required space, which allows the selection of an appropriate drive on which to continue the installation.

 

 

Ø  In the Configuration Options page, indicate the Database Destination path, the

            IP port numbers to use for the embedded HTTP server, and the Client Service

 

 

Port:

Ø  To change the default database path, select Change.

 

Ø  To use the default port numbers, type 9000 for the HTTP server and 9001 for

Ø  The Client Service port.

 

Ø  To use different port numbers, type the new port numbers (between 1024 and

Ø  49151).

 

Note: Port 2638 is reserved by the Console software as it uses the TDS protocol to

communicate with the database. Port 9002 is the preferred port for EMC Backup Advisor

product.

 

 

Ø  Review the information in the Product Configuration Summary page and click

            Next.

Ø  In the Ready to Install the Program page, click Install.

 

§  Click the check box (the default is selected) to launch the client in the default

            browser immediately after exiting the InstallShield Wizard.

 

§  Click Finish to exit the InstallShield Wizard.

            When the installation is complete, the NetWorker Management Console Setup

            Completed page appears. The box shows where the install.log file and gstd.log

            file can be viewed. It also gives the browser URL to use to start the Console

            software from any desktop.

 

Ø  8. If the Console server and the NetWorker server are installed on separate hosts,

            you must add the Console administrator to the administrator lists of the

            monitored NetWorker server. This enables the Console administrator to

            administer and monitor the target NetWorker server.

 

On the NetWorker server:

 

§  Specify the process owner of the Console daemon process depending on

            which host contains the Console server:

 

– If on a Microsoft Windows host, type:

nsraddadmin -u "user=SYSTEM, host=console_host"

 

– If on a AIX, HP-UX, Linux or Solaris only host, type:

nsraddadmin -u "user=root, host=console_host"

 

§  Specify the Console administrator user:

nsraddadmin -u "user=administrator, host=console_host"

Where console_host is the Console server hostname.

Sunday, November 24, 2013

Networker installation on Linux OS:


To access the installation software from the http://Powerlink.EMC.com website:

 

1.      Log in with administrator privileges where the NetWorker software is being

Installed.

 

2.      Create a temporary folder to download and extract the evaluation software.

 

3.     Go to the http://Powerlink.EMC.com website, select Support > Downloads and

Patches > Downloads D-R > NetWorker.

 

4.      Download the evaluation software to the temporary folder and change to that

folder.

 

5.      5. Extract the downloaded file.

 

By default, the NetWorker software is installed in the /usr directory; however, the Software can be installed in a different directory. If you have insufficient disk space On the /usr partition, choose another location to install the software.

 

Networker installation on Linux OS:

Note: The NetWorker software uses the rpm utility for installation. To install the NetWorker software on the computer designated as the NetWorker

To install the client node software:

 

1.      Log in to the NetWorker Linux client.

 

2.      Change to the directory containing the NetWorker software.

 

3.      Type the appropriate command:

 

         For Itanium:

rpm -ivh lgtoclnt-7.4-1.ia64.rpm

 

         For Intel x86:

rpm -ivh lgtoclnt-7.4-1.x86.rpm
 



Storage node installation:

 

On the computers designated as storage nodes, install the NetWorker client and storage node software. The storage node package must be installed on the NetWorker server, regardless of whether separate systems are used as designated storage nodes.

 

To install the storage node software:

 

1.      Change to the directory containing the NetWorker software.

 

2.      Type this command to install the client and storage node packages:

 

• For Itanium:

rpm -ivh lgtoclnt-7.4-1.ia64.rpm lgtonode-7.4-1.ia64.rpm

 

• For Intel for x86:

rpm -ivh lgtoclnt-7.4-1.x86.rpm lgtonode-7.4-1.x86.rpm

To install the Server software:

 

On the computer designated as the NetWorker server, install all the NetWorker software packages in the following order:

 

Client,

Storage node,

Server.

 

The NetWorker License Manager software can be installed at any point in this sequence after the client package is installed.

1.      Change to the directory containing the NetWorker software.

 

2.      Type the appropriate commands to install the client, storage node, server, and NetWorker

License Manager software:

 

For Itanium:

 

rpm -ivh   lgtoclnt-7.4-1.ia64.rpm

rpm -ivh   lgtonode-7.4-1.ia64.rpm

rpm –ivh  lgtoserv-7.4-1.ia64.rpm

rpm -ivh   lgtolicm-7.4-1.ia64.rpm

 

For Intel for x86:

 

rpm -ivh lgtoclnt-7.4-1.x86.rpm

rpm -ivh lgtonode-7.4-1.x86.rpm

rpm -ivh lgtoserv-7.4-1.x86.rpm

rpm -ivh lgtolicm-7.4-1.x86.rpm

 

Note: Installing the NetWorker License Manager software is optional. It can be installed any time after the client software.

 

The NetWorker software installation modifies these system files during installation. To keep a copy of the current configuration, save the following original files:

(cp –p “below file name”   “New name”)

 

/etc/rpc

/etc/syslog.conf

/etc/ld.so.conf

 

The following files are added during the installation process:

 

/etc/init.d/networker

/etc/init.d/rc3.d/S95networker

/etc/init.d/rc5.d/S95networker

/etc/init.d/rc0.d/K05networker

Console software:

To manage the NetWorker server, install the NetWorker Console and client software on one machine in the datazone.

 

Note: NetWorker Management Console server software is supported on the Linux x 86  

platforms. The NetWorker Management Console server software is not supported on the Linux Itanium platform.

 

To install NetWorker software on the computer that is designated as the NetWorker Console

 

Server:

 

1.      Download and install JRE version 1.5.0_11.

 

         Remove the following Mozilla file from /usr/lib/mozilla-1.7.12/plugins.

libnullplugin.so

 

         Create a symbolic link within the Mozilla plugins directory to the libjavaplugin_oji.so

 

         file. For example:

ln -s /usr/local/jre1.5.0_11/plugin/i386/ns7/libjavaplugin_oji.so

 

2.      If the NetWorker software has been downloaded from the web:

 

         Type the following command to verify that execute permissions are applied to the JRE

 

         File. For example: chmod +x j2re-1_5_0_11linux-i586.bin

 

         Change to the directory where the JRE is to be installed.

 

         Run this executable: j2re-1_5_0_09-linux-i586.bin

 

          Accept the Java licensing agreement.

 

3.      Change to the directory containing the NetWorker software.

 

4.      Type this command to install the NetWorker client software, if not already installed:

rpm -ivh lgtoclnt-7.4-1.x86.rpm

 

5.      Start the NetWorker daemons, if not already started.

 

6.     To install the NetWorker Console software, type: rpm -ivh lgtonmc-7.4-1.x86.rpm

By default, the software is installed in /opt.

7.     Run this configuration script: /opt/lgtonmc/bin/nmc_config

 

8.      Follow the prompts to install the software. For example:

 

 

         For the web server port number, use the default IP port number (9000) or use a custom

 

         IP port number. Valid IP port numbers are between 1024 and 49151.

 

         For the NetWorker Console server, use the default IP port number (9001) or use a

custom IP port number. Valid IP port numbers are between 1024 and 49151.

 

Note: Do not use IP port numbers that are already in use. Port 2638 is reserved by the NetWorker Console software by using the Tabular Data Stream (TDS) protocol to communicate with the database. Port 9002 is the preferred port for EMC Backup Advisor product.

 

9.      Start the NetWorker Console daemons if not already started:

/etc/init.d/gst start

 

         The NetWorker Console daemons include the following:

 

         gstd

         dbsrv9

         gsttclsh

 

10.  For Red Hat Enterprise Server 4 only, from the client machine with more than one JRE installed, you may want to reconfigure the usage of the JRE as follows:

 

·         Run the Java Web Start application named javaws. This application is located in the

same directory where the JRE 1.5.0_06 software was installed.

 

·         From the Java Application Runtime Settings window:

 

·         Check the JRE 1.4.2_11 version software. This forces the Java Web Start application to use JRE version 1.4.2_11 to run applications.

 

·         Uncheck the other versions of the JRE software, for example JRE version 1.5.0_06.

 

·         Start the NetWorker Console server. The Console launch page appears.

·         Specify that you want to run the Console using the Java Web Start version 1.5 software. You must type the path to the Java Web Start executable.

 

Note: There are two libraries, libXp.so.6 and libXm.so.3 (open motiff lib), that are required on Red Hat Enterprise Linux 4 and 5 to launch the nwrecover program. By default, these libraries are not part of the operating system.

 

 

11.  If the Console server and the NetWorker server are installed on separate host, you must add the Console administrator to the administrator lists of the monitored NetWorker server. This enables the Console administrator to administer and monitor the target NetWorker server.

 

On the NetWorker server:

 

·         Specify the process owner of the Console daemon process depending on which host contains the Console server:

 

– If on a Microsoft Windows host, type:

nsraddadmin -u "user=SYSTEM, host=console_host"

 

– If on a AIX, HP-UX, Linux or Solaris only host, type:

nsraddadmin -u "user=root, host=console_host"

 

·         Specify the Console administrator user:

 

nsraddadmin -u "user=administrator, host=console_host"

 

The NetWorker daemons must be started after the installation procedure:

 

1. Type this command to start the NetWorker daemons:

·         /etc/init.d/networker start

 

2. Type this command to determine if the NetWorker daemons are started:

·         ps -ef | grep nsr

 


NetWorker Client Push

Today we are going through, how to use Networker client push features Use the software distribution feature, Client Push, to update the N...