Making Incremental Backup using full backup Log only

September 3, 2015, 4:31 am

≫ Next: can you restore if you have DR file plus the required Data files on portable Storage

≪ Previous: Backup Exec

$

0

0

I need a solution

Hi Guys,

I was just wondering if I can create an Incremental backup using the log of a full backup rather than making the full backup itself. I have a NAS drive with about 20-30 Tb of data on it (we are a music / video company) and did a one time full backup of it about a couple of months ago. I did the full backup on LTO5 Tapes and had to do it in stages as the 24 tapes in the library would fill up before the backup would end. 

I now want to schedule an Incremental backup but don't want to go through doing a full backup again (Not that I don't want to do it but I don't require a 20-30 tape full backup again). So i was wondering if we can schedule an Incremental Backup that would reference to the one time backup log and do the incremental as of there. Is that possible you reckon? Does BAckup Exec refers to the real backup files or does it refer to the details in the log file to build the incremental difference?

Cheers

---

can you restore if you have DR file plus the required Data files on portable Storage

September 3, 2015, 11:05 am

≫ Next: What ports do i need for SDR restore

≪ Previous: Making Incremental Backup using full backup Log only

$

0

0

I need a solution

I did a backup to disk to a network folder. I copied the DR and the required data files to a portable harddrive. I started the server with SDR disk and i choose the option where it states the backup is stored locally. I choose the DR file then it prompted me to poin to the Data files for which I did but it prompted and error stating "is not a vaild disk cartridge device. select a valid disk cartridge device.". Is the a way you can restore locally if you have DR file and the data files on a portable or on a network shared drive.?

1441305655

What ports do i need for SDR restore

September 3, 2015, 11:10 am

≫ Next: View Volume Groups From CLI

≪ Previous: can you restore if you have DR file plus the required Data files on portable Storage

$

0

0

I need a solution

I have 2 servers on different subnet and with firewall in between.  What ports do i need to open in order for SDR option to work/communicate with the backup server. I am able to ping and talk to servers on the same subnet but i cant communicate or ping the Backup server which is on another subnet. I boot up SDR but cannot communicate with the backup server. My network settings are correct.

View Volume Groups From CLI

September 3, 2015, 11:25 am

≫ Next: Library not enabled - Drive Control is AVR

≪ Previous: What ports do i need for SDR restore

$

0

0

I need a solution

Hello,

I am trying to figure out to view the contents of a particular Volume Group from the CLI? 

Or

I would like to view what Volume Group a particular tape is assigned to?

Are either of these possible or only avaliable in the GUI?

Thanks

Daniel

Library not enabled - Drive Control is AVR

September 3, 2015, 11:58 am

≫ Next: Windows 10: SSR 2013 R2 install fails, faulting application _Setup.exe

≪ Previous: View Volume Groups From CLI

$

0

0

I need a solution

We have just added to our environment, a new NBU 7.6.0.2 Linux media server that sits behind a firewall.

The new media server is configured for SSO and has access to all SAN attached drives in-scope, emm server shows correctly, all drives show UP and robotic definition looks normal.

The NetBackup console shows the library connection for the new media server as NOT enabled and all associated tape drives are in AVR control.

We have popped some holes through the FW for port 1556 but I'm wondering if there are other ports required? Port 1556 is opened between the new media server, master server and the library control host which is also configured seperately.

The library is completely functional for everything except the new media server.

Any ideas what direction I should be looking in?

Thx,

-Kevin

Windows 10: SSR 2013 R2 install fails, faulting application _Setup.exe

September 3, 2015, 12:15 pm

≫ Next: How to use Netbackup 7.6.1 to backup mapped drives

≪ Previous: Library not enabled - Drive Control is AVR

$

0

0

I need a solution

Hi all.  I have a freshly built Windows 10 Enterprise PC in front of me, so far the only thinkgs bsides the OS and its updates installed are SEP 12.1.6 MP1 and Logitech Setpoint for the mouse/keyboard. 

