Vembu NetworkBackup v3.1.3 GA - Release Notes

Transcription

1 Vembu NetworkBackup v3.1.3 GA - Release Notes VEMBU TECHNOLOGIES

2 Vembu NetworkBackup v3.1.3 GA - Release Notes With enhanced features and fixes boosting stability and performance, Vembu NetworkBackup v3.1.3 is now available for production environment. Vembu NetworkBackup is now getting an all new transformation of being a suite. Get started to protect your Exchange Databases, MSSQL Databases, Active Directory, SharePoint, Outlook and MySQL database with Vembu NetworkBackup v New Features Seed backup migration: A key feature that let users to have their initial full backup stored in a local machine and transferred to servers via transfer medium(such as: HDD/External HDD/USB) instead transferring over WAN. This saves huge bandwidth data and consumes less time in case of large data transfer. System State backup: System State backup will backup the below components System Files COM+ Class Registration Database SYSVOL Active Directory Cluster Quorum Certificate Services Registry Internet Information Services Event Logs Windows Internet Name Service Dynamic Host Configuration Protocol Terminal Server Licensing Backup Window Setting: This feature used to stop or halt the running backup during particular hours. You need to configure start time and end time for the same in backup window setting page. Using this feature we can stop backup scheduling during peak hour. 1

3 Bandwidth throttling Setting: This feature enables the user to limit the bandwidth used by the backup process from the client machine. The client bandwidth throttling settings will be applied to each backup schedule configured in that client machine Other features in Vembu NetworkBackup Microsoft Exchange Server Backup: Vembu NetworkBackup supports backup of Microsoft Exchange servers using Exchange Server Plugin. Microsoft Exchange Server Plugin is an efficient way of backing up Microsoft Exchange servers. The Microsoft Exchange Server Plugin backup uses the VSS API [Volume Shadow Copy Services] for all Microsoft Exchange Server versions. Vembu NetworkBackup allows direct upload without dumping the data locally. Microsoft Exchange Mailbox Backup: Vembu NetworkBackup Exchange Mailbox Plugin backs up users' mailboxes. It can backup at a folder level. You can backup all the data of a particular user (mailbox) or you can backup just a folder (like for example the inbox of an user) or you could backup a sub-folder (like for example, a sub-folder in the inbox). Microsoft SQL Server Backup: Vembu NetworkBackup supports backup of Microsoft SQL servers using SQL Server Plugin. SQL Server Plugin is a flexible and efficient option while backing up Microsoft SQL servers. Vembu NetworkBackup's SQL Server plugin uses VDI API to backup database(s) and then uploads the locally dumped file to the backup server. Microsoft SharePoint Backup: Vembu NetworkBackup supports a site-collection level backup of Microsoft SharePoint Servers. Vembu NetworkBackup uses internal SharePoint dump 2

4 utility(stsadm.exe, offering a full fidelity backup) to dump the SharePoint site-collection(s) and then uploads the locally dumped file(s) to the backup server. During a full backup, the entire site-collection(s) is dumped locally and then the dumped file is transferred to the backup server. And during an incremental backup, the entire site-collection(s) is dumped locally and only the modified content since the previous full backup is transferred to the backup server. Microsoft Outlook Backup: Vembu NetworkBackup's Microsoft Outlook Plugin backs up s configured in the Outlook profile. All the s and rules at folder level are backed up with this plugin Vembu NetworkBackup should be running in the machine where Microsoft Outlook is installed to create Microsoft Outlook backups. MySQL Database Backups: Vembu NetworkBackup supports backup MySQL database(s). File Backup: Vembu NetworkBackup supports file backup on all flavors of Windows machines. Also, supports pre-configured folders, Such as, Browsers and Registry. VembuHIVE : VembuHIVETM is our proprietary, patent-pending technology for next-generation data backup, recovery, sharing, and collaboration. One of the key components of this technology is the Vembu HIVE File System (VHFS) - a file system residing over native file systems with built-in version control, security, encryption, and error correction. The inherent flexibility that allows VHFS to host any file system is the key to its ability to seamlessly support a wide range of complex restore use-cases in Vembu NetworkBackup. 3

