SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
File Archiver best practices
Author Message
Post File Archiver best practices 
Our company is new to using commvault's file archiver, and for our first foray into it, we aren't technically going to use it as an archive. It's going to be a HSM solution.

We have an application called Vista Plus. Instead of reports going from our mainframe to a printer, it goes to this application so they can be viewed and annotated electronically.

Like a backup, when these reports reach a certain age, they get sent to an archive filesystem by this application.

I want to use commvault to get everything in this archive filesystem and keep it on tape that will remain in the tape library.

So far, in our tests, it seems to be okay after a few bumpy weeks.

The rules are set up so that every file meets the archive criteria.

My question is how this environment is maintained. I have an on-site tape and an aux copy to keep offsite. What is the deal with creating new indexes? How does that impact me? How about the off-site tape rotation? Will new archive jobs that run to keep all of the data on tape keep adding onto existing tapes? Or will it replace the data on tape? Basically, how do you keep it from taking a 300 GB filesystem and having it take up 3 TB on tape after a year or so?


__._,_.___
Reply to sender ([email]bill.willis < at > swgas.com?subject=File Archiver best practices[/email]) | Reply to group ([email]commvault < at > yahoogroups.com?subject=File Archiver best practices[/email]) | Reply via web post | Start a New Topic
Messages in this topic (1)
Recent Activity: Visit Your Group

Commvault Documentation here:
http://documentation.commvault.com/
Text-Only ([email]commvault-traditional < at > yahoogroups.com?subject=Change Delivery Format: Traditional[/email]), Daily Digest ([email]commvault-digest < at > yahoogroups.com?subject=Email Delivery: Digest[/email]) &bull; Unsubscribe ([email]commvault-unsubscribe < at > yahoogroups.com?subject=Unsubscribe[/email]) &bull; Terms of Use




.

[img]http://geo.yahoo.com/serv?s=97359714/grpId=7450851/grpspId=1707277520/msgId=3460/stime=1267553007/nc1=4507179/nc2=4025304/nc3=5191953[/img]
__,_._,___

Post File Archiver best practices 
auxiliary / secondary copies are not backup jobs in their own right. When you perform an aux copy, you only copy (to the secondary) data that hasn't been copied to the secondary yet. By defining a secondary copy, you are saying "I want whatever is in my primary copy to be in my secondary" (for synchronous secondaries).
 
So, if you have 300GB in your archive and you are archiving everything, then 300GB will appear in your Primary copy, 300GB in your secondary and your main archive filesystem will be filled with stubs.
 
Does this answer your question?
 
Mark Edwards.


On Wed, Mar 3, 2010 at 04:55, genxcubca <bill.willis < at > swgas.com ([email]bill.willis < at > swgas.com[/email])> wrote:
 
Our company is new to using commvault's file archiver, and for our first foray into it, we aren't technically going to use it as an archive. It's going to be a HSM solution.

We have an application called Vista Plus. Instead of reports going from our mainframe to a printer, it goes to this application so they can be viewed and annotated electronically.

Like a backup, when these reports reach a certain age, they get sent to an archive filesystem by this application.

I want to use commvault to get everything in this archive filesystem and keep it on tape that will remain in the tape library.

So far, in our tests, it seems to be okay after a few bumpy weeks.

The rules are set up so that every file meets the archive criteria.

My question is how this environment is maintained. I have an on-site tape and an aux copy to keep offsite. What is the deal with creating new indexes? How does that impact me? How about the off-site tape rotation? Will new archive jobs that run to keep all of the data on tape keep adding onto existing tapes? Or will it replace the data on tape? Basically, how do you keep it from taking a 300 GB filesystem and having it take up 3 TB on tape after a year or so?









--
regards,

Mark P. Edwards

__._,_.___
Reply to sender ([email]mark.p.edwards < at > gmail.com?subject=Re: [commvault] File Archiver best practices[/email]) | Reply to group ([email]commvault < at > yahoogroups.com?subject=Re: [commvault] File Archiver best practices[/email]) | Reply via web post | Start a New Topic
Messages in this topic (2)
Recent Activity: Visit Your Group

Commvault Documentation here:
http://documentation.commvault.com/
Text-Only ([email]commvault-traditional < at > yahoogroups.com?subject=Change Delivery Format: Traditional[/email]), Daily Digest ([email]commvault-digest < at > yahoogroups.com?subject=Email Delivery: Digest[/email]) &bull; Unsubscribe ([email]commvault-unsubscribe < at > yahoogroups.com?subject=Unsubscribe[/email]) &bull; Terms of Use