I try running the installation for SSR 2013 R2 on this system using the download .zip file from FileConnect, and it loads the install browser (where you can click Getting Started, or do the install routine).  I click Install Now, and the window pops up with the initial progress bar which only runs for about 2 seconds before it disappears with no errors on screen.  Re-running produces identical results, same after reboots and re-downloading the installer package.  I've also downloaded two versions of the installer page with slightly different build numbers. 

The application event log for Windows shows two direct errors to this, event ID 1026, source is .Net Runtime, and it basically indicates generically that _Setup.exe was the faulting application.  Event 1000 follows which is pasted below.  Yet I installed the same version of SSR to another Windows 10 (Pro, not Ent.) today and it ran fine.  Any idea what this could be?   

Log Name:      Application
Source:        Application Error
Date:          9/3/2015 12:07:32 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      COMPUTER
Description:
Faulting application name: _Setup.exe, version: 15.0.16.0, time stamp: 0x53639516
Faulting module name: KERNELBASE.dll, version: 10.0.10240.16384, time stamp: 0x559f38c3
Exception code: 0xe0434352
Fault offset: 0x000000000002a1c8
Faulting process id: 0xfd8
Faulting application start time: 0x01d0e67bc92ebea5
Faulting application path: C:\!IT\Sym_System_Recovery_2013R2_11.1.2.54477_Multilingual_Product\SSR\SSRx64\Install\_Setup.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 267fc8ef-b576-4b92-881d-a3d2b8e6c3ef
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-09-03T19:07:32.000000000Z" />
    <EventRecordID>507</EventRecordID>
    <Channel>Application</Channel>
    <Computer>COMPUTER</Computer>
    <Security />
  </System>
  <EventData>
    <Data>_Setup.exe</Data>
    <Data>15.0.16.0</Data>
    <Data>53639516</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>10.0.10240.16384</Data>
    <Data>559f38c3</Data>
    <Data>e0434352</Data>
    <Data>000000000002a1c8</Data>
    <Data>fd8</Data>
    <Data>01d0e67bc92ebea5</Data>
    <Data>C:\!IT\Sym_System_Recovery_2013R2_11.1.2.54477_Multilingual_Product\SSR\SSRx64\Install\_Setup.exe</Data>
    <Data>C:\Windows\system32\KERNELBASE.dll</Data>
    <Data>267fc8ef-b576-4b92-881d-a3d2b8e6c3ef</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

1441327092

How to use Netbackup 7.6.1 to backup mapped drives

September 3, 2015, 1:14 pm

≫ Next: Netbackup Oracle Agent Support for Japanese Characters Set

≪ Previous: Windows 10: SSR 2013 R2 install fails, faulting application _Setup.exe

$

0

0

I need a solution

We recently migrated our end-user network shares from a Windows Server 2012 server to VNX CIFS.

Since the CIFS is not a server unto itself, the plan is to attach it as a mapped drive onto one of our existing Windows Server machines, and then use Netbackup 7.6.1 to back up the data on the mapped drive.

However, I do not know how to accomplish this.  I tried creating a new backup policy, but it requires me to assign an OS, and it expects an agent to be installed on the client.  Since our CIFS is just a collection of shares on allocated disk space, there isn't an OS, nor a client to install an agent on.  I am very new to Netbackup administration and could use any assistance you're willing to provide.

Netbackup Oracle Agent Support for Japanese Characters Set

September 3, 2015, 7:39 pm

≫ Next: BE update 2015 restart agent servers

≪ Previous: How to use Netbackup 7.6.1 to backup mapped drives

$

0

0

I need a solution

We have install Symantec Netbackup 7.6.1 in Windows Server 2012 which act as Master Server. We also have install Netbackup Client in Unix Server to backup the Oracle Database in it.

We had been asked whether the Netbackup Oracle Agent can support Japanese Character Set DB or not. How we can check whether it is support or not?>

Kindly advise

Thanks

1441359895

---

BE update 2015 restart agent servers

September 4, 2015, 1:43 am

≫ Next: Problem with pdi#_strm.bin files filling up drive

≪ Previous: Netbackup Oracle Agent Support for Japanese Characters Set

$

0

0

I need a solution

Hi all,

