Sun Microsystems and Zmanda to Deliver Comprehensive Database Backup & Recovery Solutions for MySQL Enterprise Customers

March 22, 2008 at 6:33 am (Java)

Enterprise-Wide MySQL Data Protection via Zmanda Recovery Manager (ZRM) to be Available from Sun Worldwide

SANTA CLARA, CA SUNNYVALE, CA March 18, 2008 Sun Microsystems, Inc. (NASDAQ: JAVA) and Zmanda, the open source leader in backup and recovery software, today announced they are partnering to deliver a comprehensive, global data backup and recovery solution for MySQL Enterprise subscribers. A 30-day trial of Zmanda Recovery Manager Enterprise Edition — the first open-source backup and recovery solution designed specifically for MySQL databases — is available now at http://www.mysql.com/zrm. Starting April 1, MySQL Enterprise customers will be able to purchase ZRM for MySQL directly from Sun worldwide. Zmanda and Sun have also agreed to joint-selling and co-marketing activities in support of MySQL, the world’s most popular open source database software.

“Protecting corporate data through effective backup and recovery is one of the most crucial tasks for a database administrator, and it can be a complex undertaking — especially for today’s large Web-scale applications,” said Zack Urlocker, VP of products, Sun Microsystems database group. “MySQL users have told us that global backup and recovery is very important to them, and we are thrilled that we can now offer ZRM for MySQL as an easy-to-use solution for protecting all of their MySQL data.”

“MySQL customers now have easy access to an enterprise-class backup and recovery solution designed specifically for and tightly integrated with MySQL Enterprise,” said Chander Kant, Zmanda CEO. “Through its graphical interface, ZRM for MySQL simplifies the work of a DBA, delivering comprehensive backup functionality and unique precision recovery capabilities. With ZRM, DBAs get added peace of mind and confidence when using MySQL in mission-critical environments.”

Zmanda’s ZRM for MySQL is an open source, enterprise-class backup and recovery solution for MySQL and MySQL Cluster databases. ZRM for MySQL meets the requirements of the MySQL DBA with features such as:

  • Zmanda Management Console - a set of powerful Web-based tools that lets DBAs control backup and recovery across all MySQL servers. Designed to dramatically simplify the complex process of MySQL database backup and recovery, the Zmanda Management Console has an intuitive graphical user interface and automated backup scheduler.
  • Point-in-Time recovery - ZRM for MySQL can recover a database easily to any point in time.
  • MySQL storage engine optimization - ZRM for MySQL can detect the specific storage engine being used, and then implements a backup process that is optimized for that storage engine.
  • Local and remote configuration support - ZRM for MySQL can be implemented on the database server or can manage backups of the database server from a remote system.
  • Visual log explorer - ZRM provides a powerful graphical MySQL log analyzer that enables DBAs to visually pinpoint an unwanted event or action and activate precision recovery, along with ongoing security analysis and performance audits.

The latest version of ZRM for MySQL, version 2.1, includes native support for Solaris 10 Operating Systems and Linux, and a unified global management capability designed for geographically dispersed MySQL instances. ZRM 2.1 also offers a comprehensive plug-in architecture for leading snapshot technologies provided by Solaris ZFS, Linux LVM, Microsoft Windows VSS, NetApp Data ONTAP, and Veritas VxFS. Snapshots enable DBAs to create even quicker and more consistent backup images of live MySQL databases.

“ZRM for MySQL has helped simplify my day-to-day workload as a DBA and gives me the confidence that our data storage is securely backed up,” said Joseph Sandoval, senior system administrator at Jigsaw Data Corporation. “The new MySQL relationship between Sun and Zmanda will give more MySQL customers the opportunity to protect their data using the proven, enterprise-class backup software from Zmanda.”

For more information about the new ZRM for MySQL offering, please go to http://www.mysql.com/zrm.

About Sun’s MySQL Portfolio

The MySQL product portfolio is the most popular open source database software in the world. Many of the world’s largest and fastest-growing organizations use MySQL to save time and money powering their high-volume Web sites, critical business systems, and packaged software. At http://www.mysql.com, Sun provides corporate users with commercial subscriptions and services, and actively supports the large MySQL open source developer community.

About Zmanda

