Attachment uploads are currently disabled. This is a temporary situation and will resume as normal in the coming days.
Solved!
Go to SolutionHelp with Exchange Module
I can't figure out what I'm doing wrong
I just installed Networker 7.3.1 and it's clients out to serveral new servers. The backups are working. I added the 4.1 Exchange module to the exchange server, and then added MSEXCH:IS to the save set list of the exchange server. I'm not using ALL because I don't want to get a copy of the priv.edb and pub.edb databases
When it trys backup MSEXCH:IS, I get a No Such File or Folder error. Am I missing some software somewhere? Do I have to install any Exchange related software on the Networker server?
Also, when I do a manual Exchange backup from the User Client on the Exchange server, it works.
Oh yeah, I'm still running on the demo license with no activation keys. I have to get 100% functionality before we can transfer our Networker license from old (retiring) Unix server to the new Windows server.
Thanks!
--Joel
I just installed Networker 7.3.1 and it's clients out to serveral new servers. The backups are working. I added the 4.1 Exchange module to the exchange server, and then added MSEXCH:IS to the save set list of the exchange server. I'm not using ALL because I don't want to get a copy of the priv.edb and pub.edb databases
When it trys backup MSEXCH:IS, I get a No Such File or Folder error. Am I missing some software somewhere? Do I have to install any Exchange related software on the Networker server?
Also, when I do a manual Exchange backup from the User Client on the Exchange server, it works.
Oh yeah, I'm still running on the demo license with no activation keys. I have to get 100% functionality before we can transfer our Networker license from old (retiring) Unix server to the new Windows server.
Thanks!
--Joel
- Hi Joel,
Yes, you should have separate clients for file system backup and database backup. Further, of possible, they should not run at the same time (I/O impact on machine).
I'm not sure if such guide exists, but I'm not aware of it at least.
Usually if you follow what admin guide says you should not have problems at all.
Backup practice will (should) depend on your restore requirement (but what you have listed as an example is good start). - Well, I sure thought that was the answer, but I did that and now it just fails with no status. It takes a while contacting the client, then fails.
Here's the real problem. I'm coming in to Legato with a background in NetBackup. Legato is completely foreign to me. Are there any good step-by-step resources available to show me how to get rolling with this? A good example is that now that I put nsrxchsv in the backup command field, the regular C: drive backup doesn't work. Does that mean I should create 2 clients for the Exchange backup, one the gets the system files and logs, and another that gets just the IS? It's this type of best practices that I'm looking for.
Thanks!
--Joel dpinink_silva
2 Intern
•
724 Posts
546
1
Posted August 24th, 2006 05:00
Hi Joel,
If you follow the Admin guide, and the module guide, you'll have all the steps needed.
As Hrvoje said, you'll need to create two clients, because when you leave the "backup command" field blank, Nw will use it's default command "save" to do the backup, and this command understands each saveset in the saveset list as a filesystem. So, if you leave it blank and put something like MSXCH:IS, Nw will try to backup it as a filesystem, which of course do not exist.
Every module has it's own backup command, which will understand the saveset list in it's own way.
Hope this helps....- OK, so thanks to you folks, I was able to get things working. I installed the Networker client and Exchange module on my 2nd Exchange server and created a client with the MSEXCH:IS as the save set, and the nsrxchsv.exe as the backup command. I also had to the the Override level full because today's schedule is for a Incremental. I think this is what I was missing after your suggestions about nsrxchsv.exe.
As it now stands, I have 2 clients set up for each exchange server. One client gets the System drive and the log file drive on a daily Inc and a weekly Full schedule. The other gets the IS on a weekly Full schedule.
Thanks again!
--Joel
dpinink_silva
2 Intern
•
724 Posts
546
0
Posted August 23rd, 2006 12:00