After do an update of backup server and install agents, the backups not wotks because is necessary rebbot the agents servers. Now is impossible restart our fileserver, but at the same time is important do backups. We are trying start the services manually but ther error is:

--------------------------------------------------------------------

Windows could not start the Backup Exec Remote Agent for Windows on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code 536928719.

--------------------------------------------------------------------

In other cases opened  we saw  https://www-secure.symantec.com/connect/forums/backup-exec-2014-service 

-------------------------------

There are couple of keys named PatchReboot and Reboot found at HKLM\SOFTWARE\Symantec\

--------------------------------

We don't find this key in our register. Are changed it with this update??

Probably the next week we can restart the server but until this, we need start the services agent of backup exec.

Problem with pdi#_strm.bin files filling up drive

September 4, 2015, 2:36 am

≫ Next: child bptm, shared memory and parent bptm

≪ Previous: BE update 2015 restart agent servers

$

0

0

I need a solution

We have a Windows Server 2008R2 running BE 15. The backups themselves are copied into a folder on the QuikStor drive (media is rotated out each morning) called Veritas. However, we have a myriad of IMG0000## folders that contain several pdi##_strm.bin files, some of which are very old. On our 1 TB media, half the drive space is taken up by these, and since our backups require around 500 GB, these files are causing the backups to fail. I've tried various settings for Storage, including "Media Overwrite Protection Level: None" and "Allow Backup Exec to delete all expire backup sets: <checked>". Inside the configured job, "Keep for: 4 days" is configured. Given the date stamp, which may be months old, I don't think they contain the data on our server. How do I get rid of these, so that I have sufficient data for backups? Thank you.

child bptm, shared memory and parent bptm

September 4, 2015, 3:27 am

≫ Next: Falha no Backup

≪ Previous: Problem with pdi#_strm.bin files filling up drive

$

0

0

I need a solution

Hello,
I need to know about shared memory. What is it exactly.
During backup bpbkar sends data strems to child bptm. Then child bptm store that strems in shared memory and from shared memory parent bptm took the data and write to media.

So will you please help me to understand about shared memory. What is it...

Or it is just disk storage from our hard drive. Which get in use as shared memory for temporary basis to store the data strems.

0

Falha no Backup

September 4, 2015, 5:28 am

≫ Next: Netbackup remote admin console on windows

≪ Previous: child bptm, shared memory and parent bptm

$

0

0

I need a solution

Bom dia,

Estou tento problema com o BE 2012. Está dando falha no backup informando que o agente não está ativo no servidor. Porém o servidor que ele informa não existe.

O servidor que está com o agente é 06 e ele informa que o servidor 02 não tem agente, só que ele realmente não existe.

Netbackup remote admin console on windows

September 4, 2015, 6:36 am

≫ Next: Urgent : Move of database files failed

≪ Previous: Falha no Backup

$

0

0

I need a solution

I try to export  policy attribute, schdule, backup selection etc..  from Netbackup remote windows admin console but the "Export" option is showing as inactive(grey out).

I'm not sure why it is shoiwig inactive where as i'm able to get this for unix/linx masters via java console.

I set full rights in auth.conf file  but in windows i'm not sure this exist.  i guess it is somethig else is not allowing to export the date not with auto.conf file.

Alos i would like to know is that possible i can use java consol to access WIN master server version (7.6.0.4). If yes how can i do that,  greatly appreciate if you have any tech note or solutions for these..

Urgent : Move of database files failed

September 4, 2015, 6:45 am

≫ Next: Files backed up cleanly, and restore, but the restored files are 0KB

≪ Previous: Netbackup remote admin console on windows

$

0

0

I need a solution

I have a newly installed Virtual master server but the Catalog database is installed on C: drive and I want to move it to E: drive now. When I try the command from the installlation path ''C:\Program Files\VERITAS\NetBackup\bin>nbdb_move -data E:'' it is failing with 'Move of database files failed'

Files backed up cleanly, and restore, but the restored files are 0KB

September 4, 2015, 7:49 am

≫ Next: Backup of VM DCs failing

≪ Previous: Urgent : Move of database files failed

$