Zmanda was founded in 2005 to bring the benefits of open source to enterprise backup and recovery. The company offers the world’s leading open source backup products and services, including Amanda Enterprise and Zmanda Recovery Manager (ZRM) for MySQL. Amanda Enterprise is a network backup and recovery solution based on Amanda, the world’s most popular open source data backup and recovery software with more than 1/2 million active installations worldwide. Amanda Enterprise enables the backup and recovery of business critical data associated with servers, workstations, desktops, databases and mission-critical applications across the entire network. Businesses using Amanda Enterprise can backup data to tapes, disks, optical devices and Amazon’s Simple Storage Service (S3).

ZRM for MySQL is an advanced and comprehensive backup solution for the MySQL database with precision recovery capability to any particular transaction or point in time. Today, businesses in 23 countries trust Zmanda to protect their corporate data. The company’s headquarters are located in Sunnyvale, California. For more information about Zmanda, please go to http://www.zmanda.com.

Comments

Tomcat Monitoring — Take Control of Tomcat Management

March 22, 2008 at 6:27 am (Java)

Monitor Tomcat servers in your network using Applications Manager - It helps you in monitoring performance, availability, and usage statistics of Tomcat Servers. Tomcat Monitoring provides detailed information about the Tomcat server and every web application deployed in it.

Applications Manager automatically diagnoses, notifies, and corrects performance and availability problems not only with Tomcat Servers, but also with the servers and applications in the entire IT infrastructure.

Web Transaction Statistics

The Web Transaction Analyzer that comes with ManageEngine Applications Manager allows you to view Java method level breakup of response times. It enables end to end Web Transaction monitoring, from URL to SQL queries of a web application. Application Admins can easily troubleshoot problem areas by obtaining the slow URLs and take a look at the trace (method level) all the way to the SQL query. 

Performance monitoring of Tomcat also involves delivering comprehensive fault management and proactive alert notifications, checking for impending problems, triggering appropriate actions, and gathering performance data for planning, analysis, and reporting.

Applications Manager Tomcat Performance monitoring gives the following metrics:

  • Availability
  • Response Time Details
  • Memory Usage
  • Thread Details
  • Response Summary
  • Application Summary and Details
  • Requests Per Minute for the Tomcat Server
  • Per JSP level Requests per Minute and Response Time

Tomcat Management Capabilities

  • Out-of-the-box management of Tomcat availability and performance - checks if it is running and executing requests.
  • Monitoring Tomcat over SSL is supported.
  • Monitors performance statistics such as JVM memory usage, user sessions, etc. Alerts can be configured for these parameters.
  • Based on the thresholds configured, notifications and alerts are generated. Actions are executed automatically based on configurations.
  • Performance graphs and reports are available instantly. Grouping of reports, customized reports, and graphs based on date is available.

Comments

Back to java

March 22, 2008 at 6:19 am (My Personal Info)

After about 6 month I again back to JAVA from DOTNET.

I feel free now .

Comments

Change the “Sales Message Goes Here” or “Tagline Here” text in zen cart?

October 3, 2007 at 3:37 am (LPAM)

To change the “Sales Message Goes Here” or “Tagline Here” text to say what you want open the includes/languages/english/header.php file in your text editor. Find the following line of code:
define(’HEADER_SALES_TEXT’, ‘Tagline Here’);
Replace the tagline text with your own text, making sure that the single quote marks are not left out.
Save the edited file to includes/languages/english/custom/header.php and upload it to your server.
NB: By default the text “Sales Message Goes Here” is located in includes/languages/english/classic/header.php
define(’HEADER_SALES_TEXT’, ‘Sales Message Goes Here’);

Comments

Introduction to the Struts Web Framework

September 21, 2007 at 4:16 am (Java)

This document takes you through the basics of using NetBeans IDE to develop web applications that make use of the Struts framework. The Struts framework enables you to create maintainable, extensible, and flexible web applications based on standard technologies, such as JSP pages, resource bundles, and XML.

I started from this page…….
http://www.netbeans.org/kb/50/quickstart-webapps-struts.html

and hope soon as a experiment, i can give a new look of my personal website by struts framework.

Comments

NetBeans IDE Tutorial for Accessing Data with a Struts Data Source

September 21, 2007 at 4:09 am (Java)

From the last week I started j2ee struts study. I got a great help from the netbeans website.

