I want to establish a simple backup system for 3 servers using one LTO6 Tape drive.   I keep a box of scratch tapes available at all times.  So I create 3 jobs to do a full backup of the different servers  at 8pm, 12pm and 2am on the first Monday of each month.   The 8pm full backup is set to use appendable media or overwrite if no append able media is available ( I do so because this is the first job, and scratch media is not appendable) The second and third  jobs are set to append and not overwrite.

My question is this,  if I’m positive my scratch tape will hold the data for all three servers, is this the best way to do this?   I would also follow the same logic with incremental’s the rest of the month… i.e. have the earliest job set to append or overwrite and each job later to only append, every weekday until time to do the next full.

I am trying to restore a mailbox from a saved mailbox database.  The backup set is on tape and shows as expired, therefore it does not show up when selecting from the backup sets, and it is within the date range.  The backup set was duplicated to tape for long term storage.  I tried duplicating the backup set back to disk and changed the expiry date and ran a catalog over it.  It still does not show.  What am I missing?  Can the expiration date of the backup set on tape be changed? 

Thanks to all

Situation:

I am trying to restore from DAT tape.    I have no idea if the backups have been working or if there is anything on the tapes.

I have no idea if the version of Backup exec that the customer has on CD that I can use to reinstall is the same version that was used to backup the data.    i.e. dont know if the software has been upgraded on the server since it was originally installed from media. 

The version of BE that I have access to is 10d on a Server 2003 r2 x32 server.

When attempting to inventory -  the operation is succussful but it indicates that there is nothing on the tapes.   most of the tapes read "unknown media label"

I dont know if the version of BE that was used to backup, if a backup was even performed correctly for that matter, is the same as what i am using to restore.

I installed BE exec 2012.    2012 indicates that the media is scratch.

My question is:    It is an assumption that BE is not forward compatible, that is to say version 10d will not read 12.5, etc.   However,  what is the version backward compatibilty?   Can 2012 Read a tape that was backed up with 10d?    Upon attempting to install 2012 over 10d it indicated that an interum version be installed (v12) and that a direct  in place upgrade  from 10d to 2012 was not possible.

My goal is to see if in fact there is anything on any of the tapes.   How i get there, is not important.     At this point, it appears that in fact the backups have not been working.

Thanks in advance.

I am looking to update my LiveUpdate library to accomplish client updates to the latest version. I have read through the liveupdate guide, but didnt find it very useful. I have downloaded Netbackup_7.7.1_LU_1of2.tar.gz and Netbackup_7.7.1_LU_2of2.tar.gz. Am I supposed to merge these two files, upload them to the liveupdate directory on my server and simply gunzip/tar the contents? Am I supposed to remove all of the old client version files from there?

I am using Backup Exec 2014 - Server Version is 14.1 Rev. 1786 (64 Bit)

I created a backup job on a new server with the standard Full/Incremental backup set.

I did *not* select the Snapshot Option - that tab is completely blank.

When I run the job, I get:

- Snapshot Technology: Initialization failure on: "\\IGSBACEBGS017.gs.doi.net\Shadow?Copy?Components". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).

V-79-10000-11223 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot technology that you selected cannot snap this volume.  Some reasons for this could be:

- The snapshot provider that you selected does not support the volume that you are trying to snap.  Try selecting the default snapshot provider, and then run the job again.

 -A disk with a size greater than 63 terabytes or a 4K sector disk may exist on your computer. These types of disks can cause VSS to stop unexpectedly when it creates snapshot

This server is 72 Terrabytes (native) but with formatting and RAID it shows as a 60 TB drive.

The sector size is the standard 512.

How can I back up my share?  Doesn't Symantec Backup Exec work on large drives?  Why does it try to force the snapshot option even though it is not selected?

Thanks in advance for your help!!!

How can I troubleshoot network issue with Netbackup and Linux clients.

I have Netbackup 7.1 running on Windows Server 2008 backing up several Linux and Windows clients.

In one Linux client in particular the backup runs extremely slow. 5.5 TB data takes more than 60 hours to complete. Recently had error 41 and restarted the netbackup client services. Now even the daily backups with 16GB data takes 18 hours to complete.

In comparision another Linux client with 7.7 TB data takes only 22 hours to complete.