0

0

I need a solution

Netbackup 7.6.0.4

Windows 2008r2 master and media servers

Datadomain 5.4.4.1

Hello.

I'm running into an odd issue where I am trying to restore data that I can see in the backups, and looks healthy. The files are mainly tiff, pdf, etc....image files from scanned receipts. The data is backed up from a share on a Netapp. The backup policy is an ms-windows type, and simply uses one of my media servers as the policy client, and the backup selection is the path to the file share. When I perform a restore of the data, the job finishes quickly, with a "partially successful" message. I cen see the files in the target restore location, but the file size is 0. Ive been researching the error messages "WIN32 50: The request is not supported", and "err=WIN32 1338: The security descriptor structure is invalid", but not coming up with a lot yet. Anyone experienced this before?

---

Backup of VM DCs failing

September 4, 2015, 7:50 am

≫ Next: Need to remove old server from backup list.

≪ Previous: Files backed up cleanly, and restore, but the restored files are 0KB

$

0

0

I need a solution

I have 2 DCs that have started failing backups. The DCs are 2012 R2 VMs in 2012 R2 hosts. Backup Exec is 2012 version 14.1798.

The error in the failed job details says E0008488 Access is denied. When I do a credentials test, the only failure is for MSONLINE which I have no idea what that is. Doesn't matter what account is used, same result.

Any idea what to do? Delete the job and create a new one? TThis just was working just fine up to a point where I started having media troubles (backup to disk). I finally got the media problems ironed out and all other servers are backing up successfully, it's just the two DCs that won't backup.

Jonathan

Need to remove old server from backup list.

September 4, 2015, 1:51 pm

≫ Next: migration master server from standalone to cluster

≪ Previous: Backup of VM DCs failing

$

0

0

I need a solution

I thought I had removed a server from my list. It no longer exists in our network.

For some reason after I deleted it it reappeared.

• Sym BE 2014 cant remove server.docx
• Symantec BE cannot remove old server.docx

migration master server from standalone to cluster

September 4, 2015, 6:15 pm

≫ Next: .nsf file in use, skipped

≪ Previous: Need to remove old server from backup list.

$

0

0

I need a solution

 

 

 

 

I  have amasterserver 7.6.1.1inWindows 2008with 2applianceanddeduplicateddisk backupandwantto migrateto aclusterofWindows2012 what stepsmust follow.

Thanks for your help

.nsf file in use, skipped

September 4, 2015, 6:48 pm

≫ Next: Backup Exec 2015: Jobs Saved but not Shown up

≪ Previous: migration master server from standalone to cluster

$

0

0

Copy all the children of the comment that is the source of this new discussion.

I need a solution

Hello,

thank you for your reply .

I edited the job and deselect blocking files,but this time i have a new error message of failig backup as show below.Any idea please?

Etat de fin : EchecVoir exception(s)

Développer toutRéduire tout

Informations sur le travail
Serveur du travail : BACKUP Nom du travail : 192.168.1.7 Sauvegarde 00079-Complète Début du travail : mercredi 2 septembre 2015 à 10:39:44 Type du travail : Sauvegarde Journal du travail : BEX_BACKUP_00362.xml Méthode de sauvegarde du travail : Complète

Backup Exec ne suivra pas les points de montage, points de jonction et liens symboliques quand l'indicateur de Simplified Disaster Recovery est sur ACTIVE.

Montage de lecteurs et de médias demandé : 02/09/2015 10:39:55

Aucun média à ajouter n'a pu être monté.
Activation de la protection contre le remplacement sur le média de travail.

Informations sur les périphériques et supports

Informations sur le lecteur et le média à partir du montage du média : 02/09/2015 10:40:38 Nom de la bandothèque : Bandothèque 0001 Nom du lecteur : Lecteur de bande 0001 Logement : 4 Etiquette du média : 000004L5 GUID du média : {9afbd2d0-73c7-4c16-8386-382afc5b7481} Protection contre le remplacement jusqu'au : 30/09/2015 10:40:38 Ajout possible jusqu'au : 08/09/2015 10:40:38 Nom du jeu de médias cible : Conserver les données pendant 4 semaines Conserver : 4 semaine(s) Tous les supports utilisés 000004L5