5 Offsite Copy to your Data Centers: VembuBDR allows you to store a redundant copy of your backup data in a data center of your choice with security measures of your personal preference. In the event of On-premise server crash or onsite disaster, Offsite Copy option allows instant data recovery in Offsite Servers. System Requirements: The table below gives the minimum and recommended for the Vembu NetworkBackup v3.1.3 client and VembuBDR v3.1.3 server. OS VembuBDR v3.1.3 Backup Server/Offside DR. Windows Server 2012 R2 Windows Server 2008 R2 Windows Server 2012 Ubuntu LTS Ubuntu LTS Vembu NetworkBackup v3.1.3 Client Supported Applications for backup Microsoft Exchange Server 2013, 2010, 2007, 2003 Microsoft Exchange Server DAG 2013, 2010 SQL Server 2012, 2008, 2005 Microsoft SharePoint Server 2013, 2010, 2007, 2003 MySQL 5.0 and later Microsoft Outlook 2013, 2010, 2007 Supported Servers for backup Windows Server 2012 R2, 2012 Windows Server 2008 R2, 2008 SP2 and later Windows Server 2003 SP2 and later Windows SBS 2011, 2008, 2003 RedHat Enterprise Linux 5 and later 4

6 Debian Linux 5.0 and later CentOS 5.2 and later CloudLinux 5.10 and later Fedora11 and later Ubuntu and later Gentoo Supported Desktops / Laptops for backup Windows 8, 7, XP, Vista Mac OS X 10.5 and later for Intel PC s Architecture 64 bit only Memory 8GB minimum ( recommended :16GB) 64 bit and 32 bit 1GB minimum (4GB recommended) CPU Meta Data Storage x64 architecture with 4 core Xeon (recommended : 8 core dual processor) 10% of the planned total backup size. 2 core processor - Network Card 1 Gbps - Installation Instructions Download Vembu BDR Backup Server,Vembu NetworkBackup client and Vembu OffsiteDR Server installers from the following URL: Vembu BDR Backup server- Vembu Network Client, Vembu OffsiteDR server- 5

