Expanding file spaces

[Bluidgr75]

I have little knowledge of ADSM but need to get it running backups again. I have collaborated with someone with knowledge and he says we need to expand our file spaces. I have looked through the options and it appears that the only way to expand it is to delete the current one and create a larger one in its place. Can anyone give me some points on what to do? I would really appreciate it!

 

[gubara]

Hello,



it appreas to me that you are not familiar with TSM terminology and concepts. Using your description I can hardly offer any advice. Could you post more details about the system, setup, TSM configuration (the result of commands: Q STG, Q DRIVE, Q LIBR, Q DEVCL). What error messages do you get?



Or maybe it would be easier for you to invite a TSM consultant to do the job for you instead of trying to understand TSM administration?

 

[Christoh]

Hi,



I must agree with gubara - the info you are offering here does not help much - and the person with knowledge you are referring to does not sound like he/she has much knowledge of the product either(unless you misunderstood what they were trying to say).



You don't expand your filespaces - A filespace in TSM terms is a client file system or drive. You can throw away/delete filespaces for clients to make more space in a stg pool or tape library - if that is your problem.



Do some of the commands mentioned so we can get an idea of your setup - and also maybe some kind of error message when you're doing something in particular.



Regards

Christo

 

[Bluidgr75]

This is an older version of the software (ADSM server Version 3, Release 1, Level 2.50) so I have been told that this is out of date and unsupported. I am all for calling in an engineer but have been unable to locate one that might be able to get this running again. Basically, we have this backing up one client. The backup starts to queue and stops after it transfers about 6 MB. I have been working with someone at another division of our company who has said that we are running out of file space and can see that from an error code in dsmerror.log. The tape drive is an exabyte 220 and we have more than enough scratch volumes. Every tape in the library except for 2 are scratch volumes. I am sorry that I am not familiar with terminology, this has been dumped in my lap and I am only trying to get this working so we can limp along until we migrate to a new Notes system.



Any further help is appreciated!

 

[ItsAGoodOne]

Bluidgr75,



That was a good try aswell, but really there is still nothing for us to go on. It could be a couple of things:



1> backup goes to a diskpool (follow the management class and copygroup parameters to find out which one) which is only 6 MB and there is no nextpool defined



2> nextpool is defined but maxscratch is set to 1 or none



but the chances are that it's none of those above.

You need to show us the lines in the dsmerror.log and the dsmsched.log (if the output doesn't go to your screen) and perhaps an extract from the activity log from the same time you tried to run the backup.



If you can show us these we may be able to help a little more

 

[Christoh]

Hi Bluidgr75,



Did you get my private note?

If you are really worried about this problem you should really try and give feedback as to the progress you are making.



Cheers

Christo

 

[Christoh]

Hi Bluidgr75,



Did you get my private note?

If you are really worried about this problem you should really try and give feedback as to the progress you are making.



Cheers

Christo

 

[hanneng]

It's will be useful for us to help you, if you post the result as mentioned by gubara.

I'm using Version 3, Release 1, Level 2.30 in my organization too.



Usually, dsmerror.log would tell you some glue.



regards