Opération du travail - Sauvegarde

Options de sauvegarde Opération du média - Ajouter au média, remplacer si aucun média ajoutable n'est disponible. Type de compression : Matérielle [si disponible, sinon : Aucune] Type de chiffrement : Aucun   Serveur - 192.168.1.7 Le serveur Backup Exec exécute Backup Exec version 14.1.1786.1103 avec SP-2,HF-227745. Agent for Windows(srv-lotus) exécute Backup Exec version 14.1.1786.1093 avec SP-2. Le serveur Backup Exec et Agent for Windows exécutent des versions différentes.   Les ressources suivantes qui ont été sélectionnées pour la sauvegarde peuvent être utilisées pour les futurs travaux de conversion en machine virtuelle : 'C:, D:, System?State' Les ressources suivantes qui ont été sélectionnées pour la sauvegarde ne peuvent pas être utilisées pour les futurs travaux de conversion en machine virtuelle : '192.168.1.7|D:' Technologie de cliché : démarrée pour la ressource : "\\192.168.1.7\C:". Technologie de cliché utilisée : Service de cliché instantané des volumes Microsoft (VSS). La technologie de cliché utilisée par VSS pour le volume C: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7). La connexion de contrôle réseau est établie entre 192.168.1.68:49250 <--> 192.168.1.7:10000 La connexion de données réseau est établie entre 192.168.1.68:49257 <--> 192.168.1.7:62241 Informations sur le jeu - \\192.168.1.7\C: Sauvegarde - Informations sur le jeu Nom de la famille : "Média créé le 02/09/2015 à 10:39:55" Sauvegarde de "\\192.168.1.7\C:" Jeu de sauvegarde n° 1 sur le média de stockage n° 1 Description du jeu de sauvegarde : "" Méthode de sauvegarde : Complète - Sauvegarde les fichiers (à l’aide de l’heure modifiée) Début de la sauvegarde, le 02/09/2015 à 10:41:00. Fin de la sauvegarde, le 02/09/2015 à 10:50:14. Sauvegarde - Résumé du jeu 32120 fichiers sauvegardés dans 4832 répertoires. 5 029 100 789 octets traités en 9 minutes et 14 secondes. Vitesse de débit : 519 Mo/min Type de compression : Matériel Technologie de cliché : démarrée pour la ressource : "\\192.168.1.7\D:". Technologie de cliché utilisée : Service de cliché instantané des volumes Microsoft (VSS). La technologie de cliché utilisée par VSS pour le volume D: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7). La connexion de contrôle réseau est établie entre 192.168.1.68:49250 <--> 192.168.1.7:10000 La connexion de données réseau est établie entre 192.168.1.68:49297 <--> 192.168.1.7:62302 Informations sur le jeu - \\192.168.1.7\D: Sauvegarde - Informations sur le jeu Nom de la famille : "Média créé le 02/09/2015 à 10:39:55" Sauvegarde de "\\192.168.1.7\D:" Jeu de sauvegarde n° 2 sur le média de stockage n° 1 Description du jeu de sauvegarde : "" Méthode de sauvegarde : Complète - Sauvegarde les fichiers (à l’aide de l’heure modifiée) Début de la sauvegarde, le 02/09/2015 à 10:50:48. Fin de la sauvegarde, le 02/09/2015 à 13:06:31. Sauvegarde - Résumé du jeu 698359 fichiers sauvegardés dans 19044 répertoires. 75 472 370 030 octets traités en 2 heures, 15 minutes, et 43 secondes. Vitesse de débit : 530 Mo/min Type de compression : Matériel Remarque : Ressource : "192.168.1.7|D:" ne peut pas être reproduit. Tentative de sauvegarde de volumes directement à partir du volume source. La connexion de contrôle réseau est établie entre 192.168.1.68:49250 <--> 192.168.1.7:10000 La connexion de données réseau est établie entre 192.168.1.68:49771 <--> 192.168.1.7:63014 Informations sur le jeu - Bases de données Domino sur D: Sauvegarde - Informations sur le jeu Nom de la famille : "Média créé le 02/09/2015 à 10:39:55" Sauvegarde de "Bases de données Domino sur D:" Jeu de sauvegarde n° 3 sur le média de stockage n° 1 Description du jeu de sauvegarde : "" Méthode de sauvegarde : Complète - Sauvegarde les bases de données et les journaux (Réinitialiser d’archive) Lotus Domino Agent: Démarré Début de la sauvegarde, le 02/09/2015 à 13:06:34. Sauvegarde - Détails sur le jeu Elément 192.168.1.7|D:\Lotus\Domino\data\first-team.nsf en cours d'utilisation - ignoré. Drive is not ready Fin de la sauvegarde, le 02/09/2015 à 19:36:45. Sauvegarde - Résumé du jeu 560 fichiers sauvegardés dans 21 répertoires. 1 élément a été ignoré. 260315839904 octets traités en 6 heures, 30 minutes, et 11 secondes. Vitesse de débit : 636 Mo/min Type de compression : Matériel Technologie de cliché : démarrée pour la ressource : "\\192.168.1.7\System?State". Technologie de cliché utilisée : Service de cliché instantané des volumes Microsoft (VSS). Les volumes suivants dépendent de la ressource : "C:""D:""\\?\VOLUME{EDC7E99A-79FA-11E4-A053-806E6F6E6963}" . La technologie de cliché utilisée par VSS pour le volume C: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7). La technologie de cliché utilisée par VSS pour le volume D: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7). La technologie de cliché utilisée par VSS pour le volume \\?\VOLUME{EDC7E99A-79FA-11E4-A053-806E6F6E6963} - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7). La connexion de contrôle réseau est établie entre 192.168.1.68:49250 <--> 192.168.1.7:10000 La connexion de données réseau est établie entre 192.168.1.68:50545 <--> 192.168.1.7:65215 Informations sur le jeu - \\192.168.1.7\System?State Sauvegarde - Informations sur le jeu Nom de la famille : "Média créé le 02/09/2015 à 10:39:55" Sauvegarde de "\\192.168.1.7\System?State" Jeu de sauvegarde n° 4 sur le média de stockage n° 1 Description du jeu de sauvegarde : "" Méthode de sauvegarde : Complète - Sauvegarde les fichiers (Réinitialiser d’archive) Début de la sauvegarde, le 02/09/2015 à 19:37:16. Sauvegarde - Détails sur le jeu L’autre chemin sur lequel vous pouvez stocker une copie du fichier d’informations de reprise après incident n’est pas indiqué. Indiquez ce chemin pour que Backup Exec puisse stocker une copie des fichiers d’informations de reprise après incident. Pour indiquer le chemin, cliquez sur le bouton Backup Exec, sélectionnez Configuration et paramètres > Paramètres Backup Exec > Simplified Disaster Recovery. Le fichier d'informations de reprise après incident C:\Program Files\Symantec\Backup Exec\SDR\Data\192.168.1.7.DR a bien été mis à jour. Fin de la sauvegarde, le 02/09/2015 à 19:55:37. Sauvegarde - Résumé du jeu 17 composant(s) d'état du système sauvegardé(s) 10 319 398 839 octets traités en 18 minutes et 21 secondes. Vitesse de débit : 536 Mo/min Type de compression : Matériel