here is the link of the tutorial:
http://www.netbeans.org/kb/50/tutorial-webapps-struts.html

Comments

Setting up phpMyAdmin 2.10 on Apache 2.2, FreeBSD 6.2

August 17, 2007 at 10:08 am (FreeBSD)

I. Download and Extract 

root@freebsd:/tmp# cd /tmp
root@freebsd:/tmp#
 fetch http://superb-west.dl.sourceforge.net/sourceforge/
phpmyadmin/phpMyAdmin-2.10.0.2-all-languages-utf-8-only.tar.gz
root@freebsd:/tmp#
 tar zxvf phpMyAdmin-2.10.0.2-all-languages-utf-8-only.tar.gz
 

II. Move it to the Right Place

 
root@freebsd:/tmp#
  cd phpMyAdmin-2.10.0.2-all-languages-utf-8-only
root@freebsd:
/tmp/phpMyAdmin-2.10.0.2-all-languages-utf-8-only#
 mv * /usr/local/www/phpmyadmin.aminonline.com/
 

III. Generate Configuration

 
root@freebsd:/tmp/phpMyAdmin-2.10.0.2-all-languages-utf-8-only# 
cd  /usr/local/www/phpmyadmin.aminonline.com/
root@freebsd:/usr/local/www/phpmyadmin.aminonline.com#
 mkdir config
root@freebsd:/usr/local/www/phpmyadmin.aminonline.com#
 chmod o+rw config
 

Now lets go to https://phpmyadmin.aminonline.com/scripts/
setup.php and generating the configuration file.
Remember to click save button on the website to save your
configuration, which is what will generate the configuration
 file we need. This is what I set mine up like:

phpmyadmin00.gif

phpmyadmin01.gif

IV. Apply the Configuration

Copy the configuration file that you generated using

the web interface and remove the config directory for security.

 
root@freebsd:/usr/local/www/phpmyadmin.aminonline.com#
 mv config/config.inc.php .
root@freebsd:/usr/local/www/phpmyadmin.aminonline.com#
  chmod o-rw config.inc.php
root@freebsd:/usr/local/www/phpmyadmin.aminonline.com#
  chown -R www:wheel *
root@freebsd:/usr/local/www/phpmyadmin.aminonline.com#
  rm -R config/
 

We should already have the old .htaccess we created before for our phpmyadmin.aminonline.com and so now if we try to go to the https://phpmyadmin.aminonline.com/ we should be prompted for the username and password. Then you should see the phpmyadmin website.   

Comments

Adding HTTPS support to Apache 2.2 on FreeBSD 6.2

August 17, 2007 at 9:53 am (FreeBSD)

Set Defaults for openssl

 
amin@freebsd:/home/amin> su
     Password:
root@freebsd:/home/mikey# vi /etc/ssl/openssl.cnf
     dir = /root/sslCA  # Where everything is kept
     default_days= 3650 # how long to certify for
     countryName_default= CA
     stateOrProvinceName_default = ONTARIO
     0.organizationName_default = sao

II. Create a Script to Generate the
Certificate of Authority

root@freebsd:/home/mikey# cd ~
root@freebsd:/root# vi createCA.sh
     #!/bin/sh
     ##############################################
     # CA Creator
     # http://www.freebsdmadeeasy.com/
     #
     # This Script creates a certificate of authority
     # using OpenSSL. It was written and tested on
     # FreeBSD 6.1-RELEASE  Use at your own risk
     #
     #
     ##############################################
 
     echo “Setting up the directories”
     mkdir ~/sslCA
     echo “sslCA”
     mkdir ~/sslCA/certs
     echo “sslCA/certs”
     mkdir ~/sslCA/private
     echo “sslCA/private”
     mkdir ~/sslCA/newcerts
     echo “sslCA/newcerts”
     cd ~/sslCA
     echo 1000 > serial
     touch index.txt
 
     echo “Setting the permission to 700 on sslCA”
     chmod -R 700 ~/sslCA
 
     echo “Creating the CA”
     echo “Use a strong password and keep it safe!”
     openssl req -new -x509 -days 3650 -extensions v3_ca 
-keyout private/cakey.pem -out cacert.pem -config 
/etc/ssl/openssl.cnf     

 
     more ~/sslCA/cacert.pem
     more ~/sslCA/private/cakey.pem
 
     echo “sslCA/cacert.pem”
     echo “sslCA/private/cakey.pem”
 
     echo “All Done!”
 

III. Create the Certificate of Authority

root@freebsd:/root# sh createCA.sh
     Setting up the directories
     sslCA
     sslCA/certs
     sslCA/private
     sslCA/newcerts
     Setting the permission to 700 on sslCA
     Creating the CA
     Use a strong password and keep it safe!
     Generating a 1024 bit RSA private key
     …..++++++
     …….++++++
     writing new private key to ‘private/cakey.pem’
     Enter PEM pass phrase: 
…………………………………………………………………………
sslCA/cacert.pem
     sslCA/private/cakey.pem
     All Done!

For the next step, enter *.aminonline.com for
the Common Name, to also use this certificate
for the subdomains. Leave challenge password blank,
 or it will ask for it every time the Apache restarts.

 
9:50 root@freebsd:/root# cd ~root/sslCA
9:50 root@freebsd:/root/sslCA#
  openssl req -new -nodes -out NoobTechDev-req.pem
 -keyout private/NoobTechDev-key.pem –config
  /etc/ssl/openssl.cnf
 Generating a 1024 bit RSA private key
     ……………++++++
     ….++++++
 writing new private key to ‘private/NoobTechDev-key.pem’
     -----
 You are about to be asked to enter information that will
 be incorporated into your certificate request.
What you are about to enter is what is called a
 Distinguished Name or a DN.There are quite a few
 fields but you can leave some blank
For some fields there will be a default value,
If you enter ‘.’, the field will be left blank.
     -----
Country Name (2 letter code) [CA]:
State or Province Name (full name) [ONTARIO]:
Locality Name (eg, city) []:
Organization Name (eg, company) [NoobTech]:
Organizational Unit Name (eg, section) []:
Common Name (eg, YOUR name) []:*.aminonline.com
     Email Address []:
 
 Please enter the following ‘extra’ attributes
 to be sent with your certificate request
 A challenge password []:
 Leave this blank, or it will ask for password
 every time you start up apache
An optional company name []:
root@freebsd:/root/sslCA#
 openssl ca -days 3650 -config /etc/ssl/openssl.cnf
 -out NoobTechDev-cert.pem -infiles NoobTechDev-req.pem
 Using configuration from /etc/ssl/openssl.cnf
 Enter pass phrase for /root/sslCA/private/cakey.pem:
 Enter the password you used in the earlier step.
Check that the request matches the signature
Signature ok
Certificate Details:
Serial Number: 4096 (0×1000)
Validity
Not Before: Apr 12 13:58:15 2007 GMT
Not After : Apr  9 13:58:15 2017 GMT
Subject:
countryName               = CA
stateOrProvinceName       = ONTARIO
organizationName          = sao
commonName                = *.aminonline.com
 X509v3 extensions:
 X509v3 Basic Constraints:
   CA:FALSE
   Netscape Comment:
OpenSSL Generated Certificate
X509v3 Subject Key Identifier:
66:28:06:78:DC:91:7E:7B:D1:B1:88:21:41:11:1B:10:74:31:18:AA
X509v3 Authority Key Identifier:
keyid:7A:EC:BB:DF:CF:0A:6B:8A:7B:C1:A0:ED:7D:BC:6F:61:32:EB:C1:74
DirName:/C=CA/ST=ONTARIO/O=NoobTech
serial:D1:CD:8D:62:59:1B:2F:2D
 
certificate is to be certified until Apr
   9 13:58:15 2017 GMT (3650 days)
     Sign the certificate? [y/n]:y
 
1 out of 1 certificate requests certified, commit? [y/n]y
     Write out database with 1 new entries
     Data Base Updated

IV. Configure HTTPS Virtual Hosts with generated CoA

Copy the certificate and key we generated earlier to a
public place for use with apache.
root@freebsd:/root/sslCA# mkdir /etc/ssl/crt
root@freebsd:/root/sslCA# mkdir /etc/ssl/key
root@freebsd:/root/sslCA#
cp ~/sslCA/NoobTechDev-cert.pem /etc/ssl/crt
root@freebsd:/root/sslCA#
cp ~/sslCA/private/NoobTechDev-key.pem /etc/ssl/key

 

