Has anyone else experienced this?

03/23/2015 10:58:07 - begin Duplicate
03/23/2015 10:58:08 - Info Duplicate (pid=20650) Initiating optimized duplication from @aaaal to @aaaa5
03/23/2015 10:58:08 - requesting resource stu_disk_alxaptb50xs
03/23/2015 10:58:08 - reserving resource @aaaal
03/23/2015 10:58:08 - resource @aaaal reserved
03/23/2015 10:58:08 - granted resource MediaID=@aaaa5;DiskVolume=PureDiskVolume;DiskPool=dp_disk_alxaptb50xs;Path=PureDiskVolume;StorageServer=alxaptb50xs;MediaServer=alxaptb50xs
03/23/2015 10:58:08 - granted resource stu_disk_alxaptb50xs
03/23/2015 10:58:08 - requesting resource @aaaal
03/23/2015 10:58:08 - granted resource MediaID=@aaaal;DiskVolume=PureDiskVolume;DiskPool=MSDP_BHM;Path=PureDiskVolume;StorageServer=alxaptb71xs;MediaServer=alxaptb50xs
03/23/2015 10:58:09 - Info bpdm (pid=31779) started
03/23/2015 10:58:09 - started process bpdm (pid=31779)
03/23/2015 10:58:09 - Info bpdm (pid=31779) requesting nbjm for media
03/23/2015 10:58:16 - begin writing
03/23/2015 10:58:16 - end writing; write time: 0:00:00
03/23/2015 10:58:16 - begin writing
03/23/2015 10:58:16 - end writing; write time: 0:00:00
03/23/2015 10:58:16 - begin writing
03/23/2015 10:58:16 - end writing; write time: 0:00:00
03/23/2015 10:58:17 - begin writing
03/23/2015 10:58:17 - end writing; write time: 0:00:00
03/23/2015 10:58:17 - begin writing
03/23/2015 10:58:17 - end writing; write time: 0:00:00
03/23/2015 10:58:17 - begin writing
03/23/2015 10:58:17 - end writing; write time: 0:00:00
03/23/2015 10:58:18 - begin writing
03/23/2015 10:58:18 - end writing; write time: 0:00:00
03/23/2015 10:58:18 - begin writing
03/23/2015 10:58:18 - end writing; write time: 0:00:00
03/23/2015 10:58:19 - begin writing
03/23/2015 10:58:19 - end writing; write time: 0:00:00
03/23/2015 10:58:19 - begin writing
03/23/2015 10:58:19 - end writing; write time: 0:00:00
03/23/2015 10:58:19 - begin writing
03/23/2015 10:58:19 - end writing; write time: 0:00:00
03/23/2015 10:58:19 - begin writing
03/23/2015 10:58:19 - end writing; write time: 0:00:00
03/23/2015 10:58:20 - begin writing
03/23/2015 10:58:20 - end writing; write time: 0:00:00
03/23/2015 10:58:20 - begin writing
03/23/2015 10:58:20 - end writing; write time: 0:00:00
03/23/2015 10:58:20 - begin writing
03/23/2015 10:58:20 - end writing; write time: 0:00:00
03/23/2015 10:58:21 - begin writing
03/23/2015 10:58:21 - end writing; write time: 0:00:00
03/23/2015 10:58:21 - begin writing
03/23/2015 10:58:21 - Info bpdm (pid=31779) Creating OPT_DUP_END marker
03/23/2015 11:54:21 - end writing; write time: 0:56:00
03/23/2015 11:54:21 - Info bpdm (pid=31779) EXITING with status 0
03/23/2015 11:54:21 - Info alxaptb50xs (pid=31779) StorageServer=PureDisk:alxaptb71xs; Report=PDDO Stats for (alxaptb71xs): scanned: 490765781 KB, CR sent: 324247469 KB, CR sent over FC: 0 KB, dedup: 33.9%, cache disabled
03/23/2015 11:54:21 - requesting resource @aaaal
03/23/2015 11:54:22 - granted resource MediaID=@aaaal;DiskVolume=PureDiskVolume;DiskPool=MSDP_BHM;Path=PureDiskVolume;StorageServer=alxaptb71xs;MediaServer=alxaptb50xs
03/23/2015 11:54:24 - Info bpdm (pid=5766) started
03/23/2015 11:54:24 - started process bpdm (pid=5766)
03/23/2015 11:54:24 - Info bpdm (pid=5766) requesting nbjm for media
03/23/2015 11:54:32 - begin writing
03/23/2015 11:54:32 - end writing; write time: 0:00:00
03/23/2015 11:54:32 - begin writing
03/23/2015 11:54:33 - Info bpdm (pid=5766) Creating OPT_DUP_END marker
03/23/2015 11:55:33 - end writing; write time: 0:01:01
03/23/2015 11:55:33 - Info bpdm (pid=5766) EXITING with status 0
03/23/2015 11:55:33 - Info alxaptb50xs (pid=5766) StorageServer=PureDisk:alxaptb71xs; Report=PDDO Stats for (alxaptb71xs): scanned: 383 KB, CR sent: 70 KB, CR sent over FC: 0 KB, dedup: 81.7%, cache disabled
03/23/2015 11:55:33 - Info bpdm (pid=5801) started
03/23/2015 11:55:33 - started process bpdm (pid=5801)
03/23/2015 11:55:33 - Info bpdm (pid=5801) requesting nbjm for media
03/23/2015 11:55:33 - requesting resource @aaaal
03/23/2015 11:55:33 - granted resource MediaID=@aaaal;DiskVolume=PureDiskVolume;DiskPool=MSDP_BHM;Path=PureDiskVolume;StorageServer=alxaptb71xs;MediaServer=alxaptb50xs
03/23/2015 11:55:39 - begin writing
03/23/2015 11:55:39 - end writing; write time: 0:00:00
03/23/2015 11:55:40 - begin writing
03/23/2015 11:55:40 - end writing; write time: 0:00:00
03/23/2015 11:55:40 - begin writing
03/23/2015 11:55:40 - end writing; write time: 0:00:00
03/23/2015 11:55:41 - begin writing
03/23/2015 11:55:41 - Info bpdm (pid=5801) Creating OPT_DUP_END marker
03/23/2015 12:03:41 - end writing; write time: 0:08:00
03/23/2015 12:03:41 - Info bpdm (pid=5801) EXITING with status 0
03/23/2015 12:03:41 - Info alxaptb50xs (pid=5801) StorageServer=PureDisk:alxaptb71xs; Report=PDDO Stats for (alxaptb71xs): scanned: 77092813 KB, CR sent: 25514520 KB, CR sent over FC: 0 KB, dedup: 66.9%, cache disabled
03/23/2015 12:03:41 - Info bpdm (pid=7034) started
03/23/2015 12:03:41 - started process bpdm (pid=7034)
03/23/2015 12:03:41 - requesting resource @aaaal
03/23/2015 12:03:41 - granted resource MediaID=@aaaal;DiskVolume=PureDiskVolume;DiskPool=MSDP_BHM;Path=PureDiskVolume;StorageServer=alxaptb71xs;MediaServer=alxaptb50xs
03/23/2015 12:03:42 - Info bpdm (pid=7034) requesting nbjm for media
03/23/2015 12:03:48 - begin writing
03/23/2015 12:03:48 - end writing; write time: 0:00:00
03/23/2015 12:03:48 - begin writing
03/23/2015 12:03:48 - Info bpdm (pid=7034) Creating OPT_DUP_END marker
03/23/2015 12:04:48 - end writing; write time: 0:01:00
03/23/2015 12:04:48 - Info bpdm (pid=7034) EXITING with status 0
03/23/2015 12:04:48 - Info alxaptb50xs (pid=7034) StorageServer=PureDisk:alxaptb71xs; Report=PDDO Stats for (alxaptb71xs): scanned: 5 KB, CR sent: 3 KB, CR sent over FC: 0 KB, dedup: 40.0%, cache disabled
03/23/2015 12:04:48 - requesting resource @aaaal
03/23/2015 12:04:48 - granted resource MediaID=@aaaal;DiskVolume=PureDiskVolume;DiskPool=MSDP_BHM;Path=PureDiskVolume;StorageServer=alxaptb71xs;MediaServer=alxaptb50xs
03/23/2015 12:04:49 - Info bpdm (pid=7210) started
03/23/2015 12:04:49 - started process bpdm (pid=7210)
03/23/2015 12:04:49 - Info bpdm (pid=7210) requesting nbjm for media
03/23/2015 12:04:55 - begin writing
03/23/2015 12:04:55 - end writing; write time: 0:00:00
03/23/2015 12:04:56 - begin writing
03/23/2015 12:04:56 - Info bpdm (pid=7210) Creating OPT_DUP_END marker
03/23/2015 12:05:56 - end writing; write time: 0:01:00
03/23/2015 12:05:56 - Info bpdm (pid=7210) EXITING with status 0
03/23/2015 12:05:56 - Info alxaptb50xs (pid=7210) StorageServer=PureDisk:alxaptb71xs; Report=PDDO Stats for (alxaptb71xs): scanned: 21472 KB, CR sent: 5880 KB, CR sent over FC: 0 KB, dedup: 72.6%, cache disabled
03/23/2015 12:05:56 - requesting resource @aaaal
03/23/2015 12:05:56 - granted resource MediaID=@aaaal;DiskVolume=PureDiskVolume;DiskPool=MSDP_BHM;Path=PureDiskVolume;StorageServer=alxaptb71xs;MediaServer=alxaptb50xs
03/23/2015 12:05:56 - Info bpdm (pid=7267) started
03/23/2015 12:05:56 - started process bpdm (pid=7267)
03/23/2015 12:05:57 - Info bpdm (pid=7267) requesting nbjm for media
03/23/2015 12:06:02 - begin writing
03/23/2015 12:06:02 - end writing; write time: 0:00:00
03/23/2015 12:06:03 - begin writing
03/23/2015 12:06:03 - Info bpdm (pid=7267) Creating OPT_DUP_END marker
03/23/2015 12:07:03 - end writing; write time: 0:01:00
03/23/2015 12:07:03 - Info bpdm (pid=7267) EXITING with status 0
03/23/2015 12:07:03 - Info alxaptb50xs (pid=7267) StorageServer=PureDisk:alxaptb71xs; Report=PDDO Stats for (alxaptb71xs): scanned: 490020 KB, CR sent: 148262 KB, CR sent over FC: 0 KB, dedup: 69.7%, cache disabled
03/23/2015 12:07:03 - Info bpdm (pid=7349) started
03/23/2015 12:07:03 - started process bpdm (pid=7349)
03/23/2015 12:07:03 - requesting resource @aaaal
03/23/2015 12:07:03 - granted resource MediaID=@aaaal;DiskVolume=PureDiskVolume;DiskPool=MSDP_BHM;Path=PureDiskVolume;StorageServer=alxaptb71xs;MediaServer=alxaptb50xs
03/23/2015 12:07:04 - Info bpdm (pid=7349) requesting nbjm for media
03/23/2015 12:07:10 - begin writing
03/23/2015 12:07:10 - end writing; write time: 0:00:00
03/23/2015 12:07:10 - begin writing
03/23/2015 12:07:11 - Info bpdm (pid=7349) Creating OPT_DUP_END marker
03/23/2015 12:08:11 - end writing; write time: 0:01:01
03/23/2015 12:08:11 - Info bpdm (pid=7349) EXITING with status 0
03/23/2015 12:08:11 - Info alxaptb50xs (pid=7349) StorageServer=PureDisk:alxaptb71xs; Report=PDDO Stats for (alxaptb71xs): scanned: 402 KB, CR sent: 69 KB, CR sent over FC: 0 KB, dedup: 82.8%, cache disabled
03/23/2015 12:08:11 - Info bpdm (pid=7385) started
03/23/2015 12:08:11 - started process bpdm (pid=7385)
03/23/2015 12:08:11 - Info bpdm (pid=7385) requesting nbjm for media
03/23/2015 12:08:11 - requesting resource @aaaal
03/23/2015 12:08:11 - granted resource MediaID=@aaaal;DiskVolume=PureDiskVolume;DiskPool=MSDP_BHM;Path=PureDiskVolume;StorageServer=alxaptb71xs;MediaServer=alxaptb50xs
03/23/2015 12:08:17 - begin writing
03/23/2015 12:08:17 - end writing; write time: 0:00:00
03/23/2015 12:08:17 - begin writing
03/23/2015 12:08:17 - end writing; write time: 0:00:00
03/23/2015 12:08:18 - begin writing
03/23/2015 12:08:18 - end writing; write time: 0:00:00
03/23/2015 12:08:18 - begin writing
03/23/2015 12:08:18 - end writing; write time: 0:00:00
03/23/2015 12:08:18 - begin writing
03/23/2015 12:08:18 - end writing; write time: 0:00:00
03/23/2015 12:08:18 - begin writing
03/23/2015 12:08:18 - end writing; write time: 0:00:00
03/23/2015 12:08:19 - begin writing
03/23/2015 12:08:19 - end writing; write time: 0:00:00
03/23/2015 12:08:19 - begin writing
03/23/2015 12:08:19 - end writing; write time: 0:00:00
03/23/2015 12:08:19 - begin writing
03/23/2015 12:08:19 - end writing; write time: 0:00:00
03/23/2015 12:08:20 - begin writing
03/23/2015 12:08:20 - Info bpdm (pid=7385) Creating OPT_DUP_END marker
03/23/2015 12:49:20 - end writing; write time: 0:41:00
03/23/2015 12:49:20 - Info bpdm (pid=7385) EXITING with status 0
03/23/2015 12:49:20 - Info alxaptb50xs (pid=7385) StorageServer=PureDisk:alxaptb71xs; Report=PDDO Stats for (alxaptb71xs): scanned: 328141028 KB, CR sent: 205466745 KB, CR sent over FC: 0 KB, dedup: 37.4%, cache disabled
03/23/2015 12:49:20 - requesting resource @aaaal
03/23/2015 12:49:20 - granted resource MediaID=@aaaal;DiskVolume=PureDiskVolume;DiskPool=MSDP_BHM;Path=PureDiskVolume;StorageServer=alxaptb71xs;MediaServer=alxaptb50xs
03/23/2015 12:49:21 - Info bpdm (pid=12268) started
03/23/2015 12:49:21 - started process bpdm (pid=12268)
03/23/2015 12:49:21 - Info bpdm (pid=12268) requesting nbjm for media
03/23/2015 12:49:31 - begin writing
03/23/2015 12:49:31 - end writing; write time: 0:00:00
03/23/2015 12:49:31 - begin writing
03/23/2015 12:49:31 - Info bpdm (pid=12268) Creating OPT_DUP_END marker
03/23/2015 12:50:31 - end writing; write time: 0:01:00
03/23/2015 12:50:31 - Info bpdm (pid=12268) EXITING with status 0
03/23/2015 12:50:31 - Info alxaptb50xs (pid=12268) StorageServer=PureDisk:alxaptb71xs; Report=PDDO Stats for (alxaptb71xs): scanned: 5 KB, CR sent: 3 KB, CR sent over FC: 0 KB, dedup: 40.0%, cache disabled
03/23/2015 12:50:31 - requesting resource @aaaal
03/23/2015 12:50:32 - granted resource MediaID=@aaaal;DiskVolume=PureDiskVolume;DiskPool=MSDP_BHM;Path=PureDiskVolume;StorageServer=alxaptb71xs;MediaServer=alxaptb50xs
03/23/2015 12:50:33 - Info bpdm (pid=12301) started
03/23/2015 12:50:33 - started process bpdm (pid=12301)
03/23/2015 12:50:33 - Info bpdm (pid=12301) requesting nbjm for media
03/23/2015 12:50:44 - begin writing
03/23/2015 12:50:44 - end writing; write time: 0:00:00
03/23/2015 12:50:44 - begin writing
03/23/2015 12:50:44 - Info bpdm (pid=12301) Creating OPT_DUP_END marker
03/23/2015 12:51:44 - end writing; write time: 0:01:00
03/23/2015 12:51:44 - Info bpdm (pid=12301) EXITING with status 0
03/23/2015 12:51:44 - requesting resource @aaaal
03/23/2015 12:51:44 - Info alxaptb50xs (pid=12301) StorageServer=PureDisk:alxaptb71xs; Report=PDDO Stats for (alxaptb71xs): scanned: 7 KB, CR sent: 3 KB, CR sent over FC: 0 KB, dedup: 57.1%, cache disabled
03/23/2015 12:51:44 - granted resource MediaID=@aaaal;DiskVolume=PureDiskVolume;DiskPool=MSDP_BHM;Path=PureDiskVolume;StorageServer=alxaptb71xs;MediaServer=alxaptb50xs
03/23/2015 12:51:45 - Info bpdm (pid=12386) started
03/23/2015 12:51:45 - started process bpdm (pid=12386)
03/23/2015 12:51:45 - Info bpdm (pid=12386) requesting nbjm for media
03/23/2015 12:51:51 - begin writing
03/23/2015 12:51:51 - end writing; write time: 0:00:00
03/23/2015 12:51:51 - begin writing
03/23/2015 12:51:51 - Info bpdm (pid=12386) Creating OPT_DUP_END marker
03/23/2015 12:52:51 - end writing; write time: 0:01:00
03/23/2015 12:52:51 - Info bpdm (pid=12386) EXITING with status 0
03/23/2015 12:52:52 - end Duplicate; elapsed time 1:54:45
03/23/2015 12:52:52 - Info alxaptb50xs (pid=12386) StorageServer=PureDisk:alxaptb71xs; Report=PDDO Stats for (alxaptb71xs): scanned: 16781128 KB, CR sent: 537162 KB, CR sent over FC: 0 KB, dedup: 96.8%, cache disabled
the requested operation was successfully completed (0)
 

