I have a soon to be problem with snapshots coming up. I will be deleting a directory that has 238GB in it and I would really prefer this not to get captured by a snapshot if there is anything I can do about it. I don't want to destroy the exsisting snaps either.
Does anyone know of any way to keep this out of the snap? Any thoughts on how to limit the hit?
Thanks Mike Miller General Dynamics Information Technology Michael.Miller.ctr@ustranscom.mil Michael.Miller@gdit.com Phone: 618-229-1185
you could temporarily increase your snapshot reserve space by 283G.
Short of deleting all your snapshots, not much of a choice.
On 2/7/07, Miller, Michael CTR USTRANSCOM J2 michael.miller.ctr@ustranscom.mil wrote:
I have a soon to be problem with snapshots coming up. I will be deleting a directory that has 238GB in it and I would really prefer this not to get captured by a snapshot if there is anything I can do about it. I don't want to destroy the exsisting snaps either.
Does anyone know of any way to keep this out of the snap? Any thoughts on how to limit the hit?
Thanks Mike Miller General Dynamics Information Technology Michael.Miller.ctr@ustranscom.mil Michael.Miller@gdit.com Phone: 618-229-1185
The problem will only rear its ugly head if you attempt to re-use or otherwise reclaim the 238GB. Rather than increase the snap reserve, which will reduce the amount of 'live' data you have in the volume (probably not what you're looking for), if you're using flexvols, I would temporarily increase the size of the volume by 238GB until those snaps expire and then bring it down again. If you're still using traditional volumes, you're gonna be outta luck.
Also, if the directory was created after the existing snaps, you have nothing to worry about.
If the 238GB of data exists in the existing snaps, they're going to stay there until they are deleted or expire.
Glenn (The other one)
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of tmac Sent: Wednesday, February 07, 2007 2:12 PM To: Miller, Michael CTR USTRANSCOM J2 Cc: toasters@mathworks.com Subject: Re: Snapshot question
you could temporarily increase your snapshot reserve space by 283G.
Short of deleting all your snapshots, not much of a choice.
On 2/7/07, Miller, Michael CTR USTRANSCOM J2 michael.miller.ctr@ustranscom.mil wrote:
I have a soon to be problem with snapshots coming up. I will be deleting a directory that has 238GB in it and I would really prefer this not to get captured by a snapshot if there is anything I
can do
about it. I don't want to destroy the exsisting snaps either.
Does anyone know of any way to keep this out of the snap? Any thoughts
on
how to limit the hit?
Thanks Mike Miller General Dynamics Information Technology Michael.Miller.ctr@ustranscom.mil Michael.Miller@gdit.com Phone: 618-229-1185
I am using flexvols so increasing by that amount is a thought. I'll have to look into that. Unfortunately, I am keeping weeklys for 12 weeks and the data pointers are in the snaps now.
Mike Miller General Dynamics Information Technology Michael.Miller.ctr@ustranscom.mil Michael.Miller@gdit.com Phone: 618-229-1185
-----Original Message----- From: Glenn Dekhayser [mailto:gdekhayser@voyantinc.com] Sent: Wednesday, February 07, 2007 2:28 PM To: tmac; Miller, Michael CTR USTRANSCOM J2 Cc: toasters@mathworks.com Subject: RE: Snapshot question
The problem will only rear its ugly head if you attempt to re-use or otherwise reclaim the 238GB. Rather than increase the snap reserve, which will reduce the amount of 'live' data you have in the volume (probably not what you're looking for), if you're using flexvols, I would temporarily increase the size of the volume by 238GB until those snaps expire and then bring it down again. If you're still using traditional volumes, you're gonna be outta luck.
Also, if the directory was created after the existing snaps, you have nothing to worry about.
If the 238GB of data exists in the existing snaps, they're going to stay there until they are deleted or expire.
Glenn (The other one)
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of tmac Sent: Wednesday, February 07, 2007 2:12 PM To: Miller, Michael CTR USTRANSCOM J2 Cc: toasters@mathworks.com Subject: Re: Snapshot question
you could temporarily increase your snapshot reserve space by 283G.
Short of deleting all your snapshots, not much of a choice.
On 2/7/07, Miller, Michael CTR USTRANSCOM J2 michael.miller.ctr@ustranscom.mil wrote:
I have a soon to be problem with snapshots coming up. I will be deleting a directory that has 238GB in it and I would really prefer this not to get captured by a snapshot if there is anything I
can do
about it. I don't want to destroy the exsisting snaps either.
Does anyone know of any way to keep this out of the snap? Any thoughts
on
how to limit the hit?
Thanks Mike Miller General Dynamics Information Technology Michael.Miller.ctr@ustranscom.mil Michael.Miller@gdit.com Phone: 618-229-1185
we find using snapvaults helps alleviate this problem (we regularly have large purges of logs and other data). we keep 5 or so local snapshots and then 30+ on the R200 vault. snapvault takes nightly or hourly snapshots and pushes the deltas across to the vault.
when we have large purges we can always remove the snaps older than the current one to reduce the impact on the volume but still have that data safely tucked away in the R200 vault.
if this is a once in a blue moon thing its probably easier to increase space temporarily as long as you have it. but for ongoing snapshot utilization in an environment that has hefty delete cycles the vaults seem to work very well.
-- Daniel Leeds Senior Systems Administrator Edmunds.com
-----Original Message----- From: owner-toasters@mathworks.com on behalf of Glenn Dekhayser Sent: Wed 2/7/2007 12:28 PM To: tmac; Miller, Michael CTR USTRANSCOM J2 Cc: toasters@mathworks.com Subject: RE: Snapshot question
The problem will only rear its ugly head if you attempt to re-use or otherwise reclaim the 238GB. Rather than increase the snap reserve, which will reduce the amount of 'live' data you have in the volume (probably not what you're looking for), if you're using flexvols, I would temporarily increase the size of the volume by 238GB until those snaps expire and then bring it down again. If you're still using traditional volumes, you're gonna be outta luck.
Also, if the directory was created after the existing snaps, you have nothing to worry about.
If the 238GB of data exists in the existing snaps, they're going to stay there until they are deleted or expire.
Glenn (The other one)
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of tmac Sent: Wednesday, February 07, 2007 2:12 PM To: Miller, Michael CTR USTRANSCOM J2 Cc: toasters@mathworks.com Subject: Re: Snapshot question
you could temporarily increase your snapshot reserve space by 283G.
Short of deleting all your snapshots, not much of a choice.
On 2/7/07, Miller, Michael CTR USTRANSCOM J2 michael.miller.ctr@ustranscom.mil wrote:
I have a soon to be problem with snapshots coming up. I will be deleting a directory that has 238GB in it and I would really prefer this not to get captured by a snapshot if there is anything I
can do
about it. I don't want to destroy the exsisting snaps either.
Does anyone know of any way to keep this out of the snap? Any thoughts
on
how to limit the hit?
Thanks Mike Miller General Dynamics Information Technology Michael.Miller.ctr@ustranscom.mil Michael.Miller@gdit.com Phone: 618-229-1185
it is too bad there is not a rm - no_snapshot option.
The problem will only rear its ugly head if you attempt to re-use or otherwise reclaim the 238GB. Rather than increase the snap reserve, which will reduce the amount of 'live' data you have in the volume (probably not what you're looking for), if you're using flexvols, I would temporarily increase the size of the volume by 238GB until those snaps expire and then bring it down again. If you're still using traditional volumes, you're gonna be outta luck.
Also, if the directory was created after the existing snaps, you have nothing to worry about.
If the 238GB of data exists in the existing snaps, they're going to stay there until they are deleted or expire.
Glenn (The other one)
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of tmac Sent: Wednesday, February 07, 2007 2:12 PM To: Miller, Michael CTR USTRANSCOM J2 Cc: toasters@mathworks.com Subject: Re: Snapshot question
you could temporarily increase your snapshot reserve space by 283G.
Short of deleting all your snapshots, not much of a choice.
On 2/7/07, Miller, Michael CTR USTRANSCOM J2 michael.miller.ctr@ustranscom.mil wrote:
I have a soon to be problem with snapshots coming up. I will be deleting a directory that has 238GB in it and I would really prefer this not to get captured by a snapshot if there is anything I
can do
about it. I don't want to destroy the exsisting snaps either.
Does anyone know of any way to keep this out of the snap? Any thoughts
on
how to limit the hit?
Thanks Mike Miller General Dynamics Information Technology Michael.Miller.ctr@ustranscom.mil Michael.Miller@gdit.com Phone: 618-229-1185
-- --tmac
RedHat Certified Engineer #804006984323821
Principal Consultant, RABA Technologies 240-373-3926 (office) 301-688-4705 (Lab) 214-279-3926 (eFAX)
-
David Knight -
Glenn Dekhayser -
Leeds, Daniel -
Miller, Michael CTR USTRANSCOM J2 -
tmac