Repair Cannot Determine Status Of Backup Process Use Mminfo Tutorial

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

Cannot Determine Status Of Backup Process Use Mminfo

Can be changed in the group properties/advanced tab. Assuming though that for some reason you don't have a clone, there's a good chance your data is hosed** – recover, nwrecover, winworkr are not going to get you past that EMC NetWorker Commentary and Tips PagesAbout Contact Archives Why the flag? Close Box Join Tek-Tips Today! weblink

In very, very few cases the ready/idle state is the default of the device that's in the idle state, but my recommendation is that if you've got a device wedged in Posted in NetWorker, Support | Comments Off on Screen shots don't constitutelogs 7.5(.1) changed behaviour - deleting savesets fromadv_file Posted by Preston on 2009-04-25 Yesterday I wanted to delete a few I.e., this is one of these compelling reasons for 7.5.x. RE: cannot determine the status of the backup process 605 (Instructor) 5 Jul 06 08:47 Well, move the problematic clients to a separate group and start their group manually from the https://community.emc.com/thread/78360?start=0&tstart=0

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. RE: cannot determine the status of the backup process speculos (TechnicalUser) 6 Jul 06 04:57 How can you be sure that you don't have any network problem?How often do you check Now has a client configuration wizard that works within NMC and makes Oracle backup configuration a breeze. Reporting enhancements Under reporting more generally, there's a whole raft of enhancements: Both client-report and review-res now allow you to specify additional fields to be reported on; thus, it doesn't matter

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 If they are valild, the next problem may be that the host is taking longer than the inactivity timeout of the group (30 minutes by default). Use mminfo t 2010-05-20 09:36:14 Subject: [Networker] Cannot determine status of the backup process. RE: cannot determine the status of the backup process olympe69 (TechnicalUser) (OP) 5 Jul 06 08:53 when we do the command manually after problem,is already ok.THis problem comes monday but thursday

You can not post a blank message. It has two output modes – the default is "human readable", designed for when you just want to get some information out of the server. I'd always thought that 4 was a terrible default setting, being too high, in a modern environment; you can imagine then what I thought when I found the new default setting http://www.tek-tips.com/viewthread.cfm?qid=1250522 However, when we start talking about datazones that encompass WANs, we do have to take into account the level of latency between the storage nodes and the backup server.

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, Check it out. By "portion control" I mean automatically break up cloning and staging operations into smaller, more granular activities with pauses inbetween by running operating on savesets at any one time. 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.

  1. E:\ aborted due to inactivity Networker client version is "EMC NetWorker 7.4.2.Build.431" Thu May 20, 2010 5:33 am Denis Guest Cannot determine status of the backup process.
  2. Report Abuse Like Show 0 Likes (0) Go to original post Actions More Like This Retrieving data ...
  3. You can either fix this on the router/firewall or start networker with the system enviornment variable set of NSR_KEEPALIVE_WAIT (found in the release notes p 139) Cheers!
  4. Oracle Client Configuration Step 3 Oracle Client Configuration Step 4 The above step is where things get fun.
  5. In short, client parallelism settings are typically not something that you should set blindly.
  6. You can access the archives at http://listserv.temple.edu/archives/networker.html or via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER [Morewiththissubject...] Re: [Networker] "Cannot determine status of backup process.
  7. Please, please don't send them as a picture pasted into a word document.
  8. Your support person will thank you for it, and you'll probably get resolution quicker. -- I have one other personal preference when it comes to screen shots.
  9. Use mminfo t, amar chakma Re: [Networker] Cannot determine status of the backup process.

I do strongly recommend that you give it a go – it's great at automating a lot of tests and checks against clients, meaning that if you've got even just one this page Please wait a few minutes and refresh this page. Here's (some of) the output from that backup, using NetWorker 7.5.1 as the server and client in all 3 instances: [root@nox ~]# savegrp -l full -c dopey idata 40473:savegrp: command ' Use mminfo to determine job status.* Siplace:C:\ Cannot determine status of backup process.

Use mminfo t Try increase the client attribute "inactivity timeout" to a greater value( say 300). have a peek at these guys Please see group completion details for more information.Failed: Explorer, Siplacesaveset Siplace:DISASTER_RECOVERY:\: percentage of inactive files by count: 99.86, by space: 73.62saveset Siplace:Siplace:index: percentage of inactive files by count: 0.00, by space: Sometimes there is a place for screen shots - they can be useful in certain situations. Client operating systems must not be changed.