Images duplicated:

alansfp01_1426924338
alansfp01_1426924333
alansfp01_1426924323
alansfp01_1426924283
alansfp01_1426924278
alansfp01_1426924220
alansfp01_1426924180
alansfp01_1426924054
alansfp01_1426924022
alansfp01_1426923980
alansfp01_1426923617

List of clients in policy:

ar_pd_class_c_win: 5 Clients (5 selected)

Client Name Hardware Operating System Policy Resiliency Indexing
----------------------------------------------------------------------------------------
alansfp01 Windows-x64 Windows2008 ar_pd_class_c_win Off Yes
almdtfp01 Windows-x64 Windows2008 ar_pd_class_c_win Off Yes
alsdcfp01 Windows-x64 Windows2008 ar_pd_class_c_win Off Yes
altrufp01 Windows-x86 Windows2003 ar_pd_class_c_win Off Yes
msmdnfp02 Windows-x64 Windows2008 ar_pd_class_c_win Off Yes

Hi All,

I have multiple appliances in our environment.

We have added multiple appliances in storage group. I have few queries:

1: If server will be backed up on 1 appliance then will dedup work on all appliances or will it take full backup first on all appliances in that SG then dedup will be in effect.

2. As per my understanding it will take backup copy on all appliances then dedup will work as per appliance then do we need to configure policies appliance wise?

