I have tried to use the switch -nosort but the resulting list is not
ordered in groups of volumes for same file servers while the backup dump
is indeed done server by server.
Anyhow I do agree that the best solution is to define different volsets
as suggested by Stephen and we will explore
On 4/9/2016 8:41 AM, Giovanni Bracco wrote:
> But vos listvldb provides a list of volumes alphabetically sorted by vol
> name!
> Even if it makes use of the same routine the output provided forgets
> that, I think
>
> Giovanni
Giovanni,
It is true that the output of "vos listvldb" is sorted as
But vos listvldb provides a list of volumes alphabetically sorted by vol
name!
Even if it makes use of the same routine the output provided forgets
that, I think
Giovanni
On 08/04/16 22:32, Benjamin Kaduk wrote:
On Fri, 8 Apr 2016, Giovanni Bracco wrote:
In our AFS cell we have 9
On Fri, 8 Apr 2016, Giovanni Bracco wrote:
In our AFS cell we have 9 fileservers (openafs 1.6.5 to 1.6.15) distributed
over WAN and we use the native openafs backup system, which works well (max
size of a volume is 200 GB)
We have defined a volset for all the .backup volumes of all
On Fri, 8 Apr 2016, Giovanni Bracco wrote:
> In our AFS cell we have 9 fileservers (openafs 1.6.5 to 1.6.15) distributed
> over WAN and we use the native openafs backup system, which works well (max
> size of a volume is 200 GB)
>
> We have defined a volset for all the .backup volumes of all
In our AFS cell we have 9 fileservers (openafs 1.6.5 to 1.6.15)
distributed over WAN and we use the native openafs backup system, which
works well (max size of a volume is 200 GB)
We have defined a volset for all the .backup volumes of all fileservers
and we have one AFS backup server that
