Home > Cannot Determine > Cannot Determine Status Of Backup Process Use Mminfo

Cannot Determine Status Of Backup Process Use Mminfo

Wanting to go about it quickly, I did the following: I used "nsrmm -dy -S ssid" for each saveset ID I wanted to delete, to erase it from the media database. So what might be a 5MB screen shot, or a 4MB plain text log file, should come down to 400KB or less. If you're dealing with potentially damaged media, the file/record numbers can sometimes be your saving grace. You could think of it as the heartbeat parameter. news

Here's the scenario – I created a client called ‘dopey'*, installed CentOS 5, ran a full + incremental backup, then reinstalled ‘dopey' as a Windows 2003 machine. Here's (some of) the output from that backup, using NetWorker 7.5.1 as the server and client in all 3 instances: [[email protected] ~]# savegrp -l full -c dopey idata 40473:savegrp: command ' The second is delimited format – your choice of delimiter. You can not post a blank message. https://community.emc.com/thread/78360?start=0&tstart=0

I like to rationalise it this way – consider your support "event" to be a movie. Posted in Databases, Features, NetWorker | Tagged: Oracle, Oracle Module | 17 Comments » Client operating systems should not bechanged Posted by Preston on 2009-05-04 While researching an issue today I My Kindle eBook ("Stop, Collaborate and Listen") provides the necessary details for successfully aligning IT to the needs and purpose of the business. I'll update this post accordingly. [Update - 2009-04-27] Have done some more tests on 7.5.1 on various Linux servers, comparing results to 7.4.4.

But the minimum information from the server and/or client is what you will see in the logs. Please share it.FacebookTwitterRedditEmailPrintLinkedInGoogleTumblrPinterest Related posts: Using the NetWorker Software Distribution Functionality The virtue of persistence Windows block based backup with Linux AFTDs NetWorker on Linux – Ditching ext3 for xfs Posted Lucky it's a lab server otherwise there'd be trouble at the station. Are you sure you want to continue?CANCELOKWe've moved you to where you read on your other device.Get the full title to continueGet the full title to continue reading from where you

For example, if tape drives have been experiencing issues and failures overnight from 22:00 through to 08:00 the next day, that's a 10 hour movie. Re: C:\ Cannot determine status of backup process. For example, if you wanted a list of all your groups, whether they automatically clone and which pool they clone to, it would be as simple as: C:\> list-resources -t group http://www.tek-tips.com/viewthread.cfm?qid=1250522 Use mminfo to determine job status EitanS Jul 12, 2016 8:09 AM (in response to bingo) Thank you.Now it's work fine.

nsrmmd restart interval – This is how long, in minutes, NetWorker will wait between restart attempts of an nsrmmd process. Please write to networker-request < at > listserv.temple.edu if you have any problems with this list. This is not something the average user should do without talking to their support people by the way, but, well, I am support people and it was a lab server… This This sort of "defaults" component would preferably be run as a wizard in NMC on first install, and administrators would be asked if they want to re-run it upon updates. --

  1. To do this:UNIX: Run df /nsr/tmp.Windows: Right-click the drive where the NetWorker software is installedand select Properties.• Verify that all relevant NetWorker Module binaries are installed on the RE: cannot determine
  2. Ultimately, prevent IP theft, fraud, and cybercrime.Explore products and solutions from RSA.Visit RSA.comOverviewEnterprise Network HardwareSwitchesRouters and Wireless NetworkingOverviewDocumentumLEAPInfoArchiveOverviewDell LaptopsDell DesktopsDell Thin Clients and VDI ProductsNo results foundNo results foundMODERN DATA CENTERGet
  3. If so, the firewall/router may be terminating the control connection of the backup job.
  4. By default, this is 2 minutes.

Can be changed in the group properties/advanced tab. To be more specific, client platforms must not be changed – at least while keeping the same client name. Specifically, there are three key settings, all maintained within the NetWorker server resource itself. Any ideas on what I can do to 1) figure out what is causing the problem? 2) fix it?Recent changes: Upgraded server to 7.3.2 on 11/16/2006 and client on 11/28/2007 installed

By joining you are opting in to receive e-mail. navigate to this website However, they may not be optimal in either of the following two scenarios: Very busy datazones that have a large number of devices, even if they're in the same LAN; WAN-connected The reason for this is that index data is incompatible between client platforms. Ils s'adressent exclusivement à la personne destinataire.

There's no guarantee, but it might. Are you aComputer / IT professional?Join Tek-Tips Forums! We also report on the client ID wherever possible too. (In fact, given how important it is to regularly, routinely extract details of clients and their client ID fields, the check-clients More about the author Use mminfo to determine job status." message on aix server, Brendan Sandes<= Re: [Networker] "Cannot determine status of backup process.

For example, you might have options where you can specify the following defaults for any new client: Parallelism Priority* Group Schedule Browse Policy Retention Policy Remote Access etc. Client operating systems must not be changed. Posted in Features, NetWorker | Tagged: 7.5.x, clean volume, delete saveset, nsrmm, nsrstage | 7 Comments » Ready for {reading|writing}, idle Posted by Preston on 2009-04-23 Sometimes NetWorker adminsitrators find themselves

Si > cet envoi ne vous est pas destiné, ou si vous l'avez reçu par erreur, et > afin de ne pas violer le secret des correspondances, vous ne devez pas

Where is this useful? If a recovery is waiting for the tape you're reading on to clone from, the recovery will get a chance to run before all cloning has finished, rather than you having Report Abuse Like Show 0 Likes (0) Go to original post Actions More Like This Retrieving data ... Well, what isn't always a useful command depending on the Unix environment you're on, and I'm even seeing some sites where it's not installed (e.g., Solaris platforms where the /usr/ccs area

Additionally, as a sanity check run once a week (or even once a day), how about checking to see whether there's any clients with empty indices? Must have the NetWorker regular client installed and running in order for the module software to correctly install and activate, Can work with the 7.4.x NetWorker server with the exception that Posted in NetWorker | Tagged: CLI, Enhancements, IDATA Tools | 3 Comments » Screen shots don't constitutelogs Posted by Preston on 2009-04-29 You might term this an appeal from every person http://skimwp.org/cannot-determine/cannot-determine-status-of-backup-process-networker.php I was pleasantly surprised when every beta tester for IDATA Tools v4 commented on how useful the utility was for their environment.

This is definitely changed behaviour and I don't like it, given that it's very common for backup administrators to delete one or two savesets here and there from disk. Disk backup unit space will get released at the end of each portion, meaning that instead of waiting for 500 GB to be staged, you'll see space reclaimed after approximately 100GB, It's actually easy. Please type your message and try again. 2 Replies Latest reply: Mar 6, 2007 7:27 AM by Hrvoje Crvelin "Cannot determine status of backup process." Karen McArthur Mar 6, 2007 6:34

In either of these scenarios, if you're seeing periodic phases where NetWorker goes through restarting nsrmmd processes, particularly if this is happening during backups, then it's a good idea to try Red Flag This Post Please let us know here why this post is inappropriate. That will work. Honestly, if you're about to do a new NetWorker install into a site that has Oracle, skip everything else and install 7.5.1.

That is, you can design a system where the NetWorker server is in Sydney, and you have storage nodes in Melbourne, Adelaide, Perth, Brisbane, Darwin and Hobart. Join Us! *Tek-Tips's functionality depends on members receiving e-mail. As you can see, we're just not getting a successful backup at all, since NetWorker is unable to merge the index entries from the two incompatible platforms. -- * Currently running Luckily, there's settings within NetWorker to account for this.

Please write to networker-request AT listserv.temple DOT edu if you have any problems with this list.