Please confirm.

Hi All,

In my environment SLP is working for all media servers but specially not for 1. Checked storage unit for tape drive and disk, seems good. 

Please suggest what and how can we check to resolve this issue.

Hi All,

we are conducting vulnerability Assessment (VA) test on Netbackup appliance 5230. when we are running the application , the Netbackup appliance going to sleep or hibernate mode. Is their any settings to change the same.

Thanks ,

Karthik.C

N5230 v2.6.0.3

Settings > Alerts > Callhome Registration...

...is it best to specify:

a) The address of the 'owner' of the hardware.

...or:

b) The address of the 'physical location' of the the hardware.

Thanks.

N5230 v2.6.0.3 - new build

I have the choice of upgrading:

a) From v2.6.0.3 to v2.6.1 to v2.6.1.1... which will allow a downgrade to v2.6.1, if issues are experienced.

...or:

b) From v2.6.0.3 direct to v2.6.1.1... which will NOT allow a downgrade to v2.6.1, if issues are experienced.

Any advice on upgrade path a) or b) ?

Thank you.

N5230 - v2.6.0.3 and v2.6.1.1

Hi,

Is there a definite list of the site URLs (and ports) that an appliance can and will attempt to connect to, for:

1) Callhome

2) Software downloads

3) Other purposes?

Thanks.

Hi experts,
We are facing issue in our environment where replication is set between 2 netbackup domain having appliances. When replication is running sometime network team is complaining high outbound usage from appliance. Please suggest what is causing such issue. The mpls link is 30mbps between 2 sites and there is not more than 10-15 replication jobs running simultaneously.
Nb ver : 7.6.2
Appliance :5230
Urgent help required

Hi,

I am running with a POC with Appliance 5230 installed as Master/Media with MSDP.

I enable Encryption on appliance: Main_Menu> Settings> Deduplication> Tune Encryption Enable.

Now, how to I ensure that images on pool are encrypted, and how do I test that it is secured with unautorized restore to distinct server/location.

I do see some file created under  /disk/databases/catalog/number/client_host_name/policy_name/client-host-name_backup-timestamp_C1_F1.img

should I also have a keys stored somewhere?

Have a 5220 netbackup appliance which acts as master and media server.

Recently upgraded to latest software, 2.6.1.1.  Also, purchased additional memory and another storage shelf, which was successfully installed.

Running along just fine, when i get a call from one of our "Networking Guys',  tracing packets for some other problems, but see an awful lot of traffic for a certain MAC addr.   And it's one - off from what's listed as the main interface for my 5220.  Not mine, I say.

Well, he assigned the mac address a name and IP number and now, when I https to it, VOILA, IPMI interface for my 5220.

