licence V-ray edition
Bonjour nous vendons Backupexec pour de petites structures et ce même depuis l'époque "veritas"... cepandant ces derniers temps nous rencontrons de plus en plus de problèmes sur avec les nouvelles infrastructures Donc nous achetions jusqu'à présent BE 2014 SBE http://www.symantec.com/fr/fr/backup-exec-small-business-edition/?fid=backup-exec avec un joli point dans les fonctions et avantages du produit: "Regroupe les technologies de sauvegarde et de restauration Symantec de pointe dans une solution économique conçue pour prendre en charge jusqu'à 3 serveurs/applications physiques ou virtuels." Donc génial car en général on a moins de trois serveurs ou instances virtuel de serveur, un vsphere gratis et roulez jeunesse on backup via l'agent les serveurs (cela fonctionnait bien...) (en général un DC+ serveur de fichier et un Exchange) Mais nous il nous a fallu un problème de sauvegarde chez un client pour découvrir la signification du mot "jusqu'à" de la phrase "Regroupe les technologies de sauvegarde et de restauration Symantec de pointe dans une solution économique conçue pour prendre en charge jusqu'à 3 serveurs/applications physiques ou virtuels" on nous a dit: "il faut acheter un agent supplémentaire pour les serveurs" ...OK on s'est donc tourné vers une v-ray edition vu que dans la plupart des cas clients il y'a un hyperviseur hote d'un DC et d'un Exchange. déjà il faut acheter en plus au moins vsphere essentials. Mais quelle décéption de voir qu' il n'est pas possible de sauvegarder le serveur backup exec car il ne peut pas se sauvegarder lui-même lorsqu'il est installé sur une machine virtuelle.... soit, je vais faire sa sauvegarde comme s'il s'agissait d'un serveur physique par l'agent habituel... et là, belle surprise de nouveau:qui m'annonce que lorsque l'édition v-ray est installée, elle ne couvre pas la protection des ordinateurs physiques, à moins que suffisament de licences d'agent n'aient été achetées... retours au même point qu'avec SBE il faut un agent encore et toujours... on regrette windows server sbs maintenant on regrette symantec... Merci de fournir une VRAI solution pour les petite structures ou l'on achete UNE licence et basta
Sharepoint 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.
Backup Exec 2010 R3 getting zero compression
I have a site ehere the compression ratio appears to have dropped to Zero and is now over running the tape. 2 weeks ago we were getting 1.2:1 now it is reporting 1:1 and the quantity of data backed up seems to agree with these figures. The device is an LTO 3 (HP in a ML350 G6 wis SBS2011) I have run a scsi trace and can see that bacup exec is sending a scsi compress at the start of the job. I have created some highly compressible files as per technotes and when I back these up I get 47.7:1 compression so comression is working. If I backup 6GB of XLS files in one directory I get zero compression. If I put 2GB of highly compressible files in the same directory I get 1.3:1 compression so compression is working If I zip the 6GB directory I get a 4.5 GB zip file so the XLS in native are quite compressable. The whole server is an average SBS2011 with an additional LOB server running 2008. I am trying to backup approx 450GB to an LTO3 (400/800) drive so am a bit annoyed with this. Product is fully up to date (SP4) backups are running at about 730MB/min which I am finding to be about average as system state backups drag this figure down. HELP anyone?
Backup 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. Thanks
Symantec Central Admin....
Hi, After long time back I am back....... Ok comming straight to the topic... I have the following details:- 1. BE 2012 SP1 on MS Windows 2008 R2. 2. Tape Library (4 nos. of FC drive). 3. SAN switch (2 nos.). 4. SAN Storage. 5. LUN are mounted in different servers(7-8 nos. of servers) from the storage. These LUN are taken backup. Now, we are currently taking LAN based backup from all these server to tape library. Speed..defently a issue. As data size are around 1 TB apprx. on each server and thses data need to be backed up every day (Full backup). Which defently a big deal for us. Now, we are upgrading to Enterprise License. And planning to install the media server on each server so that we can put the data directly to the tapes. I have check the below link for my further referance:- http://www.symantec.com/docs/HOWTO23028 (How CASO works) http://www.symantec.com/docs/HOWTO23023 (Installation of CASO) http://www.symantec.com/docs/TECH43297 (Diagram and working of CASO) http://www.symantec.com/docs/HOWTO21788 (Best Practices) Is there any best practrices experiance and thing need to be checked or any other pre-requisists. Please, provide me the ways ... And please let me know the linkf from where I can download the software. Any case studies... Thanks
Completed 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 ? Thanks
BE Linux Agent 2010 compatibility with BE Server 2012 for Windows
Hi, I am about to purchase "BE Server 2012 for windows" and then, I want to connect an existing "BE Linux Agent 2010" (run on Linux RHE 6.1) into a "BE Server 2012 for windows" (run on Win2k8 Storage Server). I have some questions: - Is the "BE Linux Agent 2010" compatibility with "BE Server 2012" for Windows ? (I have read the BE 2012 HCL: it is not clear) -> If yes, are there limitations ? (With BE 2012 Agent for Windows there are somme limitations) - Is the "BE Linux Agent 2012" free of charge in this particular case ? or - Have I to purchase an update for "BE Linux Agent 2010" to "BE Linux Agent 2012" ? I hope some one from Symantec can be answer me soon. Bests regards.