Networker integrates with VMWare much like Avamar. It will do guest-based backup with agents installed in the guest VMs for which the VM needs to be powered on. It will also do image-level backup using VADP using a proxy client that takes a snapshot, mounts the snap and backs up the snapshot. This reduces overhead on the ESXi host. Also, like with Avamar, CBT can be used to backup only changed blocks of data in the VMDK files. Individual file restore from VMDK can take place only on NTFS volumes.
Networker integrates with cloud services, both private and public. It will compress and encrypt the data in transit, as well as throttle bandwidth to ensure service level to applications and customers. It will handle backup, recovery, staging and cloning. Clones are infinitely appendable when storing in the cloud.
Networker integrates with DPA, providing expanded monitoring and predictive analysis.
Networker integrates with Avamar, making Avamar to be seen as a storage device. It will then use Avamar's source-based deduplication and the Avamar is referred to as the dedupe node. One advantage over Avamar is that Networker will allow multiple simultaneous backup of the smae client, for instance you can run a file level and database backup at the same time reducing time. All jobs are managed and configured through Networker, and all Networker Modules can be used. One caveat is that Networker will not manage Avamar Replication. That still needs to be configured and managed through the Avamare interface.
When a backup request is sent from Networker to Avamar, the save command spawns the avasm, which in turn spawns the nsravtar. The process then follows the normal Avamar backup routine where it checks the hash file on the storage node, creates a hash cache and compares to new data, etc.
Data Domain can act as an AFTD or FTD, it can be utilized as VTL over Fibre Channel, and it can be used wiht DD Boost. With DD Boost, you oobtain the benefit of central config and management of backup. Replication is also controlled in Networker when integrated with Data Domain. You can install DD Boost on a storage noe, or install it on the client and do client direct backup.
Thursday, November 7, 2013
Networker Module for Microsoft Applications (NMM)
NMM is the application module for all Microsoft applications and databases, including Exchange, MSSQL, Sharepoint, Active Directory DPM and HyperV. It leverages VSS-based backup and recovery, and can also use a proxy client to offload the resource use from the application servers themselves.
The backup process is started per usual with savegrp calling nsrexecd, which then calls nsrsnap, which spawns nsrsnap_vss_save, which calls the Powersnap application. This is where the backup takes place.
Backup types for NMM are "Instant" which means to take a snapshot using VSS, and can be done witho ro without rollover, which means to take it off to tape. It will do non-persistent rollover (no snapshot) and it will do serverless, or proxy client backup.
The recovery types are conventional, which is per normal restore from tape, and Instant, which is a recovery from a VSS snapshot.
Exchange 2007 can do Mailbox Server backup, which grabs the storage groups, mailbox database and transaction logs or individual storage group.
Exchange 2010 or 2010 DAG does the entire Mailbox Server which is all mailbox databases and t-logs or individual databases.
Exchange server will do full or incremental backup.
MSSQL 2005, 2008 and 2012 are supported since version 2.4 and there are two types of backup. VDI, or Virtual Device Integration is more flexible. It will do Full, incremental or differential backup, and recovery includes point-in-time, partial restores, redirected restores to another server.
The VSS backup is full every time and the database must be in simple recovery mode.
Sharepoint is a distributed server system, and NMM will backup Sharepoint 2007 and 2010 farms, content, database, web apps and search services. Only a full backup of Sharepoint can be taken, and individual file or object restore is only possible through 3rd party applications such as Kroll Ontrack.
Hyper-V 2008 uses VSS for backing up the mangaement OS, or parent partition. This backs up the images (VHD) files and is best used for DR only. It is similar to the VADP image-level backup. To get individual file restore you would need to install the agent on the guest VM itself.
The backup process is started per usual with savegrp calling nsrexecd, which then calls nsrsnap, which spawns nsrsnap_vss_save, which calls the Powersnap application. This is where the backup takes place.
Backup types for NMM are "Instant" which means to take a snapshot using VSS, and can be done witho ro without rollover, which means to take it off to tape. It will do non-persistent rollover (no snapshot) and it will do serverless, or proxy client backup.
The recovery types are conventional, which is per normal restore from tape, and Instant, which is a recovery from a VSS snapshot.
Exchange 2007 can do Mailbox Server backup, which grabs the storage groups, mailbox database and transaction logs or individual storage group.
Exchange 2010 or 2010 DAG does the entire Mailbox Server which is all mailbox databases and t-logs or individual databases.
Exchange server will do full or incremental backup.
MSSQL 2005, 2008 and 2012 are supported since version 2.4 and there are two types of backup. VDI, or Virtual Device Integration is more flexible. It will do Full, incremental or differential backup, and recovery includes point-in-time, partial restores, redirected restores to another server.
The VSS backup is full every time and the database must be in simple recovery mode.
Sharepoint is a distributed server system, and NMM will backup Sharepoint 2007 and 2010 farms, content, database, web apps and search services. Only a full backup of Sharepoint can be taken, and individual file or object restore is only possible through 3rd party applications such as Kroll Ontrack.
Hyper-V 2008 uses VSS for backing up the mangaement OS, or parent partition. This backs up the images (VHD) files and is best used for DR only. It is similar to the VADP image-level backup. To get individual file restore you would need to install the agent on the guest VM itself.
Networker Module for Databases and Applications (NMDA)
NMDA is the Networker Module for Databases and Applications. It provides integration with DB2, Informix IDS, Lotus Notes Domino, Oracle, Sybase ASE. It is a single module that supports all those databases, and to simplify licensing replaces the individual modules that were previously available for each of those.
NMDA essentially offers integration into those applications and provides Networker functionality to their backup.
The backup process is like the normal backup, except that the savegrp is called and issues a request to nsrexecd on the client. nsrexecd calls nsrdasv which loads the correct API for the database installed.
DB2 can backup database and tablespace, and its types are Full, Incremental and Incremental Delta.
Lotus Domino backs up the database files, DAOS and individual files. Its types are Full, Incremental and Incremental Delta, and on Windows-installed Lotus servers there is an additional GUI for managing the plugin.
Oracle modules will back up the database, tablespaces and data files, control files and redo files. Its backup types are Full, Incremental 0, Differential 1 and Cumulative Incremental 1.
NMDA essentially offers integration into those applications and provides Networker functionality to their backup.
The backup process is like the normal backup, except that the savegrp is called and issues a request to nsrexecd on the client. nsrexecd calls nsrdasv which loads the correct API for the database installed.
DB2 can backup database and tablespace, and its types are Full, Incremental and Incremental Delta.
Lotus Domino backs up the database files, DAOS and individual files. Its types are Full, Incremental and Incremental Delta, and on Windows-installed Lotus servers there is an additional GUI for managing the plugin.
Oracle modules will back up the database, tablespaces and data files, control files and redo files. Its backup types are Full, Incremental 0, Differential 1 and Cumulative Incremental 1.
Networker Modules Intro
Networker modules are client programs that allow applications to be backed up in a consistent state. There are modules for databases, email servers, enterprise applications and snapshot management. The main advantage of module use is that you can get online backup of application servers in a consistent state. It also allows for 3rd party integration with those applications.
Modules are client software that is loaded on the application server directly, or a proxy client can be used to offload the resource utilization. The proxy client could be on a storage node to allow client direct backup to that node, also.
The backup process is the same as a normal Networker backup, except that a backup API specific to the client called gets loaded and sends data to the save command, which sends the data to the storage node.
Recovery is similar, excpet the recovery command is used to call the API, which then pushes the data back into the application.
Disparate snapshot technologies can all be managed with Networker, both the backup and restore.
Modules are client software that is loaded on the application server directly, or a proxy client can be used to offload the resource utilization. The proxy client could be on a storage node to allow client direct backup to that node, also.
The backup process is the same as a normal Networker backup, except that a backup API specific to the client called gets loaded and sends data to the save command, which sends the data to the storage node.
Recovery is similar, excpet the recovery command is used to call the API, which then pushes the data back into the application.
Disparate snapshot technologies can all be managed with Networker, both the backup and restore.
Networker in a Firewalled Environment
Service ports are where an application is listening for connections. Connection ports are outbound connections to other servers' service ports.
Default service ports for Networker are TCP 7937-9936. They listen for and service backup requests coming from a Networker server. They are randomly chosen by the configured port range by EMC portmapper.
Connection ports are by default set to 0-0, which means use any port available. On version 7.4 and newer, port range is set to 0-0. Upgraded Networker servers that go to 7.4 or newer maintain the settings prior to upgrade to maintain compatibility.
Port ranges can be manually configured. The process daemon nsrexecd will always listen on 7937 and 7938 no matter what the value is set for. 7938 is rpcbind, or portmapper and resides in /nsr/res/nsrladb on each Networker host.
Networker 8 requires the following ports:
These add to 12 for the server. in addition, nsrlcpd requires 1 connection for each jukebox, and 2 for each FTD device connected. AFTD requires the max count settings of all devices.
To configure the port ranges, determine the port count required. User must have update port ranges resources permission. Us nsradmin -p nsrexec to add permissions, or us NMC, nsrports, nsradmin to set port ranges.
NMC SErver requires 3 ports for processes and 2 for SNMP if using DD Boost. There is 1 for the web server, 1 for RPC, and 1 for database calls. By default, 9000 is the default httpd port, 9001 is RPC, and 2368 is the default database port.
For a firewall configuration, the following rules would need to be configured:
Outbound, TCP 7937-X from server to client
Outbound TCP 7937-X from server to storage node
Inbound TCP 7937-X from client to server
Where "X" is equal to the highest port number as determined by adding all necessary processes together
Default service ports for Networker are TCP 7937-9936. They listen for and service backup requests coming from a Networker server. They are randomly chosen by the configured port range by EMC portmapper.
Connection ports are by default set to 0-0, which means use any port available. On version 7.4 and newer, port range is set to 0-0. Upgraded Networker servers that go to 7.4 or newer maintain the settings prior to upgrade to maintain compatibility.
Port ranges can be manually configured. The process daemon nsrexecd will always listen on 7937 and 7938 no matter what the value is set for. 7938 is rpcbind, or portmapper and resides in /nsr/res/nsrladb on each Networker host.
Networker 8 requires the following ports:
These add to 12 for the server. in addition, nsrlcpd requires 1 connection for each jukebox, and 2 for each FTD device connected. AFTD requires the max count settings of all devices.
To configure the port ranges, determine the port count required. User must have update port ranges resources permission. Us nsradmin -p nsrexec to add permissions, or us NMC, nsrports, nsradmin to set port ranges.
NMC SErver requires 3 ports for processes and 2 for SNMP if using DD Boost. There is 1 for the web server, 1 for RPC, and 1 for database calls. By default, 9000 is the default httpd port, 9001 is RPC, and 2368 is the default database port.
For a firewall configuration, the following rules would need to be configured:
Outbound, TCP 7937-X from server to client
Outbound TCP 7937-X from server to storage node
Inbound TCP 7937-X from client to server
Where "X" is equal to the highest port number as determined by adding all necessary processes together
Subscribe to:
Posts (Atom)