How did this happen?  I looked at the back, and there is an ethernet-looking connection labelled IPMI, but there's no cable in it. 

Not causing any trouble, but I would like to know if this is something new, or somethings that's been broadcasting a while and someone just noticed it.  Besides the "solving the mystery" aspect, I do have another appliance which I might like to get IPMI going on, and would really like to know what happened here.

Just attempted upgrading our 5230 appliance from 2.6.0.3 to 2.6.1.1 and after running for about 2 hrs or so, it failed with the following email:

Command install_NB_rpm failed to execute.

An UpgradeStatus command shows the following:

The software upgrade process failed. The appliance is rolling back to a pre-upgrade state using the Pre-upgrade checkpoint!

The following EEB's are installed on the appliance:

ET3592475-2.6.0.3-1

ET3538035-2.6.0.3-1

After some searching, I ran into another post on the forums indicating an upgrade failure with ET3592475-2.6.0.3-1 installed.

I have found the following article which indicates an updated version of this EEB. 

http://www.symantec.com/docs/TECH223591

It's a little unclear whether the new version ET3592475-2.6.0.3-2 actually resolves issues preventing the upgrade or not.

I have also opened a case with Symantec Support who have also indicated that a new version of the EEB may resolve the issue.

I'm actually very surprised more people haven't run into this yet.