.

[img]http://geo.yahoo.com/serv?s=97359714/grpId=7450851/grpspId=1707277520/msgId=3465/stime=1267597311/nc1=4507179/nc2=4025321/nc3=5741395[/img]
__,_._,___

Post File Archiver best practices 
Well, I was hoping to avoid going into this other application since I don't want to bog down the discussion by putting in details that most people probably don't care about. However, the way it works is what is kind of bugging me and I'm trying to wrap my head around how the Archiver will handle it.

Okay, so that application takes reports in Filesystem 1, and compresses them (makes a .Z file) and moves them into filesystem 2. I then archive filesystem 2.

Users in the application who need to access these archived reports make a request to the application (Vista Plus).
Vista plus requests the data from the CV tape,
then it moves the .Z file from filesystem 2 to filesystem 1
then decompresses and tar -xvf back to its original location before it was archived.

So now we have Data back in its original location which is NOT the location that I archive with CV.

Now when the next sunday rolls around, this report will be seen to be old and get re-archived to Filesystem 2, and then CV will run and re-archive.

When this data was retrieved from the tape, it doesn't remove it from the tape. It's just copied from the tape and the stub gets replaced. then the app re-archives back to filesystem 2 after a couple of days.

So then the next round of CV archive jobs presumably archives this file again, now there are 2 copies of this on the primary tape copy.

I think this was what I was worried about with the tapes filling up not only with more archive files, but eventually many copies of the SAME files.

Does this make sense?

Mark Edwards <mark.p.edwards < at > gmail.com> 3/2/2010 8:55 PM >>>

auxiliary / secondary copies are not backup jobs in their own right. When you perform an aux copy, you only copy (to the secondary) data that hasn't been copied to the secondary yet. By defining a secondary copy, you are saying "I want whatever is in my primary copy to be in my secondary" (for synchronous secondaries).

So, if you have 300GB in your archive and you are archiving everything, then 300GB will appear in your Primary copy, 300GB in your secondary and your main archive filesystem will be filled with stubs.

Does this answer your question?

Mark Edwards.


On Wed, Mar 3, 2010 at 04:55, genxcubca <bill.willis < at > swgas.com ([email]bill.willis < at > swgas.com[/email])> wrote:

Our company is new to using commvault's file archiver, and for our first foray into it, we aren't technically going to use it as an archive. It's going to be a HSM solution.

We have an application called Vista Plus. Instead of reports going from our mainframe to a printer, it goes to this application so they can be viewed and annotated electronically

Like a backup, when these reports reach a certain age, they get sent to an archive filesystem by this application.

I want to use commvault to get everything in this archive filesystem and keep it on tape that will remain in the tape library.

So far, in our tests, it seems to be okay after a few bumpy weeks.

The rules are set up so that every file meets the archive criteria.

My question is how this environment is maintained. I have an on-site tape and an aux copy to keep offsite. What is the deal with creating new indexes? How does that impact me? How about the off-site tape rotation? Will new archive jobs that run to keep all of the data on tape keep adding onto existing tapes? Or will it replace the data on tape? Basically, how do you keep it from taking a 300 GB filesystem and having it take up 3 TB on tape after a year or so?









--
regards,

Mark P. Edwards

Post File Archiver best practices 
Bill:
There are two things we noticed:
<![if !supportLists]>1) <![endif]>There is a re-stubbing feature that you can enable to re-stub (without backing up again if the file is not modified since last migration) it in the next migration job. This can be enabled via key nUSE_STUB_CACHE under data migrator section. Please see the following link:
http://documentation.commvault.com/commvault/release_8_0_0/books_online_1/english_us/features/registry_keys/registry_keys.htm
<![if !supportLists]>2) <![endif]>Instead of archiving the files quite frequently (in couple of days), you could increase your access time in the migration rules of the sub-client. This will avoid recalling the file from the tape frequently.
Kumar
From: commvault < at > yahoogroups.com [mailto:commvault < at > yahoogroups.com] On Behalf Of Bill Willis
Sent: Wednesday, March 03, 2010 2:42 AM
To: commvault < at > yahoogroups.com
Subject: Re: [commvault] File Archiver best practices



Well, I was hoping to avoid going into this other application since I don't want to bog down the discussion by putting in details that most people probably don't care about. However, the way it works is what is kind of bugging me and I'm trying to wrap my head around how the Archiver will handle it.



