Backup Central

Hi Guys:

I have a solaris host with a RedHat client.
I am not able to backup the client. it is scheduled to have backups once full in a week and rest incremental.

However when i mminfo the client, i got to know that backup has happened only for 4 days and last was on 14th NOv 2011-Full backup.

Since 14th the backup is not happening.

As per the unix SA there were no changes on Client since 14th.
The client version is 7.4.1. I checked there is no firewall. Host entry looks ok.
savefs -p is also good.

But backup is failing.

Any help will be greatly apprteciated.

Adding few lines


Till 14th the backup was working. I got this message in completed tab for index

******:index 75146:save: Saving files modified since Tue Nov 15 21:00:15 2011
******:index /nsr/index/******/db6/4eaf0000/
******:index /nsr/index/******/db6/
******:index /nsr/index/******/
******:index

The below error i am getting for scheduled backup:

1 retry attempted
7184:savefs: nothing to save

Check on the client to see if iptables or some other firewall software is running and if so, are the appropriate ports open?

Check also for any DNS changes regarding the client and verify that reverse DNS lookups between the NetWorker server and the client are working.

On Nov 17, 2011, at 10:48, "ruhailmushtaqvakil" <networker-forum < at > BACKUPCENTRAL.COM> wrote:

The below error i am getting for scheduled backup:

1 retry attempted
7184:savefs: nothing to save

+----------------------------------------------------------------------
|This was sent by mytechnicalknowledgebase < at > gmail.com via Backup Central.
|Forward SPAM to abuse < at > backupcentral.com.
+----------------------------------------------------------------------


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Ok another try?

I was able to backup one of the savesets

F40115L4 ****** 11/17/11 6 KB full /factiva

So i think if we put the directories in Saveset box we can have backup, but question remains same:
Why it failed with Saveset: All?

When i checked for some more directories like /home and /tmp i am getting a failure. They dont exists.However their backups happened on 14th of Nov.

Is it like on 15th some directories were changed or deleted or something else.

Pls help.

Calling Bingo>>>>>>>>>>>>>>>>>>>>>>>>>>.

Well, what shall i suggest if you don't even know what happened to the system. And your puzzle pieces are not really helpful. But if the OS files are really incomplete, how do you expect dependent programs to run?

- First i would look whether other applications are running fine.
- Then, if you still can, look at the OS logfiles.
- Next, try to run backups from the client first before you start with an automatic backup.
Use the command line and add verbosity-
And do not use "savefs -p" but "savegrp -p"

Good luck.

It sounds like /home and /tmp are not mounted on the client. Is the client actually working properly? On the client, what happens if you type "mount -a" as the root user?

On 11 17, 2011, at 11:14 AM, ruhailmushtaqvakil wrote:

When i checked for some more directories like /home and /tmp i am getting a failure. They dont exists.However their backups happened on 14th of Nov.

Is it like on 15th some directories were changed or deleted or something else.

Pls help.

+----------------------------------------------------------------------
|This was sent by mytechnicalknowledgebase < at > gmail.com via Backup Central.
|Forward SPAM to abuse < at > backupcentral.com.
+----------------------------------------------------------------------


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Thanks stan.

I guessed the same. However when i asked the unix SA to cat /etc/fstab on linux box.
It seems that all directories are mounted.

[root@******* ~]# cat /etc/fstab
LABEL=/1 / ext3 defaults 1 1
LABEL=/home1 /home ext3 defaults 1 2
LABEL=/tmp1 /tmp ext3 defaults 1 2
LABEL=/var1 /var ext3 defaults 1 2
LABEL=/factiva/app1 /factiva/app ext3 defaults 1 2
LABEL=/factiva/applog1 /factiva/applog ext3 defaults 1 2
LABEL=/factiva/appdat1 /factiva/appdata ext3 defaults 1 2
LABEL=/boot1 /boot ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
LABEL=SW-cciss/c0d0p3 swap swap defaults 0 0
[root@****** ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/cciss/c0d0p2 7.8G 3.3G 4.2G 45% /
/dev/cciss/c0d0p10 8.4G 247M 7.7G 4% /home
/dev/cciss/c0d0p9 3.9G 74M 3.7G 2% /tmp
/dev/cciss/c0d0p8 3.9G 311M 3.4G 9% /var
/dev/cciss/c0d0p7 30G 1.3G 27G 5% /factiva/app
/dev/cciss/c0d0p6 39G 11G 27G 28% /factiva/applog
/dev/cciss/c0d0p5 39G 179M 37G 1% /factiva/appdata
/dev/cciss/c0d0p1 122M 25M 91M 22% /boot
tmpfs 30G 0 30G 0% /dev/shm

I'd temporarily, to test, change the saveset to explicitly backup /etc, run savegrp -G "GroupYourClientIsIn" -c Clientname -vvvvv -I

That way you'll more verbosity in the logs.

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER < at > LISTSERV.TEMPLE.EDU] On Behalf Of ruhailmushtaqvakil
Sent: Thursday, November 17, 2011 12:14 PM
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Subject: [Networker] 7241:savegrp: nsrim run recently, skipping