Uncomment the following Include line in httpd.conf

root@freebsd:/usr/local/etc/apache22#
 cd /usr/local/etc/apache22
root@freebsd:/usr/local/etc/apache22#
 vi httpd.conf
     # Secure (SSL/TLS) connections
     Include etc/apache22/extra/httpd-ssl.conf

For the next part, I deleted the whole <VirtualHost>
 section and left the rest of the file intact.
 Then I added the following at the end of the file.

root@freebsd:/usr/local/etc/apache22#
  vi extra/httpd-ssl.conf
     # This must be added, or you will get a nice warning,
  when you try to host more then 1
  VirtualHost on the port 443
     # [warn] _default_ VirtualHost overlap on port 443,
# the first has precedence
     NameVirtualHost *:443
 
     <VirtualHost *:443>
 ServerName phpmyadmin.noobtechdev.com
 SSLEngine on
 SSLCertificateFile /etc/ssl/crt/NoobTechDev-cert.pem
 SSLCertificateKeyFile /etc/ssl/key/NoobTechDev-key.pem
 
 DocumentRoot /usr/local/www/phpmyadmin.noobtechdev.com
 CustomLog /usr/local/www/logs/phpmyadmin.noobtechdev.com.
 ssl.access.log combined
  ErrorLog /usr/local/www/logs/phpmyadmin.noobtechdev.com.
 ssl.error.log
  <Directory /usr/local/www/phpmyadmin.noobtechdev.com>
Order Deny,Allow
Allow from all
DirectoryIndex index.php index.html index.htm
      </Directory>
     </VirtualHost>

Now I’m going to create a directory for this new virtual
 host, and create a test page as well for testing purpose.

root@freebsd:/usr/local/etc/apache22#
 mkdir /usr/local/www/phpmyadmin.noobtechdev.com
root@freebsd:/usr/local/etc/apache22#
 echo “Hello World from SLL site” >
 /usr/local/www/phpmyadmin.noobtechdev.com/index.html
18:11 root@freebsd:/usr/local/etc/apache22#
  apachectl restart
 

Now navigate to https://phpmyadmin.noobtechdev.com/
 and you should be asked to accept a certificate from
 an untrusted authority, which is fine,
 because all we need it for is to use encryption.
After you accept the certificate you see a Hello World
from SLL site message.After this you should now have a working Apache22 with
 PHP5 and SSL. Also you should now be able
to create your own virtual hosts. It took me quite a while
 to get all this working together,
mostly because somehow I had Apache13 installed and then
 when I build my PHP5 it built it for
Apache13 and that most the source of my problems.
 But after I discovered that, and deinstalled
the Apache13 and installed Apache22, I started to
 have problems with PHP, not working with it so
I ended up having to deinstall and distclean the php
 port and reinstall that. And since that point
everything went pretty smooth following this tutorial:
http://www.freebsdmadeeasy.com/tutorials/web-server/
install-php-5-for-web-hosting.php
The one thing to note in that I’ve added a
<Directory> section to the VirtualHost.
Without that I kept getting Access Denied errors
 in my logs like so:
“… client denied by server configuration:
 /usr/local/www/ …”
Also when I tried to go to the website I got
 Restricted: Access denied

 
 
 
 

Comments

Installing PHP5 for Apache 2.2 on FreeBSD 6.2

August 17, 2007 at 9:19 am (FreeBSD)

Things to note. Installed minimal FreeBSD 6.2, and MySQL 5.1 and Apache 2.2. Now I will install PHP5 for Apache.

I. Install PHP5

Install the PHP5. If you need to reconfigure the
settings again, you can edit it by typing make config.

root@freebsd:/usr/ports/lang/php5# cd /usr/ports/lang/php5
root@freebsd:/usr/ports/lang/php5# make install
 +--------------------------------------------------+