Okay, so that application takes reports in Filesystem 1, and compresses them (makes a .Z file) and moves them into filesystem 2. I then archive filesystem 2.



Users in the application who need to access these archived reports make a request to the application (Vista Plus).

Vista plus requests the data from the CV tape,

then it moves the .Z file from filesystem 2 to filesystem 1
then decompresses and tar -xvf back to its original location before it was archived.



So now we have Data back in its original location which is NOT the location that I archive with CV.



Now when the next sunday rolls around, this report will be seen to be old and get re-archived to Filesystem 2, and then CV will run and re-archive.



When this data was retrieved from the tape, it doesn't remove it from the tape. It's just copied from the tape and the stub gets replaced. then the app re-archives back to filesystem 2 after a couple of days.



So then the next round of CV archive jobs presumably archives this file again, now there are 2 copies of this on the primary tape copy.



I think this was what I was worried about with the tapes filling up not only with more archive files, but eventually many copies of the SAME files.



Does this make sense?

Mark Edwards <mark.p.edwards < at > gmail.com> 3/2/2010 8:55 PM >>>

auxiliary / secondary copies are not backup jobs in their own right. When you perform an aux copy, you only copy (to the secondary) data that hasn't been copied to the secondary yet. By defining a secondary copy, you are saying "I want whatever is in my primary copy to be in my secondary" (for synchronous secondaries).



So, if you have 300GB in your archive and you are archiving everything, then 300GB will appear in your Primary copy, 300GB in your secondary and your main archive filesystem will be filled with stubs.



Does this answer your question?



Mark Edwards.

On Wed, Mar 3, 2010 at 04:55, genxcubca <bill.willis < at > swgas.com ([email]bill.willis < at > swgas.com[/email])> wrote:

Our company is new to using commvault's file archiver, and for our first foray into it, we aren't technically going to use it as an archive. It's going to be a HSM solution.

We have an application called Vista Plus. Instead of reports going from our mainframe to a printer, it goes to this application so they can be viewed and annotated electronically

Like a backup, when these reports reach a certain age, they get sent to an archive filesystem by this application.

I want to use commvault to get everything in this archive filesystem and keep it on tape that will remain in the tape library.

So far, in our tests, it seems to be okay after a few bumpy weeks.

The rules are set up so that every file meets the archive criteria.

My question is how this environment is maintained. I have an on-site tape and an aux copy to keep offsite. What is the deal with creating new indexes? How does that impact me? How about the off-site tape rotation? Will new archive jobs that run to keep all of the data on tape keep adding onto existing tapes? Or will it replace the data on tape? Basically, how do you keep it from taking a 300 GB filesystem and having it take up 3 TB on tape after a year or so?







--
regards,

Mark P. Edwards















******************Legal Disclaimer***************************
"This communication may contain confidential and privileged material
for the sole use of the intended recipient. Any unauthorized review,
use or distribution by others is strictly prohibited. If you have
received the message in error, please advise the sender by reply
email and delete the message. Thank you."
****************************************************************

__._,_.___
Reply to sender ([email]prvs=0678328017=param < at > commvault.com?subject=RE: [commvault] File Archiver best practices[/email]) | Reply to group ([email]commvault < at > yahoogroups.com?subject=RE: [commvault] File Archiver best practices[/email]) | Reply via web post | Start a New Topic
Messages in this topic (4)
Recent Activity: Visit Your Group

Commvault Documentation here:
http://documentation.commvault.com/
MARKETPLACE

