SEO

#1 (**permalink**) 01-16-2008, 07:31 AM

Witam,
Mama mksysb zrobiony przez nim'a, i.. chcialbym zrobic
drugi (nastepnego dnia). Komenda uzyta do zrobienia
pierwszego mksysb wygladala:
nim -o define -t mksysb ... (z -o define),
no i nie daje jej sie uzyc drugi raz - komunikat mowi ze
resource already exists (nic dziwnego). Opcja -o update
nie dziala dla resource'a mksysb - no i pytanie:
- robiac mksysb przy uzyciu nim'a, i chcac miec mksysb
co dzin/co tydzien:
- jest jakas opcja komendy 'nim' ktora pozwala na
nadpisanie poprzedniego mksysb, czy tez moze
- trzeba zrobic skrypt ktory usunie poprzednio stworzony
mksysb resource i stworzy nowy?
pozdrawiam
t

#2 (**permalink**) 01-16-2008, 07:31 AM

Sorry, using polish by default.. see please below:

Got mksysb done using NIM; used nim -o define.. - and,
what is somehow expected, cannot use same command again,
to have fresh mksysb (resource already exists).
Question is how to do fresh mksysb using NIM, any advices?
So far I though may use some script to remove old resporce,
and create new one with mksysb every day, but looks little
bit artificial.. any other suggestions pelase?
Thanks you in advance and regards
t

#3 (**permalink**) 01-16-2008, 07:31 AM

On Jan 14, 2:17 pm, ser...@gdzies.tam.na.il.pw.edu.pl wrote:
> Sorry, using polish by default.. see please below:
>
> Got mksysb done using NIM; used nim -o define.. - and,
> what is somehow expected, cannot use same command again,
> to have fresh mksysb (resource already exists).
> Question is how to do fresh mksysb using NIM, any advices?
> So far I though may use some script to remove old resporce,
> and create new one with mksysb every day, but looks little
> bit artificial.. any other suggestions pelase?
> Thanks you in advance and regards
> t

Its a mksysb resource ? Just replace the mksysb. In case you have
build a spot from the mksysb you should update/rebuild the spot.

The point is that a nim define operation defines an NIM object
referencing to a physical entity ( in this case to a mksysb ) .

hth
Hajo

#4 (**permalink**) 01-16-2008, 07:31 AM

Hi,

You can create mksysb object by host name + date of creation
(hostname_YYYYMMDDhhmmss) and remove the old one after successful
mksysb backup (-o remove). I was using it that way, not sure if NIM
will remove the mksysb files too or only object, got to check it.

Pozdrawiam :-)

#5 (**permalink**) 01-16-2008, 07:31 AM

just to be sure - by 'replace' you mean remove old
mksysb and create new one, or maybe there is an option
to 'owervrite' old one? something like 'update' for other
resources?
regards
t

#6 (**permalink**) 01-16-2008, 07:31 AM

...heee... tez pozdrawiam

#7 (**permalink**) 01-16-2008, 07:31 AM

On Jan 15, 10:27 am, ser...@gdzies.tam.na.il.pw.edu.pl wrote:
> just to be sure - by 'replace' you mean remove old
> mksysb and create new one, or maybe there is an option
> to 'owervrite' old one? something like 'update' for other

During the creation of the NIM mksysb object for a machine you can say
that the mksysb will be created or not. AFAIK you do not use it
normaly for UPDATING a mksysb.
Thus th definition of a mksysb object is a one timer. Later you use a
script to update the mksysb by either overwriting or replacing it. The
script does normaly:
- mount the exported mksysb directory on the client
- starts an mksysb -eXi on the client which will write to the mounted
nfs share

You might like to read the latest "NIM from A-Z" redbook
http://www.redbooks.ibm.com/redbooks/pdfs/sg247296.pdf

hth
Hajo

#8 (**permalink**) 01-16-2008, 07:31 AM

On Jan 15, 4:07 am, Hajo Ehlers <serv...@metamodul.com> wrote:
> On Jan 15, 10:27 am, ser...@gdzies.tam.na.il.pw.edu.pl wrote:
>
> > just to be sure - by 'replace' you mean remove old
> > mksysb and create new one, or maybe there is an option
> > to 'owervrite' old one? something like 'update' for other
>
> During the creation of the NIM mksysb object for a machine you can say
> that the mksysb will be created or not. AFAIK you do not use it
> normaly for UPDATING a mksysb.
> Thus th definition of a mksysb object is a one timer. Later you use a
> script to update the mksysb by either overwriting or replacing it. The
> script does normaly:
> - mount the exported mksysb directory on the client
> - starts an mksysb -eXi on the client which will write to the mounted
> nfs share
>
> You might like to read the latest "NIM from A-Z" redbookhttp://www.redbooks.ibm.com/redbooks/pdfs/sg247296.pdf
>
> hth
> Hajo

NIM cannot have 2 resources with the same name. Therefore you can
either use the convention noted earlier of using a date stamp in the
mksysb creation, or remove the resource before creating the new/
current one.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

mksysb, nim, zawartosc resource'a