Local account vs Service account for DNAS protection
Hi, I was interested to hear from the community as to if people tend to use local accounts or service accounts when it comes to configuring snapshot style protection for DNAS backups? Previously when we used ndmp we obviously had to use local accounts that were local to the storage array but we want to test moving away from NDMP to DNAS and as such it seems you can give it either local or domain based user so long as it has sufficient rights on the storage array. So what do people tend to use and for what reasons? Thanks in advance for any opinions/info
Can not backup synology nas to Tape
Backup EXEC 24.0 Synology DSM 7.0.0 We are trying to backup SMB Share on Synology NAS to Tape. We added NAS to File server in Backup EXEC and enabled backup user share. But Backup Exec try to backup SMB share by NDMP Protocol. Why Backup exec do that? [3816] 2025-02-13T13:47:59.967 [ndmp\ndmpcomm] - Could not resolve the "bews-ndmp" or the "ndmp" service, error code: 10109, using port 10000 [3816] 2025-02-13T13:47:59.967 [ndmp\ndmpcomm] - ndmpConnectEx: Querying the neighbour advertisement cache to discover information on 'synology_FQDN' ... [3816] 2025-02-13T13:48:01.970 [ndmp\ndmpcomm] - ndmpEstablishConnectionUsingNoSpecificAdapter: Could not connect to remote address Synology_IP and port 10000 Errorno : 10061 [3816] 2025-02-13T13:48:01.970 [ndmp\ndmpcomm] - ndmpConnectEx: unable to connect using NetworkOptions to synology_FQDN [3816] 2025-02-13T13:48:03.974 [ndmp\ndmpcomm] - ndmpConnectEx: All attempts to connect to 'synology_FQDN' failed [3816] 2025-02-13T13:48:03.974 [ndmp\ndmpcomm] - ndmpConnectEx: failed to connect to 'synology_FQDN'
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
SDRO 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.SDRO 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.SDRO 6.1: How to configure an on-premises application for disaster recovery or migration to Microsoft Azure
Symantec Disaster Recovery Orchestrator (SDRO) 6.1 lets you configure an on-premises custom application for disaster recovery (DR) or migration to the Microsoft Azure cloud. For information about preparing the cloud infrastructure for SDRO and installing the product, see the Symantec Disaster Recovery Orchestrator 6.1 Deployment Guide. For information about configuring the application for DR or migration, see the Symantec Disaster Recovery Orchestrator 6.1 Administration Guide. To configure an application for DR or migration: Identify a virtual machine in the cloud or create a new one to host the application in case a failure occurs at the on-premises site. Install and configure the application on the virtual machine to match the setup at the on-premises host. Use the Disaster Recovery Orchestrator Configuration Wizard to: Select an application from your on-premises environment. Select a virtual machine in the cloud to host the application after DR or migration. Configure the application for monitoring on its on-premises and cloud hosts. Select the application data folders that need to be replicated for consistency. For more information, see the following topics: About creating virtual machines in Azure Considerations for configuring an application for recovery Configuring an application for disaster recovery Additional SDRO documentation can be found on the SORT website.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.