I can't begin to tell you how frustrating this one is.

If a backup job targets a storage pool, and has to split a backup set into multiple "spans" across multiple members, the only place the backup set appears is under the member containing first span.

Even if the first span is in B2D folder A and all of the rest are in B2D folder B, the backup set appears only in the Backup Sets list of B2D folder A.   It makes it impossible to track how the folders are filling up.

The backup set should appear under BOTH devices, or alternatively, only under in a backup set list for the storage pool (which isn't a feature of the GUI yet).

Also, under any one device, the set should appear once.  There is a problem with each span appearing as an individual entry in the list and all of the entries are identical.  In one case, I have to wade through one backup set's 90+ indistinguishable entries in the list to locate a single-span backup set

That problem was once fixed but came back.

I was able to create a SQL Server query directly on the Backup Exec BEDB to see what I want, but I shouldn't have to do that.

Hi fellows,

I have a tape library (i6000) with both LTO4 and LTO5 tape drives, and I am using NetBackup (v7.5.0.6) to manage the tape drive cleaning. At the moment I only have tapes with labels such as, "CLN001". I have created a barcode rule for them, using HC2_CLN as media type, so they are able to clean the LTO5 tape drives.

Is there a way for me to use the same tapes (same label format CLNxxx) to clean the LTO4 drives? I know I have to use a different media type, but do I have to find new labels for them?

Every time that you swap tapes, you need to inventory a stand-alone drive or the slot in a library that has changed for the Tape to be detected.

Is their any way to make it auto.

Am using IBM IBM ULTRIUM-HH5 tape drive with Symantech Backup Exe 2012 Sp3.

How to create a single MS-SQL-Server NetBackup policy which contains multiple schedules with different retention levels on caleder schedule.

1- I want to add calendar schedule only.

2- 1st of every months backup shd have 1 year retention.

3- rest days of months retention shd be 3 weeks retention.

Hi All,

I would like to share a problem we have with one of our Windows 2008 backups and see if anyone has encountered a similar problem and if possable find a resolution.

Servers Involved:-

NBU Matser - HPUX 11.31 - NBU7504

Client - Windows 2008 x64 - NBU7507

Media server - Symantec 5220 Appliance - NBU 7506

The policy is using dedupe with accelerator and change journal - ALL_LOCAL_DRIVES (the D: drive is the problem drive)

A FULL once every 4 weeks (D: drive has 1.1 tb of data) then DIFFS daily (The Diffs are usually between 10 and 30 gigs and usually takes between 2 to 4 hours to complete)

Problem:-

Every so often the DIFF backup decides to backup 500 to 800 gigs of data and taking 10 to 20 hours to complete.

Anti virus is off during the backups and there appear not to have been any invasive maintenance (ie defraggs or data moves etc ) prior to the DIFFs going large.

We have had many calls logged with support and none have really identified the problem.

The latest was to upgrade to NBU7507 (Which we have done on the client) and this improved matters with the occurance of the BIG DIFFS being reduced drastically in frequency.

Our long term aim is to upgrade to NBU7601 but we are several weeks away from this.

Has anyone encountered a similar behaviour or is there anything that we could check or look into.

Regards

Paul

Hi,
 We backup to disk and I'm missing one of the .bkf's listed in a backup job log (there are 5, but one is missing).

 Is there any way, using Backup Exec 2012, to recover data from the remaining 4 .bkf files?

Thanks!

We have one NBU Master on 7.0.X version and we are building another on 7.5.X . We need to merge the catalog of 7.0.X into the new Catalog Data Base of 7.5.X .

Clients from 7.0.X will be moving to the 7.5.X Master and until the last client is not migrated both the masters will be in active active configuration . Hence both will be having active images . We need to merge the catalogs as the 7.0.X will be decommisioned as that is lying with the incumbent and we will get the older catalog of images to restore the historical data . [ Only objective of 7.0.x Data to be bought is to keep historical data intact as they have large number of long retention backups which will be having active images for a longer duration ]

Now challenges :

1) Both the servers will have different names so do we need to keep the same names while merging the catalog ?

