MSDP 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.1KViews0likes7CommentsSteps to restore MSDP data in new configuration
I have Netbackup 7.7.3 installed on windows server 2008 R2. MSDP is configured on it and weekly, monthly and yearly backup is going on tape using SLP. Due to some issue on Operating system and increase the size of MSDP volume I want to erase everything, but we want to save MSDP data so that after reinstall we can migrate data on new server. We have copied MSDP data on new drive and about to format the system. Hostname, drive letter and drive name and other configurations will be same leaving ip address as we are changing ip address from class b to class a. I am looking for steps I need to perform and admin guide which can help me to perform this activity. Please help me to solve my problem.Solved765Views0likes1CommentMedia server hardware replacement with Windows cloning
Dear Experts! Our customer environment is: 7.7.3 NBU server (Win2008r2) 7.7.3 Media server with MSDP pool (Win2008r2) MSDP pool size is 10g, and sitting on the FC storage, and Media server is mounted this LUN-s locally with 8 Gb Fc hba interfaces. Customer want to change the media server hw to a bigger machine. New server is the same architecture (Inter,x86) but from different vendor. Mac address, hba is changing. His planned Media Server replacement procedure: 1. deactivate the old media server and pull FC cable 2. stop the NBU server and old NBU media server 3. make a Windows image from an old NBU media server (with 3.rd party cloning/imaging tool) 4. upload Windows image to a new NBU media server (with 3.rd party cloning/imaging tool) 5. fix the Windows layer driver / hba issues and push the FC cable (do the storage config too) 5. Start the NBU server 6. Activate the new media server 7. fix the tape driver isssues 8. start the dedup services on the new media server 9. test the dedup pool, backups If any error occured, he can stop the new media server and restart the old media server. Questions: ------------- - What do you think about this scenario? - Which errors and risks the customer met? - It can work? - Do you have any special advices? I think the changing things: - hba wwn (not stored in the NBU) - ethernet mac address The constant things which doesnt change: - Windows os - Dedup pool mount points The Deduplication Administration guide said we have to deconfigure dedup pool, expire the images and import images.But it takes a long time, customer avoid that way because expire/import takes a lot of time. Thanks for your advices! BR: Pal1.1KViews0likes2Comments