Both the clients are connected to the network through bonded 10G connection to the same switch and the Netbackup LTO5 drives are connected to the same switch through a 10G fiber channel.

Please advice how I can rectify this issue.

Thanks in advance.

Hello,

I have changed last week the robotic and tape unit from LTO4 to LTO6, LTO4 labels range stop to C20140L4 and LTO6 label start from C20200L6 

I have unloaded all tapes LTO4 from the robotic and then removed old Device/Drives & Robot and then configured the new robot with "Device Configuration Wizard", I have 

So this is the situation now is this:

New LTO6 tape are right in inventory and they are correctly picked up from scratch pool.

Now I want to try to restore some data from LTO4 tapes. I have loaded into robotic but when I try to inventory I get this error:

Of course C20132 and C20133 are already in inventory as HCART (used with the old robotic) but assigned to the volume group "---" which means to me is outside of robotic.

I have tryed to change the media type to '1/2" cartridge type' into Advanced Robot Inventory during the inventory of LTO4 in order to make the same type but error is the same.

What is the right procedure to manage old LTO4 tapes and restore data from LTO4 tape using the new LTO6 drivers and robotic?

I have recently updated my site to 7.7.1 and have noticed that the only client binaries installed were the ones for the version of the OS that the master server is running. In my case one is Solaris 10 and the other is Linux 6.7. At this time I am obviously unable to push out client updates from the master for any OS that the server is not running. I am pretty sure the solution to this is to install the client binaries that I have downloaded, but just wanted to be sure on the process. I have seen other posts and checked the guides.

I have Netbackup_7.7.1_CLIENTS1.tar.gz and Netbackup_7.7.1_CLIENTS2.tar.gz so from what I have seen is I just need to upload those two files, gunzip and tar them and then run the install or NB_install file to then start installing the binaries that I need. Once that is done I should then be able to see the files added in the correct directories under /usr/openv/netbackup/client and the version file should show the 7.7.1 NB version.

Also this process in no way interferes with what is already installed and running on the master correct? This is just updating the client data?

Hello Forum, 

Is there a way to not only disable a media server down for hardware repairs and redirect jobs to another media server ? 

I've tried the nbemmcmd command to disable the media server, but jobs that have policies configured for that specific media server still direct their jobs to it and error out with status still want to use it it fail with the expected status 58 (cannot connect to server):

# nbemmcmd -updatehost -machinename <Media Server> -machinestateop set_admin_pause -machinetype media -masterserver <Master Server>

NetBackup 7.6.0.3 running on Redhat Linux 2.6 Master with 4 media servers

Thanks

I have been trying to purchase a new Backup Exec agent license (SQL server) for the past month. My vendor is telling me that there is a backlog of license requests because of the split (Symantec/Vertias) and there is nothing he can do. Is anyone else having this issue? It seems ridiculous that it takes a month to purchase a license and needless to say I am not very happy about it.

Guys, can you help me to understand, what's happening with pc backup software in Symantec / Norton.

At first I had restore anywhere, then they retired it and I had to buy Ghost. Then Ghost got retired and they replaced it with System Recovery. About year or so they retired Sytem Recovery too.

There is Nothing now. I am trying to buy equivalent to Northon pc backup and can't find equivalent package.

What happened? not interested in selling software anymore?

Hi,

I am trying to create SRT on my boot server for RHEL.

I have been following the procedure in: NetBackup_7.6_AdminGuide_BMR.pdf (Creating a Linux SRT s. 74).

I have started bmrsrtadm and followed the steps .

I did provide BMR third-party products CD and Linux Installation media but I got stuck on the step: to provideNetBackup Client.

Where do I take it from ???

I thought it is already installed on me bootserver...

Any hints/advices ?

Hi All,

I have a BACKUP EXEC 12 on a old WS 2008 where I'm backuping without problem our EMC NAS VNXe3100 using NDMP.

Now I have got a new server WS12R2 where I installed BACKUP EXEC 15 to try if all works to make migration but I'M not able to backup our EMC NAS VNXe3100 using NDMP or also CIFS. My server is updated, my BCK EXEC 15 is updated and I also installed last firmware avalable for VNXE3100 (2.4.4.22283).

From network I'm able to see all shared folder.

My error are:

