setup Malware Scanning
Hi I have some questions: inNetBackup Security and Encryption Guide doc said: For BYO setup, Instant access must be configured on MSDP storage server See the "Configuring Universal share" section in Veritas NetBackup Deduplication Guide 1- what's MSDP BYO? if MSDP server is windows, is it BYO? in Veritas NetBackup Deduplication Guide doc said: MSDP build-your-own (BYO) server prerequisites and hardware requirements to configure universal shares: The universal share feature is supported on an MSDP BYO storage server with Red Hat Enterprise Linux 7.6 or later. The universal share feature is not supported on SUSE Linux. 2- if windos is BYO too, then how about Malware Scanning? is it possible or I should deploy Redhat MSDP??? I have a windows MSDP to backup vmware vms with accelerator feature and want to deploy Malware scanning Thanks in advance125Views0likes7CommentsEncryption in netbackup MSDP multi-domain
Hello All, Looking to enable encryption on Netbackup MSDP multi domain. Does this supported by Netbackup? Also can we enable encryption on Media server where storage server is seprated from media server ? As per my understanding we have to enable encryption on both servers660Views0likes1CommentCompactation taking too long?
Hello! We have a 30T MSDP with 70% used, we expire a lot of images recently but the storage wouldn't go down, so the next logical step was to run de compactation via CRCONTROL, but it's taking too long? I started the proccess 2 days ago and it's still compacting, but the storage don't seems to respond to this. What am I doing wrong? the logs seems fine (I think...) July 20 11:14:46 INFO [000000078C403640]: COMPACT: instance 0: release space 11837480 from container 4879606 July 20 11:14:59 INFO [000000078C403640]: COMPACT: instance 0: release space 13771159 from container 4879607 July 20 11:15:07 INFO [000000078C403640]: COMPACT: instance 0: release space 7164343 from container 4879609 July 20 11:15:23 INFO [000000078C403640]: COMPACT: instance 0: release space 4810206 from container 4879611 July 20 11:15:23 INFO [000000078C403640]: COMPACT: instance 0: release space 0 from container 4879612 July 20 11:15:23 INFO [000000078C403640]: COMPACT: instance 0: release space 0 from container 4879614 Please send help.Solved821Views0likes2CommentsMSDP catalog backup drcontrol command doesn't work
I tried to configure a new policy for msdp catalog with the drcontrol command from the media server. But it does not give any response and cannot see the policy created from the java console as well. Command : /usr/openv/pdde/pdcr/bin/drcontrol --new_policy --residence BasicDisk01 --policy CDC_MSDP_Catalog_Backup1.4KViews1like4CommentsNetBackup Enhancements for Oracle VLDBs (Very Large Databases)
In this day and age, data tends to only increase in size. For our customers with ever-growing Oracle databases (DB), timely backups and restores are a challenge. We have many existing features within NetBackup to protect Oracle, and now we have added a solution for Oracle Very Large DBs (VLDB). Figure 1. Oracle policy option to select multiple MSDP storage units The designation of “Very Large” is arbitrary, but a widely accepted definition is a database that is too large for the data protection to succeed in the desired time window. Oracle DB protection struggles are focused on completing backups faster, but the ability to restore within the expected time frame is often ignored, resulting in missed Restore Time Objectives (RTOs). This new Oracle policy option allows segmenting the Oracle backup across multiple NetBackup MSDPs (Media Server Deduplication Pools) storage units with the ability to choose which storage units are used (see Figure 1). For a single stream, this results in a backup image that is in the catalog as a single image, with the image’s fragments tracked in the catalog on each storage unit selected. A single backupid makes tracking and reporting streamlined. You can also increase the number of parallel streams. Allowing simultaneous writes to multiple disk pools increases the efficiency of the streaming backup. The number of storage units to use for the best results will vary from one database to the next. Further, take advantage of multiple parallel streams to further tune your Oracle backup. Storage units are linked to disk pools, and the most effective use of this option will leverage multiple storage units that are linked to multiple unique disk pools hosted on different media servers. This solution also works with where the nodes of a single Flex Scale are managed independently and only one storage unit is presented to NetBackup. There will be affinity for the database backup to write the same file, or piece, of the database backup to the same MSDP storage unit, so do not change this configuration often. Some of the considerations will be: Number of nodes in a RAC (Real Application Cluster), Number of instances, Number of parallel streams As more parallel streams and storage units are configured for the policy, the gain in performance is geometric improvements in the backup times. This must be aligned to your backup and restore goals and your existing infrastructure to avoid creating bottlenecks in the performance. To meet the desired goals, there may be a need to add more MSDP pools rather than having a few large pools each with a single node. Additionally, consider more load balancing media servers to also share data movement responsibilities. This solution can also use Storage Lifecycle Policies (SLPs) as multiple storage targets, enabling you to maintain your current business continuity and DR (Disaster Recovery) plans for your Oracle data. When selecting multiple storage units, you would select a different SLP (Service Lifecycle Policy) for each destination. If the desired SLP is not shown, confirm that it is using supported MSDP storage units. It is key that the SLPs for this use-case all be designed and configured with the same goals, including retention levels, and different source and target storage units. For example, if splitting the Oracle backup across 2 SLPs, each SLP would use a different backup storage unit, and a different secondary operation storage unit. In the case of replications (AIR (Auto Image Replication)), the replication relationship between the on-prem MSDP and the target MSDP each needs to be under the same target primary server (see Figure 2). It is possible to replicate many-to-one, but this would remove the benefit of segmenting the image across multiple disk pools. If the replication targets of only a portion of the database went to a different NB domain or were not retained for the same period, the image would not be complete and a restore would not be possible. Figure 2. SLP configuration requirement for multiple MSDP storage units with replication When the need for a restore arises, NetBackup takes advantage of multiple sources to read and stream back to the destination, with each disk pool reading a piece of the database image simultaneously. This results in a faster restore time for a large amount of data. The Disk Pool’s Maximum I/O streams setting will need to be adjusted according to the peak performance of the disks and the potential number of restore and backup streams. This setting can be changed dynamically, without a restart of services, to meet changing needs. Consider, also, the impact of load balancing media servers in such a configuration. If all media servers have credentials to all storage servers, they can potentially perform the requested read action during a replication or restore operation. In circumstances where some media servers are already busy doing other jobs, such as backups, NetBackup will choose the next-least-busy media server to perform the requested action. For most situations, it will be best to configure only the media servers needed for these repetitive actions to have access to the disk pools in-use. Plan disk pool deployment to maximize the throughput from the Oracle clients to multiple media servers and their NetBackup deduplication volumes. Take advantage of this new parallelism to improve throughput performance for both your backup and recovery operations for your Very Large Oracle databases to meet your strict RTOs.1.7KViews3likes0CommentsDoes AIR require matching hardware on both sides?
We're looking at revamping our kinda-sorta "DR site" and moving to AIR at the same time. This'll be built on NB v9.1 most likely. I've got Data Domain on both sides right now and am simply using duplication via SLP's right now. We'd like to move to cheapiecommodity storage in the DR site, convert to AIR, and re-use the remote DD in a different role. Everything I found says OST to OST or MSDP to MSDP for AIR. Is there a mix & match option? -MarkSolved915Views0likes2CommentsMSDP 250GB /etc/nbapp-release missing
hello, Here is my netbackup rev details [root]# cat /usr/openv/netbackup/version HARDWARE LINUX_RH_X86 VERSION NetBackup 9.1.0.1 RELEASEDATE Tue Aug 24 17:26:47 CDT 2021 BUILDNUMBER 0040 ### I recently created an MSDP pool as per the tech note: https://www.veritas.com/content/support/en_US/article.100038442 however ... I forgot step #3 : Create a touch a file /etc/nbapp-release if it doesn’t exist. There is no explanation as to why the above file is required is required. Everything appears to work fine ... and it is only during my review that I realised my mistake above. However, the MSDP pool is now in use so I am worried about the implications. I need to understand if I need to destroy / rebuild the MSDP pool? I cannot find a great deal of information on this file. Have I created a future problem for myself? Can I touch touch the file and reboot the media server. Or perhaps there is a command I need to execute to "fix" it? Can someone help? Many thanks1.5KViews0likes3CommentsMSDP Down
Hello Community, We had a OS Upgrade on a Master Server on Win2008 to change it to 2019. It also had an MSDP Pool on F Drive. After Clean 2019 installand Netbackup Master Server 8.2 Setup and Catalog Recovery. We followed Process to reconnect MSDP Pool to Netbackup . https://www.veritas.com/content/support/en_US/doc/25074086-130388296-0/v33188054-130388296 However, we see below in SPAD logs. What Certificate we should look at ? We updated policies for backups to not to go to disk and changed to go to tape . They are backing up and connecting fine, so master server certificate seems ok, Not sure what certificate its talking about, Appreciate any help. ======================================== March 02 02:06:50 INFO: set entire process max log size to 0 March 02 02:06:50 INFO: set entire process max log size to 0 March 02 02:06:50 INFO: CR mode in spa db is normal ! March 02 02:06:50 INFO: Startup: loading configuration from F:\MSDP\etc\puredisk\spa.cfg March 02 02:06:50 INFO: get key from file F:\MSDP\var\keys\auth.key. March 02 02:06:50 INFO: : extended attribute support disabled March 02 02:06:50 INFO: get key from file F:\MSDP\var\keys\auth.key. March 02 02:06:50 INFO: Manager thread stack size: 0 bytes March 02 02:06:50 INFO: Task thread stack size: 0 bytes March 02 02:06:50 INFO: Max DO size: 335544320 bytes March 02 02:06:50 INFO: Fibre Channel configuration is empty. March 02 02:06:50 INFO [000002DB23E29910]: set entire process max log size to 10000000 March 02 02:06:50 INFO [000002DB23E29910]: set entire process max log size to 10000000 March 02 02:06:50 INFO [000002DB23E29910]: Startup: occurred at Tue Mar 2 02:06:50 2021 March 02 02:06:50 INFO [000002DB23E29910]: Successfully loaded configuration from F:\MSDP\etc\puredisk\spa.cfg March 02 02:06:50 INFO [000002DB23E29910]: Startup: 1854: MD5 passwd disabled March 02 02:06:50 INFO [000002DB23E29910]: Encrypted passwords match encryption keys. March 02 02:06:50 INFO [000002DB23E29910]: FIPS mode not ENABLED March 02 02:06:50 INFO [000002DB23E29910]: Startup: Instant Data Access is not enabled March 02 02:06:50 INFO [000002DB23E29910]: Startup: spad type is master March 02 02:06:50 INFO [000002DB23E29910]: Startup: master spad url is March 02 02:06:50 INFO [000002DB23E29910]: Startup: Veritas PureDisk Storage Pool Authority Version 12.0000.0019.0624. March 02 02:06:50 INFO [000002DB23E29910]: Startup: using Veritas: libdct 6.0.0.0, July 7, 2004 March 02 02:06:50 INFO [000002DB23E29910]: Startup: using Veritas PureDisk: libcr 6.1.0.0, December 13, 2006 March 02 02:06:50 INFO [000002DB23E29910]: Startup: upgrade of spa DB skipped March 02 02:06:50 INFO [000002DB23E29910]: Memory Manager: initializing March 02 02:06:50 INFO [000002DB23E29910]: Memory Manager: initialization complete March 02 02:06:50 INFO [000002DB23E29910]: Sched Manager: initializing March 02 02:06:50 INFO [000002DB23E29910]: schedule string for QueueProcess: [20 */12 * * *] March 02 02:06:50 INFO [000002DB23E29910]: alert time for QueueProcess is 21600 March 02 02:06:50 INFO [000002DB23E29910]: lifecycle for QueueProcess is 32400 March 02 02:06:50 INFO [000002DB23E29910]: schedule string for RepOrphan: [*/10 * * * *] March 02 02:06:50 INFO [000002DB23E29910]: alert time for RepOrphan is 300 March 02 02:06:50 INFO [000002DB23E29910]: lifecycle for RepOrphan is 600 March 02 02:06:50 INFO [000002DB23E29910]: schedule string for CatalogBackup: [40 3 * * *] March 02 02:06:50 INFO [000002DB23E29910]: alert time for CatalogBackup is 21600 March 02 02:06:50 INFO [000002DB23E29910]: lifecycle for CatalogBackup is 32400 March 02 02:06:50 INFO [000002DB23E29910]: schedule string for CRStats: [0 * * * *] March 02 02:06:50 INFO [000002DB23E29910]: alert time for CRStats is 300 March 02 02:06:50 INFO [000002DB23E29910]: lifecycle for CRStats is 600 March 02 02:06:50 INFO [000002DB23E29910]: Sched Manager: initialization complete March 02 02:06:50 INFO [000002DB23E29910]: PD_Replication: initializing March 02 02:06:50 INFO [000002DB23E29910]: PD_Replication: initialization complete March 02 02:06:50 INFO [000002DB23E29910]: Task Manager: initializing March 02 02:06:50 INFO [000002DB23E29910]: Task Manager: seeding random number generator March 02 02:06:50 INFO [000002DB23E29910]: Task Manager: initializing DCT Content Routing (TM) March 02 02:06:50 INFO [000002DB23E29910]: _crConfigLoadA: Set the CR context use NBU CA. March 02 02:06:50 INFO [000002DB23E29910]: Task Manager: initialization complete March 02 02:06:50 INFO [000002DB23E29910]: Connection Manager: initializing March 02 02:06:50 INFO [000002DB23E29910]: Connection Manager: initialization complete March 02 02:06:50 INFO [000002DB23E29910]: Catalog auto recovery is enabled. March 02 02:06:50 INFO [000002DB23E29910]: Catalog backup version count: 5, shadow pool size: 64 March 02 02:06:50 INFO [000002DB23E29910]: Catalog backup shadow path: F:\MSDP\databases\catalogshadow March 02 02:06:50 INFO [000002DB23E29910]: CatalogContext::get_storage_path: storage_path=F:\MSDP\data, storage_path_spa=F:\MSDP March 02 02:06:50 INFO [000002DB23E29910]: Startup: completed at Tue Mar 2 02:06:50 2021 March 02 02:06:50 INFO [000002DB23E29910]: set entire process max log size to 10000000 March 02 02:06:50 INFO [000002DB23E29910]: set entire process max log size to 10000000 March 02 02:06:50 INFO [000002DB23E29910]: Increasing maximum number of open files from 512 to 2048 March 02 02:06:50 INFO [000002DB23E29910]: History Manager: start [thread 000002DB24DCB320] March 02 02:06:50 INFO [000002DB23E29910]: Sched Manager: started [thread 000002DB24E9AFF0] March 02 02:06:50 INFO [000002DB23E29910]: DataCheck Manager: started [thread 000002DB24E9BA70] March 02 02:06:50 INFO [000002DB23E29910]: Task Manager: started [thread 000002DB2542D290] March 02 02:06:51 INFO [000002DB23E29910]: EventSystem::SpaDBEventStorage::checkConsistency Starting consistency check March 02 02:06:51 INFO [000002DB23E29910]: EventSystem::SpaDBEventStorage::checkConsistency Ending consistency check March 02 02:06:51 INFO [000002DB23E29910]: EventSystem::SpaDBDSEventStorage::checkConsistency Starting consistency check March 02 02:06:51 INFO [000002DB23E29910]: EventSystem::SpaDBDSEventStorage::checkConsistency Ending consistency check March 02 02:06:51 INFO [000002DB23E29910]: EventSystem::EventManager::EventManager m_orig_dsid = 2 March 02 02:06:51 INFO [000002DB23E29910]: EventSystem::EventManager::newEvent Adding new event. type:4, dsid:0 March 02 02:06:51 INFO [000002DB23E29910]: remove old record file F:\MSDP\databases\spa\database\eventproperties\1. March 02 02:06:51 INFO [000002DB23E29910]: NetBindAndListen: bound myself to <localhost>:10102 using IPv6 March 02 02:06:51 INFO [000002DB23E29910]: NetBindAndListen: bound myself to <localhost>:10102 using IPv4 March 02 02:06:51 INFO [000002DB23E29910]: Connection Manager: started March 02 02:06:51 INFO [000002DB23E29910]: Setting service status to running if service start March 02 02:06:54 INFO [000002DB24E9A730]: NBUAPI::GetSecurityProperties: synced security properties with master server 1, 0 March 02 02:07:24 ERR [000002DB24E9A730]: -1: CURLClient::Execute: failed to perform CURL session, error: Operation timed out after 30000 milliseconds with 0 bytes received March 02 02:07:24 ERR [000002DB24E9A730]: -1: NBUAPI::GetToken: curl error to access https://server.com:1556/netbackup/loginwithcert March 02 02:07:24 ERR [000002DB24E9A730]: -1: NBUAPI::ValidateHost: failed to get token March 02 02:07:24 ERR [000002DB24E9A730]: -1: validate_host_cert: validate the host server.com uuid 4393a0cd-e60f-4f37-bb3b-e3fc8bf42ce7 cert failed. March 02 02:07:24 ERR [000002DB24E9A730]: 25056: Agent at server.com certificate is invalid. ==================================================== Regards,Solved2.5KViews0likes5CommentsMSDP Full, but has no images on it. crcontrol doesn't release any space.
I've got an MSDP that is a trget for A.I.R., that currently shows to be 96% full in the Disk Pools section of the Admin console, and 93% full when doing a "df" from the commandline on the media server. I've tried running "/usr/openv/pdde/pdcr/bin/crcontrol --processqueueinfo" mulitle times over many days, but it still remains full. bpimagelist -server [servername] doesn't show any results. Is there a way to force a cleanup, are there files that I can just delete manually to clear the space? It's cauisng A.I.R. to fail on the source, but I don't see any imports running on the target.3.1KViews0likes7Comments