¦                     Options for php5 5.2.1_3                       ¦
¦ +----------------------------------------------------------------+ ¦
¦  [ ] CLI        Build CLI version                              ¦ ¦
¦  [ ] CGI        Build CGI version                              ¦ ¦
¦  [X] APACHE     Build Apache module                            ¦ ¦
¦  [ ] DEBUG      Enable debug                                   ¦ ¦
¦  [X] SUHOSIN    Enable Suhosin protection system               ¦ ¦
¦  [X] MULTIBYTE  Enable zend multibyte support                  ¦ ¦
¦  [X] IPV6       Enable ipv6 support                            ¦ ¦
¦  [ ] MAILHEAD   Enable mail header patch                       ¦ ¦
¦  [ ] REDIRECT   Enable force-cgi-redirect support (CGI only)   ¦ ¦
¦  [ ] DISCARD    Enable discard-path support (CGI only)         ¦ ¦
¦  [ ] FASTCGI    Enable fastcgi support (CGI only)              ¦ ¦
¦  [ ] PATHINFO   Enable path-info-check support (CGI only)      ¦ ¦
+----------------------------------------------------------------+-¦
¦                       [  OK  ]       Cancel                        ¦
+----------------------------------------------------+
 
root@freebsd:/usr/ports/lang/php5#
cp /usr/local/etc/php.ini-dist /usr/local/etc/php.ini 

II. Configure PHP5 for Apache

Add support for PHP to the Apache.

 
root@freebsd:/usr/local/etc/apache22#
cd /usr/local/etc/apache22
root@freebsd:/usr/local/etc/apache22#
 vi httpd.conf
# This line should have been added by the PHP5 installation,
 #if you had Apache22 installed
 LoadModule php5_module libexec/apache22/libphp5.so
# Then I edited the DirectoryIndex and added index.php
     <IfModule dir_module>
          DirectoryIndex index.php index.html
     </IfModule>
# And also added this to the <IfModule mime_module> section
     AddType application/x-httpd-php .php
     AddType application/x-httpd-php-source .phps

Create a test page.

root@freebsd:/usr/local/etc/apache22#
 echo “<? phpinfo(); ?>” >
 /usr/local/www/www.aminonline.com/test.php
root@freebsd:/usr/local/etc/apache22#
 apachectl configtest
         Syntax OK
root@freebsd:/usr/local/etc/apache22#
 apachectl restart
 

Now I point my browser to http://www.aminonline.com/test.php
and I should see a page showing details of my PHP configuration.
You should see a page similiar to this:

Comments

Installing MySQL Server 5.1 on FreeBSD 6.2

August 17, 2007 at 8:41 am (FreeBSD)

Installing MySQL Server 5.1 on FreeBSD 6.2

I will be installing MySQL Server 5.1 on FreeBSD 6.2 from ports.Log-in as root using the su, switch to the directory and begin the installation.

root@freebsd:/usr/ports/databases/mysql51-server# 
cd /usr/ports/databases/mysql51-server
root@freebsd:/usr/ports/databases/mysql51-server# 
make install
root@freebsd:/usr/ports/databases/mysql51-server#

We need to issue a rehash for the tcsh shell in order to
 reload the commands installed by the port.

root@freebsd:/usr/ports/databases/mysql51-server# 
rehash 

Now we need to do some configuration of the MySQL server.
Set the database to use mysql user account, which will
get created. Copy the default configuration file.

root@freebsd:/usr/ports/databases/mysql51-server#
 mysql_install_db --user=mysql
root@freebsd:/usr/ports/databases/mysql51-server# 
cp /usr/local/share/mysql/my-medium.cnf /var/db/mysql/my.cnf
root@freebsd:/usr/ports/databases/mysql51-server#
 chown mysql:wheel /var/db/mysql/my.cnf

Start the MySQL Daemon

root@freebsd:/usr/local#
 cd /usr/local ; /usr/local/bin/mysqld_safe &

 

Set the password for root user of the MySQL Database.
root@freebsd:/usr/local#
 /usr/local/bin/mysqladmin -u root password ‘xxxxx’
root@freebsd:/usr/local#
 /usr/local/bin/mysqladmin -u root -h freebsd.noobtechdev.com
password ‘xxxxx’
Add MySQL to system startup. Also make it run under
user mysql and only only the local interface 127.0.0.1
 since I will only be accessing it from the same server.

root@freebsd:/usr/local# vi /etc/rc.conf
mysql_enable=”YES”
    mysql_args=”––user=mysql ––bind-address=127.0.0.1″

I’m going to restart my server now to make sure
 that the MySQL starts, and is only bound to 127.0.0.1 

Comments

« Previous entries