Errore finale: 0xe000fefd - La connessione di rete tra il server Backup Exec e Agent for Windows Φ stata interrotta

(Translation: Network connection between Backup Exec Server and Agent for Windows was interrupted)

Errore finale: 0xe000fe28 - Impossibile stabilire una connessione di rete al server. Categoria errore finale: Errori di processo

(Translation: Enable make a network connection to server)

Errore finale: 0xe000130b - L'operazione Φ stata interrotta nel server NDMP. Per ulteriori informazioni, vedere il registro NDMP.
(Translation: Operation was interrupted on NDMP server. For further informations, see NDMP registry)

Thanks a lot to everybody.

Regards.

Lorenzo

Hi,

After some serious disaster on BE15(latest patch), I managed to get the server running again. However I am facing a different issue. 

When I select the deduplication storage and select Backup Sets tab, I see "Load Failed... The queried backup sets contain two backup sets with the same ID." . This happened after I removed this member server from CASO environment.

I checked the catalog files and they are present. I also tried the "Catrebuildindex -r" method mentioned at the post "https://www-secure.symantec.com/connect/forums/duplicate-backup-sets-same-id". This had happened a couple of times when the server was a managed server in CASO environment but after a couple of F5, I was able to see the Backup Sets and even start restores.

Any ideas?

Hi All,

I have a BACKUP EXEC 12 on a old WS 2008 where I'm backuping without problem our EMC NAS VNXe3100 using NDMP.

Now I have got a new server WS12R2 where I installed BACKUP EXEC 15 to try if all works to make migration but I'm not able to backup our EMC NAS VNXe3100 using NDMP or also CIFS. My server is updated, my BCK EXEC 15 is updated and I also installed last firmware avalable for VNXE3100 (2.4.4.22283).

From network I'm able to see all shared folder.

My error are:

Errore finale: 0xe000fefd - La connessione di rete tra il server Backup Exec e Agent for Windows Φ stata interrotta

(Translation: Network connection between Backup Exec Server and Agent for Windows was interrupted)

Errore finale: 0xe000fe28 - Impossibile stabilire una connessione di rete al server. Categoria errore finale: Errori di processo

(Translation: Enable make a network connection to server)

Errore finale: 0xe000130b - L'operazione Φ stata interrotta nel server NDMP. Per ulteriori informazioni, vedere il registro NDMP.
(Translation: Operation was interrupted on NDMP server. For further informations, see NDMP registry)

Thanks a lot to everybody.

Regards.

Lorenzo

We recently upgraded to our Netbackup environment to 7.7.1 from 7.6.0.2. Our Master/Media server is running Solaris 10.We have 3 MSDP server running Linux 6.7. We have two VMware backup hosts. One is running on Windows Server 2012 and one is running on Linux 6.7. Since the upgrade we have been seeing delays on your vmware jobs finishing. Below is the detailed status from one of the jobs.

12/03/2015 07:27:31 - Info nbjm (pid=12665) starting backup job (jobid=4065889) for client xp33app324vm, policy Omaha_VMware2, schedule Incremental
12/03/2015 07:27:33 - estimated 60517362 kbytes needed
12/03/2015 07:27:33 - Info nbjm (pid=12665) started backup (backupid=xp33app324vm_1449149253) job for client xp33app324vm, policy Omaha_VMware2, schedule Incremental on storage unit XP53TAPE008 using backup host 53tape001.botw.ad.bankofthewest.com
12/03/2015 07:27:34 - started process bpbrm (pid=31069)
12/03/2015 07:27:36 - Info bpbrm (pid=31069) xp33app324vm is the host to backup data from
12/03/2015 07:27:36 - Info bpbrm (pid=31069) reading file list for client
12/03/2015 07:27:36 - Info bpbrm (pid=31069) accelerator enabled
12/03/2015 07:27:47 - Info bpbrm (pid=31069) starting bpbkar on client
12/03/2015 07:27:47 - connecting
12/03/2015 07:27:47 - connected; connect time: 0:00:00
12/03/2015 07:27:47 - Info bpbkar (pid=7528) Backup started
12/03/2015 07:27:47 - Info bptm (pid=31481) start
12/03/2015 07:27:47 - Info bpbrm (pid=31069) bptm pid: 31481
12/03/2015 07:27:47 - Info bpbkar (pid=7528) accelerator enabled backup, archive bit processing:<disabled>
12/03/2015 07:27:47 - Info bpbkar (pid=7528) INF - Backing up vCenter server 53apps178vm, ESX host v53host025.bankofthewest.com, BIOS UUID 423a4b04-5033-addb-78c4-0cd91879e9d8, Instance UUID 503a6afe-3ad9-3b17-c4ca-bea6a0aa782a, Display Name xp33app324vm, Hostname xp33app324vm
12/03/2015 07:27:48 - Info bptm (pid=31481) using 262144 data buffer size
12/03/2015 07:27:48 - Info bptm (pid=31481) using 30 data buffers
12/03/2015 07:27:56 - Info bptm (pid=31481) start backup
12/03/2015 07:41:20 - Info bptm (pid=31481) backup child process is pid 43416
12/03/2015 07:41:20 - begin writing
12/03/2015 07:42:23 - Info bpbkar (pid=7528) INF - Transport Type =  san
12/03/2015 07:45:26 - Info bpbkar (pid=7528) accelerator sent 305325056 bytes out of 51628610560 bytes to server, optimization 99.4%
12/03/2015 07:45:30 - Info bptm (pid=31481) waited for full buffer 44 times, delayed 3785 times
12/03/2015 08:42:34 - Info bptm (pid=31481) EXITING with status 0 <----------
12/03/2015 08:42:34 - Info xp53tape008 (pid=31481) StorageServer=PureDisk:xp53tape008; Report=PDDO Stats for (xp53tape008): scanned: 50424228 KB, CR sent: 63249 KB, CR sent over FC: 0 KB, dedup: 99.9%, cache disabled
12/03/2015 08:42:38 - Info bpbrm (pid=31069) validating image for client xp33app324vm
12/03/2015 08:42:39 - Info bpbkar (pid=7528) done. status: 0: the requested operation was successfully completed
12/03/2015 08:42:39 - end writing; write time: 1:01:19
the requested operation was successfully completed  (0)

The bptm logs on the MSDP servers have server of the below entries.

09:09:56.701 [26144] <16> 4065881:bptm:26144:xp53tape010: [ERROR] PDSTS: fbu_align_extents: (6134) stream_offset(48755712512) != extent.stream_offset=(48755033088)
09:09:56.717 [26144] <16> 4065881:bptm:26144:xp53tape010: [ERROR] PDSTS: fbu_align_extents: (6134) stream_offset(48756687872) != extent.stream_offset=(48755033088)

Has anyone seen this issue post upgrade? 

We recently have upgraded to version 7.7.1 and we are seeing some issues. Among other things we have noticed that when we try and cancel replication jobs...SLP items...they take hours to actually cancel out. We did this previously in version 7.6.0.2 in order to get them to rebundle and have less SLP replication jobs running and they would cancel out almost immediately. I am not sure where to go with this one to try and troubleshoot the issue, but it would be nice if cancelling a job would actually make it go away. Is there anything I should look for or a certain log that might help figure out what is causing the delay? Maybe a new SLP related setting that I am not aware of or something like that?

We are seeing delays in VMware backup jobs finishing after upgrading to Netbackup 7.7.1. We were on version 7.6.0.2 prior to the upgrade. Our master server is Solaris 10. We have 3 MSDP servers running Linux 6.7. We have two VMware backup host servers. One is running Windows Server 2012 and the other is running Linux 6.7. The VMware backups write to the MSDP servers. Any one of the three MSDP server can write to each others disk. The delay are causing other backups to fail, since they aren't able to run during their back windows. Below is the jobs details from one of the slow jobs. 

