Here are the details of my environment before I get started. Please let me know what logs you need and what are my steps to resolving this issue.
Replication Source: NBU 188.8.131.52, Server 2008, Master/Media
Replication Target: N...
Hi there forum,
I've been having this issue for the last two months and have not been able to pin point the issue. Any suggestions/comments are welcomed.
2-3 times a week one specific tape drive will be down'd by the netbackup application. ...
Hi there Forum,
I am thinking about virtualizing my SEV server and would like to reach out to you all and find out if there are any "best practices" when attempting to do this. Not sure if there are any official instructions on the internet, but I wa...
Just wondering if the experts can help me troubleshoot the issue. I have logged a case, but it takes a long time for them to respond and it seems they arent sure how to approach this.
Here is the scenario: from Local Master.
I have finally been successfull with setting up my environment to get Manual Full Backups working. Now when I schedule incrementals, they are failing.(Status 13)
Not sure where to begin troubleshooting since I figured it would be the exa...
Drives are connected through redundant fiber path to our SAN switch.
The Drive itself was replaced last month... so I can start with troubleshooting the rest of the hardware. I'll start by replacing the Gbics and see how that goes.
Cannot get Spoold to start. I get the following error.
C:\Program Files\Veritas\pdde>spoold.exe --start
Error: 67: Database: connection to database crdb at localhost:10085 failed (could not connect to server: Connection refused (0x0000274D/1006
Thanks for your reply Mark. Here are part of the logs you requested. I only copied a part of the logs because there was a lot of info on there. Hope that helps.
Let me know if there is anything else you need from me.
Actually, Yes. The issue started right after we ran out of space on the DeDupe Backup Volume. Replications failed and we then expanded the volume (added 2TB) and rebooted both servers. After that incident the replications began failing constantly.