[root < at > ******* ~]# cat /etc/fstab
LABEL=/1 / ext3 defaults 1 1
LABEL=/home1 /home ext3 defaults 1 2
LABEL=/tmp1 /tmp ext3 defaults 1 2
LABEL=/var1 /var ext3 defaults 1 2
LABEL=/factiva/app1 /factiva/app ext3 defaults 1 2
LABEL=/factiva/applog1 /factiva/applog ext3 defaults 1 2
LABEL=/factiva/appdat1 /factiva/appdata ext3 defaults 1 2
LABEL=/boot1 /boot ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
LABEL=SW-cciss/c0d0p3 swap swap defaults 0 0
[root < at > ****** ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/cciss/c0d0p2 7.8G 3.3G 4.2G 45% /
/dev/cciss/c0d0p10 8.4G 247M 7.7G 4% /home
/dev/cciss/c0d0p9 3.9G 74M 3.7G 2% /tmp
/dev/cciss/c0d0p8 3.9G 311M 3.4G 9% /var
/dev/cciss/c0d0p7 30G 1.3G 27G 5% /factiva/app
/dev/cciss/c0d0p6 39G 11G 27G 28% /factiva/applog
/dev/cciss/c0d0p5 39G 179M 37G 1% /factiva/appdata
/dev/cciss/c0d0p1 122M 25M 91M 22% /boot
tmpfs 30G 0 30G 0% /dev/shm

+----------------------------------------------------------------------
|This was sent by mytechnicalknowledgebase < at > gmail.com via Backup Central.
|Forward SPAM to abuse < at > backupcentral.com.
+----------------------------------------------------------------------




via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

That just says what SHOULD be mounted. It does not say what IS actually mounted.

Ask the SA to type "df -kh"' and see what happens.

On 11 17, 2011, at 1:13 PM, ruhailmushtaqvakil wrote:

[root < at > ******* ~]# cat /etc/fstab
LABEL=/1 / ext3 defaults 1 1
LABEL=/home1 /home ext3 defaults 1 2
LABEL=/tmp1 /tmp ext3 defaults 1 2
LABEL=/var1 /var ext3 defaults 1 2
LABEL=/factiva/app1 /factiva/app ext3 defaults 1 2
LABEL=/factiva/applog1 /factiva/applog ext3 defaults 1 2
LABEL=/factiva/appdat1 /factiva/appdata ext3 defaults 1 2
LABEL=/boot1 /boot ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
LABEL=SW-cciss/c0d0p3 swap swap defaults 0 0
[root < at > ****** ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/cciss/c0d0p2 7.8G 3.3G 4.2G 45% /
/dev/cciss/c0d0p10 8.4G 247M 7.7G 4% /home
/dev/cciss/c0d0p9 3.9G 74M 3.7G 2% /tmp
/dev/cciss/c0d0p8 3.9G 311M 3.4G 9% /var
/dev/cciss/c0d0p7 30G 1.3G 27G 5% /factiva/app
/dev/cciss/c0d0p6 39G 11G 27G 28% /factiva/applog
/dev/cciss/c0d0p5 39G 179M 37G 1% /factiva/appdata
/dev/cciss/c0d0p1 122M 25M 91M 22% /boot
tmpfs 30G 0 30G 0% /dev/shm

+----------------------------------------------------------------------
|This was sent by mytechnicalknowledgebase < at > gmail.com via Backup Central.
|Forward SPAM to abuse < at > backupcentral.com.
+----------------------------------------------------------------------


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Well Stan, before sending an email i verified here from another unix SA here in my location and he says there is no difference, it just gives you size in kilobytes.

Please throw some light on this. Pls dont mind.

In regard to: [Networker] 7241:savegrp: nsrim run recently, skipping,...:

I was able to backup one of the savesets

F40115L4 ****** 11/17/11 6 KB full /factiva

So i think if we put the directories in Saveset box we can have backup,
but question remains same: Why it failed with Saveset: All?

In one of your earlier posts, you mentioned that the client was running
the networker 7.4.1 client.

I don't think 7.4.x is still supported, but even if it is, the early
releases in 7.4.x had a number of problems. If you're going to use
the 7.4.x series, I highly recommend you upgrade to the last point
release, probably 7.4.5.something.

Beyond that, there are several things that can cause "nothing to save"
messages. I've seen it in several different instances over the years,
sometimes because the version of the client software didn't correctly
support the OS & version of the client, and other times because of client
index corruption or because the client index data was being saved to
the wrong index. You may wish to try a

nsrck -L6 clientname

on your networker server, to do all available index checks for that client
index.

There was an earlier suggestion, I believe from Chester, to use
(on the networker server)

savegrp -pvvvv -c your_client_name_here your_client_group_here

and I also recommend you try that. Once that completes, whether it works
or not, have the admin on the client run

nsr_render_logs /nsr/logs/daemon.raw

and send you the output. That might also contain a clue as to what the
problem is.

Tim
--
Tim Mooney Tim.Mooney < at > ndsu.edu
Enterprise Computing & Infrastructure 701-231-1076 (Voice)
Room 242-J6, IACC Building 701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER