DongDong,
I see two possible reasons:
1. Your retention policy expires the version before the maximum count
"versions data exists" is reached. If the retain-extra value is set to
a low number (like 4 days) and you change the file every 3 days, this
behaviour would be as expected.
2. You forgot t
Hi all;
I have some question with backup versions, please help me~!
I setup the "copygroup" "Versions Data Exists: 3", and I use
"dsmc I " backup all the file more than 3 times , but when I use "dsmc
restore /home/1.txt -pick -ina" query how much of a file versions, I see
that
Its been a few years since I looked at a Celerra, but there should be
a command to list the devices from the Celerra's point of view. (If
nothing else, maybe a system log file?)
Once you can get this output, you should be able to figure out which
is which by comaparing the tape driver serial numb
On Apr 22, 2008, at 1:29 PM, David E Ehresman wrote:
Set Version Exists and Versions Deleted to no limit. Set Retain
versions and Retain only to 1. Delete the file from disk after 60
days. The backup will go away a day later.
If an Incremental backup on a directory, yes; but we have no
inf
Set Version Exists and Versions Deleted to no limit. Set Retain versions and
Retain only to 1. Delete the file from disk after 60 days. The backup will go
away a day later.
>>> "Whitlock, Brett" <[EMAIL PROTECTED]> 4/22/2008 11:50 AM >>>
I have a SQL user who creates a nightly backup with an
"It depends".
If you put RESOURCEUTILIZATION 10 in your dsm.opt file, it will force TSM to
start more concurrent sessions.
But if you want to control which drives restore concurrently, open more
sessions and start them one at a time.
On Tue, Apr 22, 2008 at 12:07 PM, Gill, Geoffrey L. <
[EMAIL P
You should be able to set the Retain Extra Versions to 60, Version Data
Exists and the Versions Data Deleted to nolimit and the server will,
defacto, allow TSM to keep versions based on their age. This is what you
would do to enable point-in-time restores as well. Of course, this will
mean more sto
Brett,
There are no automatic way from TSM server side to do this. However you
can use the following method to manually delete the backup files every
60 days.
1) Rename the filespace to fsname_mmddyy where _mmddyy is expiry date of
files after 60 days.
2) After 60 days delete the earlier renamed
> IMHO one of the things you need to consider is how long the migration
> processes will take.
I have done that and use collocation groups already so I understand the
ramifications of this, but those are not my questions. My questions are
more specific to restores and was wondering if a single se
I have a SQL user who creates a nightly backup with an older version of
litespeed. They only want to retain 60 days. The problem is each
nightly backup has a unique date/time stamp. Therefore TSM sees every
file as an active version. Since each version is active I am just
keeping everything. T
I use co-location by filespace only for my fileservers. That's one tape
for SYSTEM STATE, another one for SYSTEM SERVICES, another one for
SYSTEM OBJECT and then one for each drive. The only advantage is that
during a restore you can open multiple sessions (manually) ie one
session for the e: dri
If you don't already have domains on server 2 with the same names as the
ones on server 1, you'll want to EXPORT POLICY to server 2 first, and make
sure that the copy groups have valid storage pools for their destinations.
Then, when you EXPORT NODE, they'll be imported into the same policy
domains
Bjørn Nachtwey wrote:
> dear all,
>
> what happens if I move a node to another domain? Especially how does it
> work?
If you bind a node to a new policydomain, all existing data will be
retained according to the settings that apply to that data via the
management class in the new domain that appl
dear all,
what happens if I move a node to another domain? Especially how does it
work?
After testing It seems, the data backuped already stay in the old domain
an vanishes as it expires and the new data will be stored in the new
domain?
And if some data will be restored they will be read in bot
dear all,
a couple of days I asked about buta, but the question behind is quite
more simple:
if I have a node with a daily backup amount larger than one tape (e.g.
400GB daily using LTO-2), how can I do a parallel migration from staging
pool to multiple tapes?
I think if the node is collocated I
15 matches
Mail list logo
