System Recovery 2013 Server Edition vs Small Business Edition?
Hi! On our good old Windows XP machines for backup and recovery in our small business we used Symantec's Norton Ghost and Acronis True Image. Now we are switching to Windows 8.1 and will also add a Windows Server 2012 R2 Essentials (the new Microsoft Small Business Server). Because Microsoft's built-in free backup cannot be configured with advanced options and does not seem to be very reliable we are now looking for a new and hopefully better small business (paid) solution. What we actually need is an imaging solution with backup tasks that can be targeted at lokal disks as well as network shares and USB disks attached to the server for offsite rotation. Automatic nightly backups through wake on LAN or BIOS wake up timer are needed, so the backup solution should be also able to turn off the PCs after backup. Unfortunately, it turns out that there are not any reliable solutions out there in 2014! We tested Acronis business products which turned out to have nice features but are very unreliable and unusable in the end. We tested ARCserve which is ok but cannot be configured much, it actually offers only a single backup task and does not have Win 8.1 support, although it claims to be certified for this OS already - they wanted to send me some internal beta patches but we did not accept this. And so finally we came to System Recovery 2013 which was actually not easy to find between all the other solutions on the market, maybe it is the lack of marketing information available... So we finally tested SSR 2013 SP2 on our Win 8.1 desktops and it seems to work fine - better than the other solutions. There are not many changes compared to Norton Ghost but it does its job, can be configured with advanced options and that's what we need. Now the problem with Symantec System Recovery 2013 is that there is too few information on this product and there is nobody to ask. You want to buy a product and there is no info - really annoying! In the key features you read about Win 8.1 / Server 2012 R2 support (and it seems to be available through SP2) but nobody seems to care to update this info in the system requirements on Symantec's website. Does not sound very promising for a business product. The situation is even worse when looking for information about the Server editions of SSR. There is a Server Edition and a Small Business Server Edition. But what is the difference? Can they backup Hyper-V virtual machines? From the host? From the guest? Is Windows Server 2012 R2 Essentials supported in the SBS edition? The Essentials Server is actually Microsoft's new small business server so it should... I requested a callback from Symantec here in Germany but nobody seems to care. It is also still unclear how many licenses I need. In the new Windows Server 2012 R2 Essentials Microsoft allows to install the OS on the physical host + on one free Hyper-V server VM. Is this Hyper-V VM also covered by the SSR Small Business Server Edition license? Do I need any additional agents if I need to backup from the physical server AND from whithin the virtual Hyper-V server (file level recovery is needed)? How much will it finally cost? I don't find any docs especially for the server editions and I don't see any clear Hyper-V licensing statements. Again, very disappointing for a business product. But maybe someone here can provide more info to help us in our decision? Thanks in advance. AnguelSolved2.1KViews3likes16CommentsCompleted with exceptions: system volume information
We have BE 2012 running on Windows 2008 R2 server. We are backing up 5 volumes located on the server. 4 of them are LUNs from P2000 g3 SAS, directly connected via SCSI cable. System seems them as DAS disks. I: LUN1 P: LUN2 L: LUN3 E: LUN4 D: Local volume (4 RAID5 disks) Shadows copies have been enabled on all volumes.I can browse/restore data . I have plenty free space left. I have limit set as well and it is far away of reaching it. Now for no particular reasons Backup Exec 2012 completed with exception for P: I: volumes with the following warning: - Snapshot Technology: Initialization failure on: "\\xxxxx-xxx\P:". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS). V-79-10000-11242 - VSS Snapshot error. Out of disk space, or could not find an NTFS volume while creating the snapshot. Microsoft Volume Shadow Copy Service (VSS) requires an NTFS volume with enough free disk space for each physical or virtual disk volume to cache the data that changes during the backup job. Consult the Microsoft documentation for more information. That what happens when I backup to tape (LTO5 via HP Utrium 3000). When destination is HDD, I can see the following (exception for I and P): Unable to open the item \\XXXXXX-XXX\I:\System Volume Information\{573950ac-d772-11e2-905b-984be107e958}{3808876b-c176-4e48-b7ae-04046e6cc752} - skipped. Unable to open the item \\XXXXXX-XXX\I:\System Volume Information\{58fa8a79-d38e-11e2-9f73-984be107e958}{3808876b-c176-4e48-b7ae-04046e6cc752} - skipped. Unable to open the item \\XXXXXX-XXX\I:\System Volume Information\{753d8583-d9c7-11e2-94dc-984be107e958}{3808876b-c176-4e48-b7ae-04046e6cc752} - skipped. Unable to open the item \\XXXXXX-XXX\I:\System Volume Information\{753d8dd8-d9c7-11e2-94dc-984be107e958}{3808876b-c176-4e48-b7ae-04046e6cc752} - skipped. Unable to open the item \\XXXXXX-XXX\I:\System Volume Information\{8a2652dd-d88f-11e2-905b-984be107e958}{3808876b-c176-4e48-b7ae-04046e6cc752} - skipped. Unable to open the item \\XXXXXX-XXX\I:\System Volume Information\{a89b127f-d51e-11e2-905b-984be107e958}{3808876b-c176-4e48-b7ae-04046e6cc752} - skipped. Volume E: (which is the LUN from the same P2000 box) is OK. All volumes have this folder in the root. That’s OK, that’s how MSS/VSS works. And that’s where shadow copies are held. So what’s wrong then?! It is definitely not P2000 box that cause the problem as E volume is OK. (I tried hardware provider (HP) for VSS as well btw, without any results.) Any ideas ? Thanks563Views3likes1CommentBackup Exec 2012 health check guide
Hi, i'm a newbie to this backup exec 2012, and recently we have active contract on supporting this Backup Exec 2012. By supporting this, we need to perform health check or software preventive maintenance on the servers equipped with backup exec 2012 on quarterly basis. Just want to know that whether there are some guidelines or procedures/steps on what we need to include in the health check such as services, connections, patches? Please share with me if anyone know how to prepare a backup exec 2012 health check checklist in order to perform the preventive maintenance for the servers. Thanks1.6KViews2likes5CommentsSDRO 6.1: How to configure SQL Server for disaster recovery or migration to Microsoft Azure
Symantec Disaster Recovery Orchestrator 6.1 (SDRO) lets you configure your on-premises SQL Server 2008 R2 or 2012 instances for disaster recovery (DR) or migration to the Microsoft Azure cloud. You need to make identical SQL Server configurations, including users and privileges, on the on-premises and the cloud hosts. The Disaster Recovery Orchestrator Configuration Wizard lets you select the SQL Server instances that you want to configure for monitoring and the detail monitoring options as well. The wizard detects the application data folders and automatically selects them for replication. For more information, refer to the following guides: Symantec Disaster Recovery Orchestrator 6.1 Agent for Microsoft SQL Server 2008 R2 Configuration Guide Symantec Disaster Recovery Orchestrator 6.1 Agent for Microsoft SQL Server 2012 Configuration Guide Additional SDRO documentation can be found on the SORT website.519Views2likes0CommentsCIFS backup from VNXe 3150 without NDMP through BE 2012.
Hi, One my customer want to have EMC VNXe 3150 and BE 2012. We have created a CIFS server and Share folder. Is it possible to take this share foder backup without using NDMP. If yes, how. I have a link but its not for VNXe 3150:- http://www.symantec.com/docs/TECH55199 Thanks.679Views2likes4CommentsUnable Access Second Partition After Formatting Primary Partition
I recently had fully encrypted hard disk (Toshiba mq01abd075), operating system (Windows 7 Professional), two partition. C (146 GB) and D (548 GB) and 4 GB Unallocated space. I ran the system restore for partition C, after which I was unable to access the operating system. I reinstalled the operating system partition C. I installed PGP WDE, when I entered in the program, partition D does not appear to be decrypted. Partition D appears in My Computer (0 bytes), in computer management at disk management appear 548 GB RAW. If I double click on it ask me for Format, but i've never click Yes, so the second partition was never touch after the problem.After this I reinstalled twice the OS. Now I have windows 8.1 but stil,but still I have not touch the second partition. I've tried to decrypt the drive with a few tutorials such as(WinPE and put the hard disk as second partition): http://www.symantec.com/docs/TECH170574 http://www.symantec.com/business/support/index?page=content&id=TECH149478 Give me various errors suchs as: "Could not locate valid BGFS record. Recovey failed! Operation recover disk failed: Error code -11984 item not found" or "Disk 1 is not instrumented by bootguard" and others. I know was my fault. Please give me a solution. P.S: Sorry for my english, I'm not native and please move this topic if it was not posted properly596Views1like0CommentsSharepoint backup/Restore failure Cannot open database "Bdc_Service_DB_"
Friends, NBU 7.5.0.6 Master Windows 2008 R2 64Bit NBU 7.5.0.6 Media Linux Suse 10 SP 2 Sharepoint 2010 W2K8 FEWS+Index Server SQL Server 2008 on W2K8 Backend Server Sharepoint DB Backups running successfully on production setup both full and GRT. Problem: trying to restore the live backups to DR site. DR sharepoint server is all in one running both FEWS and BE SQL Server. followed this technote but no joy 1: http://www.symantec.com/business/support/index?page=content&id=TECH163248 2: can't see the microsoft shrepoint resources in the BAR gui. getting the following error in the SPSWrapper00 logs 0f38] 07/25/14 15:21:01 Total infowrapper counts 1 [0f38] 07/25/14 15:21:01 Application name is Business Data Connectivity Service [0f38] 07/25/14 15:21:01 Application services db name is Bdc_Service_DB_ae4bc5abe4764226abfcbb42ea866079 [0f38] 07/25/14 15:21:01 Exception is Cannot open database "Bdc_Service_DB_ae4bc5abe4764226abfcbb42ea866079" requested by the login. The login failed. Login failed for user 'IX\netbackup'. [0f38] 07/25/14 15:21:01 Exception in getting ServerInstanceName using ConnectionString Data Source=MTSHAREPOINT\SharePoint;Initial Catalog=Bdc_Service_DB_ae4bc5abe4764226abfcbb42ea866079;Integrated Security=True;Enlist=False;Connect Timeout=15 [0f38] 07/25/14 15:21:01 Exception is Cannot open database "Bdc_Service_DB_ae4bc5abe4764226abfcbb42ea866079" requested by the login. The login failed. Login failed for user 'IX\netbackup'. I have stopped the business data continuity service and application service but no joy. Questions: 1: how can i get rid of this error so that sharepoint resources become visible in the BAR gui? i can tell you for sure there are no permission issues on the account as the same account is being used on the production. 2: does the sharepoint resoources have to be visible for the restore? i would of thought yes because if they are not visible backup wont work so same goes for restore? any suggestion would highly be appreicated.1.2KViews1like4CommentsNetbackup Imports running longer when using AIR/Data Domain
We are using Netbackup 7.6.0.1 and Data Domain. We are using AIR to our DR site using data domain. Imports were only taking minutes to complete. Now imports are running longer. Imports are now running hours and days. What could be casue imports that used to complete within minutes now take days.Solved1.7KViews1like7CommentsSDRO 6.1: How to configure and test an on-premises-to-Microsoft Azure disaster recovery configuration
Symantec Disaster Recovery Orchestrator 6.1 (SDRO) lets you configure on-premises applications for disaster recovery (DR) or migration to the Microsoft Azure cloud. After you configure an application for DR or migration, you can run fire drills on the configuration. As part of a fire drill, SDRO tests whether an application can be migrated to or recovered in the cloud in case of a failure at the on-premises site. During the testing, SDRO brings the application online in a separate cloud network, without disrupting your production environment. The Console installation wizard prompts you to specify the network and subnet to be used for fire drills. You may specify these values at the time of installation, or later, using the Console UI. For information about creating a virtual network in the cloud for performing fire drills, see the Symantec Disaster Recovery Orchestrator 6.1 Deployment Guide. You may also need to enable clients to access applications within a fire drill network. For information about performing fire drills and changing the fire drill settings for an application, see the Symantec Disaster Recovery Orchestrator 6.1 Administration Guide. To configure and run a fire drill, perform the following tasks from the Console UI: Use the Disaster Recovery Orchestrator Configuration Wizard to configure an application for DR or migration to the cloud. The wizard configures the components that are required for performing fire drills on the application. Specify the bubble network and the subnet to be used for fire drills on the Settings tab of the application in the Console UI. The existing values are based on the recovery settings of the Console. You may change these values for your application. Run a fire drill to test the application recovery configuration. Optionally, you may view the reports of the fire drill operations that were performed earlier. For more information, see the following topics: Enabling clients to access applications within a fire drill network Configuring an application for disaster recovery Changing the disaster recovery settings of an application Testing a disaster recovery configuration by performing a fire drill Viewing reports of disaster recovery operations Additional SDRO documentation can be found on the SORT website.558Views1like0Comments