The best way to find out what's wrong with a Oracle script is to try running it manual. That is if you're running Oracle scripts from that group of course..
I think that it can be hard to find any big differences in speed and capacity, however we've had quite a few problems with SDLT drives and I think that LTO is more reliable.
I should try to find out whats wrong first. If it is working occasionally you probably have some hardware trouble. Check out NICs, switchports and Cables.
Cloning is generally a very slow process. Most cases you can't compare it with backup performance. That is true for both disk and tape reads. So I should think that what you're seeing is normal.
Hmm, RAID 5 is slow on writings because of Controlbit calculations. However I hardly think thats your problem. You didn't say anything about your client O/S but If Windows you might have problems with a fragmented FileSystem. Also make sure you don't have any autonegotiation set to On. On CPQ...
Ok. according to your specific questions.
1. In case of a Disaster recovery: Make sure you install the server as a standalone server in a workgroup. Same location, same versions and SPs. And of course the same hardware. Most important is SCSI hardware and enough disk space. Install the same...
Ok. according to your specific questions.
1. In case of a Disaster recovery: Make sure you install the server as a standalone server in a workgroup. Same location, same versions and SPs. And of course the same hardware. Most important is SCSI hardware and enough disk space. Install the same...
Hmm, John55_nt, I think you'd be better off starting a new thread for this question. However I will try to help you a bit here. The real answer here would of course be: "It depends". First you need to know where in the system you have your bottleneck. What network bandwith do you have...
I think this actually could be the result of different reasons. Network connections and system account has no permissions on the file system for instance. Also try to increase the inactivity timeout. If you're running any pre/post commands remove them for a temporary test backup to see if they...
No, not necessarly. This is only a requirement if you need to cancel rman jobs or running Index-Rcat crosschecks thru rman. Then again, thats the way you normally want to do it.
Legato will enhance the security implementation in Networker with their 7.x version. There will finally be different levels of administration accounts and possible integration with 3rd party encryption applications. When it comes to password protection of SQL server backups I would try to use...
I would re-install and re-config everything on the new server keeping the old name. In this way you can just move the indexes and Media database from the old server. That should give you a rather clean installation without any major hazzle.
Hold your horses..
To be able to read someone elses tapes you would Only have to have the same type of tapedrives and server name. Just mount the tape and run scanner ( -i \\.\Tape0) to rebulid the the indexes and mediadatabases. Then you're up and running. Great isn't it?
If you're using the built in watermarks you don't have to worry about the disk getting full. Make sure that the stage disk is for staging only though. You don't want to have any other applications accessing the disk, including Networker Index and media database.
You wont loose any data recreating the Jukebox. However, before you delete the current config unload any tapes from drives, make sure no pools are pointing at the drives. Delete the jukebox first, than the drives.
Well, you need to keep things apart. mmrecov will rebuild the BU server index only. Of course from that you can do a regular restore to restore client indexes. That is a timeconsuming process to. With the replication scenario you wont have to restore any indexes.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.