Re: Problems backing up Linux client - missed filesystem

2011-12-12 Thread Thomas Denier
-Farren Minns wrote: -

TSM Server 5.5.2.0 on Solaris

Linux Client 5.5.0.0 - Real Application Cluster v6

I have the following issue. When the backup runs as a scheduled
service it only checks/backs up the /boot filesystem.

I put the following in dsm.sys and that certainly allows me to run
manual backups, but the incremental still doesn't work.

virtualmountpoint /

Any ideas?

I generally don't recommend using maintenance level 0 of a new
release of TSM code. Before Version 6 came out we were generally
getting good results with 5.5.1.0 client code. We are now getting
good results with 6.2.2.0 client code on systems with OS levels
supported for use with 6.2 client code.

Thomas Denier

Re: Problems backing up Linux client - missed filesystem

2011-12-12 Thread Minns, Farren - Chichester
OK, thanks for the advice.

Regards

Farren




-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Thomas 
Denier
Sent: 12 December 2011 16:49
To: ADSM-L@vm.marist.edu
Subject: Re: [ADSM-L] Problems backing up Linux client - missed filesystem

-Farren Minns wrote: -

TSM Server 5.5.2.0 on Solaris

Linux Client 5.5.0.0 - Real Application Cluster v6

I have the following issue. When the backup runs as a scheduled
service it only checks/backs up the /boot filesystem.

I put the following in dsm.sys and that certainly allows me to run
manual backups, but the incremental still doesn't work.

virtualmountpoint /

Any ideas?

I generally don't recommend using maintenance level 0 of a new
release of TSM code. Before Version 6 came out we were generally
getting good results with 5.5.1.0 client code. We are now getting
good results with 6.2.2.0 client code on systems with OS levels
supported for use with 6.2 client code.

Thomas Denier


John Wiley  Sons Limited is a private limited company registered in England 
with registered number 641132.
Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, 
United Kingdom. PO19 8SQ.



Re: Problems backing up Linux client - missed filesystem

2011-12-12 Thread Ehresman,David E.
Have you checked your dsmsched.log on the client for errors?  Have you checked 
your tsm server actlog for the same time period for informative messages?

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Minns, 
Farren - Chichester
Sent: Monday, December 12, 2011 12:01 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Problems backing up Linux client - missed filesystem

OK, thanks for the advice.

Regards

Farren




-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Thomas 
Denier
Sent: 12 December 2011 16:49
To: ADSM-L@vm.marist.edu
Subject: Re: [ADSM-L] Problems backing up Linux client - missed filesystem

-Farren Minns wrote: -

TSM Server 5.5.2.0 on Solaris

Linux Client 5.5.0.0 - Real Application Cluster v6

I have the following issue. When the backup runs as a scheduled
service it only checks/backs up the /boot filesystem.

I put the following in dsm.sys and that certainly allows me to run
manual backups, but the incremental still doesn't work.

virtualmountpoint /

Any ideas?

I generally don't recommend using maintenance level 0 of a new
release of TSM code. Before Version 6 came out we were generally
getting good results with 5.5.1.0 client code. We are now getting
good results with 6.2.2.0 client code on systems with OS levels
supported for use with 6.2 client code.

Thomas Denier


John Wiley  Sons Limited is a private limited company registered in England 
with registered number 641132.
Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, 
United Kingdom. PO19 8SQ.



Re: Problems backing up Linux client - missed filesystem

2011-12-12 Thread Minns, Farren - Chichester
Hi

Yes, and not actually seeing errors.

The backup runs fine, but only check the /boot filesystem.

Regards

Farren






-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Ehresman,David E.
Sent: 12 December 2011 17:07
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Problems backing up Linux client - missed filesystem

Have you checked your dsmsched.log on the client for errors?  Have you checked 
your tsm server actlog for the same time period for informative messages?

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Minns, 
Farren - Chichester
Sent: Monday, December 12, 2011 12:01 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Problems backing up Linux client - missed filesystem

OK, thanks for the advice.

Regards

Farren




-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@vm.marist.edu] On Behalf Of Thomas 
Denier
Sent: 12 December 2011 16:49
To: ADSM-L@vm.marist.edu
Subject: Re: [ADSM-L] Problems backing up Linux client - missed filesystem

-Farren Minns wrote: -

TSM Server 5.5.2.0 on Solaris

Linux Client 5.5.0.0 - Real Application Cluster v6

I have the following issue. When the backup runs as a scheduled
service it only checks/backs up the /boot filesystem.

I put the following in dsm.sys and that certainly allows me to run
manual backups, but the incremental still doesn't work.

virtualmountpoint /

Any ideas?

I generally don't recommend using maintenance level 0 of a new
release of TSM code. Before Version 6 came out we were generally
getting good results with 5.5.1.0 client code. We are now getting
good results with 6.2.2.0 client code on systems with OS levels
supported for use with 6.2 client code.

Thomas Denier


John Wiley  Sons Limited is a private limited company registered in England 
with registered number 641132.
Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, 
United Kingdom. PO19 8SQ.



John Wiley  Sons Limited is a private limited company registered in England 
with registered number 641132.
Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, 
United Kingdom. PO19 8SQ.



Re: Problems backing up Linux client - missed filesystem

2011-12-12 Thread Richard Sims
If your scheduler is not running under CAD, any changes made to dsm.sys and 
dsm.opt will not be known to that scheduler process until it is restarted.

You should also review the output of 'dsmc q opt' and 'dsmc q inclexcl' for 
containing what you actually want, as compiled specifications.  An option of 
virtualmountpoint / seems pointless.

Richard Sims