Unable to start postgresql 8.3 service for MSDP
Hi , I'm using Netbackup 7.5 and just move netbackup to new server and recovered full catalog. After that unable to restart postgresql 8.3 service , Deduplication services and backup is giving 2074 error "storage server is down " Waiting for solution. Thanks , NEERAJ MEHTA937Views4likes3CommentsUpgrade Symantec Netbackup Puredisk (PDDO) 6.6 to Symantec Netbackup 7.5
Hi All, Can you give me how to 'Upgrade Symantec Netbackup Puredisk (PDDO) 6.6 to Symantec Netbackup 7.5 ? This is existing environment : Puredisk Server version : 6.6 (bundle with Suse Enterprise) Platform : Suse Enterprise Linux 10 Storagepool : 4 TB (/Storage/data) I need this solution because netbackup versin 6.x end off support from symantec : http://www.symantec.com/connect/blogs/be-aware-netbackup-6x-end-support-life-fast-approaching Thanks in advance. Regards, Ahmad740Views2likes2CommentsNetbackup Appliances 5230 with PureDisk: How many streams?
Hi all, We recently migrated to Netbackup Appliances running Netbackup 7.6.0.1 (Appliance version 2.6.0.1 ) We are running 2 appliances per site, each site is its own NBU domain (We use AIR to replicate). Each appliance is configured with a 70TB PureDisk volume. We are quite new to PureDisk that is running on these systems, but at this moment they are limited to 80 streams maximum in the diskpool object (Which seems pretty low to me) At the moment we are running out of resources due to this maximum that has been set. What is the maximum streamcount a 5230 Appliance PureDisk can safely handle? Note that we are using AIR to replicate all our images, but replication is being done during the day, not during backup times... Any advice is greatly appreciated! Thanks!1KViews1like2CommentsPureDisk Agent Config File Update is stalled
Hi, I am troubleshooting SPAR replication issue on 6.6.3 PureDisk. On the Destination Storage Pool SPAR jobs start and keep being queued with 0% progress until 24h watchdog kills them. On the Source Storage Pool the SPAR job is killed by watchdog after 4h at 33%. Tried to run update agent configuration (the Source SPA is an Agent on Destination pool) using the "Config File Update" but that job got queued at 0% and is not progressing on the target SPA. I have just re-activated - set all the settings from scratch - the SPAR policy on the Source Storage Pool. The SPAR activation job completed successfully on the Source SPA. Ran SSH session from one to another and the other way. Any ideas where is the connection problem? SSH keys? Strange. Any help or tips welcome!1.1KViews1like2CommentsMSDP encryption (ServerOptions=agent_crypt) (or should it be =encrypt)
Hi Forum, Page 30 of the NetBackup Deduplication Guide v7.5 says that... by default MSDP encryption is disabled by default, but they it is recommended by Symantec. Page 70 says that to enable encryption that we need to add "agent_crypt" to "ServerOptions=" in the ContentRouter.cfg file. But looking at the comments in the file: ; [no]agent_crypt : always disable/enable client-side encryption; ; [no]encrypt : always disable/enable encryption; ...indicates that using "agent_crypt" instructs the client-side deduplication agent to encrypt data. At our site we are not implementing client side deduplication so it woudl seem to me that setting :agent_crypt" won't have any effect. My questions are: 1) Is "agent_crypt" really the option to use if what we are trying to achieve is encryption of the post-dedupe blocks on teh MSDP data storage local to teh MSDP media server? 2) What does the "ServerOptions=encrypt" option do, and how is it different to "agent_crypt" ? 3) If we can determine which option really does enable post-dedupe encryption - then does anyone know what the CPU overhead is ? 4) Are there any particular models of CPU (SPARC or Intel or AMD) that implement the encryption/decryption in their hardware instruction sets - i.e. are there any CPUs that are much better suited for use with MSDP encryption ? Thanks, Dave.Solved1.8KViews1like4CommentsNTFS cluster blocking factor for MSDP database and MSDP data volumes?
Hi Forum - I've read elsewhere that is is recommended to format the NFTS volumes that will be used to house the MSDP database and MSDP data with a cluster size of 64 KB (i.e. 128 traditional 512 byte sectors). However if if look at a slightly populated MSDP server, I see most files are less than 64 KB. Does anyone have an opinion on this? Top folders with files... F:\MSDP_Data\history\dataobjects 12 F:\MSDP_Data\history\errors 12 F:\MSDP_Data\history\retention 12 F:\MSDP_Data\history\segments 12 F:\MSDP_Data\history\tasks 12 F:\MSDP_Data\history\tlogs 12 F:\MSDP_Data\log\pddb 43 F:\MSDP_Data\queue 83 F:\MSDP_Data\data 26,205 F:\MSDP_Data\processed 103,610 Total = 130119 Table of file sizes... = 0 75 > 0 29,708 > 4 28,285 > 8 22,436 > 16 12,058 > 32 4,585 > 64 18,802 > 1,024 879 > 10,240 836 > 102,400 220 > 204,800 12,118 > 409,600 108 > 1,024,000 9 Total = 1301191.1KViews1like4Comments