12/03/2015 08:39:37 - Info nbjm (pid=12665) starting backup job (jobid=4065919) for client sql53092vm, policy Omaha_VMware_SQL, schedule Incremental
12/03/2015 08:39:38 - estimated 38973558 kbytes needed
12/03/2015 08:39:38 - Info nbjm (pid=12665) started backup (backupid=sql53092vm_1449153577) job for client sql53092vm, policy Omaha_VMware_SQL, schedule Incremental on storage unit XP53TAPE008 using backup host 53tape001.botw.ad.bankofthewest.com
12/03/2015 08:39:38 - started process bpbrm (pid=40696)
12/03/2015 08:39:40 - Info bpbrm (pid=40696) sql53092vm is the host to backup data from
12/03/2015 08:39:40 - Info bpbrm (pid=40696) reading file list for client
12/03/2015 08:39:40 - Info bpbrm (pid=40696) accelerator enabled
12/03/2015 08:39:49 - connecting
12/03/2015 08:39:49 - connected; connect time: 0:00:00
12/03/2015 08:39:49 - Info bpbrm (pid=40696) starting bpbkar on client
12/03/2015 08:39:50 - Info bptm (pid=40986) start
12/03/2015 08:39:50 - Info bpbkar (pid=2844) Backup started
12/03/2015 08:39:50 - Info bpbrm (pid=40696) bptm pid: 40986
12/03/2015 08:39:50 - Info bpbkar (pid=2844) accelerator enabled backup, archive bit processing:<disabled>
12/03/2015 08:39:50 - Info bpbkar (pid=2844) INF - Backing up vCenter server 53apps178vm, ESX host v53host030.bankofthewest.com, BIOS UUID 42045880-2f95-1fee-fa56-4f3c65d4164a, Instance UUID 50049e93-61b0-0ab2-3f5b-b141cb28f6a1, Display Name sql53092vm, Hostname SQL53092VM.botw.ad.bankofthewest.com
12/03/2015 08:39:51 - Info bptm (pid=40986) using 262144 data buffer size
12/03/2015 08:39:51 - Info bptm (pid=40986) using 30 data buffers
12/03/2015 08:39:55 - Info bptm (pid=40986) start backup
12/03/2015 08:40:25 - Info bptm (pid=40986) backup child process is pid 41677
12/03/2015 08:40:25 - begin writing
12/03/2015 08:40:34 - Info bpbkar (pid=2844) INF - Transport Type =  san
12/03/2015 08:47:19 - Info bptm (pid=40986) waited for full buffer 2 times, delayed 148 times
12/03/2015 08:47:21 - Info bpbkar (pid=2844) accelerator sent 717710848 bytes out of 33181077504 bytes to server, optimization 97.8%
12/03/2015 10:10:23 - Info bptm (pid=40986) EXITING with status 0 <----------
12/03/2015 10:10:23 - Info xp53tape009 (pid=40986) StorageServer=PureDisk:xp53tape008; Report=PDDO Stats for (xp53tape008): scanned: 32406122 KB, CR sent: 142286 KB, CR sent over FC: 0 KB, dedup: 99.6%, cache disabled
12/03/2015 10:10:29 - Info bpbrm (pid=40696) validating image for client sql53092vm
12/03/2015 10:10:30 - Info bpbkar (pid=2844) done. status: 0: the requested operation was successfully completed
12/03/2015 10:10:30 - end writing; write time: 1:30:05
the requested operation was successfully completed  (0)

We are seeing the below error in the bptm logs. 

09:09:55.303 [26144] <16> 4065881:bptm:26144:xp53tape010: [ERROR] PDSTS: fbu_align_extents: (6130) stream_offset(48750986240) != extent.stream_offset=(48750957568)
09:09:56.701 [26144] <16> 4065881:bptm:26144:xp53tape010: [ERROR] PDSTS: fbu_align_extents: (6134) stream_offset(48755704832) != extent.stream_offset=(48755033088)
09:09:56.701 [26144] <16> 4065881:bptm:26144:xp53tape010: [ERROR] PDSTS: fbu_align_extents: (6134) stream_offset(48755712512) != extent.stream_offset=(48755033088)
09:09:56.717 [26144] <16> 4065881:bptm:26144:xp53tape010: [ERROR] PDSTS: fbu_align_extents: (6134) stream_offset(48756687872) != extent.stream_offset=(48755033088)

Has anyone experience the above issue? 

I am running backup exec 2014 and i am trying to restore a file from a backup to a VM on one of its network drives. The backups work great, but i tested the restore and get this every time " The backup exec server was unable to connect to remote machine (null) becuase a network interface mating the selected bakcup via netowrk parameters could not be found." 

We are having an issue which might be related to the service account NBU is using for backups and restores. How do I find out what the service account is that NBU is using?