Results 1 to 4 of 4

Thread: ZRM for MySQL 2.1 released

  1. #1

    Default ZRM for MySQL 2.1 released

    Zmanda Recovery Manager (ZRM) for MySQL version 2.1, a robust and
    intelligent solution for backup and recovery of MySQL databases is now
    available.

    Significant feature is the support for storage and filesystem snapshots
    as backup. This release also supports MySQL server 5.1 GA.

    ZRM for MySQL source packages and binary packages for Linux and
    Solaris are available. Whitepaper to install and configure ZRM 2.1 is
    available at Zmanda network ([url]http://network.zmanda.com[/url]).

    Downloads: [url]http://www.zmanda.com/download-zrm.php[/url]
    Documentation: [url]http://mysqlbackup.zmanda.com/index.php/Zmanda_Recovery_Manager_for_MySQL_Users_Manual[/url]

    Ask questions in this sub-forum.

    Thanks,
    Paddy

  2. #2

    Default

    Significant feature is the support for storage and filesystem snapshots
    as backup. This release also supports MySQL server 5.1 GA.
    What does this feature means exactly? backups using snapshots was aviable alredy in 2.0...

    from releas anounce:
    Converting storage snapshots into regular backups
    I didn find any detailed info about that... What is it doing, how can I use it ?

  3. #3

    Default

    Quote Originally Posted by venoosek View Post
    Significant feature is the support for storage and filesystem snapshots
    as backup. This release also supports MySQL server 5.1 GA.
    What does this feature means exactly? backups using snapshots was aviable alredy in 2.0...

    from releas anounce:
    Converting storage snapshots into regular backups
    I didn find any detailed info about that... What is it doing, how can I use it ?
    This talks about backup types on the basis of, where backup destination directory is. If backup destination is snapshot, then called as “snapshot as a backup”. If backup destination is normal file system directory then it is “Regular backup”.

    Regular backup: In this, the backup process copies important data at a different location.
    Hence normal backups will do following thing:
    1. Take a snapshot.
    2. Mount a snapshot.
    3. Copy required data from mounted snapshot.
    4. After copy, delete a snapshot.
    In some cases above mentioned process might be time consuming, disk space consuming, if backup data is large, and it also generates lot of disk IO, to avoid this, we have a feature called “snapshot as a backup”.

    snapshot as a backup: Will just keep snapshot as it is, will not copy data to file system directory and will use snapshot during restore. So this will save time, disk IO and disk space.
    Hence snapshot as a backup will do following thing:
    1. Take a snapshot.
    2. Keep snapshot in mounted state.
    Then restore process will be,
    1. Mount a snapshot (if snapshot has been un-mounted) .
    2. Restore a backup.

    copy-converted backup: If we want to copy snapshot based backup data to normal file system directory, we just convert snapshot based backup to normal backup to preserve a backed up data. Once copy has been done, snapshot gets deleted.

  4. #4

    Default

    Hi all,
    Can any one say from where i can download MySQL-zrm-enterprise-socket-server-2.1.xx.rpm file.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •