Re: TSM 6.3

2012-02-22 Thread Bos, Karel
Hi,

Any info in db2diag.log?

https://www-304.ibm.com/support/docview.wss?uid=swg21383716

Kind regards,

Karel

-Oorspronkelijk bericht-
Van: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Namens Killam, 
Perpetua
Verzonden: woensdag 22 februari 2012 10:40
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: [ADSM-L] TSM 6.3

ANYONE HAD ISSUES AFTER UPGRADING TO TSM6.3 FROM 6.2.1 on aix 6.1

Didn't have problems with another upgrade

Opened a ticket with IBM , WILL SEE WHAT THEY SAY


ANR7801I Subsystem process ID is 5112088.
ANR0900I Processing options file /opt/tivoli/tsm/server/bin/dsmserv.opt.
ANR7811I Using instance directory /opt/tivoli/tsm/server/bin.
ANR4726I The ICC support module has been loaded.
ANR0990I Server restart-recovery in progress.
ANR0152I Database manager successfully started.
ANR1380I The buffer pool monitor switch is enabled.
ANR0171I rdbdb.c(7225): Error detected on 1:1, database in evaluation
mode.
ANR0152I Database manager successfully started.
ANR0171I dbiconn.c(1952): Error detected on 0:1, database in evaluation
mode.
ANR0162W Supplemental database diagnostic information:  -1:08003:-9
([IBM][CLI Driver] CLI0106E  Connection is closed. SQLSTATE=08003).
ANR1382E The server failed with error code 4522 when attempting to
update a database parameter.

Tsm server won't start



--
___

This email may be privileged and/or confidential, and the sender does not waive 
any related rights and obligations.
Any distribution, use or copying of this email or the information it contains 
by other than an intended recipient is unauthorized. If you received this email 
in error, please advise the sender (by return email or otherwise) immediately. 
You have consented to receive the attached electronically at the above-noted 
email address; please retain a copy of this confirmation for future reference.

Ce courriel est confidentiel et protégé. L'expéditeur ne renonce pas aux droits 
et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce 
courriel ou des renseignements qu'il contient par une personne autre que le 
(les) destinataire(s)
désigné(s) est interdite. Si vous recevez ce courriel par erreur, veuillez en 
aviser l'expéditeur immédiatement, par retour de courriel ou par un autre 
moyen. Vous avez accepté de recevoir le(s) document(s)
ci-joint(s) par voie électronique à l'adresse courriel indiquée ci-dessus; 
veuillez conserver une copie de cette confirmation pour les fins de reference 
future.





Dit bericht is vertrouwelijk en kan geheime informatie bevatten enkel bestemd 
voor de geadresseerde. Indien dit bericht niet voor u is bestemd, verzoeken wij 
u dit onmiddellijk aan ons te melden en het bericht te vernietigen. Aangezien 
de integriteit van het bericht niet veilig gesteld is middels verzending via 
internet, kan Atos Nederland B.V. niet aansprakelijk worden gehouden voor de 
inhoud daarvan. Hoewel wij ons inspannen een virusvrij netwerk te hanteren, 
geven wij geen enkele garantie dat dit bericht virusvrij is, noch aanvaarden 
wij enige aansprakelijkheid voor de mogelijke aanwezigheid van een virus in dit 
bericht. Op al onze rechtsverhoudingen, aanbiedingen en overeenkomsten 
waaronder Atos Nederland B.V. goederen en/of diensten levert zijn met 
uitsluiting van alle andere voorwaarden de Leveringsvoorwaarden van Atos 
Nederland B.V. van toepassing. Deze worden u op aanvraag direct kosteloos 
toegezonden.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Atos Nederland B.V. group liability cannot be 
triggered for the message content. Although the sender endeavours to maintain a 
computer virus-free network, the sender does not warrant that this transmission 
is virus-free and will not be liable for any damages resulting from any virus 
transmitted. On all offers and agreements under which Atos Nederland B.V. 
supplies goods and/or services of whatever nature, the Terms of Delivery from 
Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly 
submitted to you on your request.

Atos Nederland B.V. / Utrecht
KvK Utrecht 30132762


Re: Server DB restore from offsite TSM server SNAPSHOT

2012-02-21 Thread Bos, Karel
Hi,

From memory one should do the upd server force sync=yes on the target machine.

In this case ON server-B do upd server server-a forcesync=yes.

After restore of the DB server-server comm will be down again because 
out-of-sync issues.

Regards,

Karel

-Oorspronkelijk bericht-
Van: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Namens Zoltan 
Forray/AC/VCU
Verzonden: dinsdag 21 februari 2012 15:45
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: [ADSM-L] Server DB restore from offsite TSM server SNAPSHOT

I am trying to experiment with doing a V5 to V6 conversion by first restoring 
the V5 server to a test server.

We have very little experience doing DB restores and none involving an offsite 
TSM server.  My first attempts failed.  I think I know how to fix it but the 
docs on how to perform a DB restore are a little contradictory to what I want 
to do.

SERVER-A performs DB SNAPSHOT backups to SERVER-B via server-to-server 
definitions.

Installed a same-level TSM server onto a test machine.
Did dsmserv format to prepare DB space to the equivalent of  SERVER-A.
Replaced the test server volhist, devconfig and dsmserv.opt files from copies 
of SERVER-A like-files.

Tried to do a dsmserv restore db volumenames=name.I.got.from.volhist
devclass=SERVER-B

Since I tried this over a month ago, I don't recall the error but I think it 
has to do with the server-to-server definition being out of sync since this is 
not the original SERVER-A.

My guess is to bring up the test server and manually do a UPDATE SERVER 
SERVER-B FORCESYNCE=YES

However, when I go through the book scenarios on restoring a server DB, it
says:

Attention: Do not start the server until after you restore the database (the 
next step). Starting the server before the restore would destroy any existing 
volume history files.

So, how do I do this?  Do I bring up the test server first and correct the sync 
before replacing the volhist file?

Am I wrong in how I  am trying to do this?  Is there a better/different way to 
do this?

Looking for any suggestions/hints.


Zoltan Forray
TSM Software  Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zfor...@vcu.edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will never 
use email to request that you reply with your password, social security number 
or confidential personal information. For more details visit 
http://infosecurity.vcu.edu/phishing.html






Dit bericht is vertrouwelijk en kan geheime informatie bevatten enkel bestemd 
voor de geadresseerde. Indien dit bericht niet voor u is bestemd, verzoeken wij 
u dit onmiddellijk aan ons te melden en het bericht te vernietigen. Aangezien 
de integriteit van het bericht niet veilig gesteld is middels verzending via 
internet, kan Atos Nederland B.V. niet aansprakelijk worden gehouden voor de 
inhoud daarvan. Hoewel wij ons inspannen een virusvrij netwerk te hanteren, 
geven wij geen enkele garantie dat dit bericht virusvrij is, noch aanvaarden 
wij enige aansprakelijkheid voor de mogelijke aanwezigheid van een virus in dit 
bericht. Op al onze rechtsverhoudingen, aanbiedingen en overeenkomsten 
waaronder Atos Nederland B.V. goederen en/of diensten levert zijn met 
uitsluiting van alle andere voorwaarden de Leveringsvoorwaarden van Atos 
Nederland B.V. van toepassing. Deze worden u op aanvraag direct kosteloos 
toegezonden.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Atos Nederland B.V. group liability cannot be 
triggered for the message content. Although the sender endeavours to maintain a 
computer virus-free network, the sender does not warrant that this transmission 
is virus-free and will not be liable for any damages resulting from any virus 
transmitted. On all offers and agreements under which Atos Nederland B.V. 
supplies goods and/or services of whatever nature, the Terms of Delivery from 
Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly 
submitted to you on your request.

Atos Nederland B.V. / Utrecht
KvK Utrecht 30132762


ADMIN password exp errors during proxy backups

2012-02-21 Thread Bos, Karel
Hi,

Running for years TSM backup services we got used to do reg node XXX us=none 
and use password expiration on almost all our backup stuff.

Nowadays we get VSS backups so first thing we ran into was the proxy stuff 
needing administrators to run. OK, no issue just reg the clients without 
us=none.

After a while we run in the newest feature. NODE passwords get reset after 
expiration completely automatically (like it should) BUT the administrator 
connected to that node (and used by the VSS backups) DO NOT, resulting in:

ANR0470W Session # for administrator USER_ID refused - administrator 
password has expired.

http://www-01.ibm.com/support/docview.wss?uid=swg21460596

Above mention link pretty much tells me we CANT use password expiration anymore 
on any of the VSS backups or any proxy backup for that matter. Or do I overlook 
something?

Kind regards,

Karel







Dit bericht is vertrouwelijk en kan geheime informatie bevatten enkel bestemd 
voor de geadresseerde. Indien dit bericht niet voor u is bestemd, verzoeken wij 
u dit onmiddellijk aan ons te melden en het bericht te vernietigen. Aangezien 
de integriteit van het bericht niet veilig gesteld is middels verzending via 
internet, kan Atos Nederland B.V. niet aansprakelijk worden gehouden voor de 
inhoud daarvan. Hoewel wij ons inspannen een virusvrij netwerk te hanteren, 
geven wij geen enkele garantie dat dit bericht virusvrij is, noch aanvaarden 
wij enige aansprakelijkheid voor de mogelijke aanwezigheid van een virus in dit 
bericht. Op al onze rechtsverhoudingen, aanbiedingen en overeenkomsten 
waaronder Atos Nederland B.V. goederen en/of diensten levert zijn met 
uitsluiting van alle andere voorwaarden de Leveringsvoorwaarden van Atos 
Nederland B.V. van toepassing. Deze worden u op aanvraag direct kosteloos 
toegezonden.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Atos Nederland B.V. group liability cannot be 
triggered for the message content. Although the sender endeavours to maintain a 
computer virus-free network, the sender does not warrant that this transmission 
is virus-free and will not be liable for any damages resulting from any virus 
transmitted. On all offers and agreements under which Atos Nederland B.V. 
supplies goods and/or services of whatever nature, the Terms of Delivery from 
Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly 
submitted to you on your request.

Atos Nederland B.V. / Utrecht
KvK Utrecht 30132762


Re: Server DB restore from offsite TSM server SNAPSHOT

2012-02-21 Thread Bos, Karel
Zoltan,

SERVER-A performs DB SNAPSHOT backups to SERVER-B via server-to-server 
definitions.

U will want to access the DB backup made by the production server, so ur test 
server should be able to access it (and there comes the upd server forcesync 
in).

Regards,

Karel

-Oorspronkelijk bericht-
Van: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Namens Zoltan 
Forray/AC/VCU
Verzonden: dinsdag 21 februari 2012 16:14
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: Re: [ADSM-L] Server DB restore from offsite TSM server SNAPSHOT

Karel,

Thanks for the idea.

This would be fine/work if I was actually restoring/replacing a production 
server.  I am only trying to restore the DB to a test server.  If I did the 
sync from SERVER-B, it would sync the wrong, production, running server,  not 
the test machine I am trying to restore the DB to,  which has a different IP 
address than the production machine.


Zoltan Forray
TSM Software  Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zfor...@vcu.edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will never 
use email to request that you reply with your password, social security number 
or confidential personal information. For more details visit 
http://infosecurity.vcu.edu/phishing.html



From:   Bos, Karel karel@atos.net
To: ADSM-L@VM.MARIST.EDU
Date:   02/21/2012 10:07 AM
Subject:Re: [ADSM-L] Server DB restore from offsite TSM server
SNAPSHOT
Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU



Hi,

From memory one should do the upd server force sync=yes on the target machine.

In this case ON server-B do upd server server-a forcesync=yes.

After restore of the DB server-server comm will be down again because 
out-of-sync issues.

Regards,

Karel

-Oorspronkelijk bericht-
Van: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Namens Zoltan 
Forray/AC/VCU
Verzonden: dinsdag 21 februari 2012 15:45
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: [ADSM-L] Server DB restore from offsite TSM server SNAPSHOT

I am trying to experiment with doing a V5 to V6 conversion by first restoring 
the V5 server to a test server.

We have very little experience doing DB restores and none involving an offsite 
TSM server.  My first attempts failed.  I think I know how to fix it but the 
docs on how to perform a DB restore are a little contradictory to what I want 
to do.

SERVER-A performs DB SNAPSHOT backups to SERVER-B via server-to-server 
definitions.

Installed a same-level TSM server onto a test machine.
Did dsmserv format to prepare DB space to the equivalent of  SERVER-A.
Replaced the test server volhist, devconfig and dsmserv.opt files from copies 
of SERVER-A like-files.

Tried to do a dsmserv restore db volumenames=name.I.got.from.volhist
devclass=SERVER-B

Since I tried this over a month ago, I don't recall the error but I think it 
has to do with the server-to-server definition being out of sync since this is 
not the original SERVER-A.

My guess is to bring up the test server and manually do a UPDATE SERVER 
SERVER-B FORCESYNCE=YES

However, when I go through the book scenarios on restoring a server DB, it
says:

Attention: Do not start the server until after you restore the database (the 
next step). Starting the server before the restore would destroy any existing 
volume history files.

So, how do I do this?  Do I bring up the test server first and correct the sync 
before replacing the volhist file?

Am I wrong in how I  am trying to do this?  Is there a better/different way to 
do this?

Looking for any suggestions/hints.


Zoltan Forray
TSM Software  Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zfor...@vcu.edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will never 
use email to request that you reply with your password, social security number 
or confidential personal information. For more details visit 
http://infosecurity.vcu.edu/phishing.html






Dit bericht is vertrouwelijk en kan geheime informatie bevatten enkel bestemd 
voor de geadresseerde. Indien dit bericht niet voor u is bestemd, verzoeken wij 
u dit onmiddellijk aan ons te melden en het bericht te vernietigen. Aangezien 
de integriteit van het bericht niet veilig gesteld is middels verzending via 
internet, kan Atos Nederland B.V. niet aansprakelijk worden gehouden voor de 
inhoud daarvan. Hoewel wij ons inspannen een virusvrij netwerk te hanteren, 
geven wij geen enkele garantie dat dit bericht virusvrij is, noch aanvaarden 
wij enige aansprakelijkheid voor de mogelijke aanwezigheid van een virus in dit 
bericht. Op al onze rechtsverhoudingen, aanbiedingen en overeenkomsten 
waaronder Atos Nederland B.V. goederen en/of diensten levert zijn met 
uitsluiting van alle andere voorwaarden de Leveringsvoorwaarden van Atos 
Nederland B.V. van toepassing. Deze worden u op aanvraag direct kosteloos

TSM 6.3 installation issues.....

2012-02-14 Thread Bos, Karel
Hi,

Just wanted to try the new version of TSM, 6.3. As I ran out of AIX systems to 
play with I started with a windows system. Quickly discovering TSM server can't 
run on X32 anymore so time to find X64.
VMware system installed, 4 GB mem etc. Windows X64 installed, TSM package etc. 
Wizzard configure minimal env. Wait Wait Wait, init failed. Click oK to see 
way, empty screen..

All in all I find TSM as of  the 6 series pretty painfull to install and 
configure. Often running into DB2 related errors with not easy to find out why 
reasons. I had hoped over time installation process and running TSM on DB2 
would improve but seeing TSM 6.3 (well not seeing it atm) I wonder if that's 
the case.

Anyone else sharing this view and also missing the easy way it was with 5. And 
below?

Regards,

Karel





Dit bericht is vertrouwelijk en kan geheime informatie bevatten enkel bestemd 
voor de geadresseerde. Indien dit bericht niet voor u is bestemd, verzoeken wij 
u dit onmiddellijk aan ons te melden en het bericht te vernietigen. Aangezien 
de integriteit van het bericht niet veilig gesteld is middels verzending via 
internet, kan Atos Nederland B.V. niet aansprakelijk worden gehouden voor de 
inhoud daarvan. Hoewel wij ons inspannen een virusvrij netwerk te hanteren, 
geven wij geen enkele garantie dat dit bericht virusvrij is, noch aanvaarden 
wij enige aansprakelijkheid voor de mogelijke aanwezigheid van een virus in dit 
bericht. Op al onze rechtsverhoudingen, aanbiedingen en overeenkomsten 
waaronder Atos Nederland B.V. goederen en/of diensten levert zijn met 
uitsluiting van alle andere voorwaarden de Leveringsvoorwaarden van Atos 
Nederland B.V. van toepassing. Deze worden u op aanvraag direct kosteloos 
toegezonden.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Atos Nederland B.V. group liability cannot be 
triggered for the message content. Although the sender endeavours to maintain a 
computer virus-free network, the sender does not warrant that this transmission 
is virus-free and will not be liable for any damages resulting from any virus 
transmitted. On all offers and agreements under which Atos Nederland B.V. 
supplies goods and/or services of whatever nature, the Terms of Delivery from 
Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly 
submitted to you on your request.

Atos Nederland B.V. / Utrecht
KvK Utrecht 30132762


Re: reclaim space in stgpool

2012-02-07 Thread Bos, Karel
Hi,

Whats the Q stg f=d output?

Whats the error u get if u do move data on this volume?

Kind regards,

Karel

-Oorspronkelijk bericht-
Van: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Namens Tim Brown
Verzonden: dinsdag 7 februari 2012 14:24
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: [ADSM-L] reclaim space in stgpool

Trying to reclaim space in disk pool defined with devc=file,l TSM level 6.3



The query command shows the volumes have reclaimable space but the reclaim gets 
the message



ANR2111W RECLAIM STGPOOL: There is no data to process for DEVT_PRIM.



tsm: TSMPOK_SERVER1q vol 0038.bfs f=d



   Volume Name: D:\DEVT_PRIM1\0038.BFS

 Storage Pool Name: DEVT_PRIM

 Device Class Name: DEVT_PRIM

Estimated Capacity: 2.0 G

   Scaled Capacity Applied:

  Pct Util: 47.3

 Volume Status: Full

Access: Read/Write

Pct. Reclaimable Space: 55.1

   Scratch Volume?: Yes

   In Error State?: No

  Number of Writable Sides: 1

   Number of Times Mounted: 24

 Write Pass Number: 1

 Approx. Date Last Written: 02/03/2012 04:02:19

Approx. Date Last Read: 02/03/2012 04:43:34

   Date Became Pending:

Number of Write Errors: 0

 Number of Read Errors: 0

   Volume Location:

Volume is MVS Lanfree Capable : No

Last Update by (administrator):

 Last Update Date/Time: 01/31/2012 13:09:15

  Begin Reclaim Period:

End Reclaim Period:

  Drive Encryption Key Manager:

   Logical Block Protected: No



Thanks,



Tim Brown
Systems Specialist - Project Leader
Central Hudson Gas  Electric
284 South Ave
Poughkeepsie, NY 12601
Email: tbr...@cenhud.com mailto:tbr...@cenhud.com
Phone: 845-486-5643
Fax: 845-486-5921
Cell: 845-235-4255




This message contains confidential information and is only for the intended 
recipient. If the reader of this message is not the intended recipient, or an 
employee or agent responsible for delivering this message to the intended 
recipient, please notify the sender immediately by replying to this note and 
deleting all copies and attachments.






Dit bericht is vertrouwelijk en kan geheime informatie bevatten enkel bestemd 
voor de geadresseerde. Indien dit bericht niet voor u is bestemd, verzoeken wij 
u dit onmiddellijk aan ons te melden en het bericht te vernietigen. Aangezien 
de integriteit van het bericht niet veilig gesteld is middels verzending via 
internet, kan Atos Nederland B.V. niet aansprakelijk worden gehouden voor de 
inhoud daarvan. Hoewel wij ons inspannen een virusvrij netwerk te hanteren, 
geven wij geen enkele garantie dat dit bericht virusvrij is, noch aanvaarden 
wij enige aansprakelijkheid voor de mogelijke aanwezigheid van een virus in dit 
bericht. Op al onze rechtsverhoudingen, aanbiedingen en overeenkomsten 
waaronder Atos Nederland B.V. goederen en/of diensten levert zijn met 
uitsluiting van alle andere voorwaarden de Leveringsvoorwaarden van Atos 
Nederland B.V. van toepassing. Deze worden u op aanvraag direct kosteloos 
toegezonden.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Atos Nederland B.V. group liability cannot be 
triggered for the message content. Although the sender endeavours to maintain a 
computer virus-free network, the sender does not warrant that this transmission 
is virus-free and will not be liable for any damages resulting from any virus 
transmitted. On all offers and agreements under which Atos Nederland B.V. 
supplies goods and/or services of whatever nature, the Terms of Delivery from 
Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly 
submitted to you on your request.

Atos Nederland B.V. / Utrecht
KvK Utrecht 30132762


Re: TSM 5.5 and AIX 7.1

2012-01-26 Thread Bos, Karel
Isn't tsm 5.5. (abt to go) end of life?

-Oorspronkelijk bericht-
Van: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Namens Ochs, Duane
Verzonden: woensdag 25 januari 2012 22:59
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: TSM 5.5 and AIX 7.1

Good day,
Has anyone attempted to run TSM server 5.5 on AIX 7.1 ?
I see the supported OS list for 5.5 indicates 6.1, which is currently 
installed, but I assume testing of 5.5 on 7.1 is outside the product scope.

Any experiences would be appreciated.
Thanks


Follow Quad/Graphics in social mediahttp://www.qg.com/socialmedia 
http://facebook.com/quadgraphics  
http://www.youtube.com/user/QuadGraphicsVideos  
http://linkedin.com/companies/8199






Dit bericht is vertrouwelijk en kan geheime informatie bevatten enkel bestemd 
voor de geadresseerde. Indien dit bericht niet voor u is bestemd, verzoeken wij 
u dit onmiddellijk aan ons te melden en het bericht te vernietigen. Aangezien 
de integriteit van het bericht niet veilig gesteld is middels verzending via 
internet, kan Atos Nederland B.V. niet aansprakelijk worden gehouden voor de 
inhoud daarvan. Hoewel wij ons inspannen een virusvrij netwerk te hanteren, 
geven wij geen enkele garantie dat dit bericht virusvrij is, noch aanvaarden 
wij enige aansprakelijkheid voor de mogelijke aanwezigheid van een virus in dit 
bericht. Op al onze rechtsverhoudingen, aanbiedingen en overeenkomsten 
waaronder Atos Nederland B.V. goederen en/of diensten levert zijn met 
uitsluiting van alle andere voorwaarden de Leveringsvoorwaarden van Atos 
Nederland B.V. van toepassing. Deze worden u op aanvraag direct kosteloos 
toegezonden.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Atos Nederland B.V. group liability cannot be 
triggered for the message content. Although the sender endeavours to maintain a 
computer virus-free network, the sender does not warrant that this transmission 
is virus-free and will not be liable for any damages resulting from any virus 
transmitted. On all offers and agreements under which Atos Nederland B.V. 
supplies goods and/or services of whatever nature, the Terms of Delivery from 
Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly 
submitted to you on your request.

Atos Nederland B.V. / Utrecht
KvK Utrecht 30132762


Re: Deleting STG POOL

2012-01-24 Thread Bos, Karel
I used to do an audit vol volname fix=yes to clear the pointers to no 
longer avail data. Think it was a now issues.


-Oorspronkelijk bericht-
Van: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Namens Vandeventer, 
Harold [BS]
Verzonden: maandag 23 januari 2012 19:03
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: Re: Deleting STG POOL

Thanks to everyone for the continued suggestions.

The DEL VOL volname DISCARD=NO was successful, deleted the volumes without 
any issues.

I had tried various reclaim/migrate tasks, Q CONTENT, etc; everything implied 
they were empty.

It boils down to why didn't the volumes get deleted when the initial reclaim 
processes ran.

Thanks again for all the suggestions.



Harold Vandeventer
Systems Programmer
State of Kansas - Department of Administration - Office of Information 
Technology Services harold.vandeven...@da.ks.gov
(785) 296-0631


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Allen 
S. Rout
Sent: Monday, January 23, 2012 11:25 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Deleting STG POOL

On 01/20/2012 03:50 PM, Vandeventer, Harold [BS] wrote:
 I'm confident they're empty; just trying to prove it before I delete.

 CONTENT isn't providing anything, and I can display content of volumes in 
 other pools.


Are they PENDING?

- Allen S. Rout






Dit bericht is vertrouwelijk en kan geheime informatie bevatten enkel bestemd 
voor de geadresseerde. Indien dit bericht niet voor u is bestemd, verzoeken wij 
u dit onmiddellijk aan ons te melden en het bericht te vernietigen. Aangezien 
de integriteit van het bericht niet veilig gesteld is middels verzending via 
internet, kan Atos Nederland B.V. niet aansprakelijk worden gehouden voor de 
inhoud daarvan. Hoewel wij ons inspannen een virusvrij netwerk te hanteren, 
geven wij geen enkele garantie dat dit bericht virusvrij is, noch aanvaarden 
wij enige aansprakelijkheid voor de mogelijke aanwezigheid van een virus in dit 
bericht. Op al onze rechtsverhoudingen, aanbiedingen en overeenkomsten 
waaronder Atos Nederland B.V. goederen en/of diensten levert zijn met 
uitsluiting van alle andere voorwaarden de Leveringsvoorwaarden van Atos 
Nederland B.V. van toepassing. Deze worden u op aanvraag direct kosteloos 
toegezonden.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Atos Nederland B.V. group liability cannot be 
triggered for the message content. Although the sender endeavours to maintain a 
computer virus-free network, the sender does not warrant that this transmission 
is virus-free and will not be liable for any damages resulting from any virus 
transmitted. On all offers and agreements under which Atos Nederland B.V. 
supplies goods and/or services of whatever nature, the Terms of Delivery from 
Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly 
submitted to you on your request.

Atos Nederland B.V. / Utrecht
KvK Utrecht 30132762


Re: Mix tape and disk on the same HBA port

2012-01-24 Thread Bos, Karel
Rule still holds but for very small env just do both over same ports. Pretty 
small change of hitting troubles with low utilization of the fabric.

Virtual adapters don't change physical usage.

Regards,

Karel

-Oorspronkelijk bericht-
Van: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Namens Hans 
Christian Riksheim
Verzonden: dinsdag 24 januari 2012 12:00
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: Mix tape and disk on the same HBA port

I usually separate disk and tape but now I have a customer with a very small 
system and another two port HBA for a small Power-server does not come cheap.

So I am wondering if this rule still holds true or is it something for 
Mythbusters to take care of? What are the consequences of mixing them?

If true what about NPIV? Will tape and disk on different virtual adapters 
attached to the same HBA port still break the rule?

Hans Chr.






Dit bericht is vertrouwelijk en kan geheime informatie bevatten enkel bestemd 
voor de geadresseerde. Indien dit bericht niet voor u is bestemd, verzoeken wij 
u dit onmiddellijk aan ons te melden en het bericht te vernietigen. Aangezien 
de integriteit van het bericht niet veilig gesteld is middels verzending via 
internet, kan Atos Nederland B.V. niet aansprakelijk worden gehouden voor de 
inhoud daarvan. Hoewel wij ons inspannen een virusvrij netwerk te hanteren, 
geven wij geen enkele garantie dat dit bericht virusvrij is, noch aanvaarden 
wij enige aansprakelijkheid voor de mogelijke aanwezigheid van een virus in dit 
bericht. Op al onze rechtsverhoudingen, aanbiedingen en overeenkomsten 
waaronder Atos Nederland B.V. goederen en/of diensten levert zijn met 
uitsluiting van alle andere voorwaarden de Leveringsvoorwaarden van Atos 
Nederland B.V. van toepassing. Deze worden u op aanvraag direct kosteloos 
toegezonden.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Atos Nederland B.V. group liability cannot be 
triggered for the message content. Although the sender endeavours to maintain a 
computer virus-free network, the sender does not warrant that this transmission 
is virus-free and will not be liable for any damages resulting from any virus 
transmitted. On all offers and agreements under which Atos Nederland B.V. 
supplies goods and/or services of whatever nature, the Terms of Delivery from 
Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly 
submitted to you on your request.

Atos Nederland B.V. / Utrecht
KvK Utrecht 30132762


Re: How to run a manual Exchange backup ?

2012-01-04 Thread Bos, Karel
What abt just firing off the GUI and select the group u want?


-Oorspronkelijk bericht-
Van: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Namens Minns, Farren 
- Chichester
Verzonden: woensdag 4 januari 2012 12:40
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: How to run a manual Exchange backup ?

Hi all,



I need to run a full exchange backup against just one Exchange storage group.



The current command that backs up all groups is as follows :-



tdpexcc backup * incr /tsmoptfile=dsm.opt /logfile=excsch.log /excserver=chi-mb 
 excincr.log



To back up just one group (in this case called 4B StorageGroup), can I just run 
the following ?



tdpexcc backup '4B StorageGroup incr' /tsmoptfile=dsm.opt 
/logfile=excsch_4B.log /excserver=chi-mb  excincr_4B.log



Regards



Farren


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.







Dit bericht is vertrouwelijk en kan geheime informatie bevatten enkel bestemd 
voor de geadresseerde. Indien dit bericht niet voor u is bestemd, verzoeken wij 
u dit onmiddellijk aan ons te melden en het bericht te vernietigen. Aangezien 
de integriteit van het bericht niet veilig gesteld is middels verzending via 
internet, kan Atos Nederland B.V. niet aansprakelijk worden gehouden voor de 
inhoud daarvan. Hoewel wij ons inspannen een virusvrij netwerk te hanteren, 
geven wij geen enkele garantie dat dit bericht virusvrij is, noch aanvaarden 
wij enige aansprakelijkheid voor de mogelijke aanwezigheid van een virus in dit 
bericht. Op al onze rechtsverhoudingen, aanbiedingen en overeenkomsten 
waaronder Atos Nederland B.V. goederen en/of diensten levert zijn met 
uitsluiting van alle andere voorwaarden de Leveringsvoorwaarden van Atos 
Nederland B.V. van toepassing. Deze worden u op aanvraag direct kosteloos 
toegezonden.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Atos Nederland B.V. group liability cannot be 
triggered for the message content. Although the sender endeavours to maintain a 
computer virus-free network, the sender does not warrant that this transmission 
is virus-free and will not be liable for any damages resulting from any virus 
transmitted. On all offers and agreements under which Atos Nederland B.V. 
supplies goods and/or services of whatever nature, the Terms of Delivery from 
Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly 
submitted to you on your request.

Atos Nederland B.V. / Utrecht
KvK Utrecht 30132762


Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code

2011-05-12 Thread Bos, Karel
Hi,

Dunno if u already looked at these options: THROUGHPUTDATATHRESHOLD and 
THROUGHPUTTIMETHRESHOLD. After a couple of crashes due to log filling up, a 
couple of years back, I standard added them to all my clients (with low values 
to only kill the slowest/hung ones) and untill now never had any issues with 
the V5.5 and below log space under normal backup loads. 

Log filling only happend when some sys admin made some changes to the biggest 
file servers we had but even this was handled like it should be done by ITSM.

Regards,

Karel




Van: ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] namens Loon, EJ van - SPLXO 
[eric-van.l...@klm.com]
Verzonden: donderdag 12 mei 2011 11:11
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code

Hi Paul!
We are already running 5.5.5.2 and the log is still filling up, even
after switching from rollforward to normal mode.
Management currently is questioning whether TSM is the right product for
the future. Although I'm a big fan of TSM for 15 years, I'm really in
doubt too...
Kind regards,
Eric van Loon
KLM Royal Dutch Airlines

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Paul Fielding
Sent: woensdag 11 mei 2011 20:05
To: ADSM-L@VM.MARIST.EDU
Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code

Hi folks, if this has already been commented on, my apologies, I hvaen't
been following closely but just noticed this thread.

We were experiencing log pinned issues after upgrading to 5.5.0.0 code
at
one of my client sites.  What we were finding was that, occasionally,
I'd
get up in the morning and look at the server to see it completely bogged
down with a huge number of backups still attempting to run, but nothing
was
moving - the log was at 84% (over it's trigger), and it had been firing
off
db backups for the last 4h to no avail, the log wasn't getting low
enough.

A key symptom was that in the actlog we were seeing messages to the
effect
of Recovery log is at 84%, transactions will be delayed by 3ms (or
something like that).

In opening a ticket, it was found there was an issue in the 5.5.0.0 code
where, when the recovery log gets too full, it would start delaying
transactions in order to prevent the log from filling too quickly.
However,
the side effect was that the pinning transaction would also get delayed,
causing a bit of a never-ending loop.  Transactions keep getting
delayed,
pinned transaction never gets to finish, and everything would just grind
to
a halt.  I would have to halt the server and restart in order to get
things
back to normal.

IBM recognized this as an issue and recommended going to any 5.5.5.0
level
of code, where the problem was supposed to be fixed.  I installed
5.5.5.2,
and the problem has indeed gone away.   It was supposed to be fixed at
5.5.5.0, though perhaps they didn't quite get it done at that code level
as
they hoped?  I'd try installing 5.5.5.2 and see what happens

regards,

Paul


On Wed, May 11, 2011 at 9:03 AM, Loon, EJ van - SPLXO
eric-van.l...@klm.com
 wrote:

 Hi Robert!
 Thanks you very much for your reply! Several others on this list
 reported this behavior and (as far as I know) three other users opened
a
 PMR too. I hope they have more luck, because I'm stuck. Level 2 keeps
on
 saying that the log keeps on growing because of slow running client
 sessions. Indeed I see slow running client sessions, but they are
slowed
 down by the fact that TSM is delaying all transactions because the log
 is used for more that 80% during a large part of the backup window!
Now
 they refuse to help me, unless I buy a Passport Advantage
contract!!
 Kind regards,
 Eric van Loon
 KLM Royal Dutch Airlines

 -Original Message-
 From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf
Of
 Robert Clark
 Sent: woensdag 11 mei 2011 16:05
 To: ADSM-L@VM.MARIST.EDU
 Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code

 I believe we've been seeing this problem as well.

 One night in the busiest backup period, I issued a q actlog
 begint=now-00:30, and got no results back but an error.

 I started dsmadmc -console on that server, and could see that the
 console
 output was most of an hour behind. (And the console output was
scrolling
 so fast that it could barely be read.)

 In that case, I think we determined that SQL LiteSpeed was set to some
 rediculously small transaction size, and this was causing way too many
 actlog entries.

 I think I also noted that the session number incremented by something
 like
 100,000 in an hour.

 Asking the users of SQL LiteSpeed to make some changes was enough to
 rememdy this problem, although we continue to fight with the logs
 getting
 full.

 Thanks,
 [RC]



 From:   Loon, EJ van - SPLXO eric-van.l...@klm.com
 To: ADSM-L@VM.MARIST.EDU
 Date:   05/11/2011 02:05 AM
 Subject:Re: [ADSM-L] TSM Recovery 

Unable to restore Server2 instance

2011-03-14 Thread Bos, Karel
Hi,

We are testing some ITSM 6.2 server installs. We have 2 instances
running on 1 Win2k3 server. Made a database backup of server2 and trying
to restore it on the same. 

E:\TSMSRV\server2E:\TSMSRV\SERVER\DSMSERV -k Server2 restore db
todate=03/14/2011 totime=12:54:55 source=dbb

ANR4912I Database  full restore in progress and DB transaction log bytes
transferred  9,461,771.
ANR1364I Input volume CONFIGM.DBV.300104513 closed.
ANR0514I Session 500 closed volume CONFIGM.DBV.300104513.
ANR0403I Session 512 ended for node CONFIGM (Windows).
ANR0403I Session 500 ended for node $$_TSMDBMGR_$$ (DB2/NT).
ANR0406I Session 513 started for node $$_TSMDBMGR_$$ (DB2/NT) (Tcp/Ip
nuwnlap385.nuon.local(2023)).
ANR0403I Session 513 ended for node $$_TSMDBMGR_$$ (DB2/NT).
ANR2970E Database rollforward terminated - DB2 sqlcode 1271 sqlerrmc
TSMDB1 0

DB2CLP=DB20FADE
DB2INSTANCE=Server2
DB2PATH=E:\TSMSRV\db2

Anyone out there that can shed some light on this. Documentation points
to incorrect set parm, but changing it into TSMDB1 doesn't solve a
thing.

Please reply 2 personal email also.

(boy I really like the DB2 stuff one now needs to know to be able to run
this backup application )
set
Best regards, Met vriendelijke groet,
Karel Bos
MS Global Practice IT Infrastructure Services
Commvault/IBM Tivoli  Storage Manager specialist Operations Central
Atos Origin Nederland B.V. 
Naritaweg 52, 1R.10 
1043 BZ Amsterdam
The Netherlands 
karel@atosorigin.com 
+31(0)88 2659543
www.nl.atosorigin.com 


ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.


Re: Windows servers with a kazillion files and Win2K8...

2011-02-28 Thread Bos, Karel
Image backups an option? 

Might get the fs back-up under control, but what about a FS restore
using file based back-ups? Doing a multi million object restore will
take ages.


Best regards, Met vriendelijke groet,
Karel Bos
MS Global Practice IT Infrastructure Services
Commvault/IBM Tivoli  Storage Manager specialist Operations Central
Atos Origin Nederland B.V. 
Naritaweg 52, 1R.10 
1043 BZ Amsterdam
The Netherlands 
karel@atosorigin.com 
+31(0)88 2659543
www.nl.atosorigin.com 


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Strand, Neil B.
Sent: maandag 28 februari 2011 16:51
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Windows servers with a kazillion files and Win2K8...

Wanda,
   If it is a 32 bit system, the most memory that can be addressed is
4G.
2^32 = 4,294,967,296 bytes
4,294,967,296 / (1,024 x 1,024) = 4,096 MB = 4GB

Moving to a 64bit system would allow additional memory to be fed to the
beast.

If the windows servers are not running the application but simply
providing filespace to the application that is running on another
server, see if the following is possible:
- Implement DFS and provide a virtual tree that is composed of multiple
physical data repositories. Each repository could be backed up using a
proxy - recovery may be a bit convoluted, but possible.  Identify the
problem not as a backup problem but a data management problem that
requires some level of granularity to be introduced to the environment.

Cheers,
Neil Strand
Storage Engineer - Legg Mason
Baltimore, MD.
(410) 580-7491
Whatever you can do or believe you can, begin it.
Boldness has genius, power and magic.


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Friday, February 25, 2011 2:35 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Windows servers with a kazillion files and
Win2K8...

Thanks for the reply and the reference; I'll read that.
It's a 32 bit system.
Do you think adding RAM will help with the issues navigating the file
tree?

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Storer, Raymond
Sent: Friday, February 25, 2011 2:22 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Windows servers with a kazillion files and
Win2K8...

Wanda, is this a 32 or 64 bit system? An NTFS file system will support
about 4 Billion files on a single volume
http://technet.microsoft.com/en-us/library/cc781134(WS.10).aspx . If you
are having performance issues with this and you can switch it to a 64bit
platform and add loads of RAM, I would do it.

Ray

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
Prather, Wanda
Sent: Friday, February 25, 2011 2:03 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Windows servers with a kazillion files and Win2K8...

I have a site with an application that generates kazillions of tiny
files that are stored forever.
I've already yelled about it, but it's a purchased, customer-facing
black-box app that they really can't change.
(Naturally, when it was bought umpty years ago, nobody thought about the
problem reaching this size or what the ramifications would be.)  Every
day the app creates more files.

They have multiple Win2K3 servers that already have multiple luns
containing over 35M files each, one is over 75M files.

We are using journaling to back them up successfully (most days).
But it's a struggle just to expand the file tree with Windows explorer,
and there are exposures on the days when the journal gets overrun (takes
72 hours for TSM to scan the filesystem and revalidate the journal).

Looking for anything that might help save our bacon.

Has anybody had experience with this issue and Win2K8?
Does Win2K8 do any better than Win2K3 at handling huge numbers of files
in 1 NTFS directory?
Upgrading the OS is something application-independent we might be able
to do.

Thanks for any insight!
W


Wanda Prather  |  Senior Technical Specialist  |
wprat...@icfi.commailto:wprat...@icfi.com  |
www.jasi.comwww.jasi.com%20 ICF Jacob  Sundstrom  | 401 E. Pratt St,
Suite 2214, Baltimore, MD 21202 | 410.539.1135


CONFIDENTIALITY NOTICE:  This email and any attachments are for the
exclusive and confidential use of the intended recipient.  If you are
not the intended recipient, please do not read, distribute or take
action in reliance upon this message. If you have received this in
error, please notify us immediately by return email and promptly delete
this message and its attachments from your computer system. We do not
waive attorney-client or work product privilege by the transmission of
this message.

IMPORTANT:  E-mail sent through the Internet is not secure. Legg Mason
therefore recommends that you do not send any confidential or sensitive
information to us via electronic mail, including social security
numbers, account numbers, or personal identification numbers. Delivery,
and 

Re: Upgrading from TSM 5.5 to 6.2

2010-09-09 Thread Bos, Karel
http://publib.boulder.ibm.com/infocenter/tsminfo/v6r2/index.jsp

Topic upgrade V5 to V6.2 :)

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
David E Ehresman
Sent: donderdag 9 september 2010 13:52
To: ADSM-L@VM.MARIST.EDU
Subject: Upgrading from TSM 5.5 to 6.2

What Redbooks or other documentation do you recommend in preparing for a
5.5 to 6.2 upgrade?

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

VTA ACSLS configuration on AIX, howto?

2010-09-09 Thread Bos, Karel
Hi,

Config:

ITSM V6.2 server running on AIX v6
Centricstor V4
Firewall inbetween


We are trying to connect the ITSM server to the Centricstor emulating a
ACSLS libary. 
Configured firewall and rc.acs_ssi (based on
http://www-01.ibm.com/support/docview.wss?rs=663context=SSGSG7uid=swg2
1231145loc=en_UScs=UTF-8lang=en ). Telnet on the used port is working
from both sides, but

* Rpcinfo test described in the link hangs;
* event.log shows
[csi_rpccall.c:473] ONC RPC: csi_rpccall():
status:STATUS_NI_FAILURE; failed: clnttcp_create()
RPC TCP client connection failed, RPC: 1832-018 Port mapper failure
Errno = 1752134516(NULL)
Remote Internet address:XXX.YYY.112.197, Port: 0;
*Define library
09/09/10   13:28:50  ANR2017I Administrator  issued command:
DEFINE
  LIBRARY acslib libtype=acsls acsid=4
(SESSION: 9)
09/09/10   13:33:51  ANR8856E ACSAPI sequence(5) request (0) timed
out, elapse
  time=00: 05:01. (SESSION: 9)
09/09/10   13:33:51  ANR8855E ACSAPI(acs_query_server) response with
  unsuccessful status,
status=STATUS_IPC_FAILURE. (SESSION:
  9)


Any ideas?

Regards,

Karel
Ps. Anybody has a HOWTO doc on configure ACSLS for ITSM to work in a
setting like this?  
ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: Copy Pool question

2010-07-14 Thread Bos, Karel
* Backup old prim stg to new copy stg = short time extra tape storage
needed
* delete old copy stg volumes = free up old copy volumes
* migrate old prim stg to new prim stg = take all the time you need

Regards,
K



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Grigori Solonovitch
Sent: woensdag 14 juli 2010 16:16
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Copy Pool question

Ther is no other solution. You can only speed up process:
1) expiry will remove the oldest data from old primary and copy pools;
2) you can migrate the newest data slowly from old primary pool th new
primary pool;
3) after completion of moving/expirying of old primary pool just remove
all remaing volume in old copy pool (copy will be in the new copy pols
as well)m 
From: ADSM: Dist Stor Manager [ads...@vm.marist.edu] On Behalf Of Ronald
Le Large [rlela...@epo.org]
Sent: Wednesday, July 14, 2010 4:26 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Copy Pool question

I have a related issue...
I have a new primary stg pool and a new copy pool.
I have also an 'old' primary pool and an 'old' copy pool.

There is no new data arriving in the 'old' primary pool because backup
data is send to the 'new' primary pool. This data is of course copied to
the new copy pool. So far so good.

ButI am gradually migrating the data in the old primary stg pool to
the new primary stg pool.
And as a result the data which has already a copy in the old copy pool.
is copied again during the backup stg process from the new primary
pool to new copy pool.

This is not only time and resource consuming but this also consumes a
lot of scratch tapes.

How can I avoid this?
As far as  I know, I can not migrate data from a copy pool. to another
(copy)storage pool. So expiration seems to be the only solution but then
I am 'wasting' tapes for a long time.

Any suggestions ?

Ronald




 Grigori
 Solonovitch
 Grigori.Solonovi
To
 t...@ahliunited.co ADSM-L@VM.MARIST.EDU
 M
cc
 Sent by: ADSM:
 Dist Stor
Subject
 Manager  Re: [ADSM-L] Copy Pool question
 ads...@vm.marist
 .EDU


 10-07-2010 00:37


 Please respond to
 ADSM: Dist Stor
 Manager
 ads...@vm.marist
   .EDU






Hello Andy,
If you want to use new copy pools without changing existing copy pools
(allow them to expiry slowly) you need:
1) keep existing primary and copy pools as they are;
2) create new primary pools (on the same disk or VTL);
3) change destination in all management classes to new primary pools;
4) create new copy pools (on new VTL);
5) backup new primary pools to new copy pools;
6) after some time old primary and copy pols will expiry.
I think only this way of changing copy pools is available. It is working
fine and I am able to restore data from new and old pools.
I have migrated all my data recently and I am waiting for comlete
expiration of data in old pools now.
In addition, you can migrate data from old primary pools to new primary
pools by move data slowly, if you couldn't wait for complete expiry
time.
Regards,
Grigori


From: ADSM: Dist Stor Manager [ads...@vm.marist.edu] On Behalf Of
Huebner,Andy,FORT WORTH,IT [andy.hueb...@alconlabs.com]
Sent: Friday, July 09, 2010 7:16 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Copy Pool question

We will be swapping out our old VTLs for new VTLs.  Our copy pools will
remain unchanged.

Are these statements accurate?
On the day of the switch we start running the BackupSTG process against
the new VTLs with all of the existing data residing on the old VTLs, the
new data will be copied to the copy pools, the existing data will
remain.
As we migrate the data from old to new, the BackupSTG process will not
duplicate the data.  Meaning I will not have 2 copies of the same object
in the copy pool.
As we migrate the date from old to new, the BackupSTG process will not
recopy the data to the copy pool.




Andy Huebner

This e-mail (including any attachments) is confidential and may be
legally privileged. If you are not an intended recipient or an
authorized representative of an intended recipient, you are prohibited
from using, copying or distributing the information in this e-mail or
its attachments.
If you have received this e-mail in error, please notify the sender
immediately by return e-mail and delete all copies of this message and
any attachments.

Thank you.

Please consider the environment before printing this Email.

CONFIDENTIALITY AND WAIVER: The information contained in this electronic
mail message and any attachments hereto may be legally privileged and
confidential. The information is intended only for the recipient(s)
named in this message. If you are not the intended recipient you are

Re: update stg collocate=node

2010-05-17 Thread Bos, Karel
Hi,

Reclamation and/or move data. Issue move data on filling tapes, let
reclamation do the full's (or move them aswell).

Regards,

Karel



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Mehdi Salehi
Sent: maandag 17 mei 2010 11:32
To: ADSM-L@VM.MARIST.EDU
Subject: Re: update stg collocate=node

So, possible to force them become collocated?

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: Trouble backing up large directory tree

2010-04-27 Thread Bos, Karel
If you have problems running dir/s you might have system issues already.

Would take a look at the memeff diskcache option, but this will take up
some free disk space.

http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp?topic=/
com.ibm.itsmfdt.doc/ans5331.htm

Regards,
K.



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Lee, Gary D.
Sent: dinsdag 27 april 2010 17:05
To: ADSM-L@VM.MARIST.EDU
Subject: Trouble backing up large directory tree

Tsm client 6.2, server v5.5.4.
Client os win 2003 server SUSe sles9 under vm 5.3.

I have a directory tree, don't know how large, tried a dir/s to get a
file count, stopped it after 35 minutes.

Getting ans1030e  during backup.

Have already tried memoryefficientbackup yes in dsm.opt.

And, restructuring is out of the question.  This is a blackboard server
and application created and managed.

Where do I go from here?

Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310

 
ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: Viewing storage used in pool during backup

2010-03-04 Thread Bos, Karel
Hi,

Storage usage is updated after a transaction is completed.

Regards,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Lee, Gary D.
Sent: donderdag 4 maart 2010 17:11
To: ADSM-L@VM.MARIST.EDU
Subject: Viewing storage used in pool during backup

Tsm cerver 5.5.4 on zlinux suse sles 9.
Tdp for sqlserver v5.5.3.

I can se a session going with a q ses, with a value of bytes transferred
for instance 131 gB right now.
However a q stg on the disk pool into which the data is supposed to be
going shows 0% used.

This makes no sense.

Any help appreciated.

Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310

 
ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: New to TSM V6.1

2010-02-25 Thread Bos, Karel
Hi,

Useful information can be found @
http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp

Regards/Met vriendelijke groet,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Sabar Martin Hasiholan Panggabean
Sent: donderdag 25 februari 2010 10:09
To: ADSM-L@VM.MARIST.EDU
Subject: New to TSM V6.1

Hi,



Just recently I've installed TSM V6.1. I just wonder, is there any
document that tells me about differences or what change from TSM version
5.x.x to this new version.

Anyway, I have couple of questions on this new version (actually I've a
lot) :



1.   Where is the dsmadmc utility command ? I can't find it ! Does
IBM remove it ? Or change the name ?

2.   How to extend the tsm DB and LOG if we need bigger size catalog
? or the new TSM DB doesn't work like it was ?





Best Regards,



Martin P

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: ANR9999D error mounting tape

2010-02-25 Thread Bos, Karel
Hi,

ANR8468I LTO volume PV0001L3 dismounted from drive LTO1 

Loading an LTO3 tape in a LTO1 drive won't work. Otherway around is in 
read-only activities supported.


Kind Regards/Met vriendelijke groet,

Karel


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario 
Behring
Sent: donderdag 25 februari 2010 12:11
To: ADSM-L@VM.MARIST.EDU
Subject: ANRD error mounting tape

Hi list,


I am getting the following error on a TSM Server 5.5.3.0 running on a Windows 
box when trying to use the Library.the error message below happened during 
a BACKUP DB executionwhile attempting to mount the tape specified in the 
VOL parameter:

02/24/2010 16:07:38  ANR8468I LTO volume PV0001L3 dismounted from drive LTO1
  (mt4.0.0.4) in library LTOLIB1. (SESSION: 93, PROCESS:
  50)
02/24/2010 16:07:38  ANRD_0521343731 (pvrntp.c:1271) Thread34: Could 
not
  determine media type, rc = 1 (SESSION: 93, PROCESS: 
50)
02/24/2010 16:07:38  ANRD Thread34 issued message  from: (SESSION:
  93, PROCESS: 50)
02/24/2010 16:07:38  ANRD Thread34  10660EC2 Unknown  (SESSION: 93,
  PROCESS: 50)
02/24/2010 16:07:38  ANRD Thread34  054EE9C0 Unknown  (SESSION: 93,
  PROCESS: 50)
02/24/2010 16:07:38  ANRD Thread34  FF9DD746 Unknown  (SESSION: 93,
  PROCESS: 50)
02/24/2010 16:07:38  ANRD Thread34  840FC085 Unknown  (SESSION: 93,
  PROCESS: 50)


There is more of this message, since I´ve issued the SET CONTEXTMESSAGING to 
ON.the library is a LTO ULTRIUM3C...

Any help is appreciated.

Mario




ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever 

Re: Alerts in event viewer

2009-12-17 Thread Bos, Karel
Hi,

Using the TDP its ment for doing online (thus changing) back-ups. It
will let you back-up the database and log files, without giving errors
if succesfull. In case of errors it will be logged into the log files
and windows event viewer. Based on the error message corrective actions
can be taken.

As noted, the files back-upped in the TDP back-up should be excluded
from normal file system back-ups. 


Kind regards,

Karel


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
ashish sharma
Sent: donderdag 17 december 2009 11:30
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Alerts in event viewer

Hello Grigori,

I know TDP can backup exchange but just want to confirm that does it
gives any type of alerts in event viewer while backing up changing
files?

On Thu, Dec 17, 2009 at 3:34 PM, Grigori Solonovitch
g.solonovi...@bkme.com
 wrote:

 You have two options:

 1) stop Exchange Server and use TSM Client to make offline backup;

 2) install TDP for SQL and make online backups for Exchange database 
 (database files and logs have to be excluded from normal TSM Client
backup).

 Good luck!



 Grigori G. Solonovitch



 Senior Technical Architect



 Information Technology  Bank of Kuwait and Middle East 
 http://www.bkme.com



 Phone: (+965) 2231-2274  Mobile: (+965) 99798073  E-Mail:
 g.solonovi...@bkme.com



 Please consider the environment before printing this Email





 -Original Message-
 From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf 
 Of ashish sharma
 Sent: Thursday, December 17, 2009 12:08 PM
 To: ADSM-L@VM.MARIST.EDU
 Subject: [ADSM-L] Alerts in event viewer



 Hello,



 I want to backup my exchange server using TDP. The quesion i am having

 is

 that , will i get alerts related to log files in the event viewer or 
 there

 will be no alert? When i use simple BA client , my event viewer is 
 full of

 alerts due to failed backup of log files



 --

 Best Regards

 Ashish Sharma

 ST Microelectronics Ltd.

 919717003853



 Please consider the environment before printing this Email.

 
 This email message and any attachments transmitted with it may 
 contain confidential and proprietary information, intended only for 
 the named recipient(s). If you have received this message in error, or

 if you are not the named recipient(s), please delete this email after 
 notifying the sender immediately. BKME cannot guarantee the integrity 
 of this communication and accepts no liability for any damage caused 
 by this email or its attachments due to viruses, any other defects, 
 interception or unauthorized modification. The information, views, 
 opinions and comments of this message are those of the individual and
not necessarily endorsed by BKME.




--
Best Regards
Ashish Sharma
ST Microelectronics Ltd.
919717003853

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If 

Re: TSM 5.3.4 Policy problem

2009-12-17 Thread Bos, Karel
Erm, can't update the active policy set :)

 Update copygroup DOM_SRV SET_SRV MC_90DAYS type=backup
verexists=nolimit verdeleted=nolimit retextra=60 retonly=60

Validate and activate the set afterwards.

Kind regards,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
David E Ehresman
Sent: donderdag 17 december 2009 17:24
To: ADSM-L@VM.MARIST.EDU
Subject: Re: TSM 5.3.4 Policy problem

If you REALLY want to keep data in TSM for 60 days, you need

Update copygroup DOM_SRV ACTIVE MC_90DAYS type=backup verexists=nolimit
verdeleted=nolimit retextra=60 retonly=60

Otherwise, multiple backups run during a day can result in files
expiring in less than 60 days.

David

 William ZHANG william.zh...@st.com 12/16/2009 11:27 PM 
Hello,

Thanks Grigori,Karel,
I want to retain deleted data 60days in TSM.
So should I input:

Update copygroup DOM_SRV ACTIVE MC_90DAYS type=backup verexists=60
verdeleted=60 retextra=60 retonly=60

But got error, said, active policy cannot be modified, So could anyone
can tell me how can I modified my policy set and copygroup so that I can
get what I want?


Many thanks!

William


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Bos, Karel
Sent: Wednesday, December 16, 2009 6:27 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM 5.3.4 Policy problem

I would take a look at the RETExtra/Only parm of the copy group, they
manage the data by date instead of versions. Managing retention time
using the versions parameters can give some unintended results (an extra
backup of a changed file will reduce the period you can restore from for
instance).

Kind regards,

Karel


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Grigori Solonovitch
Sent: woensdag 16 december 2009 10:31
To: ADSM-L@VM.MARIST.EDU
Subject: Re: TSM 5.3.4 Policy problem

Yes, but it is better to use 60 instead of 59.

Grigori G. Solonovitch

Senior Technical Architect

Information Technology  Bank of Kuwait and Middle East
http://www.bkme.com 

Phone: (+965) 2231-2274  Mobile: (+965) 99798073  E-Mail:
g.solonovi...@bkme.com 

Please consider the environment before printing this Email


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
William ZHANG
Sent: Wednesday, December 16, 2009 12:28 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TSM 5.3.4 Policy problem

Hello All,



I meet a problem,

If I want to retain deleted data 60days in TSM, what commands should I
input to modified policy in TSM?



should the versions data exists  and versions data deleted be
modified from 2 to 59 , right?



These are my configuration:

---

tsm: SHITSM01q copygroup



PolicyPolicyMgmt  Copy  Versions
Versions   Retain  Retain

DomainSet Name  Class Group Data
DataExtraOnly

NameName  NameExists
Deleted Versions Version

- - - - 
  ---

DOM_SRV   ACTIVEMC_90DAYS STANDARD 2
1   90  90

DOM_SRV   SET_SRV   MC_90DAYS STANDARD90
90   90  90

STANDARD  ACTIVESTANDARD  STANDARD 2
1   30  60

STANDARD  STANDARD  STANDARD  STANDARD 2
1   30  60

---

tsm: SHITSM01q domain f=d



  Policy Domain Name: DOM_SRV

Activated Policy Set: SET_SRV

Activation Date/Time: 05/10/2007 11:09:44

   Days Since Activation: 951

Activated Default Mgmt Class: MC_90DAYS

  Number of Registered Nodes: 3

 Description:

 Backup Retention (Grace Period): 60

Archive Retention (Grace Period): 1,095

  Last Update by (administrator): ADMIN

   Last Update Date/Time: 07/30/2009 11:30:05

Managing profile:

 Changes Pending: Yes



  Policy Domain Name: STANDARD

Activated Policy Set: STANDARD

Activation Date/Time: 05/09/2007 12:41:05

   Days Since Activation: 952

Activated Default Mgmt Class: STANDARD

  Number of Registered Nodes: 1

 Description: Installed default policy domain.

 Backup Retention (Grace Period): 30

Archive Retention (Grace Period): 365

  Last Update by (administrator): SERVER_CONSOLE

   Last Update Date/Time: 05/09/2007 12:41:05

Managing profile:

 Changes Pending: No



---

tsm: SHITSM01q mgmtclass



PolicyPolicyMgmt  Default

Re: TSM 5.3.4 Policy problem

2009-12-16 Thread Bos, Karel
I would take a look at the RETExtra/Only parm of the copy group, they
manage the data by date instead of versions. Managing retention time
using the versions parameters can give some unintended results (an extra
backup of a changed file will reduce the period you can restore from for
instance).  

Kind regards,

Karel


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Grigori Solonovitch
Sent: woensdag 16 december 2009 10:31
To: ADSM-L@VM.MARIST.EDU
Subject: Re: TSM 5.3.4 Policy problem

Yes, but it is better to use 60 instead of 59.

Grigori G. Solonovitch

Senior Technical Architect

Information Technology  Bank of Kuwait and Middle East
http://www.bkme.com

Phone: (+965) 2231-2274  Mobile: (+965) 99798073  E-Mail:
g.solonovi...@bkme.com

Please consider the environment before printing this Email


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
William ZHANG
Sent: Wednesday, December 16, 2009 12:28 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TSM 5.3.4 Policy problem

Hello All,



I meet a problem,

If I want to retain deleted data 60days in TSM, what commands should I
input to modified policy in TSM?



should the versions data exists  and versions data deleted be
modified from 2 to 59 , right?



These are my configuration:

---

tsm: SHITSM01q copygroup



PolicyPolicyMgmt  Copy  Versions
Versions   Retain  Retain

DomainSet Name  Class Group Data
DataExtraOnly

NameName  NameExists
Deleted Versions Version

- - - - 
  ---

DOM_SRV   ACTIVEMC_90DAYS STANDARD 2
1   90  90

DOM_SRV   SET_SRV   MC_90DAYS STANDARD90
90   90  90

STANDARD  ACTIVESTANDARD  STANDARD 2
1   30  60

STANDARD  STANDARD  STANDARD  STANDARD 2
1   30  60

---

tsm: SHITSM01q domain f=d



  Policy Domain Name: DOM_SRV

Activated Policy Set: SET_SRV

Activation Date/Time: 05/10/2007 11:09:44

   Days Since Activation: 951

Activated Default Mgmt Class: MC_90DAYS

  Number of Registered Nodes: 3

 Description:

 Backup Retention (Grace Period): 60

Archive Retention (Grace Period): 1,095

  Last Update by (administrator): ADMIN

   Last Update Date/Time: 07/30/2009 11:30:05

Managing profile:

 Changes Pending: Yes



  Policy Domain Name: STANDARD

Activated Policy Set: STANDARD

Activation Date/Time: 05/09/2007 12:41:05

   Days Since Activation: 952

Activated Default Mgmt Class: STANDARD

  Number of Registered Nodes: 1

 Description: Installed default policy domain.

 Backup Retention (Grace Period): 30

Archive Retention (Grace Period): 365

  Last Update by (administrator): SERVER_CONSOLE

   Last Update Date/Time: 05/09/2007 12:41:05

Managing profile:

 Changes Pending: No



---

tsm: SHITSM01q mgmtclass



PolicyPolicyMgmt  Default   Description

DomainSet Name  Class Mgmt

NameName  Class ?

- - - -


DOM_SRV   ACTIVEMC_90DAYS Yes

DOM_SRV   SET_SRV   MC_90DAYS Yes

STANDARD  ACTIVESTANDARD  Yes   Installed
default

 management
class.

STANDARD  STANDARD  STANDARD  Yes   Installed
default

 management
class.

--

Please consider the environment before printing this Email.

This email message and any attachments transmitted with it may contain
confidential and proprietary information, intended only for the named
recipient(s). If you have received this message in error, or if you are
not the named recipient(s), please delete this email after notifying the
sender immediately. BKME cannot guarantee the integrity of this
communication and accepts no liability for any damage caused by this
email or its attachments due to viruses, any other defects, interception
or unauthorized modification. The information, views, opinions and
comments of this message are those of the individual and not necessarily
endorsed by BKME.

ÿþDit bericht is 

Re: C:\windows\assembly exclude ????

2009-12-03 Thread Bos, Karel
Hi,

I don't know Win2008, but is this assembly directory by any change part of the 
system state/opject or something part of the back-up?

With 2003 and other versions, if there was an operating system excludes most of 
the time you could found it being part of the system state/object back-up. In 
the other case, if MS does exclude it from back-up its probably not needed for 
the restore anyways 

Regards,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Robert 
Ouzen Ouzen
Sent: donderdag 3 december 2009 14:10
To: ADSM-L@VM.MARIST.EDU
Subject: Re: C:\windows\assembly exclude 

Richard 

Sorry forget it !!  I saw doing dsmc q inclexcl  that the assembly 
directory is exclude

Excl Directory C:\Windows\assemblyOperating System

It is a workaround to back it anyway ? 

I already did a lot of include option without any result.

Regards Robert 

-Original Message-
From: Richard Sims [mailto:r...@bu.edu]
Sent: Thursday, December 03, 2009 1:59 PM
To: רוברט אוזן
Subject: Re: C:\windows\assembly exclude 

Robert -

As we keep telling people, DO NOT just look at your options files to see 
excludes, do 'dsmc q inclexcl' to get the compiled results, from server client 
options and the Windows OS.

Richard

On Dec 3, 2009, at 6:12 AM, Robert Ouzen Ouzen wrote:

 Hi to all



 I configure a new server to backup , Windows server 2008 with TSM 
 version 6.1.2.0  64Bit . I notice that the folder c:\windows \assembly 
 is EXCLUDE (red mark)



 I double check my dsm.opt and no sign of exclude or exclude.dir  at 
 all  ???



 How can I backup this folder , request of the administrator



 T.I.A Regards



 Robert Ouzen

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery 

Re: ANS0299E Scheduler cannot be started manually because the value of MANAGEDSERVICES option is SCHEDULE.

2009-12-02 Thread Bos, Karel
Are their no typo's in the service names?

D:\Program Files\Tivoli\TSM\baclientdsmcutil update cad /name:TSM
Client Accep tor /cadschedname:TSM Client Schedueler 



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Timothy Hughes
Sent: woensdag 2 december 2009 17:19
To: ADSM-L@VM.MARIST.EDU
Subject: ANS0299E Scheduler cannot be started manually because the value
of MANAGEDSERVICES option is SCHEDULE.

Hello All,

For some reason, I am having trouble starting a Windows 2003 client
Tivoli backup schedule. This issue started late yesterday. I have
changed the dsm.opt file several times but to no avail. Any one with any
suggestions on this

12/02/2009 09:33:26 ANS0299E Scheduler cannot be started manually
because the value of MANAGEDSERVICES option is SCHEDULE.
12/02/2009 09:33:26 Scheduler has been stopped.

12/02/2009 09:33:41 ANS0299E Scheduler cannot be started manually
because the value of MANAGEDSERVICES option is SCHEDULE.
12/02/2009 09:33:41 Scheduler has been stopped.

12/02/2009 10:49:07 ANS0299E Scheduler cannot be started manually
because the value of MANAGEDSERVICES option is SCHEDULE.
12/02/2009 10:49:07 Scheduler has been stopped.


Manages services option I have the

Button checked for Both

Note this opt file is tailored for VM/VCB backup

DSM.opt file

NODENAME
TCPCLIENTADDRESS
PASSWORDACCESS GENERATE
TCPSERVERADDRESS
VMCHOST
VMCUSER
VMLIST
SUBFILEBACKUP YES
SUBFILECACHEPATH d:\tsmsubfile
SUBFILECAcHESIZE 100
commmethod tcpip
MANAGEDSERVICES WEBCLIENT schedule
DOMAINALL-LOCAL  -H:

VMBACKUPTYPE FILE




D:\Program Files\Tivoli\TSM\baclientdsmcutil update cad /name:TSM
Client Accep tor /cadschedname:TSM Client Schedueler

TSM Windows NT Client Service Configuration Utility Command Line
Interface - Version 6, Release 1, Level 0.2
(C) Copyright IBM Corporation, 1990, 2009, All Rights Reserved.
Last Updated Jul  5 2009
TSM Api Version 6.1.0

Command: Update TSM Client Service Parameters
Machine: SNI275(Local Machine)


Opening Registry Keys ...

Located service 'TSM Client Acceptor' .

Updated registry value 'CadSchedName' .

Windows 2003
Tivoli client V6.1


Thanks in Advance!

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is 

Re: how to show the backup time of a fileset?

2009-09-23 Thread Bos, Karel
Hi,

WAD. 

The field is for successful file system backups, not for partial made
backups.

Regards,

Karel


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Mehdi Salehi
Sent: woensdag 23 september 2009 10:35
To: ADSM-L@VM.MARIST.EDU
Subject: Re: how to show the backup time of a fileset?

It is a standard incremental backup.
I noticed that when I backup a filesystem Last Backup Start Date/Time
gets a value. but if backing up a directory inside a filesystem, this
field does not change.
For example:
# dsmc  inc /home -subdir=yes (sets the time in tsm server) # dsmc  inc
/home/mehdi -subdir=yes (does not set the time in tsm server)

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: LTO4 and compression

2009-08-27 Thread Bos, Karel
Hi,

Its on you device class definitions. 

 Device Class Name: LTO_PRIM
   Device Type: LTO
Format: DRIVE
  
You can change the default from drive to ultrium 4c for forced compression. 
This will only help if you data is not already compressed (being compressed 
data by nature like .jpg/zip etc or due to host based compression).

(from help upd dev)
-UPDate DEVclass--device_class_name---

--+--+--+--+---
   '-LIBRary--=--library_name-'  '-FORMAT--=--+-DRIVE-+-'   
  +-ULTRIUM---+ 
  +-ULTRIUMC--+ 
  +-ULTRIUM2--+ 
  +-ULTRIUM2C-+ 
  +-ULTRIUM3--+ 
  +-ULTRIUM3C-+ 
  +-ULTRIUM4--+ 
  '-ULTRIUM4C-' 
Met vriendelijke groet/kind regards,

Karel
_


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of 
Lars-Erik Öhman
Sent: donderdag 27 augustus 2009 12:25
To: ADSM-L@VM.MARIST.EDU
Subject: LTO4 and compression

Where do I enable compression for LTO4 tapes/drives in a 3584 library? The 
tapes only fill up to 800 GB.

A0L4TAPEPOOL1  LTO4CLASS   771.2 G 98.4 
 Full
A1L4TAPEPOOL1  LTO4CLASS   783.7 G 96.6 
 Full
A2L4TAPEPOOL1  LTO4CLASS   784.3 G 97.5 
 Full
A00015L4TAPEPOOL1  LTO4CLASS   795.8 G 99.8 
 Full
A00025L4TAPEPOOL1  LTO4CLASS   794.5 G 99.8 
 Full
A00011L4TAPEPOOL2  LTO4CLASS   804.2 G100.0 
 Full
A00024L4TAPEPOOL2  LTO4CLASS   805.1 G100.0 
 Full
A3L4COPYPOOL1  LTO4CLASS   780.8 G 96.9 
 Full
A00018L4COPYPOOL1  LTO4CLASS   793.5 G 99.9 
 Full
A00027L4COPYPOOL1  LTO4CLASS   804.2 G100.0 
 Full

Library 3584 L32 firmware version 8620
4 drives IBM ULT3580-TD4 fimware version 89B2

I have searched and not found any information how to enable compression.

/Larsa

Lars-Erik Öhman
IT Systems, servers and applications

Carnegie Investment Bank AB
Gustav Adolfstorg 18
103 38 Stockholm
tel. +46 8 58 86 88 14
www.carnegie.sehttp://www.carnegie.se/

Some days you're the bug, some days you're the windshield




This communication is from a Carnegie company within the Carnegie Group.

The information contained in it, including any attachment or enclosure, is 
intended only for the person or entity to which it is addressed and may contain 
confidential and/or privileged material. Any unauthorised use, review, 
retransmissions, dissemination, copying or other use of, or taking of any 
action in reliance upon, this information by persons or entities other than the 
intended recipient is prohibited. If you received this in error, please contact 
the sender and delete or shred the material immediately. Thank you.

Opinions, conclusions and other information expressed in this message are not 
given or endorsed by my firm or employer unless otherwise indicated by an 
authorised representative independent of this message.

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze 

Re: VTL Tape Size

2009-07-07 Thread Bos, Karel
Hi,

I think your volume size should be something fitting the data type going
into the storage pool. Putting 100GB exchange db files on 10gb volumes
or 1kb files on 100GB volumes doesn't seem efficient.

Regads,

Karel


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Huebner,Andy,FORT WORTH,IT
Sent: dinsdag 7 juli 2009 16:36
To: ADSM-L@VM.MARIST.EDU
Subject: VTL Tape Size

We are about to bring up new TSM servers and one of questions that has
come up is how big to make the VTL tapes?  We currently use 100GG and
have tried 10GB with our test server.
The question is what size it popular and why?

Andy Huebner



This e-mail (including any attachments) is confidential and may be
legally privileged. If you are not an intended recipient or an
authorized representative of an intended recipient, you are prohibited
from using, copying or distributing the information in this e-mail or
its attachments. If you have received this e-mail in error, please
notify the sender immediately by return e-mail and delete all copies of
this message and any attachments.
Thank you.

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: TSM ADmin Center and CentricStor

2009-06-16 Thread Bos, Karel
Hi,

Just go to the itsm admin command line and try to query those volumes
from there. I don't think you will get a reply anytime soon, although
the AdminCenter (last time I took a look at it) is really slow by
itself.

When we were looking into the CentricStor the very small volume size
caused issues in other backup products also. We were thinking about
splitting the backup load over multiple pools (as we have now) and have
multiple volume sizes in the CentricStor. 5GB for file system backups,
100GB for TDP etc. This would reduce the absurd large number of volumes
to a more realistic number.


Regards,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Francisco Molero
Sent: dinsdag 16 juni 2009 13:34
To: ADSM-L@VM.MARIST.EDU
Subject: TSM ADmin Center and CentricStor

Hi, 

we have and installation with both products. Which is my problem? it is
the number of volumes that CentricStore creates in order to optimize its
performance. In our case, we have defined in CentricStore 45000 volumes
of 5 GB ( this is for  incremental backups and it is a Fujitsu
Recommendation).
When we connect the AdminCenter to TSM Server it hangs  because Admin
Center tries  to run queries to TSM Server .. 

Any suggestions ?? 

Regards,

Fran





ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: HSM reconcilliation (Windows-Client)

2009-06-04 Thread Bos, Karel
Did you ran expire inventory?

Regards,

Karel



Hello everybody,

I'm trying to set up HSM (TSM 5.5.2)  for our Windows fileserver. For
testing purposes I've created a folder c:\temp\hsmtest and put a file
into that folder. I set up a hsm job for that folder and ran it whicht
worked as
expected: The file has been moved into the tsm archive and has been
replaced by a stub file. Retrieving the file also worked as expected.
Next (after migrating the file into the archive again) I deleted the
stubfile to test the reconsilliation (the archive copy groups retain
version value is set to nolimit). I ran the reconsilliation via the
HSM Client GUI, but after that the deleted file was still in the archive
(is still listed when looking for it via the search  retrieve command
in the GUI).

Why is this so? What do I have to do to get rid of the deleted file in
the archive?

Thanks in advance for you help!

kind regards,
Stephan

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Filetype library sharing

2009-05-27 Thread Bos, Karel
Hi,


I have 2 ITSM server (5.4) running on one Windows box. One library
client, one library manager. They share (among other STA's) a LTO
library, which is working fine.

Now, I'm trying to get a filetype library working in the same manner as
the LTO library. What I did was:

- defined the file type library on the library manager. 
- defined a path from the library client to this library on the library
manager.
- defined library on the library client

Now its time to define the devclass on the library client pointing to
this filetype library, but which one to select??? 

Devclass file has no option to point to the shared library, generictape
didn't do it either. Removablefile gives nice errors 5/27/2009 3:02:53
PM ANR8935E A compatible device class for shared library FILELIB1 on
server  was not found.

Thanx,

Karel

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: q vol Issue with _some_ drm volumes

2009-05-04 Thread Bos, Karel
Database back-up tapes don't belong to a storage pool, so won't show up
on a q vol command.

Regards,
K.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Stephan Boldt
Sent: maandag 4 mei 2009 13:20
To: ADSM-L@VM.MARIST.EDU
Subject: q vol Issue with _some_ drm volumes

Hello everybody,

I wonder why _some_ of my dbsnapshot-type drmvolumes can be queried with
q vol and some don't (example ouput below). That occurres quite
strange to me. Any ideas what can be the cause?

kind reagards,
Stephan

 example output: ---

tsm: TSMq drm s=dbs

Volume NameState   Last Update   Automated
   Date/Time LibName
   -   ---

000302L2   Vault   04/30/2009 10:23:04
[...]
000330L2   Vault   04/30/2009 10:23:32

tsm: TSMq vol 000302L2

Volume Name   Storage  Device  EstimatedPct
Volume
  Pool NameClass Name   Capacity   Util
Status
  ---  --  -  -

000302L2  COPYPOOL_I-  LTO2  310.0 G   55.8
Full
   BM3583

tsm: TSMq vol 000330L2
ANR2034E QUERY VOLUME: No match found using this criteria.
ANS8001I Return code 11.

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK 

Re: Journaling

2009-03-25 Thread Bos, Karel
He is not, you are.



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
william dourado
Sent: woensdag 25 maart 2009 12:23
To: ADSM-L@VM.MARIST.EDU
Subject: Journaling

Dear all,
 
I  have had problems with journaling, so I deleted the journal files,
installed the last supported client version for wk2 server 5.3.4.0.
 
I always believed that to resume journaling all I had to do was perform
an incremental(complete)  backup NOT a always backup.
 
However a colleague thinks a always backup (full) is required for the
journal to be up to date?
 
Is he correct?
 
TSM Server  5.4.2.0 Windows Environment.
 
 
Thanks
 
Bill

_
View your Twitter and Flickr updates from one place - Learn more!
http://clk.atdmt.com/UKM/go/137984870/direct/01/
ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: TSM library manager instance

2009-03-16 Thread Bos, Karel
Hi,

Just give them their own ports and you should be fine. 


Regards/Met vriendelijke groet,

Karel
_

Karel Bos

Technical Expert  
PU EIS SMS MSS-WEST

Atos Origin Nederland B.V.
Naritaweg 52
1043 BZ Amsterdam
Office: +31 (0)88 265 95 43
Fax:+31 (0)20
Mobile:+31 (0)6 51 29 88 01
Mail: karel@atosorigin.com


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Mark Devine
Sent: maandag 16 maart 2009 15:59
To: ADSM-L@VM.MARIST.EDU
Subject: TSM library manager instance

Hey folks,

(AIX 5.3 / TSM 5.4.3)

Any snags with adding a library manager TSM server instance alongside an
active TSM server on the same host?  They will share HBAs, NICs, etc.

The current TSM server is clustered (HACMP), so I'm proposing moving
these in tandem during a failover.

-- Mark

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: TDP Exc Backup full to empty tape

2009-03-11 Thread Bos, Karel
Any reason for doing this? Tape will not be useable without
corresponding DB back-up tape.

Regards,

Karel



-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Mario Behring
Sent: woensdag 11 maart 2009 14:02
To: ADSM-L@VM.MARIST.EDU
Subject: TDP Exc Backup full to empty tape

Hi list,

I need to perform a full backup from a MS Exchange Server using TDP for
Exchange. However, I need to do it on a empty tape, outside the regular
scheduled backup operations.

Can I do this from the command line? Is there any parameter that I can
use to specify that the data from this particular operation should be
written on a empty tape? I have to send this tape away, with only this
data on it.

I am running TSM Server 5.4, TDP for Exchange 5.3.3 and I have an
automated library.

Thanks in advance.

Mario

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: lanfree question:

2009-03-05 Thread Bos, Karel
Hi,

You can use a storage agent on another machine. Data will be sent over
the LAN to that machine, so its partial LANfree. 

Regards,

k

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
goc
Sent: donderdag 5 maart 2009 11:53
To: ADSM-L@VM.MARIST.EDU
Subject: lanfree question:

boy, i'm confused ... we are apparentlly getting oracle exodata on
try/buy and there is backup questions of course ..

i have only quick one: can i do lanfree backups from machine which
doesn't have storage agent installed ?

i mean another machine has sta installed and sees tsm tape drives as
local ... and stuff ?

i was always confused with LANFreetcpserveraddress parameter which in my
sick logic tells me that LANfree server can be anywhere ...

... or am i babbling ?

thanks for your time.

--

Dick Cavett  - If your parents never had children, chances are...
neither will you.

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: Deleting primary storage volumes

2009-03-05 Thread Bos, Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Remco Post
Sent: donderdag 5 maart 2009 16:26
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Deleting primary storage volumes

On 5 mrt 2009, at 16:12, Huebner,Andy,FORT WORTH,IT wrote:

 If you delete a primary volume TSM also deletes the data from the copy

 pool.

 not true.

Deleting prim. Vol will delete all the data from copy stg vols also.

From the help del vol command 

  If the volume being deleted is a primary storage pool volume, the
  server checks whether any copy storage pool has copies of files
  that are being deleted. When files stored in a primary storage
  pool volume are deleted, any copies of these files in copy storage
  pools are also deleted.



Regards,
K.
ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: How do you keep track of DB Backup

2009-03-02 Thread Bos, Karel
DRM :)

select state,count(*) as DRMEDIA from drmedia

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Christian Svensson
Sent: donderdag 26 februari 2009 19:51
To: ADSM-L@VM.MARIST.EDU
Subject: How do you keep track of DB Backup

Hi,
I got a generic question for you all. How do you keep in track of your
Database Backup Tape Volumes?
I know you can see in Volhist the label of the volume, but how do you
keep in track to get it back from the vault?
Do you have a script or do you call it back one day in advance? 

Please, I'm really interested of your feedback and how you deal with it?

Best Regards
Christian Svensson

Cell: +46-70-325 1577
E-mail: christian.svens...@cristie.se
Skype: cristie.christian.svensson
ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: TS error - ANR1330E and ANR1331E

2009-03-02 Thread Bos, Karel
Hi,

Sounds like corruption (due to HW failure?).

http://www.adsm.org/forum/showthread.php?t=8304 


Met vriendelijke groet,

Karel
_

Karel Bos

Technical Expert  
PU EIS SMS MSS-WEST

Atos Origin Nederland B.V.
Naritaweg 52
1043 BZ Amsterdam
Office: +31 (0)88 265 95 43
Fax:+31 (0)20
Mobile:+31 (0)6 51 29 88 01
Mail: karel@atosorigin.com


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Abayomi Oni
Sent: maandag 2 maart 2009 13:44
To: ADSM-L@VM.MARIST.EDU
Subject: TS error - ANR1330E and ANR1331E

I get the error below when I run the command  to initiate migration.
Kindly help with possible solutions



03/02/2009 13:07:52  ANR1330E The server has detected possible
corruption in an
  object being restored or moved. The actual
values for the
  incorrect frame are: magic 53454652 hdr
version 0002 hdr
  length  0032 sequence number 0001 data
length
  0003FFB0 server id  segment id
32006177
  crc . (PROCESS: 28)
03/02/2009 13:07:52  ANR1331E Invalid frame detected.  Expected
magic 53454652
  sequence number 0001 server id 
segment id
  35209435. (PROCESS: 28)
03/02/2009 13:07:52  ANR1330E The server has detected possible
corruption in an
  object being restored or moved. The actual
values for the
  incorrect frame are: magic 53454652 hdr
version 0002 hdr
  length  0032 sequence number 0001 data
length
  0003FFB0 server id  segment id
32006177
  crc . (PROCESS: 28)
03/02/2009 13:07:52  ANR1331E Invalid frame detected.  Expected
magic 53454652
  sequence number 0001 server id 
segment id
  35209435. (PROCESS: 28)





This email and any attachments are confidential and may also be
privileged. If you are not the addressee, do not disclose, copy,
circulate or in any other way use or rely on the information contained
in this email or any attachments. If received in error, notify the
sender immediately and delete this email and any attachments from your
system. Emails cannot be guaranteed to be secure or error free as the
message and any attachments could be intercepted, corrupted, lost,
delayed, incomplete or amended. First City Monument Bank Plc and its
subsidiaries do not accept liability for damage caused by this email or
any attachments and may monitor email traffic.

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please 

Re: Preferred TSM Platform

2009-02-25 Thread Bos, Karel
Hi,

Use the OS you have the best support for in your shop. In our case we
have ITSM servers running on AIX and Windows. 

Regards,

Karel Bos

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Ian Smith
Sent: woensdag 25 februari 2009 11:31
To: ADSM-L@VM.MARIST.EDU
Subject: Preferred TSM Platform

Hi

 

I am sure this question has been asked many times, however with server
and OS development what is the favored OS for TSM v5? I have always
preferred AIX however never been keen on Solaris and am considering
Windows instead.

 

Will v6 be compatible with the Windows platform?

 

Ian Smith

 

Dell Corporation Limited is registered in England and Wales. Company
Registration Number: 2081369 Registered address: Dell House, The
Boulevard, Cain Road, Bracknell,  Berkshire, RG12 1LF, UK.
Company details for other Dell UK entities can be found on
www.dell.co.uk.

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: Make empty volume a scratch tape

2009-02-02 Thread Bos, Karel
Storage Management Server for AIX-RS/6000 - Version 5, Release 5, Level
1.1

Still has some of those 0.0 util volumes now and then.

Regards,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Richard Sims
Sent: maandag 2 februari 2009 14:09
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Make empty volume a scratch tape

On Feb 1, 2009, at 9:24 PM, Paul Dudley wrote:

 The pct util is 0.0, the tape is in read/write access state and the 
 volume state is full. How can I make this a scratch tape as it has no 
 data on it?

That's an old-chestnut TSM database problem which, as Mark says, is
corrected by an Audit Volume.  Out of curiosity, what is your TSM server
level?  Hopefully, newer levels are not exhibiting this problem.

Note that a Pct Util of 0.0 does not mean that a tape is empty, thanks
to the sorely inadequate 1 decimal position that the product is still
using, where 0.04179% will round to 0.0%.  In today's very-high-
capacity tape world, 1 decimal position is absurdly insufficient to be
helpful to customers, and leads to misinterpretations like this.

Richard Sims

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: Hardware upgrade question(s)

2009-01-28 Thread Bos, Karel
Only black and white found in text. :P


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
KIRAN-SYSTEMS
Sent: woensdag 28 januari 2009 10:26
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Hardware upgrade question(s)

Please find my suggestions in RED Color



Regards,

Kiran M.





-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
goc
Sent: Wednesday, January 28, 2009 2:29 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Hardware upgrade question(s)



hi all, i'm sure you can help me ...

we are getting ready for hardware upgrade of our old TSM servers , old
servers

are IBM p640 and new ones are p520 or something like that i really don't
know

because management simply forgets to forward this information :-) ...
anyhow

i know there was a lot of discussion here on list about migration of TSM
to new

hardware and i was always missing a part ... the procedure should go

something like

this i believe (please correct me and add stuff)



- install new servers

- cable connections to switches

Install IBM  device drivers for the Library

- install TSM server software

- define TSM db and logs

- define drives (can i define drives if they are already defined to

old TSM server?)



Enable Library Sharing by defining shared library for the new TSM
server.

- ?

- ?

- when and how should i import the database ?



Restore Database by taking the Old server Latest DB tape

- can i have 2 TSM server running parallel using same drives in tape

library (3584 with LTO3) ?



You can use Library Sharing Among two TSM instances



http://www-01.ibm.com/support/docview.wss?rs=1019
http://www-01.ibm.com/support/docview.wss?rs=1019context=SSSQWCdc=DB5
20d
c=DB560uid=swg21145017loc=en_UScs=UTF-8lang=enrss=ct1019tivoli
context=SSSQWCdc=DB520dc=DB560uid=swg21145017loc=en_UScs=UTF-8lan
g=en
rss=ct1019tivoli



I think the above link helps you



sheesh. so many questions !



thanks in advance ... and i'll check the list for additional answers



//

goran

Disclaimer:
This email message (including attachments if any) may contain
privileged, proprietary, confidential information, which may be exempt
from any kind of disclosure whatsoever and is intended solely for the
use of addressee (s). If you are not the intended recipient, kindly
inform us by return e-mail and also kindly disregard the contents of the
e-mail, delete the original message and destroy any copies thereof
immediately. You are notified that any dissemination, distribution or
copying of this communication is strictly prohibited unless approved by
the sender.

DQ Entertainment (DQE) has taken every reasonable precaution to minimize
the risk of transmission of computer viruses with this e-mail; DQE is
not liable for any damage you may sustain as a result of any virus in
this e-mail. DQE shall not be liable for the views expressed in the
e-mail. DQE reserves the right to monitor and review the content of all
messages sent to or from this e-mail address

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are 

Re: Collocation

2009-01-20 Thread Bos, Karel
It will append if the prev. used tape is available for writing and not full 


Kind regards/Met vriendelijke groet,

Karel
_

Karel Bos

Technical Expert  
PU EIS SMS MSS-WEST

Atos Origin Nederland B.V.
Naritaweg 52
1043 BZ Amsterdam
Office: +31 (0)88 265 95 43
Fax:+31 (0)20
Mobile:+31 (0)6 51 29 88 01
Mail: karel@atosorigin.com


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Lepre, 
James
Sent: maandag 19 januari 2009 20:31
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Collocation

Hello Everyone

 

I have a question regarding collocation

 

 

I have a VTL and would like to start using collocation for various reasons.  My 
question is and I cant remember the answer what is it.  If I collocate the pool 
and start a backup each node will get their own tape, however will the next 
nights backup get appended to the first night tape providing it is not full or 
will the next nights backup go on a separate tape.  

 

Thank you 

 

James 

 

 


  
  
---
Confidentiality Notice: The information in this e-mail and any attachments 
thereto is intended for the named recipient(s) only.  This e-mail, including 
any attachments, may contain information that is privileged and confidential  
and subject to legal restrictions and penalties regarding its unauthorized 
disclosure or other use.  If you are not the intended recipient, you are hereby 
notified that any disclosure, copying, distribution, or the taking of any 
action or inaction in reliance on the contents of this e-mail and any of its 
attachments is STRICTLY PROHIBITED.  If you have received this e-mail in error, 
please immediately notify the sender via return e-mail; delete this e-mail and 
all attachments from your e-mail  system and your computer system and network; 
and destroy any paper copies you may have in your possession. Thank you for 
your cooperation.

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus 

Re: ANS4014E

2009-01-13 Thread Bos, Karel
Yeah, using down level clients to restore data can be interesting :)

K

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Richard Sims
Sent: dinsdag 13 januari 2009 13:29
To: ADSM-L@VM.MARIST.EDU
Subject: Re: ANS4014E

If encryption is involved, this may be the situation described in
Technote 1281972.

More likely, I would suspect that the client attempting the restoral is
not the one which performed the backup, and that the backup client was
at a higher level, as summarized in APAR IC53549.  The dsmerror.log may
contain more detail.  Restoring at lower levels is always iffy, as data
structures may have changed over time.

Richard Sims

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: Backupset media goes to Copypool too?

2008-12-29 Thread Bos, Karel
Luckely the subject is backup set. 


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Adrian C. Pardo
Sent: maandag 29 december 2008 14:19
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Backupset media goes to Copypool too?

Remco

TSM is with us for more than 10 years now, if you have migrated your
archived data from earlier tape system to LTO1..and then to LTO4, when
LTO10 is Ready, you will keep migrating your archive data, so the 25
years could be completed.

So, when you have such a requirement you must think your migration path
of older data...is part of the job

10 years is an standard here

Adrian Pardo
Buenos Aires- Argentina




-Mensaje original-
De: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] En nombre de
Remco Post Enviado el: Domingo, 28 de Diciembre de 2008 21:06
Para: ADSM-L@VM.MARIST.EDU
Asunto: Re: [ADSM-L] Backupset media goes to Copypool too?

On Dec 28, 2008, at 23:38 , Cheung, Richard wrote:

 Business requirements to have quarterly backups to be retained for 25 
 years


You mean a business requirements to retain some data for 25 years?
Backups are not archives. Really repeat after me, backups are not
archives. I can think of no legitimate reason to retain backups for
more than maybe 2 years, and even that is pushing it.

Here's a bit of free consultancy ;)

When retaining TSM backupsets, are you also retaining:

1- drives that can read the tapes
2- software versions that can read the media and interpret the data
3- hardware that can run that software

Have you considered that even enterprise archival tapes are only
guaranteed for 10 years?

This is a very hard problem to solve and I really don't believe that
it's easy to have TSM be part of the solution. If you have a real
business-case, make a real design, assume nothing but open standards.
You'll probably wind up writing tapes in tar or cpio format with plain-
text, pdf or maybe odf formatted files and copying those tapes over
every year or so. IBM is a very big company, but I doubt that even IBM
will guarantee availability of software that can interpret current TSM
on-tape format in 25 years. And that is just one link in the chain.

In the old days there were people that specialized in retaining data,
called archivists. Now, in current day and age, anyone thinks that can
do this on a PC, but really there are just to many thing to think of.

 -Original Message-
 From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf 
 Of Nick Laflamme
 Sent: Sunday, 28 December 2008 3:39 AM
 To: ADSM-L@VM.MARIST.EDU
 Subject: Re: [ADSM-L] Backupset media goes to Copypool too?

 On Dec 26, 2008, at 9:10 PM, Cheung, Richard wrote:

 Hi...

 So if i wanted these to be kept offsite AND onsite, do I need to 
 issue a manual copy command?

 The following is speculation, but I'll bet a beer at SCIDS that the 
 premise is valid.

 If you want two backup sets, run the command twice. Presumably, after 
 each one, you'll CHECKOUT the LIBVOLs on which the backup set was 
 created. What you do with the media once it's out of the library is up

 to you. Send one to an off-site repository, or store one is a user's 
 office so they know they have a copy of their data, it's up to them.

 Like database backups, backup sets are created on a device type but 
 are not part of storage pools. They're just different.

 Remind me, why are you so gung-ho to have backup sets in the first 
 place? What problem are you solving?

 Nick

 html
 body
 font face=arial color=#808080 size=-2img alt=Santos Logo 
 src=http://www.santos.com/library/logo.gif;
 brSantos Ltd A.B.N. 80 007 550 923br
 Disclaimer: The information contained in this email is intended only 
 for the use of the person(s) to whom it is addressed and may be 
 confidential or contain privileged information.
 If you are not the intended recipient you are hereby notified that any

 perusal, use, distribution, copying or disclosure is strictly 
 prohibited.
 If you have received this email in error please immediately advise us 
 by return email and delete the email without making a copy./font 
 font face=arial color=#008000 size=-2Please consider the 
 environment before printing this email/font /body /html

--
Met vriendelijke groeten,

Remco Post
r.p...@plcs.nl
+31 6 248 21 622


Re: backupset location

2008-12-24 Thread Bos, Karel
Hi,

You don't create a backup set into a storage pool. You use a devclass.
So, even though the backup set is created into the same device class as
the primary pool is using, the set is not in the pool and will not be
copied into the copypool. 


Kind regards/Met vriendelijke groet,

Karel
_

Karel Bos

Technical Expert  
PU EIS SMS MSS-WEST

Atos Origin Nederland B.V.
Naritaweg 52
1043 BZ Amsterdam
Office: +31 (0)88 265 95 43
Fax:+31 (0)20
Mobile:+31 (0)6 51 29 88 01
Mail: karel@atosorigin.com


-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Cheung, Richard
Sent: woensdag 24 december 2008 1:04
To: ADSM-L@VM.MARIST.EDU
Subject: backupset location

Hi all

Just a quick query to round out the year...

Lets say I have two media pools, a on-site tape pool called LTO, and the
offsite copy of this LTO pool called COPYPOOL.

If I have generated a backup set into my standard LTO media pool, will
these tapes which are holding the backup set then automatically also be
copied into the COPYPOOL ?   If that is the case, are there really any
need to me to explicitly check out these 'backup set' tapes out of my
LTO media pool / library - when there may be already an offsite copy
automatically generated into the COPYPOOL ? 

Please advise.

Happy Christmas and a safe and joyous New Year to everyone

Richard


html
body
font face=arial color=#808080 size=-2img alt=Santos Logo
src=http://www.santos.com/library/logo.gif;
brSantos Ltd A.B.N. 80 007 550 923br
Disclaimer: The information contained in this email is intended only for
the use of the person(s) to whom it is addressed and may be confidential
or contain privileged information. 
If you are not the intended recipient you are hereby notified that any
perusal, use, distribution, copying or disclosure is strictly
prohibited. 
If you have received this email in error please immediately advise us by
return email and delete the email without making a copy./font font
face=arial color=#008000 size=-2Please consider the environment
before printing this email/font /body /html

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and 

Re: The Intergrated Solutions Console BAD performance.

2008-12-16 Thread Bos, Karel

We worked around the Intergrated thingy by using tsmmanager. 




-Original Message-
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Richard Rhodes
Sent: dinsdag 16 december 2008 18:05
To: ADSM-L@VM.MARIST.EDU
Subject: Re: The Intergrated Solutions Console BAD performance.

We quite using it a long time ago, and won't try again until TSM v6.1
comes out.






 Minns, Farren -
 Chichester
 fmi...@wiley.com
To
  ADSM-L@VM.MARIST.EDU
 Sent by: ADSM:
cc
 Dist Stor
 Manager
Subject
 ads...@vm.marist The Intergrated Solutions Console
 .EDU BAD performance.


 12/16/2008 09:30
 AM


 Please respond to
 ADSM: Dist Stor
 Manager
 ads...@vm.marist
   .EDU






Hi all (running TSM 5.4.1.2 on Solaris) ... Solutions Console 6.0.1

Whilst I try to use the ISC as little as often there are times when it
would be handy, especially when I'm out of the office and someone is
covering me.

At present I have it running on a Solaris box with lots of free memory
and the performance of it is so bad as to be almost a joke.

Do other people have similar issues? If so, does anyone have any tips
with regards to making it run acceptable?

Any help would be much appreciated.

Many thanks

Farren Minns



This email (and any attachment) is confidential, may be legally
privileged and is intended solely for the use of the individual or
entity to whom it is addressed. If you are not the intended recipient
please do not disclose, copy or take any action in reliance on it. If
you have received this message in error please tell us by reply and
delete all copies on your system.

Although this email has been scanned for viruses you should rely on your
own virus check as the sender accepts no liability for any damage
arising out of any bug or virus infection. Please note that email
traffic data may be monitored and that emails may be viewed for security
reasons.

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, PO19 8SQ.



ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin 

Re: Reclamation

2008-12-09 Thread Bos, Karel
Hi,

If all files needed for reclaimation are in the diskpool, only the
target tape is mounted. 


Met vriendelijke groet/kinds regards,

Karel
_

Karel Bos

Technical Expert  
PU EIS SMS MSS-WEST

Atos Origin Nederland B.V.
Naritaweg 52
1043 BZ Amsterdam
Office: +31 (0)88 265 95 43
Fax:+31 (0)20
Mobile:+31 (0)6 51 29 88 01
Mail: [EMAIL PROTECTED]


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Stephan Boldt
Sent: dinsdag 9 december 2008 17:20
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Reclamation

So, if your diskpool is large enough, relamation would only need the
target tape and NOT the source tape? (because all data that is moved
during migration is also cached on disk!) Is this true?

kind regards,
Stephan

2008/12/9 Mark Stapleton [EMAIL PROTECTED]

 When TSM tries to access a file for any purpose (restore, reclamation,

 etc.), it will ALWAYS try to use a copy of the file residing in a 
 disk-based device class storage pool--even if the file isn't available

 (due to disk downage).

 --
 Mark Stapleton ([EMAIL PROTECTED]) CDW Berbee System engineer
 7145 Boone Avenue North, Suite 140
 Brooklyn Park MN 55428-1511
 763-592-5963
 www.berbee.com


  -Original Message-
  From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On 
  Behalf Of Stephan Boldt
  Sent: Tuesday, December 09, 2008 7:47 AM
  To: ADSM-L@VM.MARIST.EDU
  Subject: Re: [ADSM-L] Reclamation
 
  Just a dumb question: Is there a possibility to do the reclamation 
  of the primary tape pools via the cached data in the disk pools?
 
  kind regards,
  Stephan
 
  2008/12/8 Allen S. Rout [EMAIL PROTECTED]
 
On Mon, 8 Dec 2008 12:27:46 -0500, Lepre, James
  [EMAIL PROTECTED]
   said:
  
I have a question on how reclamation works.  I have a small
 library
with 24 slots and 2 Drives.  When I start reclamation say at 90%
 it
puts in tape 1 and then put in another tape to reclamate to.  It

then ask for tapes that are not in the library so I am 
constantly checking in and out tapes to reclamate this one tape.

Could
  someone
tell me how the process actually is supposed to work maybe I am 
doing something incorrect.
  
   In general, you'll expect a full volume to have at least two 
   partial files (aggregates) on it: the one hanging off the 
   beginning, and the one hanging off the end.
  
   You may have several others, too, if you are constricted (as it 
   appears you are): Every time you finish a volume, there's a 
   partial file there.  It's possible the other halves might get 
   disproportionately collected.
  
   So, the checking in and out is to be expected.
  
  
   How many tapes in your collection?  You may be able to make a case
  for
   acquiring a larger library.  This can be exceptionally attractive 
   if you can point out that now you have to be onsite to service
 restores.
   If you have all your data in the library, most activity can go 
   unattended.
  
   I view handling-by-humans as the largest risk my tapes go through.
   Minimizing those occasions is well worth it, in the long run.
  
  
   - Allen S. Rout
  
 
  No virus found in this incoming message.
  Checked by AVG - http://www.avg.com
  Version: 8.0.176 / Virus Database: 270.9.15/1838 - Release Date:
  12/8/2008 6:16 PM


ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 

Re: Database size, Split to multiple instances or wait for version 6.1

2008-12-04 Thread Bos, Karel
Ok, 350GB tsm db backing up in 1 hour? How did you get it that fast? 

Regards,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Conradt, Jeremy
Sent: donderdag 4 december 2008 17:19
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Database size, Split to multiple instances or wait for
version 6.1

Expiration takes about 1 hour.  DB Backup takes about 1 hour 15 minutes.

Thanks,
Jeremy 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Wanda Prather
Sent: Wednesday, December 03, 2008 7:01 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Database size, Split to multiple instances or wait
for version 6.1

How long does it take you now to do Expiration and DB backup?



On Wed, Dec 3, 2008 at 4:24 PM, Conradt, Jeremy 
[EMAIL PROTECTED] wrote:

 I have a TSM server currently running version 5.3.5 on Windows 2003 
 that we plan to upgrade soon.
 The problem I have is our database has grown to 350 GB.
 The question I have is will version 6.1 of TSM be better capable of 
 maintaining a database this size and much larger or should I break it 
 apart?
 I would rather keep everything together so we can make better use of 
 de-duplication that may be coming out with version 6.
 Thanks,
 Jeremy




ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

ITSM server core dumps during restore of large oracle database

2008-12-02 Thread Bos, Karel
Hi,

While doing a full Oracle Online database restore the ITSM server core
dumps with the following error message in the Windows Event viewer:

TSM Server Diagnostic: ANRD: ADSM Exception Information: file =
pkthread.c, line = 2301,Code = c005, Address = 07FF7FC530AC
Attempt to read data at address 141bc519

Env:
ITSM server (library client) = Storage Management Server for Windows -
Version 5, Release 5, Level 1.1
ITSM server (library manager) = same (running on the same box)
Machine runs Windows X64, has 16 GB mem and 4 quad core CPU's and is a
dedicated ITSM server with little load.
 
Client
ITSM storage agent  = Storage Management Server for Windows
- Version 5, Release 5, Level 1.0
ITSM TDP= Client
Version: Version 5, release 5, level 0.2
ITSM BA client  = Client Version:
Version 5, release 5, level 0.2

Oracle database tdp restores runs over the SAN, has good performance but
never end (after been running for pretty much the whole day) because the
ITSM server core dumps. ITSM library manager, running on the same
machine, stays up and running.
This happens with every full restore (different days, different
back-ups, on different tapes).  

Any ideas?

Best regards/Met vriendelijke groet,

Karel
_

Karel Bos

Technical Expert  
PU EIS SMS MSS-WEST

Atos Origin Nederland B.V.
Naritaweg 52
1043 BZ Amsterdam
Office: +31 (0)88 265 95 43
Fax:+31 (0)20
Mobile:+31 (0)6 51 29 88 01
Mail: [EMAIL PROTECTED]


ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be 

Re: del volhist?

2008-11-19 Thread Bos, Karel
Try

delete volhist todate=today type=dbb volume=VolumeName force=yes 

Or sometihing like that.

Regards,

karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Remco Post
Sent: woensdag 19 november 2008 10:11
To: ADSM-L@VM.MARIST.EDU
Subject: del volhist?

Hi,

I'm running tsm 5.5.1.1 on win64, did a backup db to devclass drm
(devtype=file),and wanted to delete only that one dbbackup so I issued:

tsm: serverdel volhist todate=today t=dbb dev=drm ANR6978E DELETE
VOLHISTORY: Invalid device class UNKNOWN.
ANS8001I Return code 3.

but, yes the deviceclass drm does exist:

Device   DeviceStorageDevice   Format Est/
Max Mount
ClassAccess   PoolType
Capacity Limit
Name StrategyCount   (MB)
---------
--
DISK Random  4
DRM  Sequential  1FILE DRIVE
100.020
DRM-REMO-Sequential  0SERVER
100.020
  TE
T10KB-LO-Sequential  4ECARTRID-DRIVE
1,843,20 6
  CAL   GE 0.0
T10KB-RE-Sequential  2ECARTRID-DRIVE
1,843,20 6
  MOTE  GE 0.0

so, I must be doing something wrong, or is this a TSM error?

--
Met vriendelijke groeten/Kind regards,

Remco Post, PLCS
+31624821622

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your 

Re: PROBLEM with TSM 5.5.1.0 combined with VTL systems and RELABELSCRATCH=YES

2008-11-18 Thread Bos, Karel
Hi,

Thanx for the info. Seems to be not only limited to virtual tape
libraries. Got a I2000 complaining bout unmatching labels. Just checked,
library is configured to relabel scratch volumes (why, I do really not
know):

Serial Number: ADIC203100978_LL1
AutoLabel: OVERWRITE
Relabel Scratch: Yes

Lately it is giving a lot of :

11/17/2008 2:35:28 PM ANR8808E Could not write label X  on the
volume in drive DH2_131 (/dev/rmt0) of library ADIC because that volume
is already labeled with Y which is still defined in a storage pool
or volume history.

ITSM server
Storage Management Server for AIX-RS/6000 - Version 5, Release 5, Level
1.1


Regards,

Karel


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Arbes, Thorsten
Sent: dinsdag 18 november 2008 15:39
To: ADSM-L@VM.MARIST.EDU
Subject: PROBLEM with TSM 5.5.1.0 combined with VTL systems and
RELABELSCRATCH=YES

Dear TSM guys,

Some bad news about TSM Server version 5.5.1.0 in combination with VTL
systems (FalconStor and NetApp systems) and the parameter
'RELABELSCRATCH'.
This parameter seems to be buggy.
In our TSM Server environment the complete TSM (virtual) tape inventory
seems to be shuffled.

The fact is that tape labels are not written to the tape volumes
correctly.
That means that the physical written tape labels do NOT match the
barcode of a tape volume within the TSM inventory.

In our case some restore job could not be started because the incorrect
tape volume was mounted for this restore session.
The session was stopped because the data was unavailable to server, seen
in the activity log.

The IBM support team (tech 2) is working on this issue but I?d guess it
needs some time to find a permanent solution.


So please do not set the parameter 'RELABELSCRATCH' to 'YES' in order to
avoid the same situation like we have now on 11 TSM servers now.



Mit freundlichen Gruessen / kind regards / Selamlar / ??? / ??
  / ?? / ?dv?zlettel / Com os melhores
cumprimentos

Thorsten Arbes
Campus Communication Services - Office Communication - Backup Group MGI
METRO Group Information Technology GmbH

Before printing, please think about ENVIRONMENTAL responsibility
Geschaeftsfuehrung/Management Board: Heinz-Josef Boeck
(Vorsitzender/CEO), Heike Schneberger, Dr. Dirk Toepfer, Dr. Gerd
Wolfram Sitz Duesseldorf, Amtsgericht Duesseldorf, HRB 18232/Commercial
Register of the Duesseldorf Local Court, HRB 18232 

This e-mail message is intended exclusively for the addressee. If the
e-mail was sent to you by mistake, would you please call us immediately?
In this case, we also request you to destroy the e-mail and to neither
use the content nor disclose them in any manner to third parties,
because the message can contain confidential information which may be
protected by professional secrecy.


Re: Offsite reclamation problem

2008-11-04 Thread Bos, Karel
No :)


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Thomas Denier
Sent: dinsdag 4 november 2008 18:14
To: ADSM-L@VM.MARIST.EDU
Subject: Offsite reclamation problem

We have a 5.4.2.0 TSM server running under mainframe Linux. We have five
tape drives available for our primary tape storage pool and five tape
drives available for our copy storage pool. We run offsite tape
reclaimation with 'maxproc=5'. If a client runs a restore while off
reclamation is going on, TSM will take a tape drive away from
reclamation. This is done by cancelling a reclamation process, rather
than having a process go into mount point wait. TSM does not start a
replacement process when this happens. A restore that runs for a couple
of minutes can leave a pair of tape drives sitting idle for hours. Is
there any configuration setting or release level upgrade that will cause
TSM to handle this situation more intelligently?

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: Offsite reclamation problem

2008-11-04 Thread Bos, Karel
Still kinda strange that TSM can't simply pause a task instead of
blundly canceling it.


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Mark Stapleton
Sent: dinsdag 4 november 2008 18:47
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Offsite reclamation problem

To expand that no, TSM has a hardset list of tape tasks, restores
being at the top. Backups are at the bottom of this hierarchy, and other
tape operations are kinda amorphously between them. It makes sense,
actually. Restores are the real reason why we're all here, right?

There is nothing to be done for resuming tape operations after a restore
is done, short of an external script that looks for the number of
reclamation processes running. You can't start the old one up again (to
get your count back to five) without stopping them all, and then
restarting them.
 
--
Mark Stapleton ([EMAIL PROTECTED])
CDW Berbee
System engineer
7145 Boone Avenue North, Suite 140
Brooklyn Park MN 55428-1511
763-592-5963
www.berbee.com
 
 -Original Message-
 From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf 
 Of Bos, Karel
 Sent: Tuesday, November 04, 2008 11:22 AM
 To: ADSM-L@VM.MARIST.EDU
 Subject: Re: [ADSM-L] Offsite reclamation problem
 
 No :)
 
 
 -Original Message-
 From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf 
 Of Thomas Denier
 Sent: dinsdag 4 november 2008 18:14
 To: ADSM-L@VM.MARIST.EDU
 Subject: Offsite reclamation problem
 
 We have a 5.4.2.0 TSM server running under mainframe Linux. We have 
 five tape drives available for our primary tape storage pool and five 
 tape drives available for our copy storage pool. We run offsite tape 
 reclaimation with 'maxproc=5'. If a client runs a restore while off 
 reclamation is going on, TSM will take a tape drive away from 
 reclamation. This is done by cancelling a reclamation process, rather 
 than having a process go into mount point wait. TSM does not start a 
 replacement process when this happens. A restore that runs for a
couple
 of minutes can leave a pair of tape drives sitting idle for hours. Is 
 there any configuration setting or release level upgrade that will 
 cause TSM to handle this situation more intelligently?

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does no

Re: Tape Reclamation Problem / Auditdb

2008-10-02 Thread Bos, Karel
Hi,

Know issue.

- update vol XXX acc=reado
- audit vol  XXX fix=yes
- update vol XXX acc=offsite

Should be fine now.


Regards/Met vriendelijke groet,

Karel
_

Karel Bos

Technical Expert  
PU EIS SMS MSS-WEST

Atos Origin Nederland B.V.
Naritaweg 52
1043 BZ Amsterdam
Office: +31 (0)88 265 95 43
Fax:+31 (0)20
Mobile:+31 (0)6 51 29 88 01
Mail: [EMAIL PROTECTED]


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Jeff White
Sent: donderdag 2 oktober 2008 10:36
To: ADSM-L@VM.MARIST.EDU
Subject: Tape Reclamation Problem / Auditdb

Hi

TSM Server v5.3.3.1
Running on AIX

I have a problem where an offsite volume continues to be reclaimed many
times, even though it's utilization is 0% and pct_reclaimable space is
0%.
The reclaim process starts then ends, the starts again etc. Been doing
that for the last 3 days.

On the IBM support site, there is a hit, which was last updated in May
2008


Space reclamation is always processing the same volumes, even after
successfull completion. Problem possibly caused by inconsistency in the
DB archival storage information.

An offline database AUDIT on the archstorage subset will help to recover
from this situation:

dsmserv auditdb archstorage logmode=rollforward fix=yes

Having researched the forum, I found a similar hit, where it was
recommended to Upd vol x acc=readw Audit vol x fix=yes Upd vol
x acc=offsite

I've done this, and the reclaim has stopped, hopefully it will not
re-appear.

But if it does and I have to run the 'dsmserv auditdb archstorage
logmode=rollforward fix=yes', how long is that likely to take, as I will
need the TSM server offline? Database size is 180gb, if that is
relevant.

Thanks


Jeff White



This e-mail and any attachments are confidential and intended solely for
the addressee and may also be privileged or exempt from disclosure under
applicable law. If you are not the addressee, or have received this
e-mail in error, please notify the sender immediately, delete it from
your system and do not copy, disclose or otherwise act upon any part of
this e-mail or its attachments.

Internet communications are not guaranteed to be secure or virus-free.
The Barclays Group does not accept responsibility for any loss arising
from unauthorised access to, or interference with, any Internet
communications by any third party, or from the transmission of any
viruses. Replies to this e-mail may be monitored by the Barclays Group
for operational or business reasons.

Any opinion or other information in this e-mail or its attachments that
does not relate to the business of the Barclays Group is personal to the
sender and is not given or endorsed by the Barclays Group.

Barclays Bank PLC.Registered in England and Wales (registered no.
1026167).
Registered Office: 1 Churchill Place, London, E14 5HP, United Kingdom.

Barclays Bank PLC is authorised and regulated by the Financial Services
Authority.


Re: Library manager/library conundrum

2008-10-02 Thread Bos, Karel
Mark,

As said, check your paths. The error says:
- there is no tape in this drive (mixed up elements nummers, tape is put
in one drive, windows opens another one);
- tape is in the correct drive, but TSM is unable to communicatie with
the drive (driver issue, firmware issues, other connection issues).

Checking drive things on windows with:
- ITSM device manager (serial number/ \\.\tapeX mapping
- communication with the drive via lbtest/mttest.exe utils (part of tsm
install)
- and anything else you can find to make shure things are happening as
you think they are :)

Mounts are performed by the library manager, communication is done from
the library client. Because your tape is mounted on the library manager
doesn't mean the library client is able to connect and talk to this
drive.



Regards,

Karel Bos

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Mark Stapleton
Sent: donderdag 2 oktober 2008 18:27
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Library manager/library conundrum

From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Remco Post
 do you have the paths for the library client configured correctly on 
 the library manager? Are the paths up? Al SAN ports enabled on the 
 library client?

As I said, the client's request for a tape mount is honored by the
manager, and it appears that the client gets an acknowledgement that the
tape is mounted, because it tries to talk to the tape volume. That's
when we get the 

   ANR8779E Unable to open drive \\.\tape4, error number=123

error.
 
--
Mark Stapleton ([EMAIL PROTECTED])
CDW Berbee
System engineer
7145 Boone Avenue North, Suite 140
Brooklyn Park MN 55428-1511
763-592-5963
www.berbee.com
 


Re: Active Storage Pools

2008-09-30 Thread Bos, Karel
It would be that more pratical if you could just update your diskpool
with something like upd stg XX cache=yes activestorage=yes, leaving
just cached copies of the active version on disk.



cpreston ha scritto:
 Howard Coles wrote:

 1.  Is anyone on the list here actually using it?
 2.  Is there a way just to copy a node's data (not all the nodes in a

 domain or storage pool) to the active pool?




 Looks like the answer to #1 is No. ;)  I've tried to talk a number of
TSM admins into this, and so far haven't gotten any takers. They tell me
that the challenge is that it is another administrative task.  The copy
of active data does not replace anything you're already doing.  It's an
additional copy (that must be managed by the expiration process) to an
additional pool that must be reclaimed just like any other pool.  Both
of these increase the number and/or duration of administrative tasks,
which is the last thing that the TSM admins I've talked to want to do.

 As to #2, I asked about this a while back, and someone said you could
say COPY ACTIVE-DATA NODENAME, but that is NOT in the documentation; nor
can I find it anywhere else.

 If you experiment with it, I'd love to see how things go.

 +-
 +-
 |This was sent by [EMAIL PROTECTED] via Backup Central.
 |Forward SPAM to [EMAIL PROTECTED]
 +-
 +-
 --
 --


 Nessun virus nel messaggio in arrivo.
 Controllato da AVG - http://www.avg.com
 Versione: 8.0.169 / Database dei virus: 270.7.4/1695 -  Data di 
 rilascio: 27/09/2008 13.11


ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos 

Re: Too many dbb being kept

2008-09-24 Thread Bos, Karel
Database volumes only expire when off-site (or delete volhist t=dbb)
(still early so could be overlooking something).

Regards,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Gill, Geoffrey L.
Sent: woensdag 24 september 2008 1:58
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Too many dbb being kept

I also have this problem with dbsnapshots and have tried everything I
know to get rid of 3 dbsnapshot tapes I have on a 5.5.1.0 system with no
luck. They will just not go away. They stay in the volhist no matter
what I do to try and remove them and are now 14 months old. Everything
matches another system I have, same OS, same level as this one and that
one works fine.
They don't show in q drm, they do show in volhist and will not delete
with the proper command, they do show in q libvol

At this point I don't think it's me anymore. Then again...

Geoff Gill
TSM Administrator
PeopleSoft Sr. Systems Administrator
SAIC M/S-G1b
(858)826-4062 (office)
(858)412-9883 (blackberry)
Email: [EMAIL PROTECTED] 

 -Original Message-
 From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf
Of
 Steven Harris
 Sent: Tuesday, September 23, 2008 4:06 PM
 To: ADSM-L@VM.MARIST.EDU
 Subject: Re: Too many dbb being kept
 
 Joni
 
 try Q DRM on each of those tapes.  They may be in  COURIERRETRIEVE 
 status.  If so, recall the ones that are offsite from the vault and
run
 MOVE DRM to make them go scratch.
 
 Regards
 
 Steve
 
 Steven Harris
 TSM Admin, Sydney Australia
 
 Richard Sims wrote:
  Review the expiration eligibility rules as documented with the Set 
  DRMDBBackupexpiredays command relative to the output of a Query 
  DRMedia command.
 
 Richard Sims
 

 
 
  No virus found in this incoming message.
  Checked by AVG - http://www.avg.com
  Version: 8.0.169 / Virus Database: 270.7.0/1685 - Release Date:
 9/22/2008 4:08 PM
 
 

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On 

Re: Manually update tcp_name

2008-09-24 Thread Bos, Karel
Help update node on the itsm server:

   HLAddress
   

  Specifies the client IP address that the server contacts to
  initiate scheduled events. This optional parameter is used only
  when SESSIONINITIATION is set to SERVERONLY, regardless of any
  addresses previously used by the client to contact the server. If
  SESSIONINITIATION SERVERONLY is not in use, this option has no
  effect.

   

  The address can be specified either in numeric or host name
  format. If a numeric address is used, it will be saved without
  verification by a domain name server. If the address is not
  correct, it can cause failures when the server attempts to contact
  the client. Host name format addresses will be verified with a
  domain name server. Verified names will be saved and resolved with
  Domain Name Services when the server contacts the client.

   LLAddress
   

  Specifies the client port number on which the client listens for
  sessions from the server. This optional parameter is used only
  when SESSIONINITIATION is set to SERVERONLY, regardless of any
  addresses previously used by the client to contact the server. If
  SESSIONINITIATION SERVERONLY is not in use, this option has no
  effect.
 
Regards,

Karel


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Shawn Drew
Sent: woensdag 24 september 2008 15:53
To: ADSM-L@VM.MARIST.EDU
Subject: Manually update tcp_name

Does anyone know how to update the tcp_name in the nodes tables?  It's
also the TCP/IP Name  in the  q node f=d output.

From what I've been reading, this is updated by backup/archive clients
when they connect to the server *if* they have the ability.
My Storserver ABC clients and my NAS clients aren't able to update this.

Unfortunately, someone must have incorrectly tried to connect to a NAS
node with a B/A client, so this tcp_name has been set on my NAS node
incorrectly, and I can't figure out how to clear it.  This is messing
with some reporting functions.

Any ideas?

Regards,
Shawn

Shawn Drew


This message and any attachments (the message) is intended solely for
the addressees and is confidential. If you receive this message in
error, please delete it and immediately notify the sender. Any use not
in accord with its purpose, any dissemination or disclosure, either
whole or partial, is prohibited except formal approval. The internet can
not guarantee the integrity of this message. BNP PARIBAS (and its
subsidiaries) shall (will) not therefore be liable for the message if
modified. Please note that certain functions and services for BNP
Paribas may be performed by BNP Paribas RCC, Inc.

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify 

Re: Decommission Procedure

2008-09-23 Thread Bos, Karel
We..
- remove the association
- rename the node from node to zdate_to_be_deleted_node
Daily checks include checking for node names with expired date in the
name.

Regards,

Karel


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Rhodes
Sent: dinsdag 23 september 2008 13:13
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Decommission Procedure

We . . . .
- remove the association
- rename the node from node to zzrt_node
- in the Contacts we put the date it was retired, and the date it to be
deleted

Once a month we go through the retired nodes and delete those that are
eligible.

Rick





 Shawn Drew
 [EMAIL PROTECTED]
 CAS.BNPPARIBAS.CO
To
 MADSM-L@VM.MARIST.EDU
 Sent by: ADSM:
cc
 Dist Stor
 Manager
Subject
 [EMAIL PROTECTED] Decommission Procedure
 .EDU


 09/22/2008 12:17
 PM


 Please respond to
 ADSM: Dist Stor
 Manager
 [EMAIL PROTECTED]
   .EDU






When a Node is decommissioned we typically
- lock the node
- remove it from the schedules
- A script periodically checks for old file systems (Based on retention)
and identifies file systems ready to be removed
- We remove the expired filesystems (and the last active versions) then
remove the node

Mr Sims recently suggested changing the MAXNUMMP to 0 to allow restores
but not backups.

What are some other decommission procedures out there?   I'm trying to
find the best way to do this so the decommissioned nodes will be
obviously distinguishable from the active nodes.

Regards,
Shawn

Shawn Drew


This message and any attachments (the message) is intended solely for
the addressees and is confidential. If you receive this message in
error, please delete it and immediately notify the sender. Any use not
in accord with its purpose, any dissemination or disclosure, either
whole or partial, is prohibited except formal approval. The internet can
not guarantee the integrity of this message. BNP PARIBAS (and its
subsidiaries) shall (will) not therefore be liable for the message if
modified. Please note that certain functions and services for BNP
Paribas may be performed by BNP Paribas RCC, Inc.



-
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If the
reader of this message is not the intended recipient or an agent
responsible for delivering it to the intended recipient, you are hereby
notified that you have received this document in error and that any
review, dissemination, distribution, or copying of this message is
strictly prohibited. If you have received this communication in error,
please notify us immediately, and delete the original message.

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended 

Re: Tsm client for as/400

2008-09-18 Thread Bos, Karel
\o/ more fuel for the car :)

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Lee, Gary D.
Sent: donderdag 18 september 2008 13:51
To: ADSM-L@VM.MARIST.EDU
Subject: Tsm client for as/400

Just was up on the download page.
Has the as/400 client gone the way of the dinosaur?

Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: License problem

2008-09-16 Thread Bos, Karel
Missing the part from version X, Release X, level X.X

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Martins Armando
Sent: dinsdag 16 september 2008 16:50
To: ADSM-L@VM.MARIST.EDU
Subject: License problem

Hello,

After upgrading my tsm server to the version Version 5, Release 4,
Level 4.0.

I have this message on the activity log :
ANR2812W License Audit completed - ATTENTION: Server is NOT in
compliance with license terms

I've try to run the command reg lic file=tsmee.lic but i have this
error:
ANR2852I Current license information:
ANR2032E REGISTER LICENSE: Command failed - internal server error
detected.
ANRD ThreadId 24 issued message 2032 from:
ANRD ThreadId 24  0x089d261c  outTextf+0x3c ANRD ThreadId 24
0x0858de5e  lmRegisterLicense+0x67e ANRD ThreadId 24  0x080bcbd2
AdmCommandLocal+0x732 ANRD ThreadId 24  0x080bc45f
admCommand+0x15cf ANRD ThreadId 24  0x0887b0ab
SmAdminCommandThread+0x4b ANRD ThreadId 24  0x080abd13
StartThread+0xa3 ANRD ThreadId 24  0x00c6a3cc  *UNKNOWN* ANRD
ThreadId 24  0x00bda96e  *UNKNOWN*

Thanks for you help,

--
Martins Armando

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: How does VCB backups handle resource utilization?

2008-09-11 Thread Bos, Karel
Hi,

As for me, producer sessions are the ones collecting the data and
sessions are the ones moving data. So with this table and a resource of
4 I expect to see a maximum number of 3 sessions tranfering data to my
TSM server and one which gets the file list and inspecting the client. 


Regards/Met vriendelijke groet,

Karel


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Schneider, John
Sent: donderdag 11 september 2008 17:50
To: ADSM-L@VM.MARIST.EDU
Subject: Re: How does VCB backups handle resource utilization?

Wanda,
My point exactly.  When I set RESOURCEUTILIZATION 10, I got
between 4 and 8 tape mounts, but I only expected to get 4.  I could
never tell why.  So I lowered it to RESOURCEUTILIZATION 4, and now only
get 2 tape mounts.  But according to the table below, I should only get
1.  So something doesn't work according to the documentation somewhere,
at least in regards to lan-free clients. 
I am the only one who has had this experience?

By the way, just to bury the problem, I increased the maxnummp
from 2 to 8 on all my proxynodes, and now they don't get the error
anymore.  But I don't see why they should need more than 2, when
RESOURCEUTILIZATION is set to 4.  It still doesn't make sense to me.


Best Regards,

John D. Schneider
Phone: 314-364-3150
Cell: 314-750-8721
Email:  [EMAIL PROTECTED] 


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Wanda Prather
Sent: Wednesday, September 10, 2008 6:17 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] How does VCB backups handle resource utilization?

Well, now you've confused me, as well...

When I set RESOURCEUTILIZATION 10, I get 8 sessions, but 4 are producers
and
4 are consumers - so how did you get 8 tape mounts?



On Wed, Sep 10, 2008 at 5:54 PM, Schneider, John
[EMAIL PROTECTED]wrote:

 Ok, now we are getting down to the nitty gritty.  Your example 
 completely contradicts what is in the Performance Guide, which
provides
 a table which I reproduce below.  I hope email doesn't mess up the 
 columns.  It looks correct to me, I assure you.  :-)

 RESOURCEUTILIZATION valueMaximum number   Unique number of
 Threshold
 of sessions  producer sessions
 (seconds)
 1  1   0   45
 2  2   1   45
 3  3   1   45
 4  3   1   30
 5  4   2   30
 6  4   2   20
 7  5   2   20
 8  6   2   20
 9  7   3   20
 10 8   4   10
 0 (default)2   1   30

 A Resourceutil of 4 is a max of three sessions, and only one
producer
 session, i.e. a tape mount.  A Resourceutil of 5 is required for 2
tape
 mounts, and so on.  If my client maxnummp=2, then a resourceutil of 4 
 should not overrun it.

 UNLESS... either the manual is wrong and the algorithm is not what is 
 stated.  Or does the algorithm work differently in a Lan-free client 
 situation?  We have another Lan-free client in a different TSM 
 environment, and we used to have a Resourceutil of 10  for a certain 
 client there, and I would swear there were times when I saw 8 tape 
 mounts.  (The client maxnummp must have been high enough to permit 
 this).  So does Resourceutil really work like the table above, or do 
 Lan-free clients or proxynode clients operate under a different set of

 rules?  Anyone able to enlighten me?

 Best Regards,

 John D. Schneider


 -Original Message-
 From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf
Of
 Bos, Karel
 Sent: Wednesday, September 10, 2008 11:48 AM
 To: ADSM-L@VM.MARIST.EDU mailto:ADSM-L@VM.MARIST.EDU
 Subject: Re: [ADSM-L] How does VCB backups handle resource
utilization?

 It's late and it's long ago, but I seem to remember something about 
 these mount point and resourceutil things in the line of:

 Resource 4, # mountpoint
 - 1 admin session
 - 1 mountpoint for diskpools
 - 2 mountpoint max for tape mounts

 So in you case, going directly to tape, you will get a max of 3 
 mountpoints (because there is no diskpool) to tape.


 Regards/Met vriendelijke groet,

 Karel


 -Original Message-
 From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf
Of
 Schneider, John
 Sent: woensdag 10 september 2008 18:27
 To: ADSM-L@VM.MARIST.EDU mailto:ADSM-L@VM.MARIST.EDU
 Subject: Re: How does VCB backups handle resource utilization?

 Howard,
  But resourceutilization is 4 now.  It should give

Re: Library Master/Client Not In Sync

2008-09-10 Thread Bos, Karel
Hi,

Volume is already checked in on the library manager and has the correct
owner ship? (just to confirm).
What about performing an audit library on the client?
Doing this audit on the library client will sync its status about
volumes in use with the library manager thus freeing this already
deleted volume. If all goes well that is.

Regards,

Karel


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Welton, Charles
Sent: dinsdag 9 september 2008 21:25
To: ADSM-L@VM.MARIST.EDU
Subject: Library Master/Client Not In Sync

Hello:
 
In our environment, we have nine separate TSM instances all running
server version 5.4.3.0 on AIX 5.3.  One of the nine TSM instances acts
as our library master.  Well... this last weekend, we were having issues
with our library master and to resolve the issue, it needed to be
restarted.  At the same time the library master was down, one of the
other TSM instances was doing a MOVE DRMEDIA 101198L4 TOST=COURIERR
W=Y.  So because the library master was down, it never got the message
that the client had deleted 101198L4.  We tried to checkin this tape but
received the following:
 
09/07/08 21:59:41 ANR8443E CHECKIN LIBVOLUME: Volume 101198L4 in
library
   SUN2079 cannot be assigned a status of SCRATCH.
(SESSION:
   58661, PROCESS: 34)
 
According to the library master, this tape is not a scratch volume.  In
a attempt to resolve the issue, we were attempting to perform the
following steps:
 
# 1: checkin libv sun2079 101198L4 status=private checklabel=no-- on
library master
# 2: define volume sun2079-pool1 101198L4 access=readw  --
on client
# 3: then delete the volume from the storagepool
-- on client
 
When we did # 1 on the library master, it automatically assigned
ownership to the client in question.  We then attempted to do # 2... but
received the following:
 
09/08/08 16:50:31 ANR2400E DEFINE VOLUME: Volume 101198L4 is already
defined
   in a storage pool or has been used previously to
store   
   export, database dump, or database backup
information.   
   (SESSION: 319073)
 
At this point... we are stuck.  Has anyone ever ran into a similar
situation and resolved it?  Any suggestions?
 
Thank you...
 
 
Charles Welton
 
This e-mail contains information which (a) may be PROPRIETARY IN NATURE
OR OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only
for the use of the addressee(s) named above. If you are not the
addressee, or the person responsible for delivering this to the
addressee(s), you are notified that reading, copying or distributing
this e-mail is prohibited. If you have received this e-mail in error,
please contact the sender immediately.

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, 

Re: How does VCB backups handle resource utilization?

2008-09-10 Thread Bos, Karel
It's late and it's long ago, but I seem to remember something about
these mount point and resourceutil things in the line of:

Resource 4, # mountpoint
- 1 admin session
- 1 mountpoint for diskpools
- 2 mountpoint max for tape mounts

So in you case, going directly to tape, you will get a max of 3
mountpoints (because there is no diskpool) to tape. 


Regards/Met vriendelijke groet,

Karel


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Schneider, John
Sent: woensdag 10 september 2008 18:27
To: ADSM-L@VM.MARIST.EDU
Subject: Re: How does VCB backups handle resource utilization?

Howard,
But resourceutilization is 4 now.  It should give me fewer mount
points, not more.  So why I am overrunning the client's maximum mount
points of 2 when resourceutilization is 4?
The reason I can't just increase the client's maximum mount
points until the message goes away is that there is a maximum of 64
virtual tape drives, so I can't have every client grabbing 4 virtual
tapes drives at once.  There is also no reason to have all these small
clients mounting multiple tape drives at once, since most of them don't
have much data or take long to back up.
I also just have this concept in my head that TSM is designed
according to logical rules, and works as designed.  So if it is not
behaving the way I think it will, perhaps I don't understand the rules
properly, and I need to fix my understanding.

Best Regards,

John D. Schneider
Phone: 314-364-3150
Cell: 314-750-8721
Email:  [EMAIL PROTECTED] 


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Howard Coles
Sent: Wednesday, September 10, 2008 10:39 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] How does VCB backups handle resource utilization?

Either increase the maximum allowed mountpoints or put a line in the
client DSM.OPT along the lines of resourceutilization 5 (5 works well
with 2 mountpoints allowed)

See Ya'
Howard


 -Original Message-
 From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf 
 Of Schneider, John
 Sent: Wednesday, September 10, 2008 10:35 AM
 To: ADSM-L@VM.MARIST.EDU
 Subject: [ADSM-L] How does VCB backups handle resource utilization?
 
 Greetings,
 We are running TSM 5.4.3.0 server on AIX 5.3ML5.  The Lan-free VCB

 proxy is running TSM client 5.5.0.6.
 We are getting an unexpected result with our VMWare Consolidated 
 Backups.  We are just starting to run these in volume, and we are 
 getting frequent messages:
 
 09/10/08 00:02:06 ANR0539W Transaction failed for session 4448 for
 node
EPCEMI11. This node has exceeded its maximum 
 number of
mount points. (SESSION: 4448)
 
 09/10/08 00:02:06 ANR0539W Transaction failed for session 4449 for
 node
EPCSTL11. This node has exceeded its maximum 
 number of
mount points. (SESSION: 4449)
 
 09/10/08 00:02:07 ANR0539W Transaction failed for session 4439 for
 node
EPCSGF01RO. This node has exceeded its maximum 
 number of
mount points. (SESSION: 4439)
 
 09/10/08 00:02:07 ANR0539W Transaction failed for session  for
 node
EPCSGF01RO. This node has exceeded its maximum 
 number of
mount points. (SESSION: )
 
 
 The destination storage pool is a virtual tape library, which is why 
 mount points are involved.
 
 In the Lan-free proxy server running VCB, the Resourceutilization is 
 set to 4, and the maximum mount points is 8.  On the proxy clients 
 themselves, I understand they inherit the Resourceutilization of the 
 proxy server, so they would be 4 also.  Their maximum mount points is 
 set to 2.  When Resourceutilization is 4, aren't the maximum mount
 points of 2 enough?   According to the Performance Tuning Guide,
 Resourceutilization of 4 should not allow more than one mounted tape.
 
 We aren't getting the error for all clients, just a fraction of them.
 So maybe it is only happening for larger clients where the
 Resourceutilization algorithm to mount another tape kicks in?   We
 could
 always just jack the maximum mount points for the clients up and up 
 until the problem goes away, but I don't understand why the client is 
 trying to mount more than 2 tapes with Resourceutilization set to 4.
 
 
 Best Regards,
 
 John D. Schneider
 Lead Systems Administrator - Storage
 Sisters of Mercy Health Systems
 3637 South Geyer Road
 St. Louis, MO  63127
 Phone: 314-364-3150
 Cell: 314-750-8721
 Email:  [EMAIL PROTECTED]
 
 
 This e-mail contains information which (a) may be PROPRIETARY IN
NATURE
 OR
 OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only 
 for the use of the addressee(s) named above. If you are not the 
 addressee, or the person responsible for delivering this to the 
 addressee(s), you are notified that reading, copying 

Re: How do I clear cache data from disk storage pool?

2008-09-08 Thread Bos, Karel
Upd stg XXX chache=no
For all volumes in this stg pool, move data volume_name wait=yes
Any data still left behind can be moved to the new stg pool or next stg.

Regards,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Davis, Adrian
Sent: maandag 8 september 2008 14:35
To: ADSM-L@VM.MARIST.EDU
Subject: How do I clear cache data from disk storage pool?

I have a disk storage pool that I wish to rename. I have already
redirected new data (originally for this storage pool) to another
storage pool.

After renaming the storage pool I was getting a number of Data storage
transaction ? was aborted. errors when running expire
inventory. Renaming the storage pool back to its original named seems
to have stopped these errors.

All of the data in the storage pool has been migrated.

I am guessing that this is because there are still references to the
cached data. If this is the case, how can I clear references to the data
cached in the storage pool?

Any ideas?

Many Thanks,
   =Adrian=

DISCLAIMER

This message is confidential and intended solely for the use of the
individual or entity it is addressed to. If you have received it in
error, please contact the sender and delete the e-mail. To see the full
version of this disclaimer please visit the following address:
http://www.lewisham.gov.uk/AboutThisSite/EmailDisclaimer.htm

For advice and assistance about online security and protection from
internet threats visit the Get Safe Online website at
http://www.getsafeonline.org


ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to 

Re: How do I clear cache data from disk storage pool?

2008-09-08 Thread Bos, Karel
Nop, cached data will still be there untill overwritten by new data,
expired by retention policy or deleted.

Move data will not move the data in this case. Because of the cache=no
it will only clean up any database refs to this cached data and give
back the space. Delete vol discard=yes will do much the same but I don't
like deleting things :) and think that the move data is a much nicer way
of getting these volumes cleaned.

Regards,

Karel

 

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Davis, Adrian
Sent: maandag 8 september 2008 14:48
To: ADSM-L@VM.MARIST.EDU
Subject: Re: How do I clear cache data from disk storage pool?

Karel,

Thanks for the quick response...

Do I still have to do the move data even if I no longer want the cached
data?

Will upd stg XXX cache=no cause the server to delete references to the
cached data? Do I need to run expire inventory after setting
cache=no?

Many Thanks,
   =Adrian=
 
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Bos, Karel
Sent: 08 September 2008 13:34
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] How do I clear cache data from disk storage pool?

Upd stg XXX chache=no
For all volumes in this stg pool, move data volume_name wait=yes Any
data still left behind can be moved to the new stg pool or next stg.

Regards,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Davis, Adrian
Sent: maandag 8 september 2008 14:35
To: ADSM-L@VM.MARIST.EDU
Subject: How do I clear cache data from disk storage pool?

I have a disk storage pool that I wish to rename. I have already
redirected new data (originally for this storage pool) to another
storage pool.

After renaming the storage pool I was getting a number of Data storage
transaction ? was aborted. errors when running expire
inventory. Renaming the storage pool back to its original named seems
to have stopped these errors.

All of the data in the storage pool has been migrated.

I am guessing that this is because there are still references to the
cached data. If this is the case, how can I clear references to the data
cached in the storage pool?

Any ideas?

Many Thanks,
   =Adrian=

DISCLAIMER

This message is confidential and intended solely for the use of the
individual or entity it is addressed to. If you have received it in
error, please contact the sender and delete the e-mail. To see the full
version of this disclaimer please visit the following address:
http://www.lewisham.gov.uk/AboutThisSite/EmailDisclaimer.htm

For advice and assistance about online security and protection from
internet threats visit the Get Safe Online website at
http://www.getsafeonline.org


DISCLAIMER

This message is confidential and intended solely for the use of the
individual or entity it is addressed to. If you have received it in
error, please contact the sender and delete the e-mail. To see the full
version of this disclaimer please visit the following address:
http://www.lewisham.gov.uk/AboutThisSite/EmailDisclaimer.htm

For advice and assistance about online security and protection from
internet threats visit the Get Safe Online website at
http://www.getsafeonline.org


ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing

Re: audit volume

2008-08-25 Thread Bos, Karel
Audit vol on a copy stg volume will not delete files on the primary stg
volume(s). Damaged files marked as deleted will be copied on the next
backup stg run.

Regards/Met vriendelijke groet,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
David E Ehresman
Sent: maandag 25 augustus 2008 17:22
To: ADSM-L@VM.MARIST.EDU
Subject: audit volume

I've done an audit volume fix=yes on a copy pool volume and damaged
files were deleted.  Will a Backup Stgpool re-copy them, or have they
been deleted from the primary pool also?

David

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: Migrating from old server to new server.

2008-08-14 Thread Bos, Karel
Hi,

Whenever I have to move or add a server to our ITSM landscape, I use the
enterprise config option. Simply add the new server to the config
manager, activate my sync all important stuff policy (admins, scripts,
domains and all things I want available on all my servers), deactivated
this policy (without deleting the just sync stuff) and put the new ITSM
server in my sync stuff enterprise config manager policy. One place to
update admin passwords, generic scripts and more gooddies. 

Regards,

Karel




-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Shawn Drew
Sent: woensdag 13 augustus 2008 17:25
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Migrating from old server to new server.

Take a look at the export commands (and Import if appropriate)

tsm: TSMhelp export
EXPORT Commands

EXPORT Commands

Use the EXPORT commands to copy information from a Tivoli Storage
Manager server to sequential removable media.

The following is a list of EXPORT commands for Tivoli Storage Manager:

 EXPORT ADMIN (Export Administrator Information)
 EXPORT NODE (Export Client Node Information)
 EXPORT POLICY (Export Policy Information)
 EXPORT SERVER (Export Server Information)


Regards,
Shawn

Shawn Drew





Internet
[EMAIL PROTECTED]

Sent by: ADSM-L@VM.MARIST.EDU
08/13/2008 11:15 AM
Please respond to
ADSM-L@VM.MARIST.EDU


To
ADSM-L
cc

Subject
[ADSM-L] Migrating from old server to new server.





Is there anyway to move, copy, or migrate all definitions from old TSM
server to a new TSM server? I want to basically to see if it is possible
to transfer everything over to the new server domains, management
classes, device classes everything.


Dave Hensley


Although this e-mail and any attachments are believed to be free of any
virus or other defect which might affect any computer system, it is the
responsibility of the recipient to check that it is virus-free and the
sender accepts no responsibility or liability for any loss, injury,
damage, cost or expense arising in any way from receipt or use thereof
by the recipient.

The information contained in this electronic mail message is
confidential information and intended only for the use of the individual
or entity named above, and may be privileged.  If the reader of this
message is not the intended recipient, you are hereby notified that any
dissemination, distribution or copying of this communication is strictly
prohibited.  If you have received this transmission in error, please
contact the sender immediately, delete this material from your computer
and destroy all related paper media.  Please note that the documents
transmitted are not intended to be binding until a hard copy has been
manually signed by all parties.
Thank you.


This message and any attachments (the message) is intended solely for
the addressees and is confidential. If you receive this message in
error, please delete it and immediately notify the sender. Any use not
in accord with its purpose, any dissemination or disclosure, either
whole or partial, is prohibited except formal approval. The internet can
not guarantee the integrity of this message. BNP PARIBAS (and its
subsidiaries) shall (will) not therefore be liable for the message if
modified. Please note that certain functions and services for BNP
Paribas may be performed by BNP Paribas RCC, Inc.

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van 

Re: What version of TDP for MS SQL 2005 should use.

2008-08-06 Thread Bos, Karel
64 bits OS on 32 hardware?
Should go for the 16 bit ITSM client.


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Pambos Kyriakides
Sent: woensdag 6 augustus 2008 8:54
To: ADSM-L@VM.MARIST.EDU
Subject: What version of TDP for MS SQL 2005 should use.

I have a 32 bit machine with 64 bit Windows 2003 sever and a MS SQL 2005
64 bit installed.

What version of TSM TDP should I use?







Thanks



Pambos Kyriakides

Storage and Database Administration

Systems Support Group, I.T. Division

Bank of Cyprus Pcl.

Tel. +357-22-128627

Mob. +357-99-592158

Fax. +357-22-337770





**
Please don't print this e-mail unless you really need to.

IMPORTANT: The contents of this email and any attachments are
confidential. They are intended for the named recipient(s) only.
If you have received this email in error, please notify the system
manager or the sender immediately and do not disclose the contents to
anyone or make copies thereof.
*** eSafe scanned this email for viruses, vandals, and malicious
content. ***

**

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: CHECKIN problom

2008-05-22 Thread Bos, Karel
Hi,

- audit library XXX checklabel=barcode
- check act log for errors/warnings/info
- checkin libv

Should be reporting about a missing tape removed from lib invent

Kind regards,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Jeff White
Sent: donderdag 22 mei 2008 13:23
To: ADSM-L@VM.MARIST.EDU
Subject: Re: CHECKIN problom

Thanks Rama

The SHOW SLTS command showed 

Drives   : 4
Slots: 128
Changers : 2
Import/Exports   : 255

And listed 128 element addresses: (i have split these into lines for
ease of reading)

Slot 0   
status Allocated  
element number 1026  
barcode present  
barcode value C10343L3 
devT=LTO 
mediaT=417   
elemT=ANY

then displayed then next 127 until:

Slot 127 
status Full  
element number 1153  
barcode present  
barcode value C10384L3 
devT=LTO 
mediaT=417   
elemT=ANY


So the 128th slot shows a status of full

??

Jeff


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Choudarapu, Ramakrishna (GTS)
Sent: 21 May 2008 14:37
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] CHECKIN problom

Jeff,

May be SHOW SLOTS lib-name would get you more information on your
problem...

Regards, Rama

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Jeff White
Sent: Wednesday, May 21, 2008 9:19 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] CHECKIN problom


Hi

 

TSM Server v5.4.0.0

TS3500 tape library, SCSI attached

LTO3 tapes

 

Hi

 

I have a problem running the CHECKIN command.

 

My TS3500 tape library has approx 700 slots across two frames. A number
of tapes have been returned because at last i have managed to get
approval to expire data more aggressively than previously.

 

So, i load in approx 120 tapes into the entry port and i can see all of
the tapes are loaded into slots in the library. Frame A is full and
Frame B is now being used. From the library display, i can see all of
those tapes in IMPORT status. 

 

From the library web display, my TSM logical library has  a max carts
value of 400 of which 229 are used.

 

When i run 'CHECKIN LIBVOL lib-name SEARCH=YES STATUS=SCRATCH CHECKL=B'
i got 36 tapes loaded and then received the following message:

 

ANR8382W Library CO3500 is now full

 

Subsequent CHECKIN commands simply show the ANR8382W message above. 

 

I know the tapes are in there and the library display shows them. I have
performed a library inventory (from the TS3500) but this has had no
effect.

 

A 'Q LIBR libr F=D' command does'nt show anything that indicated a limit
on the number of tapes it can have in the library.

 

Any thoughts appreciated

 

Jeff White




Woolworths plc
Registered Office: 242 Marylebone Road, London NW1 6JL Registered in
England, Number 104206

This e-mail is only intended for the person(s) to whom it is addressed
and may contain confidential information.  Unless stated to the
contrary, any opinions or comments are personal to the writer and do not
represent the

official view of the company.  If you have received this e-mail in
error, please notify us immediately by reply e-mail and then delete this
message from your system Please do not copy it or use it for any
purposes,  or disclose its contents to any other person.  Thank you for
your co-operation.




Email scanned for viruses and unwanted content by emailsystems

Information regarding this service can be found at www.emailsystems.com


This message w/attachments (message) may be privileged, confidential or
proprietary, and if you are not an intended recipient, please notify the
sender, do not use or share it and delete it. Unless specifically
indicated, this message is not an offer to sell or a solicitation of any
investment products or other financial product or service, an official
confirmation of any transaction, or an official statement of Merrill
Lynch. Subject to applicable law, Merrill Lynch may monitor, review and
retain e-communications (EC) traveling through its networks/systems. The
laws of the country of each sender/recipient may impact the handling of
EC, and EC may be archived, supervised and produced in countries other
than the country in which you are located. This message cannot be
guaranteed to be secure or error-free. This message is subject to terms
available at the following link:
http://www.ml.com/e-communications_terms/. By messaging with Merrill
Lynch you consent to the foregoing.


--
Email 

Re: Damaged Tape During Restore - Theoretical Question

2008-05-15 Thread Bos, Karel
Hi,

If the tape itself is readable, all readable data will be restored and
the damage part will be reported (error log) and skipped. Restore will
take somewhat longer because of the retries on the damaged part of the
tape.


Regards,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Jeff White
Sent: donderdag 15 mei 2008 12:36
To: ADSM-L@VM.MARIST.EDU
Subject: Damaged Tape During Restore - Theoretical Question

Hi

 

TSM Server V 5.4.0.0

TSM Client v5.4.0.2

Both running on Windows 2003

 

I am doing some DR testing and must assume that my onsite tapes are not
available to me and our offsite tapes are the ones we will restore from.

 

During the restore process, i have found that one of the LTO3 tapes is
damaged and cannot be read. In the event of a real DR, I would not be
able to recreate the volume as i don't have the onsite copy of the
tapes. I am restoring a 500gb Windows drive and i have restored about
300gb when i hit the error. 

 

Should the restore 'skip' the data on the damaged tape and continue, or
should it fail the restore? The restore in question has spent 15 hours
trying to read the tape, but is receiving hundreds of I/O error, error
1104 (no more data on tape). If i made the tape 'unavailable', would it
say 'data unavailable to server' and continue or would it fail?

 

I have cancelled the restore for now and will recreate the damaged tape
from the live server and start again when that is complete, but the
management here want to know what would happen in the event of a real
disaster recovery being invoked. Would they lose the remaining 200gb yet
to be restored?

 

Thanks

 

Jeff




Woolworths plc
Registered Office: 242 Marylebone Road, London NW1 6JL Registered in
England, Number 104206

This e-mail is only intended for the person(s) to whom it is addressed
and may contain confidential information.  Unless stated to the
contrary, any opinions or comments are personal to the writer and do not
represent the official view of the company.  If you have received this
e-mail in error, please notify us immediately by reply e-mail and then
delete this message from your system Please do not copy it or use it for
any purposes,  or disclose its contents to any other person.  Thank you
for your co-operation.




Email scanned for viruses and unwanted content by emailsystems

Information regarding this service can be found at www.emailsystems.com
ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its 

Re: Error after installing updated TDPExchange client 5.3.3

2007-10-15 Thread Bos, Karel
Hi,

Passport advantage site is the site for base level software, including
the TDP's. These base level software packages contian the lic files.

Other way is copying the .lic files from a working client.

Regards,

Karel


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Daniel Lane
Sent: maandag 15 oktober 2007 15:50
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Error after installing updated TDPExchange client 5.3.3

Hello Everyone,

I am getting the following error after installing the latest client
version of TDP for Exchange 5.3.3.  The previous client was 5.2.2.  The
file it is looking for is not there.  Does anyone have any ideas on how
to correct this?

ACN0053E License file (E:\Program
Files\Tivoli\TSM\TDPExchange\excclient.lic) could not be opened.
Thank You,
Dan Lane
Systems Administrator
The American Board of Family Medicine, Inc.
[EMAIL PROTECTED]mailto:[EMAIL PROTECTED] - Email This email message
and any attachments are confidential and may be privileged. If you are
not the intended recipient, please notify the American Board of Family
Medicine immediately -- by replying to this message or by sending an
email to [EMAIL PROTECTED]mailto:[EMAIL PROTECTED]. If you are not the
intended recipient, you must immediately destroy all copies of this
message and any attachments without reading or disclosing their
contents. Thank you.
For more information regarding the American Board of Family Medicine,
please visit us at https://www.theabfm.org/.;

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your 

Re: DR restore of a virtual volume

2007-09-27 Thread Bos, Karel
Hi,

Issue command prepare and see in the output file the correct command.
All commands and steps for recovery your ITSM server should be in their.
Works only before the crash... ;-)


Regards,

Karel
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Larry Clark
Sent: donderdag 27 september 2007 14:56
To: ADSM-L@VM.MARIST.EDU
Subject: DR restore of a virtual volume

ServerA backups up the TSM DB to a virtual volume on ServerB.

ServerA is lost and the TSM DB on the virtual volume on ServerB is
required to recreate it.

How is that virtual volume restored?

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: DR restore of a virtual volume

2007-09-27 Thread Bos, Karel
Hi,

In case of the password being out-of-sync you need to do an update
server ServerA forcesync=yes on ServerB. 

Regards,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Nicholas Cassimatis
Sent: donderdag 27 september 2007 15:18
To: ADSM-L@VM.MARIST.EDU
Subject: Fw: DR restore of a virtual volume

ServerA's devconfig file will have an entry for the virtual volume
device class on ServerB.  So it knows where to go to get it.  It's the
same concept as with a physical tape in a physical library, with a
little tweak for the Virtual part.

I've done it twice, but it's been a while.  Once it worked just fine,
the other time the password was out of sync to access ServerB from
ServerA, so we had to reset it (I don't remember the procedure, but it
was in the Admin Guide/Reference).

Nick Cassimatis

- Forwarded by Nicholas Cassimatis/Raleigh/IBM on 09/27/2007 09:14
AM
-

ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 09/27/2007
08:55:42 AM:

 ServerA backups up the TSM DB to a virtual volume on ServerB.

 ServerA is lost and the TSM DB on the virtual volume on ServerB is 
 required to recreate it.

 How is that virtual volume restored?

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: Archives across Wan Best practices

2007-09-25 Thread Bos, Karel
Full bck = archive or backup set?

Or, could you get around your problem by using backup sets.

Regards,
Karel


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Sims
Sent: dinsdag 25 september 2007 15:56
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Archives across Wan Best practices

On Sep 25, 2007, at 9:38 AM, Hayden, Mark wrote:

 Hi All, just wanted to be pointed in the right direction to find 
 information on best practices on Archives across the T1 WAN? We are 
 having trouble finishing monthly archives on weekends running normal 
 Archives. I have tried to talk with upper management about getting rid

 of Archives, but no go. We are running TSM 5.3.4 with older versions 
 of clients up to 5.3.4. Please advise Thanks

Mark -

Exactly what is trying to be achieved?  It kinda sounds like they are
trying to perform what amounts to a full backup over what was a high-
speed link in 1962, based upon old-thinking full+incremental backups.
TSM Incremental may supply what they actually need; otherwise, client
compression would be the best they could probably do with the networking
they have and approach they are trying to use.  We could advise better
if we had more information.

Richard Sims

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: Object counts per node

2007-09-13 Thread Bos, Karel
Hi,

Q occ. Format is not that great.

Node Name  Type Filespace   FSID StorageNumber of  Physical
Logical
Name Pool Name  Files Space
Space
   Occupied
Occupied
   (MB)
(MB)
--  -- - -- - -
-

Regards,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Nick Laflamme
Sent: donderdag 13 september 2007 19:36
To: ADSM-L@VM.MARIST.EDU
Subject: Object counts per node

We haven't done a good job of keeping balanced the number of nodes on
our farm of TSM servers, so we're looking at manually moving some of
them off of a server whose DB is close to full and can't be easily
extended. I can't find, though, any TSM queries that would show me how
many files or other objects a node owns. I can find information about
how large a filespace is and about how much storage space a node's data
takes, but not the number of objects adding up to that much space.

Any SQL queries I try to get me into that direction get me this is a
large query warning, which seem depressingly accurate based on how long
I wait for them before giving up.

TSM 5.3.4.2 on AIX, so we can't use any new commands from TSM 5.4 yet.

The crude way would be to guess that Windows or Mac clients have more
small objects and move those first, but if I can be just a wee bit more
scientific about this, I'd gladly make the effort.

Any suggestions?

Thanks,
Nick

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be 

Re: tsm window cluster services manual or automatic.

2007-09-04 Thread Bos, Karel
Did you add the ITSM service to the cluster manager, so that these
resource will be started on the active cluster node? 
If so, have you set the resource dependency correctly?

Most of this is in the client documentation on the ITSM in a Windows
Cluster Env. Part (or something close to that).

Regards,

Karel


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Gill, Geoffrey L.
Sent: dinsdag 4 september 2007 17:37
To: ADSM-L@VM.MARIST.EDU
Subject: Re: tsm window cluster services manual or automatic.

All nodes housing the failover service should have the service set to
manual. What I have come across in situations like this is the password
has not been set properly on the other nodes which causes the service to
fail when starting. You should look at your logs and see what the
messages are telling you.

 
Geoff Gill
TSM Administrator
PeopleSoft Sr. Systems Administrator
SAIC M/S-G1b
(858)826-4062
Email: [EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Gary Osullivan
Sent: Tuesday, September 04, 2007 8:28 AM
To: ADSM-L@VM.MARIST.EDU
Subject: tsm window cluster services manual or automatic.

hi
 
We have successfully installed tsm client 5.3.3 on a windows cluster
environment + it is going well except for one small scheduling issue.
 
I set the tsm service(s) client acceptor, tsm scheduler
service  startup type=MANUAL for all the cluster nodes.
 
For the purpose of failover I thought this was the way to go.
 
 EXAMPLE: 
 
 Client machine#1 goes down for x reason the resources shift to one of
the other available nodes in the cluster.
 
My schedule will run on the node that currently has the resource
assigned.
 
PROBLEM: 
 
If we are installing window patches + we reboot a node (the tsm schedule
services are not automatically restarted, We end up with missed
schedule.
 
Can we run tsm window cluster backups with all the nodes (physical,
virtual) TSM services running in automatic mode ? (what is the
negative).
 
ps: I'm using schedmode = prompted
 
Gary
 
 
 

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for 

Re: Looking for suggestions to speed up restore for a Windows server

2007-08-27 Thread Bos, Karel
Hi,

With 5.3 ITSM server, look at group by node also. This will reduce the #
of tapes use per node without creating the need for extra stg pools. For
crital systems create their one colloc group for less critical system
create small colloc groups and all the other system can be put into one
colloc group. 

I haven't seen a large restore on a wintel file server system where the
problem wasn't at the backup client most of the restore time. Starting
up the restore could hammer the ITSM server for a time, but after the
restore starts to sent large amounts of data (thus many files), all
restore sessions went into sent-wait.

Regards,

Karel


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Kelly Lipp
Sent: maandag 27 augustus 2007 23:40
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Looking for suggestions to speed up restore for a Windows
server

How about periodic Image backups of the file server volumes?  Couple
that with daily traditional TSM backups and perhaps you have something
that works out better at the DR site.

The problem is as you described it: lots of files to create.  Did you
observe that you were pecking through tapes, or was the bottleneck at
the file create level on the Windows box?  Or could you really tell?

Even if you create another pool for the directory data (which is easy to
implement) you would still have that stuff on many different tapes.
What about a completely new storage pool hierarchy for that one client?
And then aggressively reclaim the DR pool to keep the number of tapes at
a very small number.

I'd really like to know where the bottleneck really was.  If it's file
create time on the client itself, speeding up other things won't help.
If that's the case, then I like the image backup notion periodically.
Even if you did this once/month, the number of files that you would
restore would be fairly small compared to the overall file server.  And
the TSM client does this for you automagically so the restore isn't
hard.

And this also brings up the fact that a restore of this nature in the a
non DR situation probably isn't much better!

Thanks,

Kelly 


Kelly J. Lipp
VP Manufacturing  CTO
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
719-266-8777
[EMAIL PROTECTED]

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Kauffman, Tom
Sent: Monday, August 27, 2007 12:40 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Looking for suggestions to speed up restore for a
Windows server

We had our fall D/R hotsite test last week and all went well -- except
for the recovery of our primary Windows 2003 file sharing system. It
just takes WAY too long.

Part of the problem is the sheer number of files/directories per drive
-- I'm working with the Intel/Windows admin group to try some changes
when we swap this system out in November.

Part of the problem is that the directory structure is scattered over a
mass of other backups. I'm looking for suggestions on this.

The system is co-located by drive, but only for five of the nine logical
drives on the system. I may have to bite the bullet and run all nine
logical drives through co-location.

Is there any way to force the directory structure for a given drive to
the same management class/storage pool as the data? I'm thinking I may
have finally come up with a use for a second domain, with the default
management class being the one that does co-location by drive. If I go
this route -- how do I migrate all of the current data? Export/Import?
How do I clean up the off-site copies? Delete volume/backup storage
pool?

I'm on TSM Server 5.3.2.0, with a 5.3 (not sure of exact level) client.

TIA

Tom Kauffman
NIBCO, Inc
CONFIDENTIALITY NOTICE:  This email and any attachments are for the
exclusive and confidential use of the intended recipient.  If you are
not the intended recipient, please do not read, distribute or take
action in reliance upon this message. If you have received this in
error, please notify us immediately by return email and promptly delete
this message and its attachments from your computer system. We do not
waive attorney-client or work product privilege by the transmission of
this message.

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 

Re: Servermigration and IP-Replacement

2007-08-21 Thread Bos, Karel
Hi,

In windows the ITSM node password is saved in a registry key containing both 
ITSM servername and ITSM nodename. So your ITSM server name should be the same. 
Also setting your clients to polling could help.

Why don't you simple restore your DB this new server?

Regards,

Karel


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Wanda 
Prather
Sent: dinsdag 21 augustus 2007 15:51
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Servermigration and IP-Replacement

The client's IP address is saved as part of the node definition (do a q node 
f=d and you'll see it.), so that isn't a problem.

However, test the move on ONE client before you flop the IP addresses. 
All the client data will move fine with an EXPORT, but it used to be that if 
your server platform changed, the client password wouldn't work anymore.

Never got a real explanation of why, something about the way the password gets 
encrypted.  Don't know if it's still an issue, but I ran into it a couple of 
versions ago going from an AIX to a Windows TSM server.

W


 Hi Folks,
 we're in the process of replacing one of our TSM servers.
 Old machine is TSM 5.2.2.3 on Solaris, New machine is TSM 5.4.0.3 on 
 Win2k3.

 To minimize impact on the clients I thought of this:
 1. ex/import all nodes/schedules/domains... to new server (some with 
 data, some without) 2. swap IP-addresses of the servers 3. disable 
 sessions on old server, enable on new one 4. hope it works...

 Now TSM learns the IP-address of a client at first contact. So the 
 question is, will the new server import the client address and 
 initiate the incremental correctly?
 If I have to manually touch every client, I can also go through a 
 step-by-step migration and adjust the optfile to the new servers' IP.

 Anybody has tried this already?

 Best regards,
 Michael
 --
 Dipl.-Inform. (FH) Michael H. Bartl  Mail: [EMAIL PROTECTED]
 SpaceNet AG, Technik  Tel:  089 / 32356-151
 Joseph-Dollinger-Bogen 14 Fax:  089 / 32356-299
 D-80807 Muenchen   http://www.space.net/

 Vorstand: Sebastian v. Bomhard
 Aufsichtsratsvorsitzender: Alexander Grundner-Culemann
 Firmensitz: München, HRB: 136055 (Amtsgericht München)
 USt-IdNr.: DE813185279


ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free 

Re: Servermigration and IP-Replacement

2007-08-21 Thread Bos, Karel
I missed that part... 


 
-Mensaje original-
De: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] En nombre de
Allen S. Rout
Enviado el: Martes, 21 de Agosto de 2007 13:32
Para: ADSM-L@VM.MARIST.EDU
Asunto: Re: [ADSM-L] Servermigration and IP-Replacement

 On Tue, 21 Aug 2007 16:01:04 +0200, Bos, Karel
[EMAIL PROTECTED] said:


 Why don't you simple restore your DB this new server?

You can't restore DB backups across architectures. :)


- Allen S. Rout

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: How do I restore damaged files on a Copy Storage Pool volume?

2007-08-20 Thread Bos, Karel
Hi,

Upd vol volume name acc=offsite and then move data volume name

Regards,

Karel


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
William Boyer
Sent: maandag 20 augustus 2007 17:28
To: ADSM-L@VM.MARIST.EDU
Subject: Re: How do I restore damaged files on a Copy Storage Pool
volume?

Just do a DEL VOL copypoolvolume DISCARD=YES

And the next time BA STG runs the files that were on that damanged tape
will be re-copied to new copypool media.

Bill Boyer


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Davis, Adrian
Sent: Monday, August 20, 2007 11:15 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: How do I restore damaged files on a Copy Storage Pool
volume?

When I try to mark the volume as destroyed...

update volume lu0141 access=destroyed

...I get the following messages...

ANR2116E UPDATE VOLUME: Access mode for volume LU0141 cannot be changed
to destroyed - volume does not belong to a primary storage pool.
ANR2212I UPDATE VOLUME: No volumes updated.

Regards,
   =Adrian=

Adrian Davis * System Administrator * SunGard Vivista * (Unit 72) 1st
Floor, Romer House, 132 Lewisham High Street, Lewisham, London, SE13
6JG, UK * Tel +44 (0)20 8463 8571 (DDI)  * www.sungard.com/Vivista

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Wilkinson, Brent
Sent: 20 August 2007 16:09
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] How do I restore damaged files on a Copy Storage
Pool volume?

Mark the volume destroyed then run a backup stg. This will replace the
files that no longer exist in the copy pool.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Davis, Adrian
Sent: Monday, August 20, 2007 9:09 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] How do I restore damaged files on a Copy Storage Pool
volume?


How do I restore damaged files on a Copy Storage Pool volume?

restore volume works from Copy to Primary only - How can I do this the
other way?

Many Thanks,
   =Adrian=

Adrian Davis * System Administrator * SunGard Vivista * (Unit 72) 1st
Floor, Romer House, 132 Lewisham High Street, Lewisham, London, SE13
6JG, UK * Tel +44 (0)20 8463 8571 (DDI)  * www.sungard.com/Vivista




DISCLAIMER

This message is confidential and intended solely for the use of the
individual or entity it is addressed to. If you have received it in
error, please contact the sender and delete the e-mail. To see the full
version of this Disclaimer please click here:
http://www.lewisham.gov.uk/AboutThisSite/EmailDisclaimer.htm

For advice and assistance about online security and protection from
internet threats visit the Get Safe Online website at
www.getsafeonline.org


DISCLAIMER

This message is confidential and intended solely for the use of the
individual or entity it is addressed to. If you have received it in
error, please contact the sender and delete the e-mail. To see the full
version of this Disclaimer please click here:
http://www.lewisham.gov.uk/AboutThisSite/EmailDisclaimer.htm

For advice and assistance about online security and protection from
internet threats visit the Get Safe Online website at
www.getsafeonline.org

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze 

Re: TSM Error ANS1009W

2007-07-25 Thread Bos, Karel
Hi,

You can export the updated reg key to a file and import this as part of
your installation process. Should be nice if the ITSM client corrected
the key at installation.

Regards,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
LeBlanc, Patricia
Sent: woensdag 25 juli 2007 15:54
To: ADSM-L@VM.MARIST.EDU
Subject: Re: TSM Error ANS1009W

 Right, I found thisbut my questions wasis there another fix for
this?  I don't want to have to update the registry on every server I
install on.

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Del Hoobler
Sent: Wednesday, July 25, 2007 9:26 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] TSM Error ANS1009W

Pattie,

Search this list server.. and you will see the answer or use the power
of GOOGLE search and you will find the answer:

http://www-1.ibm.com/support/docview.wss?uid=swg21243837

Thanks,

Del



ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 07/25/2007
08:44:29 AM:

  Has anyone experienced this error before?

 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\BackupRestore\File
 sN
 otToBackup\DRM. RC = 13.


 I am now using V5.4.1.0 and am seeing this error each time I install 
 the client.  I have over 1000 servers to upgrade and cannot spend the 
 time updating the registry key each time.  Anyone know a fix?

 Thanks
 pattie

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos 

Re: TSM Server DB Backups

2007-07-18 Thread Bos, Karel
Hi,

You plan your ITSM db backups depending on how much data you want to
loose or time want to spent rerunning ran jobs (...). And things like
re-use delays on storage pools should be also taken into account.

After having to deal with a database restore to a point before the last
reclamation run of our primary storage pools without having reuse delay
set 0, we are a bit more carefull.

Regards,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Timothy Hughes
Sent: woensdag 18 juli 2007 15:14
To: ADSM-L@VM.MARIST.EDU
Subject: Re: TSM Server DB Backups

We actually backup ours after nightly backups complete and before
migration. Is there a specific recommended order or is it up to each
individual site and it's environment?

Helder Garcia wrote:

 You should backup db after migration and before expiration.

 On 7/17/07, Gregory Lynch [EMAIL PROTECTED] wrote:


 Hello all,

 How many times a day should I be backing up the TSM DB and should it 
 be after migration?


 Thanks

 Greg


 ***
 Gregory Lynch
 Lead Programmer Analyst
 IT Infrastructure/Systems Administration Stony Brook University 
 Medical Center HSC Level 3, Room 121  ZIP 8037
 Phone: 631-444-9783
 [EMAIL PROTECTED]

 This e- mail message, including any attachments, is for the sole use 
 of the intended recipient(s) and may contain confidential and 
 privileged information.
 Any unauthorized review, use, disclosure or distribution is
prohibited.
 If you are not the intended recipient, please contact the sender by 
 e-mail and destroy all copies of the original.




 --
 Helder Garcia

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin


Re: TSM and Windows Cluster Environment

2007-07-12 Thread Bos, Karel
Hi,

Yep, we and others have. 

What are the problems you are running into? Installing ITSM clients in a
cluster is described in the ITSM client documentation.

Regards,

Karel 


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Mochnaczewski
Sent: donderdag 12 juli 2007 17:19
To: ADSM-L@VM.MARIST.EDU
Subject: TSM and Windows Cluster Environment

Hi *,

Has anyone successfully implemented TSM in a Windows Cluster environment
? We are running into various problems when trying to configure the TSM
client on certain servers in the cluster and IBM is not being very
helpful.

TSM Server : 5.3.3.0 running on AIX 5.2 ML9


Rich

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: Maximum Capacity for a File Device Class

2007-07-11 Thread Bos, Karel
Hi,

Help upd devcl

 For example, MAXCAPACITY=5G specifies that the maximum capacity for
a
 volume in this device class is 5 gigabytes.The value specified
should
 be less than or equal to the maximum supported size of a file on
the
 target file system. 

Think that the part  be less than or equal to the maximum supported
size of a file on the target file system is helpful.

Regards,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Joni Moyer
Sent: woensdag 11 juli 2007 16:31
To: ADSM-L@VM.MARIST.EDU
Subject: Maximum Capacity for a File Device Class

Hey Everyone,

I recently upgraded to TSM 5.3.4.2 on an AIX server.  Prior to this I
had set the maximum capacity to be 63 GB, but would anyone happen to
know where I can find the maximum setting for a file device class at
this TSM version?  I have found everything but the info. that I actually
wanted in the manuals, so I think I must be looking in the wrong
location.  Any help is appreciated.  Thanks!

Device Class Name: DBBFILE
Device Access Strategy: Sequential
Storage Pool Count: 0
   Device Type: FILE
Format: DRIVE
 Est/Max Capacity (MB): 64,512.0
   Mount Limit: 1
  Mount Wait (min):
 Mount Retention (min):
  Label Prefix:
   Library:
 Directory: /tsmprod/db1backup
   Server Name:
  Retry Period:
Retry Interval:
Shared:
High-level Address:
  Minimum Capacity:
  WORM: No
  Drive Encryption:
   Scaled Capacity:


Joni Moyer
Highmark
Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966
Fax: (717) 302-9826
[EMAIL PROTECTED]


ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers 

Re: Cannot define a path to a drive: help, please?

2007-06-19 Thread Bos, Karel
Hi,

Possibly you have to delete and redefine all your drives, paths and
library in ITSM to pick up the added drive in the library.
Afterall you have changed the library by adding a drive.


Regards,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Joni Moyer
Sent: dinsdag 19 juni 2007 16:12
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Cannot define a path to a drive: help, please?

Hi Chris,

This is an EMC CDL 4400 with dual heads.  I am emulating an IBM 3584 and
nothing has been changed on this system since I defined the library,
drives, paths from a week ago.  I pretty much just went to add 1 more
drive and it's path and I'm getting the error you see below where it
doesn't want to recognize the element number.  At this point I'm not
quite sure what the real issue is with the defining the path, but as you
can see it's not liking the element number.


Joni Moyer
Highmark
Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966
Fax: (717) 302-9826
[EMAIL PROTECTED]




Chris McKay [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
06/19/2007 10:05 AM
Please respond to
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU


To
ADSM-L@VM.MARIST.EDU
cc

Subject
Re: Cannot define a path to a drive: help, please?






Hi Joni,

I did have this exact problem, but with a Windows server. What type of
Library do you have??  Did you update any firmware lately?? We have a
3584 library, and found the firmware was the problem. I had to downgrade
the firmware, let it detect the drive define the drive, then update the
firmware again.

Hopefully this may be of some assistance.

Take Care,

Chris

ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU writes:
Hi Everyone!

I have a TSM server on AIX 5.3 and TSM is 5.3.4.2.  I have defined a
drive: vlto2-68 with define drive cdlb_dev vlto2-68.

   Library Name: CDLB_DEV
  Drive Name: VLTO2-68
 Device Type: UNKNOWN
 On-Line: Yes
Read Formats:
   Write Formats:
 Element:
 Drive State: UNKNOWN
 Volume Name:
Allocated to:
 WWN:
   Serial Number:

I then tried to define a path to the drive and it will not let me:

06/19/07 09:53:26 ANR2017I Administrator LIDZR8V issued command:
DEFINE PATH
   tsmdev vlto2-68 srctype=server desttype=drive 
library=cd
   lb_dev device=/dev/rmt68  (SESSION: 497257)
06/19/07 09:53:26 ANR8972E DEFINE PATH: Unable to find the element
number
   for drive VLTO2-68 in library CDLB_DEV.
(SESSION:

   497257)

I have already defined 40 other drives  their paths successfully, but 
this one is giving me issues.  From the server it does appear as:

  rmt68U0.1-P2-I2/Q1-W2102000D77BD375D-LB   IBM
3580 Ultrium Tape Drive (FCP)

ManufacturerIBM
Machine Type and Model..ULT3580-TD2
Serial Number...1182255815
Device Specific.(FW)53Y2

And since this is a virtual drive I then looked at the CDL and the 
serial numbers do match.

Has anyone ever had this issue?  Does anyone have any suggestions on 
what I might be doing wrong?  Thanks in advance!


Joni Moyer
Highmark
Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966
Fax: (717) 302-9826
[EMAIL PROTECTED]





__
This message is for the sole use of the intended recipients and may
contain confidential and privileged information. Any unauthorized
review,
use, disclosure or distribution is prohibited. If you are not an
intended
recipient, please contact the sender by reply email and destroy all
copies
of the original message. Thank you for your cooperation.

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

Re: Cannot define a path to a drive: help, please?

2007-06-19 Thread Bos, Karel
Hi Joni,
 
You only delete the library within ITSM, you don't delete any volumes
with data  on them. Your volumes are bound to a devices class and that
isn't deleted. So your data should be fine. 
 
- delete path to drives
- delete drives
- delete path to library
- delete library
 
- define library
- define path to library (wait till its ready for operations in the act
log)
- define drives
- define path to drives
 
-checkin libvolumes stat=scratch (private volumes will issue a can't
assing status scratch error;
-checkin libvolumes stat=private
 
This is done many times with our every growing real 3584 library.
 
An other this we have done before is rebooting the ITSM server. This
does many detects (define drives) and will init the ITSM library as
well, but:
- Can take a LONG time to register the hardware change (library frame
extention took more than an our to fail and with above proc it was done
in 10 min.);
- Can fail;
- Needs system down time.
 
Regards,
 
Karel



From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Joni Moyer
Sent: dinsdag 19 juni 2007 17:24
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Cannot define a path to a drive: help, please?



Hi Karel, 

I already have data that is written to media that are defined to
cdlb_dev, so I couldn't possibly delete the library.  I'm a little
confused as to what my options would be at this point.  I would only be
able to delete the drives  paths  re-define, but deleting the library
isn't really an option when data is already written is it?  Just let me
know either way.  Thanks! 


Joni Moyer
Highmark  
Storage Systems, Storage Mngt Analyst III
Phone Number: (717)302-9966 
Fax: (717) 302-9826 
[EMAIL PROTECTED]
 



Bos, Karel [EMAIL PROTECTED] 
Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 

06/19/2007 10:56 AM 
Please respond to
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU


To
ADSM-L@VM.MARIST.EDU 
cc
Subject
Re: Cannot define a path to a drive: help, please?






Hi,

Possibly you have to delete and redefine all your drives, paths and
library in ITSM to pick up the added drive in the library.
Afterall you have changed the library by adding a drive.


Regards,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Joni Moyer
Sent: dinsdag 19 juni 2007 16:12
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Cannot define a path to a drive: help, please?

Hi Chris,

This is an EMC CDL 4400 with dual heads.  I am emulating an IBM 3584 and
nothing has been changed on this system since I defined the library,
drives, paths from a week ago.  I pretty much just went to add 1 more
drive and it's path and I'm getting the error you see below where it
doesn't want to recognize the element number.  At this point I'm not
quite sure what the real issue is with the defining the path, but as you
can see it's not liking the element number.


Joni Moyer
Highmark
Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966
Fax: (717) 302-9826
[EMAIL PROTECTED]




Chris McKay [EMAIL PROTECTED]
Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
06/19/2007 10:05 AM
Please respond to
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU


To
ADSM-L@VM.MARIST.EDU
cc

Subject
Re: Cannot define a path to a drive: help, please?






Hi Joni,

I did have this exact problem, but with a Windows server. What type of
Library do you have??  Did you update any firmware lately?? We have a
3584 library, and found the firmware was the problem. I had to downgrade
the firmware, let it detect the drive define the drive, then update the
firmware again.

Hopefully this may be of some assistance.

Take Care,

Chris

ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU writes:
Hi Everyone!

I have a TSM server on AIX 5.3 and TSM is 5.3.4.2.  I have defined a
drive: vlto2-68 with define drive cdlb_dev vlto2-68.

   Library Name: CDLB_DEV
  Drive Name: VLTO2-68
 Device Type: UNKNOWN
 On-Line: Yes
Read Formats:
   Write Formats:
 Element:
 Drive State: UNKNOWN
 Volume Name:
Allocated to:
 WWN:
   Serial Number:

I then tried to define a path to the drive and it will not let me:

06/19/07 09:53:26 ANR2017I Administrator LIDZR8V issued command:
DEFINE PATH
   tsmdev vlto2-68 srctype=server desttype=drive 
library=cd
   lb_dev device=/dev/rmt68  (SESSION: 497257)
06/19/07 09:53:26 ANR8972E DEFINE PATH: Unable to find the element
number

Re: Define path problems

2007-06-12 Thread Bos, Karel
Hi,

By any change has there been a hardware change?

- delete drive from ITSM config,
- reboot Windows
- define drive serial=autodetect
- define path to drive 


Regards,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Chris McKay
Sent: dinsdag 12 juni 2007 14:25
To: ADSM-L@VM.MARIST.EDU
Subject: Define path problems

Hi All,

I am having problems with replacing a SCSI LTO tape drive in my 3584
library. Usually a routine procedure, but this time I am having major
difficulties. Whenever I try to redefine the path for this particular
drive I get the following error: ANR8972E DEFINE PATH: Unable to find
the element number for drive DRIVE3 in library 3584LIB

I have been talking with both TSM software support, and hardware
support, and still not much luck. The drive is being detected by the
server properly, and the library detects the drive fine as well. We have
tried two different drives as well. I did notice the library specialist
does report a different serial number than the library itself reports
though..
The server is Windows 2000. Has anyone seen this before? Any ideas???

Take Care,

Chris

Chris McKay
Systems Administrator
York Catholic District School Board




__
This message is for the sole use of the intended recipients and may
contain confidential and privileged information. Any unauthorized
review, use, disclosure or distribution is prohibited. If you are not an
intended recipient, please contact the sender by reply email and destroy
all copies of the original message. Thank you for your cooperation.
ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms 

Re: volume owner

2007-06-12 Thread Bos, Karel
Hi,

1) You can change ownership of a scratch volume by using the 'upd libv
owner= stat=' command. See help upd libv
2) Yes, the volumes used by the library client (TSMSun) will be return
to the scratch pool. The scratch pool is managed by the library manager
and both ITSM servers can use tapes from the same scratch pools.
3) TSMSky is the library manager and as such managing the total number
of scratch tapes. If TSMSky is running out of scratch tapes, there are
no scratch tapes available. Not something you would like to see happen.

The q libv command will not work on the library client. 

Regards,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Avy Wong
Sent: dinsdag 12 juni 2007 17:24
To: ADSM-L@VM.MARIST.EDU
Subject: volume owner

Hello,
  I noticed that when I do a query ' q libv' , it shows a list of
volumes with 'Private ' and 'Scratch' status. We have two instances,
TSMSky and TSMSun shared the same library 3584.
My question is ...
1) how do you designate ownership to volumes?
2) does the ownership change back to null, once it has returned to
scratch?
then TSMSky or TSMSun can claim the scratch for their use later?
3) If TSM Sky ran out of scratch volumes, will it move automatically to
TSMSun to use those scratch volumes under ownership of TSMSun?

tsm: TSMSkyq libv

Library Name Volume Name Status Owner  Last Use
  HomeDevice
Element Type
--- -- --
- --- --
SkyLTO CA0001  Scratch
1,282   LTO
SkyLTO   CA0002  Scratch
1,283   LTO
SkyLTO   CA0003  PrivateTSMSkyData
  1,284   LTO
SkyLTO   CA0004  PrivateTSMSun
Data
  1,288   LTO
SkyLTO   CA0005  Scratch
1,291   LTO
SkyLTO   CA0006  PrivateTSMSky  Data
1,292   LTO
SkyLTO   CA0007  PrivateTSMSky
Data
  1,307   LTO
SkyLTO   CA0008  Scratch
1,323   LTO
SkyLTO   CA0009  PrivateTSMSun
Data
  1,325   LTO
SkyLTO   CA0010  PrivateTSMSun
Data
  1,326   LTO
SkyLTO   CA0011  Scratch
1,344   LTO

Thank you.

Avy Wong
Business Continuity Administrator
Mohegan Sun
1 Mohegan Sun Blvd
Uncasville, CT 06382
ext 28164

**
The information contained in this message may be privileged and
confidential and protected from disclosure. If the reader of this
message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, you
are hereby notified that any dissemination, distribution, or copy of
this communication is strictly prohibited. If you have received this
communication in error, please notify us immediately by replying to the
message and deleting it from your computer.

**

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden 

Re: Tape checkin

2007-05-23 Thread Bos, Karel
Hi,

Instead of the 'label libv' you can set the library in ITSM to autolabel
new tapes. 

Regards,

Karel


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Bell, Charles (Chip)
Sent: woensdag 23 mei 2007 16:46
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Tape checkin

Yes, we use the checklabel=barcode option on tapes that TSM has already
initialized in the past. If they are brand new tapes, we use 'label
libvol'.
Pros: 1. Bypassing drives + using waittime=0 = quicker checkin...duh,
you knew that. 2. We did not always have available drives, or one was
taken while a checkin was in progress, which will fail a checkin job.
Not good if there are no watchful operators around. We've had that
happen where an alert operator is absent, and tapes that failed to
checkin the previous day were still in the bulk door, the next operator
removes tapes (after the drm checkout script runs) that he/she believes
need to be going offsite, and sends them off via the courier. Unless
less you like putting your Sherlock hat on and putting your spyglass to
the offsite vendor's downloaded tape inventory, comparing what you think
should be in your library, just use the checkl=b.  :)

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Chris McKay
Sent: Wednesday, May 23, 2007 9:26 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Tape checkin

Hi all,

We were told to use the following command to check-in tapes brought back
from the vault: 'checkin libvol 3584lib search=bulk checklabel=yes
status=scratch waittime=0

I have also checked in tapes using the checklabel=barcode option
(usually only when checking in brand new tapes), which bypasses the
drives. I was thinking this would be a much better option to use all of
the time, as it is much faster and would cause less wear and tear on the
tape drives themselves. Does anyone have any pros and cons of the two
different options, and what would you recommend.

Any info would be appreciated.

Regards,

Chris
-
Confidentiality Notice:
The information contained in this email message is privileged and
confidential information and intended only for the use of the individual
or entity named in the address. If you are not the intended recipient,
you are hereby notified that any dissemination, distribution, or copying
of this information is strictly prohibited. If you received this
information in error, please notify the sender and delete this
information from your computer and retain no copies of any of this
information.

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, 

Re: Tape checkin

2007-05-23 Thread Bos, Karel
Yep.

AutoLabel: Yes 

Regards,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Bell, Charles (Chip)
Sent: woensdag 23 mei 2007 17:19
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Tape checkin

For 3584?

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Bos, Karel
Sent: Wednesday, May 23, 2007 10:03 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Tape checkin

Hi,

Instead of the 'label libv' you can set the library in ITSM to autolabel
new tapes. 

Regards,

Karel


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Bell, Charles (Chip)
Sent: woensdag 23 mei 2007 16:46
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Tape checkin

Yes, we use the checklabel=barcode option on tapes that TSM has already
initialized in the past. If they are brand new tapes, we use 'label
libvol'.
Pros: 1. Bypassing drives + using waittime=0 = quicker checkin...duh,
you knew that. 2. We did not always have available drives, or one was
taken while a checkin was in progress, which will fail a checkin job.
Not good if there are no watchful operators around. We've had that
happen where an alert operator is absent, and tapes that failed to
checkin the previous day were still in the bulk door, the next operator
removes tapes (after the drm checkout script runs) that he/she believes
need to be going offsite, and sends them off via the courier. Unless
less you like putting your Sherlock hat on and putting your spyglass to
the offsite vendor's downloaded tape inventory, comparing what you think
should be in your library, just use the checkl=b.  :)

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Chris McKay
Sent: Wednesday, May 23, 2007 9:26 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Tape checkin

Hi all,

We were told to use the following command to check-in tapes brought back
from the vault: 'checkin libvol 3584lib search=bulk checklabel=yes
status=scratch waittime=0

I have also checked in tapes using the checklabel=barcode option
(usually only when checking in brand new tapes), which bypasses the
drives. I was thinking this would be a much better option to use all of
the time, as it is much faster and would cause less wear and tear on the
tape drives themselves. Does anyone have any pros and cons of the two
different options, and what would you recommend.

Any info would be appreciated.

Regards,

Chris
-
Confidentiality Notice:
The information contained in this email message is privileged and
confidential information and intended only for the use of the individual
or entity named in the address. If you are not the intended recipient,
you are hereby notified that any dissemination, distribution, or copying
of this information is strictly prohibited. If you received this
information in error, please notify the sender and delete this
information from your computer and retain no copies of any of this
information.

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached

Re: Expiring Files that Have Been Exluded

2007-03-28 Thread Bos, Karel
Hi,

If you want to manage data with different retention times for one
back-up client, I would define 2 nodes on the ITSM server, one for each
dsm.sys entry. By doing so, the data backupped under one dsm.sys entry
will not get expired by the exclude of the other entry.

Regards,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Andrew Carlson
Sent: woensdag 28 maart 2007 17:15
To: ADSM-L@VM.MARIST.EDU
Subject: Expiring Files that Have Been Exluded

We have a situation where we have two entries in our dsm.sys.  One of
the entries contains an inclexcl that excludes certain database
filesystems, though the exlclude is using exclude not exclude.fs.  The
other has no inclexcl, so that when the DB person runs their backup
script, the files are backed up.  He is using selelctive backup
statements.  We thought this all was working, until we noticed, because
we needed a restore, that we did not have as many backup versions as we
thought we should.  What we discovered, is that the backup using the
inclexcl list is expiring backups in those directory.filesystems even
though they are excluded.  Is this the way it works?  Would it work the
same way if we used exclude.fs instead?  the manual says that exclude.fs
and exclude.dir are dropped outright, but for exclude, and etc, it only
says the file is not backed up - it does not specify that the file will
be expired.

Thanks for any input you can provide.

P.S.  TSM 5.3.2.3 on AIX 5.2.8 with Sun Solaris client version 5.3.0.

--
Andy Carlson

---
Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License:
$8.95/month, The feeling of seeing the red box with the item you want in
it:Priceless.

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, 

Re: backup TotalStorage

2007-03-21 Thread Bos, Karel
Hi,

Install 2 linux ITSM backup clients (one on each) and one wintel ITSM
backup client, register the nodes on the itsm server and schedule the
back-ups.

Regards,

Karel
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: woensdag 21 maart 2007 11:17
To: ADSM-L@VM.MARIST.EDU
Subject: backup TotalStorage

hello

Is possible to backup IBM TotalStorage DS400 with TSM?
I have 3 volumes defined , 2 linux and 1 windows on this storage How can
i backup them?

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: missed backup

2007-03-20 Thread Bos, Karel
Hi,

Hi,

(dsm)sched.log and dsm(error).log at the client can give some extra
info. Workaround could be to set the schedmode to polling.

Regards,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Gill, Geoffrey L.
Sent: dinsdag 20 maart 2007 16:58
To: ADSM-L@VM.MARIST.EDU
Subject: missed backup

What we have are 2 windows clients, one on 5.3.4.0 and another on
5.3.4.8. Both of these clients consistently show missed, yet you can
restart the scheduler service and it will communicate and pick up the
schedule. The log on the client shows no attempt to start and the TSM
server only has the standard messages when the attempt to contact a
client fails. Gui and command line access from the client work just
fine.

 

I've asked those folks to verify certain things but have not heard back
so I thought while waiting for a response I'd throw this out there.
Besides the standard NIC/switch mismatch, which I have seen cause this,
is there something DNS wise that might cause this and does anyone have
any suggestions for other things to check? 

 

 

Geoff Gill
TSM Administrator
PeopleSoft Sr. Systems Administrator
SAIC M/S-G1b
(858)826-4062
Email: [EMAIL PROTECTED] 

 

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Re: Migrate disk pools to new media

2007-02-27 Thread Bos, Karel
Hi,

I would just setup the new diskpools in your ITSM servers, update the
copy groups to back-up to the new pools, update the old diskpools
pointing your next stg to the new diskpool and start migration. 

Regards,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Keith Arbogast
Sent: dinsdag 27 februari 2007 15:06
To: ADSM-L@VM.MARIST.EDU
Subject: Migrate disk pools to new media

We have two TSM servers on AIX, both at 5.3.4.1.

We have six disk pools on one server containing 2 1/2 TB data, and seven
on the other containing 6 1/2 TB data.

We need to migrate the disk pools to new disk media, and retire the old
media.

The current disk pools are on IBM 4300 SATA. The new disk media is
Hitachi AMS 500 SATA.

What would be the best way to migrate to the new media?

Thank you,
Keith Arbogast
Indiana University

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request

Re: TAPEPOOL made up of mixed LTO2 LTO3 media

2007-02-21 Thread Bos, Karel
Hi,

I assume it's the same with LTO2 drives and a mix of LTO1 and LTO2
tapes. That works for me.

Regards,

Karel

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Bill Dourado
Sent: woensdag 21 februari 2007 12:58
To: ADSM-L@VM.MARIST.EDU
Subject: TAPEPOOL made up of mixed LTO2  LTO3 media
Importance: High

Hi,

We are about to replace our  all  HP LTO-2 tape drives by  LTO-3, in our
NEO 4000 library.

My question is,  seeing the new drives can read and write both LTO-2
and LTO-3 media,   can any given  existing tapepool be made up of
both LTO-2 and LTO-3 media ?

My problem is that I don't have enough tape slots in the library and
don't want to introduce a large number of LTO-3 tapes in one go.

Also a few of our LTO-2 tapes are fairly new and it would be a shame to
write them off.

(TSM  Server for Windows 5.3)

Thanks

Bill



**
This electronic mail message, including any attachments, is a
confidential communication exclusively between Babcock International
Group PLC or its subsidiary company and the intended recipient(s)
indicated as the addressee(s). It contains information which is private
and may be proprietary or covered by legal professional privilege. If
you receive this message in any form and you are not the intended
recipient you must not review, use, disclose or disseminate it.
We would be grateful if you could contact the sender upon receipt and in
any event you should destroy this message without delay.
Anything contained in this message that is not connected with the
business of Babcock International Group PLC is neither endorsed by nor
is the liability of this company.
Babcock International Group PLC
Company number 2342138
Registered in England
2 Cavendish Square
London W1G 0PX
Telephone: +44(0)20 7291 5000
Fax: +44(0)20 7291 5055
Website: www.babcock.co.uk
**

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

Archive based on access/modification time/date

2007-02-12 Thread Bos, Karel
Hi,

I need to do some archive runs based on access and/or modification date on a 
monthly basis. If I look at the Archive client, I can set some filters to get 
the files I need to archive, but on the command line I cannot find these 
options.

Anyone?

Regards,

Karel
ITSM server V5.3.4.X on Win2K and AIX
ITSM Client (anywhere from 3.X to 5.3.4.8 on WinX/AIX/Sun)

-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Christian 
Demnitz
Sent: maandag 12 februari 2007 12:37
To: ADSM-L@VM.MARIST.EDU
Subject: Christian Demnitz ist außer Haus.

Ich werde ab  12.02.2007 nicht im Büro sein. Ich kehre zurück am 13.02.2007.

Ich werde Ihre Nachricht nach meiner Rückkehr beantworten.
ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request

Re: Volume Reclamation warning

2007-02-12 Thread Bos, Karel
Hi,

It means that 44 volumes have more than XX% reclamable space. So, upd
stg YY reclaim=XX or (ITSM5.4) reclaim stg YY th=XX dur=ZZ to kick off
reclamation.

Regards,

Karel


-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
RODOLFICH, NICHOLAS
Sent: maandag 12 februari 2007 16:08
To: ADSM-L@VM.MARIST.EDU
Subject: Volume Reclamation warning

Hello All,
On my operational report I am getting a value of 44 for the
Volume Reclamation Warning line. Does anyone know what this means and/or
how to reduce this number it needs to be?

Thanks

Nicholas 





This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you have received this email in error please notify the
system manager. This message contains confidential information and is
intended only for the individual named. If you are not the named
addressee you should not disseminate, distribute or copy this e-mail.

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request

  1   2   3   4   >