Use mminfo t amar chakma I also read a post on this forum sometime back where a firewall was configured and it kills the idle backup session after certain period. Then, right click the server (absolute topmost entry in the configuration tree) and choose "Properties". 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 check over here nsrmmd control timeout – This is the number of minutes NetWorker waits for storage node requests to be completed.

There's a good reason why I find this inappropriate. What had been a tried and true version of saveset deletion under 7.4.x and below appears to not be so useful under 7.5.1. I have to say, and I'll be blunt here, I find the policy change reasonably inappropriate.

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

Use mminfo to determine job status EitanS Jul 12, 2016 4:19 AM Hi,I have a 2003 networker server V7.6.4 Build 1070. Designed for system administrators and managers alike, it focuses on features, policies, procedures and the human element to ensuring that your company has a suitable and working backup system. 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. However, with NetWorker, a product that features excellent logging, there is no substitute for sending through the appropriate log files to your support provider.

I recently get >>> this message for one of my servers : >>> >>> "Cannot determine status of backup process. Archive for the ‘NetWorker' Category « Previous Entries Next Entries » Basics - Adding new clients in 7.4.4 andhigher Posted by Preston on 2009-05-13 One of the policy changes made in Imagine my surprise when, instead of seeing a chunk of space being freed up, I got a lot of the following notifications: nsrd adv_file warning: Failed to fetch the saveset(ss_t) structure this content 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

Some people do have a tendency to shoot of a screen request when they request support, and as a long term provider of support and consulting in NetWorker, I'd just like 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 For both cloning and staging, you also get a level of reporting not normally available. It's maddening, right?

jumbo 11 is 378 and jumbo update 1 is 386. I realise that when the server bootstraps itself, it still needs to fall back on standard defaults, and that's fine. Confirm and manage identities. Others servers in the group >>> are ok. >>> >>> May someone can help me to understand what happen and how to repair it ? >>> >>> Many Thanks >>> >>>

I would have to say that in 99.99% of cases this is due to one of the following two things: The data was never properly backed up in the first place. The reason for this is that index data is incompatible between client platforms. Requires features that exist only in Networker 7.5.x as the underlying client. Confirm and manage identities.

Using this analogy, sending a screen shot is akin to sending one single frame from a 10 hour movie and asking someone to provide you a complete plot summary and script This is obviously just a small inconvenience, but if you've not picked up on this yet, you should be aware of it when you start working with these newer versions of Consider the following examples: In a disk to tape cloning operation, a disk backup unit may be reported as "ready for reading, idle". Use mminfo t, Denis Re: [Networker] Cannot determine status of the backup process.

Explorer: OSSR_B level=full, 268 MB 00:01:07 138 files Explorer: OSSR_C level=full, 57 GB 00:44:07 269536 files* Explorer:DISASTER_RECOVERY:\ 80889:save: Created disaster recover logical object. E:\ aborted due to inactivity Networker client version is "EMC NetWorker 7.4.2.Build.431" +---------------------------------------------------------------------- |This was sent by sriharsha212 < at > gmail.com via Backup Central. |Forward SPAM to abuse < at Backups may consistently fail at specific points. All rights reserved.PrivacyLegalContactUnited StatesProductsSolutionsShopSupportServicesPartnersCompanyMy AccountLog InBROWSE PRODUCTSStorageServersConverged InfrastructureData ProtectionSecurityNetworkingContent ManagementDell Products for WorkSearch Products by NameProducts A-ZShop EMC ProductsProduct CommunitySoftware DownloadsLive ChatContact SalesCall 1-866-438-3622Call 1-866-438-3622Storage CategoriesOverviewEnterpriseEntry & MidrangeSoftware DefinedAll-FlashCloudManagement & NetworkingStorage

Failing to rename a client in these circumstances can result in index corruption. Explorer: DISASTER_RECOVERY:\ level=full, 15 KB 00:44:09 4 files risco-bk: index:Explorer level=full, 4 KB 00:00:01 4 files* Siplace:All savefs Siplace: succeeded.* Siplace:DISASTER_RECOVERY:\ savegrp: suppressed 103 lines of output.* Siplace:DISASTER_RECOVERY:\ skip: SIPLACEProLog.ldf *