/comentary

After the last few upgrades I'm beginning to think that Symantec/Veritas is more interested in continuous "new shiny features" to attract Managers rather than fixing and perfecting last week's shiny.  The quality and the Admin Friendly quotients have both fallen off a cliff...

/end comentary

So far the only one of my Appliances that I've attempted the 2.6.0.2->2.6.1.1 upgrade on has failed twice.

The first time due to not enough unallocated space in the BASE unit (why can't they check for that in the pre-check and also flag it in the Release Notes?).

Support was able to find that error, alert me to it, and point me to the KB on resizing and moving stuff around.

After I did some serious resizing and moving on all my Appliances (proactive moves) I tried this one again...

Now I've also got the dreaded "Command install_NB_rpm failed to execute." failure.  I'm waiting for Support to tell me which of their EEBs are somehow incompatible.

List of installed EEBs:
SYMC_NBAPP_EEB_ET3487431-2.6.0.2-4
SYMC_NBAPP_EEB_ET3512671-2.6.0.2-1
SYMC_NBAPP_EEB_ET3535636-2.6.0.2-1
SYMC_NBAPP_EEB_ET3535636-2.6.0.2-2
SYMC_NBAPP_EEB_ET3570768-2.6.0.2-1

Hi all,

I am in need of confirmation or explanation on some logging I see in the detailed status.

When I see this in the detailed status (for an Incremental backup):

04/15/2015 07:02:43 - Info bpbkar (pid=98149) accelerator sent 1115317760 bytes out of 5630247936 bytes to server, optimization 80.2%

Does this mean the Accelerator has found 5630247936 bytes of new/changed data on the client of which 1115317760 bytes is new data to the backup appliance? 

And how does this related to:

04/15/2015 07:02:45 - Info netbackup (pid=164455) StorageServer=PureDisk:netbackup; Report=PDDO Stats for (netbackup): scanned: 5498334 KB, CR sent: 268206 KB, CR sent over FC: 0 KB, dedup: 95.1%, cache disabled

I see that the client-side-dedup has found scanned: 5498334 KB of new/changed data of which sent: 268206 KB is sent to the Backup Appliance as this is new unique data.

Please correct me where I am wrong or comfirm I am understanding this correctly.

Many thanks

Regards,

Ronald

Hi,

Is there any documentation about NetBackup 5220?

Thanks!

Firstly, a link, to all appliance documentaton:

http://www.symantec.com/docs/DOC2792

.

My question...

Appendix C, on page 112, of the Appliance v2.6.0.4 HIIC guide, details how to add an expansion shelf to an operational 52xx appliance:

http://www.symantec.com/docs/DOC7642

.

...and the 5330 v2.6.1 HIC guide details how to add an expansion shelf to a v2.6.1 5330:

http://www.symantec.com/docs/DOC7584

...as does the 5330 v2.6.1.1 HIC guide:

http://www.symantec.com/docs/DOC7593

.

...but the 5230 v2.6.1 and 5230 v2.6.1.1 HIC guides do not detail how to add an expansion shelf to an already operational v2.6.1(1) 5230 appliance.

. 

So, my question, where can I find the procedure to add an expansion shelf to an already operational v2.6.1(.1) 5230 appliance?

Hi,

Can you configure a master and media server in a single appliance?

How do I do it? I already configured a master server. 

Thanks. :)