2) IP's Should be the same or not ? I feel IP's can be dynamic .

3) Recovery without Import is another procedure but I am not sure will it help me or not [ No clue how it is performed ]

4) Last resort to get Support from Symantec Consulting to get this done ;)

TIA

Abby !

As the 52xx Appliances do not support iSCSI attach I am just wondering what is seen as best practice for securing VMware data when the datastores reside on an iSCSI attached SAN.

I guess there are two options:

1. Create 1 or more VMware Proxy Backup Servers (Hot-Add) within the ESX environment

2. Install 1 or more physical Proxy Backup Servers (Hot-Add) which have an iSCSI connection to the SAN

Are there any more preferable ways to do this, or if not which of the above is best in terms of functionality and performance ?

Thanks,

AJ.

Hi All,

We are planning to upgrade some master servers that are running currently on 6.5. We want to upgrade it to 7.5.

These are clustered Master servers(Solaris).

Please share some step by step instruction to upgrade process.

We don't have any media servers . Master itself acting as a media server.

I had got several pdf documents for the upgrade process. But it would be great if some of you can share some handy Notes that i can refer in upgrade process.

Thanks in Advance

I recently started having a problem where all the tapes export randomly from the ML6000. It has two partitions. I have Backup Exec 2012 (Backup Exec Server Version 14.0 Rev. 1798 [64 bit]) on Windows 2008 R2 Standard. It started doing this with SP2 so I upgraded to SP4 and it still occurs. I have tried deleting the export job and re-adding, that didn't work. I had thought that was causing it but found that during the backup job that the tapes were exported. Any ideas? Or, do I have to get with the ML6000 vendor?

Thanks,

John

I need some assistance.
We are thinking to upgrade our vCenter from a Windows machines, to the vCenter Virtual Appliance, which runs on Linux.
Do you think Netbackup will still work, if we decide to use the Linux based virtual appliance.
Any thoughts or views would be appreciated.

I need some help with a future change in our domain. Actually we are using production network to do client backups.

All clients and media servers are using production domain FQDNs, in order to avoid network congestion during backups we are going to use a new domain (xxx.backup) and all the backups should be done using this new network.

Here are my thoughts:

  -In order to restore clients, I think I can manage it as stated in https://www-secure.symantec.com/connect/forums/can-netbackup-merge-client-data-new-name . I mean, We need to change client´s bp.conf file for backups and for restores use the altpath or the relinking method.

 -About media servers, I have the following doubt:

                -Should I keep the same name in the emm and add a new alias for the server plus configuring network routes in order to force the backup traffic to use the backup interface?

 -About the change in our master server I´m very worried. We have two master servers acting as an active/passive cluster using VCS. Virtual name is NOT using FQDN name (let´s say is called "netbackup") but cluster members name are like "servername.domain.com". Do we need Symantec professional services or we can go ahead as netbackup is not using the FQDN??

Maybe none of this is necessary and just configure the REQUIRED_INTERFACE property in all bp.conf files as we are going to keep the current domain infrastructure.

How to expand deduplication storage size with backup exec 2012 

Dear Experts and Symantecians,

Kindly let me know when will Netbackup support for vmware ESX 5.5 will be available. As of today it is not. I have checked the compatibility list.

Regards,

Hi, 

I'm having some issues installing Backup Exec 2012 on HP OEM Windows Server 2012? I am faced with this error " You cannot install a Backup Exec Server or remote Administratior on a Windows 8/Server 2012 computer. 

Ive searched a load of forums and they all indicate that it is compatibility issues. But I dont understand as I have installed Backup Exec 2012 version 14.0 on Windows Server 2012 Standard before. 

The only real differences between the installs is, the successfull install was installed using CD and the failing install i am using ISO which was downloaded. 

Can anyone shed some light on this at all?

Hello Everybody!!

I would like to know if somebody has faced this: 