[url=http://us.ard.yahoo.com/SIG=14kjhg846/M=493064.13983314.13948445.13298430/D=groups/S=1707277520:MKP1/Y=YAHOO/EXP=1267677685/L=/B=UMnBJkSO5_k-/J=1267670485108726/K=LSyh3QW5qDWMz32nWdFU_A/A=6015306/R=0/SIG=11vlkvigg/*http://advision.webevents.yahoo.com/hobbiesandactivitieszone/]Hobbies & Activities Zone: Find others who share your passions! Explore new interests.[/url]


Text-Only ([email]commvault-traditional < at > yahoogroups.com?subject=Change Delivery Format: Traditional[/email]), Daily Digest ([email]commvault-digest < at > yahoogroups.com?subject=Email Delivery: Digest[/email]) &bull; Unsubscribe ([email]commvault-unsubscribe < at > yahoogroups.com?subject=Unsubscribe[/email]) &bull; Terms of Use




.

[img]http://geo.yahoo.com/serv?s=97359714/grpId=7450851/grpspId=1707277520/msgId=3473/stime=1267670484/nc1=4507179/nc2=4025338/nc3=4836037[/img]
__,_._,___

Post File Archiver best practices 
Why don't you just archive filesystem 1 - this 'application' seems to be duplicating functionality somewhat?
You can get Commvault to simply archive filesystem 1 on a weekly basis. Compression can be done by the client to place the file in the archive.


I'm interested in how "vista plus" requests the archive file from Commvault. normally when a stub file is 'opened' the HSM filesystem driver will do the 'requesting'. Does Vista-Plus have a script or commandline interface to Commvault? 
 
m

On Wed, Mar 3, 2010 at 18:42, Bill Willis <bill.willis < at > swgas.com ([email]bill.willis < at > swgas.com[/email])> wrote:
Well, I was hoping to avoid going into this other application since I don't want to bog down the discussion by putting in details that most people probably don't care about.   However, the way it works is what is kind of bugging me and I'm trying to wrap my head around how the Archiver will handle it.
 
Okay, so that application takes reports in Filesystem 1, and compresses them (makes a .Z file) and moves them into filesystem 2.   I then archive filesystem 2.
 
Users in the application who need to access these archived reports make a request to the application (Vista Plus).
Vista plus requests the data from the CV tape,
then it moves the .Z file from filesystem 2 to filesystem 1
then decompresses and tar -xvf back to its original location before it was archived.
 
So now we have Data back in its original location which is NOT the location that I archive with CV.
 
Now when the next sunday rolls around, this report will be seen to be old and get re-archived to Filesystem 2, and then CV will run and re-archive.
 
When this data was retrieved from the tape, it doesn't remove it from the tape.  It's just copied from the tape and the stub gets replaced.   then the app re-archives back to filesystem 2 after a couple of days.
 
So then the next round of CV archive jobs presumably archives this file again, now there are 2 copies of this on the primary tape copy.
 
I think this was what I was worried about with the tapes filling up not only with more archive files, but eventually many copies of the SAME files.
 
Does this make sense?

Mark Edwards <mark.p.edwards < at > gmail.com ([email]mark.p.edwards < at > gmail.com[/email])> 3/2/2010 8:55 PM >>>
 
auxiliary / secondary copies are not backup jobs in their own right. When you perform an aux copy, you only copy (to the secondary) data that hasn't been copied to the secondary yet. By defining a secondary copy, you are saying "I want whatever is in my primary copy to be in my secondary" (for synchronous secondaries).
 
So, if you have 300GB in your archive and you are archiving everything, then 300GB will appear in your Primary copy, 300GB in your secondary and your main archive filesystem will be filled with stubs.
 
Does this answer your question?
 
Mark Edwards.


On Wed, Mar 3, 2010 at 04:55, genxcubca <bill.willis < at > swgas.com ([email]bill.willis < at > swgas.com[/email])> wrote:
 
Our company is new to using commvault's file archiver, and for our first foray into it, we aren't technically going to use it as an archive. It's going to be a HSM solution.

We have an application called Vista Plus. Instead of reports going from our mainframe to a printer, it goes to this application so they can be viewed and annotated electronically

Like a backup, when these reports reach a certain age, they get sent to an archive filesystem by this application.

I want to use commvault to get everything in this archive filesystem and keep it on tape that will remain in the tape library.

So far, in our tests, it seems to be okay after a few bumpy weeks.

The rules are set up so that every file meets the archive criteria.

My question is how this environment is maintained. I have an on-site tape and an aux copy to keep offsite. What is the deal with creating new indexes? How does that impact me? How about the off-site tape rotation? Will new archive jobs that run to keep all of the data on tape keep adding onto existing tapes? Or will it replace the data on tape? Basically, how do you keep it from taking a 300 GB filesystem and having it take up 3 TB on tape after a year or so?










--
regards,

Mark P. Edwards








--
regards,

Mark P. Edwards




__._,_.___
Reply to sender ([email]mark.p.edwards < at > gmail.com?subject=Re: [commvault] File Archiver best practices[/email]) | Reply to group ([email]commvault < at > yahoogroups.com?subject=Re: [commvault] File Archiver best practices[/email]) | Reply via web post | Start a New Topic
Messages in this topic (5)
Recent Activity: Visit Your Group

Commvault Documentation here:
http://documentation.commvault.com/
Text-Only ([email]commvault-traditional < at > yahoogroups.com?subject=Change Delivery Format: Traditional[/email]), Daily Digest ([email]commvault-digest < at > yahoogroups.com?subject=Email Delivery: Digest[/email]) &bull; Unsubscribe ([email]commvault-unsubscribe < at > yahoogroups.com?subject=Unsubscribe[/email]) &bull; Terms of Use




.

[img]http://geo.yahoo.com/serv?s=97359714/grpId=7450851/grpspId=1707277520/msgId=3480/stime=1267787462/nc1=4507179/nc2=4025338/nc3=5733757[/img]
__,_._,___

Post File Archiver best practices 
Filesystem 1 is heavily used. It's 1 TB of reports that are constantly being worked. We're just looking to move the older reports off, and this app automatically "archives" to filesystem 2. But for this app, filesystem 2 can only be disk or a raw tape dump, so we didn't want to select tape for that. We'd rather commvault provide the tape handling.

Mark Edwards <mark.p.edwards < at > gmail.com> 3/5/2010 3:10 AM >>>

Why don't you just archive filesystem 1 - this 'application' seems to be duplicating functionality somewhat?
You can get Commvault to simply archive filesystem 1 on a weekly basis. Compression can be done by the client to place the file in the archive.


I'm interested in how "vista plus" requests the archive file from Commvault. normally when a stub file is 'opened' the HSM filesystem driver will do the 'requesting'. Does Vista-Plus have a script or commandline interface to Commvault?

m

On Wed, Mar 3, 2010 at 18:42, Bill Willis <bill.willis < at > swgas.com ([email]bill.willis < at > swgas.com[/email])> wrote:
Well, I was hoping to avoid going into this other application since I don't want to bog down the discussion by putting in details that most people probably don't care about. However, the way it works is what is kind of bugging me and I'm trying to wrap my head around how the Archiver will handle it.

Okay, so that application takes reports in Filesystem 1, and compresses them (makes a .Z file) and moves them into filesystem 2. I then archive filesystem 2.

Users in the application who need to access these archived reports make a request to the application (Vista Plus).
Vista plus requests the data from the CV tape,
then it moves the .Z file from filesystem 2 to filesystem 1
then decompresses and tar -xvf back to its original location before it was archived.

So now we have Data back in its original location which is NOT the location that I archive with CV.

Now when the next sunday rolls around, this report will be seen to be old and get re-archived to Filesystem 2, and then CV will run and re-archive.

When this data was retrieved from the tape, it doesn't remove it from the tape. It's just copied from the tape and the stub gets replaced. then the app re-archives back to filesystem 2 after a couple of days.

So then the next round of CV archive jobs presumably archives this file again, now there are 2 copies of this on the primary tape copy.

I think this was what I was worried about with the tapes filling up not only with more archive files, but eventually many copies of the SAME files.

Does this make sense?

Mark Edwards <mark.p.edwards < at > gmail.com ([email]mark.p.edwards < at > gmail.com[/email])> 3/2/2010 8:55 PM >>>

auxiliary / secondary copies are not backup jobs in their own right. When you perform an aux copy, you only copy (to the secondary) data that hasn't been copied to the secondary yet. By defining a secondary copy, you are saying "I want whatever is in my primary copy to be in my secondary" (for synchronous secondaries).

So, if you have 300GB in your archive and you are archiving everything, then 300GB will appear in your Primary copy, 300GB in your secondary and your main archive filesystem will be filled with stubs.

Does this answer your question?

Mark Edwards.


On Wed, Mar 3, 2010 at 04:55, genxcubca <billwillis < at > swgas.com ([email]bill.willis < at > swgas.com[/email])> wrote:

Our company is new to using commvault's file archiver, and for our first foray into it, we aren't technically going to use it as an archive. It's going to be a HSM solution.

We have an application called Vista Plus. Instead of reports going from our mainframe to a printer, it goes to this application so they can be viewed and annotated electronically

Like a backup, when these reports reach a certain age, they get sent to an archive filesystem by this application.

I want to use commvault to get everything in this archive filesystem and keep it on tape that will remain in the tape library.

So far, in our tests, it seems to be okay after a few bumpy weeks.

The rules are set up so that every file meets the archive criteria.

My question is how this environment is maintained. I have an on-site tape and an aux copy to keep offsite. What is the deal with creating new indexes? How does that impact me? How about the off-site tape rotation? Will new archive jobs that run to keep all of the data on tape keep adding onto existing tapes? Or will it replace the data on tape? Basically, how do you keep it from taking a 300 GB filesystem and having it take up 3 TB on tape after a year or so?










--
regards,

Mark P. Edwards








--
regards,

Mark P. Edwards

Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB