Lotus Domino Databases are Missing from Selection List
I am running BE 2014, 14.1 Rev 1786 -64Bit. I have a Windows Server 2008R2, running Lotus Notes 8.5. Today I went to restore a mail file (.nsf) and found that it, along with most of my other mail files were not backed up on the tape I was using. I'm not sure how long this goes back as I'm still investigating this. When looking at the selection list, the entire /Data/Mail directory is selected under the Lotus Domino option in the selection list, but when you browse into it, only recently created NSF files are listed. I was able to resolve the issue by followingTECH165059but this apparently does not resolve this issue from occuring again. This is a massive issue - how can I ever trust Symantec to backup all of my Domino databases without manually checking to ensure each one is present on the tape (this is not an acceptable solution)? To make this even more of a concern... Symantec has known of thisissueat least as far back as version 2012, if not more. I'm running 2014 so the issue was known but not resolved during a major update. To reiterate, Backup Exec has 1 job, and it failed at that 1 job but conitnued to claim that it was actually doing that 1 job. What can I put into place so that I can trust the system? Is this resolved in BE15? Thanks
Backup Exec 2014 splitting Domino jobs
Is it possible to split our Domino backup jobs into smaller sets? For instance, can we backup mail\A-M in one job, and mail\N-Z in a second job. Creating the selections is doable......but if the Domino server is using DAOS and transaction logging, how does BackupExec handle that? The .nlo files and transaction logs are shared between all databases on the Domino server. Thanks in advance, NickBackup data from Lotus Domino Agent.
Hello, I am facing problems with my Lotus Domino Backup. I have a virtualization enviroment and my Lotus Domino Server is a VM and I installed the Backup Exec Agent in this machine to perform a data backup only. The problem is the backup throughput because is very slow, this backup has a total of 600GB and a throughput 500 MB/Min. This backup takes 20 hours approximately to finish and I others backups is faster, just Lotus Domino Server has this low throughput. Today the backup is performed to tape but I made a test, I performed a backup to disk and the throughput is the same. Can someone help in this case? Thanks
Troubleshooting Domino Agent with BackupExec 12.5
All, A client is running Lotus Domino under Windows 2003 and BackupExec 12.5. Over the weekend, the IT department migrated the Domino installation to a new disk as its existing disk was filling up. However, the BackupExec console is no longer showing the Lotus Domino Databases tree in the selections for the server. (The Domino and BackupExec installations reside on the same server.) The IT department is doing some troubleshooting of the Domino server which appears to be unrelated to this. My question is: If Domino is moved to another disk, is there anything that needs to be done in BackupExec so BE can see that there are valid Domino databases on the server?Backup Exec with Oracle RAC 11g
Hello, Any idea about this error and how can I resolve it ? I have BE 2012 SP3 and windows 2008 R2 SP1 and I need to backup Oracle RAC on windows 2008 server. thanks Le script de la base de données a renvoyé une erreur. Pour plus d'informations, dans les journaux des travaux, reportez-vous à la section de sortie du script de la base de données. Sortie RMAN Recovery Manager: Release 11.2.0.4.0 - Production on Tue Feb 18 16:47:16 2014 Copyright (c) 1982, 2011, Oracle and/or its affiliates. All rights reserved. connected to target database: DBOCT (DBID=631434509) # ----------------------------------------------------------------- # RMAN command section # ----------------------------------------------------------------- RUN { ALLOCATE CHANNEL ch0 TYPE 'SBT_TAPE'; SEND 'BSA_SERVICE_HOST=172.20.53.210,NBBSA_TOTAL_STREAMS=1,NBBSA_JOB_COOKIE={C51D77C9-4954-405D-9AF0-97B251F41C72},NBBSA_DB_DEVICE_NAME=Oracle-Win::\\RAC-DBOCT-631434509\DBOCT'; BACKUP FULL FORMAT 'BE_U' TABLESPACE 'OCT' FORCE; RELEASE CHANNEL ch0; } using target database control file instead of recovery catalog allocated channel: ch0 channel ch0: SID=739 instance=dboct2 device type=SBT_TAPE channel ch0: Symantec/BackupExec/1.1.0 sent command to channel: ch0 Starting backup at 18-FEB-14 channel ch0: starting full datafile backup set channel ch0: specifying datafile(s) in backup set input datafile file number=00007 name=+DGDATA/dboct/datafile/oct.282.831899057 input datafile file number=00008 name=+DGDATA/dboct/datafile/oct.283.831899073 channel ch0: starting piece 1 at 18-FEB-14 released channel: ch0 RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: failure of backup command on ch0 channel at 02/18/2014 16:47:21 ORA-19506: echec de creation du fichier sequentiel, nom="BE_6mp0uo0o_1_1", parms="" ORA-27028: skgfqcre : sbtbackup a renvoye une erreur ORA-19511: Erreur recue de la couche de gestionnaire de supports, texte du message d'erreur : EXIT Recovery Manager complete. Périphériques acquis : 1 Flux de données utilisés : 0 Etat de fin du travail Fin du travail : mardi 18 février 2014 à 16:45:18 Etat de fin : Echec Erreur finale : 0xe0000340 - Le script de la base de données a renvoyé une erreur. Pour plus d'informations, dans les journaux des travaux, reportez-vous à la section de sortie du script de la base de données. Catégorie d'erreur finale : Erreurs des ressources