We are configuring a Netbackup clustered server and it has worked during a failover. During a reboot of the active node  the netbackup servers failed over to the second node. the first node rebooted well but when we try to move the netbackup server services to the first node we have faced whit this message under the cluster log:

3:34:10.978 [5908] <4> NBClusterApp::runCommand: Entering, with command:/usr/openv/netbackup/bin/goodies/netbackup start

13:34:11.082 [5908] <4> NBClusterApp::runCommand: NetBackup Authentication daemon started.

13:34:11.143 [5908] <4> NBClusterApp::runCommand: NetBackup network daemon started.

13:34:11.188 [5908] <4> NBClusterApp::runCommand: NetBackup client daemon started.

13:34:12.221 [5908] <4> NBClusterApp::runCommand: NetBackup SAN Client Fibre Transport daemon started.

13:34:13.975 [5908] <4> NBClusterApp::runCommand: NetBackup Database Server started.

13:34:14.011 [5908] <4> NBClusterApp::runCommand: NetBackup Authorization daemon started.

13:34:14.715 [5908] <4> NBClusterApp::runCommand: NetBackup Event Manager started.

13:34:15.526 [5908] <4> NBClusterApp::runCommand: NetBackup Audit Manager started.

13:34:20.706 [5908] <4> NBClusterApp::runCommand: NetBackup Deduplication Manager started.

13:34:30.878 [5908] <4> NBClusterApp::runCommand: NetBackup Deduplication Engine started.

13:34:31.608 [5908] <4> NBClusterApp::runCommand: NetBackup Enterprise Media Manager started.

13:34:32.171 [5908] <4> NBClusterApp::runCommand: NetBackup Resource Broker started.

13:34:32.768 [5908] <4> NBClusterApp::runCommand: Media Manager daemons started.

13:34:33.693 [5908] <4> NBClusterApp::runCommand: NetBackup request daemon started.

13:34:34.080 [5908] <4> NBClusterApp::runCommand: NetBackup compatibility daemon started.

13:34:34.588 [5908] <4> NBClusterApp::runCommand: NetBackup Job Manager started.

13:34:35.373 [5908] <4> NBClusterApp::runCommand: NetBackup Policy Execution Manager started.

13:34:36.079 [5908] <4> NBClusterApp::runCommand: NetBackup Storage Lifecycle Manager started.

13:34:36.788 [5908] <4> NBClusterApp::runCommand: NetBackup Indexing Manager started.

13:34:37.612 [5908] <4> NBClusterApp::runCommand: NetBackup Remote Monitoring Management System started.

13:34:38.263 [5908] <4> NBClusterApp::runCommand: NetBackup Key Management daemon started.

13:34:39.286 [5908] <4> NBClusterApp::runCommand: NetBackup Service Layer started.

13:34:40.215 [5908] <4> NBClusterApp::runCommand: NetBackup Agent Request Server started.

13:34:40.933 [5908] <4> NBClusterApp::runCommand: NetBackup Bare Metal Restore daemon started.

13:34:41.446 [5908] <4> NBClusterApp::runCommand: NetBackup Vault daemon started.

13:34:41.509 [5908] <4> NBClusterApp::runCommand: NetBackup CloudStore Service Container started.

13:34:41.766 [5908] <4> NBClusterApp::runCommand: VCS 

13:34:41.784 [5908] <4> NBClusterApp::runCommand: NetBackup Service Monitor started.

13:34:41.963 [5908] <4> NBClusterApp::runCommand: NetBackup Bare Metal Restore Boot Server daemon started.

13:34:41.964 [5908] <4> NBClusterApp::runCommand: Exiting

13:34:41.964 [5908] <4> NBClusterApp::startApp: Exiting

13:34:41.964 [5908] <4> Online::main: Starting Application completed with status 0. 

13:34:43.176 [6241] <16> monitor:processStatus: Some Processes are DOWN while others are UP

13:34:43.176 [6241] <16> monitor:processStatus: Following Process are found DOWN: nbevtmgr nbstserv nbpem nbjm nbaudit nbsl nbrmms nbemm nbrb 

13:34:43.176 [6241] <16> monitor:processStatus: Following Process are found UP: vmd bprd bpdbm NB_dbsrv 

13:35:43.606 [6412] <16> monitor:processStatus: Some Processes are DOWN while others are UP

13:35:43.606 [6412] <16> monitor:processStatus: Following Process are found DOWN: nbevtmgr nbstserv nbpem nbjm nbaudit nbsl nbrmms nbemm nbrb 

13:35:43.606 [6412] <16> monitor:processStatus: Following Process are found UP: vmd bprd bpdbm NB_dbsrv 

13:36:43.814 [6599] <16> monitor:processStatus: Some Processes are DOWN while others are UP

13:36:43.815 [6599] <16> monitor:processStatus: Following Process are found DOWN: nbevtmgr nbstserv nbpem nbjm nbaudit nbsl nbrmms nbemm nbrb 

13:36:43.815 [6599] <16> monitor:processStatus: Following Process are found UP: vmd bprd bpdbm NB_dbsrv 

13:36:44.442 [6615] <4> Offline::main: Offline called with 2 Parameters

13:36:44.442 [6615] <4> Offline::main: Initializing NBCluster using /usr/openv/netbackup/bin/cluster/NBU_RSP file

13:36:44.443 [6615] <4> NBClusterApp::stopApp: Executing Command : /usr/openv/netbackup/bin/bpclusterkill -forcekill -timeout 120 15,TERM -verbose

13:36:44.839 [6616] <4> standard_shutdown: 

13:36:44.839 [6616] <4> standard_shutdown: Looking for NetBackup processes that need to be terminated.

13:36:44.849 [6616] <4> standard_shutdown: Stopping nbcssc...

13:36:44.936 [6616] <4> standard_shutdown: Suspending or cancelling selective jobs...

13:36:46.106 [6616] <4> standard_shutdown: Stopping bprd...

13:37:06.140 [6616] <4> standard_shutdown: Stopping bpcompatd...

13:37:06.302 [6616] <4> standard_shutdown: Stopping bpdbm...

13:37:11.862 [6616] <4> standard_shutdown: 

13:37:11.863 [6616] <4> standard_shutdown: The following processes are still active

13:37:11.865 [6616] <4> standard_shutdown:     root  6258     1   0 13:34:56 ?           0:01 /usr/openv/netbackup/bin/admincmd/bpstsinfo -UPDATE

13:37:11.865 [6616] <4> standard_shutdown:     root  6145     1   0 13:34:35 ?           0:00 /usr/openv/netbackup/bin/bpdbm

13:37:11.867 [6616] <4> standard_shutdown:  They will be terminated....

13:37:11.869 [6616] <4> standard_shutdown: Killing remaining processes...

13:37:11.989 [6616] <4> standard_shutdown: 

13:37:11.990 [6616] <4> standard_shutdown: Looking for Media Manager processes that need to be terminated.

13:37:11.994 [6616] <4> standard_shutdown: Stopping ltid...

13:38:45.000 [6616] <2> standard_shutdown: /usr/openv/netbackup/bin/bp.kill_all FORCEKILL  2>&1 < /dev/null has been running for 121 seconds.  Timing out.

13:38:45.000 [6616] <16> bpclusterkill main: standard_shutdown() failed: 76.

13:39:00.001 [6616] <2> find_processes: total malloc-ed = 4096

13:39:00.012 [6616] <2> get_solaris_processes: 121 files considered, 119 files opened/read

13:39:00.012 [6616] <2> find_processes: progs_list_size = 4096 == total calculated size = 4096 == (total_space_used = 404 + whats_left = 3692)

13:39:00.013 [6616] <2> find_processes: realloc down to 404

13:39:00.013 [6616] <2> kill_process: PID 5925 /usr/openv/netbackup/bin/vnetd -standalone killed by signal 15.

13:39:00.013 [6616] <2> kill_process: PID 5985 /usr/openv/db//bin/NB_dbsrv @/usr/openv/var/global/server.conf @/usr/openv/var/ killed by signal 15.

13:39:00.013 [6616] <2> kill_process: PID 6101 vmd  killed by signal 15.

13:39:00.013 [6616] <2> kill_process: PID 5928 /usr/openv/netbackup/bin/bpcd -standalone killed by signal 15.

13:39:02.013 [6616] <2> find_processes: total malloc-ed = 4096

13:39:02.019 [6616] <2> get_solaris_processes: 118 files considered, 116 files opened/read

13:39:02.019 [6616] <2> find_processes: progs_list_size = 4096 == total calculated size = 4096 == (total_space_used = 140 + whats_left = 3956)

13:39:02.019 [6616] <2> find_processes: realloc down to 140

13:39:02.019 [6616] <8> kill_stragglers: Process 5985 /usr/openv/db//bin/NB_dbsrv @/usr/openv/var/global/server.conf @/usr/openv/var/ still running.

13:39:02.019 [6616] <8> kill_stragglers: 1 processes still running.

13:39:02.019 [6616] <16> bpclusterkill main: kill_stragglers() failed: 11.

13:39:12.229 [6616] <4> bpclusterkill main: Stopping vmd...

13:39:32.476 [6616] <4> bpclusterkill main: 

13:39:32.476 [6616] <4> bpclusterkill main: Looking for more NetBackup processes that need to be terminated.

13:39:37.601 [6616] <4> bpclusterkill main: Shutdown command completed with status 0.

13:39:37.606 [6615] <4> NBClusterApp::stopApp: returning status : 2816

13:39:37.606 [6615] <4> NBClusterApp::deleteLinks: Entering

13:39:37.607 [6615] <4> NBClusterApp::deleteLinks: Removing link /usr/openv/volmgr/misc/robotic_db

13:39:37.607 [6615] <4> NBClusterApp::deleteLinks: Removing link /usr/openv/netbackup/db

13:39:37.607 [6615] <4> NBClusterApp::deleteLinks: Removing link /usr/openv/netbackup/vault/sessions

13:39:37.608 [6615] <4> NBClusterApp::deleteLinks: Removing link /usr/openv/var/global

13:39:37.608 [6615] <4> NetBackupApp::postOffline: Entering

13:39:37.608 [6615] <4> NBClusterApp::runCommand: Entering, with command:/usr/openv/netbackup/bin/vnetd -standalone

13:39:37.656 [6615] <4> NBClusterApp::runCommand: Exiting

13:39:37.656 [6615] <4> NBClusterApp::runCommand: Entering, with command:/usr/openv/netbackup/bin/bpcd -standalone

13:39:37.709 [6615] <4> NBClusterApp::runCommand: Exiting

13:39:37.709 [6615] <4> NBClusterApp::stopApp: Exiting

13:39:37.709 [6615] <4> Offline::main: Stop completed with status 99. 

we have been successfully backing up our EV environment every weekend using back up exec 2010 r3

the back up job goes through verification stage but finishes with an error

"Full_EVBackup -- The job failed with the following error: Backup Exec cannot place the Enterprise Vault vault stores or index locations into backup mode. Ensure that the selection is valid for a backup operation, and then try the job again."

so far I have restarted backup exec services and retried job but i get the same error

can anybody assist

thanks

Lois

Hello Everyone ,

    I was looking for using Netbackup to backup multi-tenant environment. The environment was build on OVM so there is no agent from NB to support it. I don't have any problem to treat each VM as a client. However , I need to have each environment totally seperated as this is multi-tenant and security purposes.

1- Can I use multiple Master servers with the same EMM server? if I will do that , is it supported ? How the licencing will work in that case?

2- If the first point is not supported. what is the proposed solutions to implement backup for multi-tenant environment and completely seperate them?

Thanks in advance.

Is be2012 allow mult-session parallel backup how it affetc the performance if paralledl run on same subet sinle interface ? any reference?