Opération du travail - Vérification

Serveur - 192.168.1.7   Informations sur le jeu - \\192.168.1.7\C: Vérification - Informations sur le jeu Vérification de "\\192.168.1.7\C: " Jeu de sauvegarde n° 1 sur le média n° 1 Description du jeu de sauvegarde : "" Début de la vérification, le 02/09/2015 à 19:56:40. Fin de la vérification, le 02/09/2015 à 19:57:13. Vérification - Résumé du jeu 32120 fichiers vérifiés dans 4832 répertoires. 5 029 100 789 octets traités en 33 secondes. Vitesse de débit : 8720 Mo/min   Informations sur le jeu - \\192.168.1.7\D: Vérification - Informations sur le jeu Vérification de "\\192.168.1.7\D: " Jeu de sauvegarde n° 2 sur le média n° 1 Description du jeu de sauvegarde : "" Début de la vérification, le 02/09/2015 à 19:57:13. Fin de la vérification, le 02/09/2015 à 20:05:45. Vérification - Résumé du jeu 698359 fichiers vérifiés dans 19044 répertoires. 75 472 370 030 octets traités en 8 minutes et 32 secondes. Vitesse de débit : 8435 Mo/min   Informations sur le jeu - Bases de données Domino sur D: Vérification - Informations sur le jeu Vérification de "Bases de données Domino sur D:" Jeu de sauvegarde n° 3 sur le média n° 1 Description du jeu de sauvegarde : "" Début de la vérification, le 02/09/2015 à 20:05:45. Fin de la vérification, le 02/09/2015 à 20:33:28. Vérification - Résumé du jeu 560 fichiers vérifiés dans 21 répertoires. 260315839904 octets traités en 27 minutes et 43 secondes. Vitesse de débit : 8957 Mo/min   Informations sur le jeu - \\192.168.1.7\System?State \\192.168.1.7\System?State Vérification - Informations sur le jeu Vérification de "\\192.168.1.7\System?State \\192.168.1.7\System?State" Jeu de sauvegarde n° 4 sur le média n° 1 Description du jeu de sauvegarde : "" Début de la vérification, le 02/09/2015 à 20:33:28. Vérification - Détails sur le jeu   Fin de la vérification, le 02/09/2015 à 20:34:17. Vérification - Résumé du jeu Contenu vérifié. 10 319 398 839 octets traités en 49 secondes. Vitesse de débit : 12051 Mo/min