When configuring a new N5230 as a master/media in v2.6.1.1, the process auto-created a standard backup policy which has the following as "Backup selections" within this auto-created backup policy:

/msdp/cat/databases/catalogshadow
/msdp/cat/databases/datacheck
/msdp/cat/databases/spa
/msdp/data/dp1/pdvol/etc
/msdp/data/dp1/pdvol/var
/usr/openv/lib/ost-plugins/pd.conf
/usr/openv/lib/ost-plugins/mtstrm.conf

However, the appliance has also auto-configured itself with an exclude list of:

# cat /usr/openv/netbackup/exclude_list
/advanceddisk
/cat
/msdp/data/
/msdp/cat/
/config

.

So, this new auto-created standard backup policy will ignore the first five selections of the backup policy that it created.

Needless to say, I'm confused.

Can anyone explain:

1) Whether this is correct?  And why?

...or:

2) Whether this is incorrect?  And why?

Hi,

Our company just bought Netbackup Appliance and currently in the midst of setting the appliance.

Now there is 2 HBA card used with 4 port already zone in SAN switch.

Storage we used Netapp and all the WWN already insert in initiator group and present it to all related LUN.

I've perform query in the appliance ( Manage>FibreChannel>Scan and Manage>FibreChannel>Show).

The result all is Netapp storage but in the format that I can't understand and doing comparison with the Netapp LUN.

So the question is, how to exactly to verify that the LUN already zoning to the Netbackup Appliance?

Thanks

Hello,

I deployed an NBU5230 version 2.6.0.4 as an MSDP media server. We have performance issue with tape out from the appliance MSDP so I do a little research on the internet. I found that there are some settings we can tune on the contentrouter.cfg and pd.conf file.

My question is there are more than one location of those configuration files, which file should I edit?

e.g.

/usr/openv/pdde/pdcr/etc/contentrouter.cfg

/disk/etc/puredisk/contentrouter.cfg

Thanks & regards,

Chan KH.