7 Limitations File Backup 1) The Files/Folders tree in this page is based on Java Script. So when a folder has 1000s of files, then the java script takes time to load the tree. Please be patient 2) File/folder filters will not work for unicode files/folders in mapped network drives. Microsoft Exchange Server Backup 1) A Storage Group configured for backup in a backup schedule cannot be configured in a second backup schedule. If required, the first schedule has to be deleted first and thereafter configured in the second backup schedule. 2) Every time a new Database is added under a Storage Group of the Exchange Server, then before running a differential or incremental backup, "Additional Full Backup" should be configured to run through the "Edit Exchange Server Backup" configuration. 3) When you try to restore an Exchange Database's full backup which was empty during its first full backup, then restore operation will fail. Hence you should ensure that Exchange Database is not empty when a full backup is scheduled. Microsoft Exchange Mailbox Backup 1) It is recommended that only critical mailboxes be configured for backup using the Vembu NetworkBackup Exchange Mailbox Backup. Backing up all the mail boxes individually takes much longer time than backing up the Entire database due to limitations of the MAPI protocol. 2) Local temporary dump location configured for Exchange Server backup should not contain special characters like single quote('), double quote("), 6

8 forward slash(/), backward slash(\), question(?), colon(:), asterisk(*), lesser than(<), greater than(>), pipe( ) and plus(+). 3) Please ensure that the dump location configured for the backup schedule has enough space and has valid read and write permissions to accommodate the users mailbox dump data. Also, the dump location full path should be less than 256 characters. 4) If an Exchange Mailbox name(user name) contains forward slash(/) or reverse slash(\), that mailbox might not be backed up. You will need to change the full name of that mailbox without the slash characters to get them backed up. 5) If any special character is present in any folder name (present under a user), that character will be replaced with another set of valid characters while creating the dump file. Microsoft SQL Backup 1) If locally dumped SQL Server database(s) backup data is deleted manually while backup is in progress, then Vembu NetworkBackup will not have the information about the manually deleted file in client machine backup report and in server backup report. 2) Local Dump path configured for SQL Server database(s) backup is not recommended to have special characters like single quote('), double quote("), forward slash(/), backward slash(\), question(?), colon(:), asterisk(*), lesser than(<), greater than(>), pipe( ) and plus(+). 3) Please ensure that the dump location configured for the backup schedule has enough space and has valid read and write permission to accommodate the SQL Server database dump data. Also, the dump location (full path) should be less than 256 characters. 4) If Vembu NetworkBackup is killed while SQL Server database(s) backup schedule configured with multiple database(s) dump process is active, then in the next schedule locally dumped files for the database will be transferred to backup server and dump process for the remaining database(s) will be processed in the next schedule. 5) If SQL Server database(s) backup schedule is suspended while local dump is in progress, then Vembu NetworkBackup will suspend the backup after completing the current MS SQL database dump process. On resuming the same backup schedule, the dump process will not occur in the next schedule; 7

9 instead, the locally dumped files will be transferred to server and an error message will be reported in backup report. 6) In multiple databases backup, if a database does not support Differential/Transaction Log backups, then that Differential/Transaction Log backup will be skipped for that database and the error message will be reported in backup report. 7) Number of differential backups count should be greater than or equal to 2. 8) If the local dump location is configured as a FAT32 disk partition, then the local dump file size should not exceed 4 GB as the FAT32 file system cannot hold file size more than 4 GB. In this case, Vembu NetworkBackup cannot dump the data files and the backup schedule will fail. Microsoft SharePoint 1) For WSS2.0/SPS2003, only the sites added from 'SharePoint Settings' page will be listed in 'Add SharePoint Site Backup' page. 2) Though the whole SharePoint Server or a whole portal site is selected for backup, only a site-collection level of backup will be done. Hence, to restore all the site-collections under a portal site, you need to restore the site-collections under that portal site one by one using STSADM.EXE. 3) Restoring default site-collections in WSS2.0/SPS2003 is not permitted. This attempt is strictly not recommended for WSS2.0/SPS ) A site-collection whose total size exceeds 15 GB cannot be backed up as this is being a limitation with STSADM.EXE [which Vembu NetworkBackup uses] itself. However, in such cases, you can use Vembu NetworkBackup's SQL Server backup feature for backing up the SQL databases being used by the SharePoint Server. 5) Vembu NetworkBackup should be run with Administrator privileges to list and backup SharePoint sites as STSADM.EXE can be run only with Administrator permissions. 6) If the dump path of the SharePoint backup exceeds 255 characters, dump process will fail. Hence, make sure, you have entered a shorter dump path to enable the dump to complete successfully. 7) Restoring SharePoint 'Central Administration' may not bring the original Central Administration's whole UI and its functionalities. 8

10 Other Limitations 1. If any special character is present in any folder name (present under a user), that character will be replaced with another set of valid characters while creating the dump file. 2. The feature to resume a restore from where it left off is supported only at a file level and not at a block level. That is, if a restore failed/aborted while transferring a large file, the restore job, when it resumes, will restore that file again from the beginning. 3. The tree display in the Vembu NetworkBackup Web Console will take a long time to load if a directory contains 1000s of files/directories under it. 4. Aborting a continuous backup from the server side will only make the client begin the next schedule, making the backup start again. 5. Vembu NetworkBackup does not allow restoring the selected mailbox to an alternate Exchange Server. If needed,.pst files can be restored to alternate Exchange Server manually after restoring the files to local disk from backup server. 6. While restoring the complete contents of the selected folder to the original mailbox folder, the existing folder contents will not be deleted prior to performing the restore and restore process will append all s to the folders. It may result in duplicate items within the original folder. 7. Search and restoring individual mails is not supported, however restoring up to mailbox folders is supported using Vembu NetworkBackup Exchange Mailbox plugin. 8. If you have configured Clustered Exchange Server backups, then Exchange Server name cannot be edited from the Exchange Server configuration page. If you would like to backup a different Exchange Server, then you need to delete the Exchange Server backups that have already been created. Technical Support For feedback, comments or issues, please call us: For US, Canada customers: For UK customers: (Or) at vembu-support@vembu.com 9