Etat de fin du travail
Fin du travail : mercredi 2 septembre 2015 à 20:35:17 Etat de fin : Echec Erreur finale : 0xe00084b8 - Une défaillance s'est produite lors de la sauvegarde. Consultez le journal des travaux pour plus de détails. Catégorie d'erreur finale : Erreurs du travail Pour plus d'informations sur cette erreur, reportez-vous au lien V-79-57344-33976

Exceptions

Cliquez sur une exception ci-dessous pour la localiser dans le journal de travail.   Sauvegarde -- Bases de données Domino sur D: Elément 192.168.1.7|D:\Lotus\Domino\data\first-team.nsf en cours d'utilisation - ignoré. Sauvegarde -- \\192.168.1.7\System?State L’autre chemin sur lequel vous pouvez stocker une copie du fichier d’informations de reprise après incident n’est pas indiqué. Indiquez ce chemin pour que Backup Exec puisse stocker une copie des fichiers d’informations de reprise après incident. Pour indiquer le chemin, cliquez sur le bouton Backup Exec, sélectionnez Configuration et paramètres > Paramètres Backup Exec > Simplified Disaster Recovery.

11343921

Backup Exec 2015: Jobs Saved but not Shown up

September 4, 2015, 11:02 pm

≫ Next: GEN 3 media restoration issue on IBM TS3500 Library

≪ Previous: .nsf file in use, skipped

$

0

0

I need a solution

We are testing Backup Exec 15.  We created few jobs to backup couple servers.  The jobs ran fine daily as scheduled.  Then we cannot create new backup jobs any more.  We can add a new server.  We can install the agent on the server. We can create a backup job but when we click OK to save the job, the job is not seen anywhere.  We try to create another job, same problem.  We can select what to back up and change schedule but when we hit OK to save, we dont see the job anywhere.  

Weird thing is BKExec does not let us chose the same name for the bk job when we try again as it says there is already a job with that name and BKExec increases the job number evey time we create a new job.  Like we create the 1st job with the default name "Server A Backup 100", save the job, don't see the job anywhere.  Then we create a new job, BKExec gives us the default name "Server A Backup 101".  If we change the name to "Server A Backup 100" then it says "A policy with the same name already exists." That means the previous job was saved but somehow we dont see it.  And BKExec still shows the server "never backed up".  All existing jobs are still running as scheduled.

Have you guys seen anything like that and know the solution?

Thanks.